Jayjader

joined 10 months ago
MODERATOR OF
[–] Jayjader@jlai.lu 3 points 1 day ago* (last edited 1 day ago)

Titre: Pains aux chocolat et chocolatines

Sous-titre : une France divisée est une France forte

Histoire de perdre tout le monde avant même qu'ils ouvrent le livre 😁

Le contenu du livre serait une revue des périodes de la France qui ont connu une grande division au sein de la société, et comment ces périodes ont contribué à la "grandeur" de la France. Guerres de religion entre cathos et protestants, la Résistance à l'occupation nazie, la covid et les anti-vax, l'affaire Dreyfus, il y a de quoi remplir plus d'un bouquin! Même le titre du bouquin pourrait être exploré comme une explication de la diversité (et qualité !) de la gastronomie française.

Bon, c'est pas dit que ça convainc grand monde a part des réacs, des accélérationistes, et peut-être quelques maoïstes...

[–] Jayjader@jlai.lu 1 points 1 day ago* (last edited 1 day ago)

D'abord Villepin, puis Ciotti. Et beh

[–] Jayjader@jlai.lu 2 points 1 day ago (1 children)

Perso j'ai toujours vu "hoot-hoot" pour les hiboux et chouettes. C'est la première fois que je lis "twit twoot" !

[–] Jayjader@jlai.lu 2 points 2 days ago

Not at all. I don't even know if the devs have already considered it and decided against releasing it with such functionality.

[–] Jayjader@jlai.lu 3 points 3 days ago (2 children)

Not from the platform, but you can control what the landing bay on the surface requests with circuit connections.

[–] Jayjader@jlai.lu 4 points 3 days ago (2 children)

I would try to dump the asteroid chunks instead of excess ore - you're paying electricity to crush chunks and then potentially throwing away the output. Of course, if you're avoiding circuit conditions then there's not much better way than to throw the excess ore, plate, etc off the back.

[–] Jayjader@jlai.lu 2 points 3 days ago (1 children)

In case you haven't found out yet, it's the landing pad. Better quality ones have a greater radar range/radius.

[–] Jayjader@jlai.lu 2 points 5 days ago

L'utilite que je vois au opt-in c'est que ca réduit a 1 clic ce qui autrement peut prendre beaucoup de temps, et que un/e nouveau/lle jlailutin/e n'a pas besoin de savoir épeler les instances ni de les découvrir etc avant de pouvoir les filtrer (comme pour une de-federation, sauf que du coup tu peux quand meme "revenir en arrière" au niveau individuel si tu sais ce que tu fais/veux).

[–] Jayjader@jlai.lu 3 points 6 days ago

Not just a Russian general, a rank in the army of the Soviet union (which comes off even worse to me)

[–] Jayjader@jlai.lu 4 points 1 week ago (2 children)

Appliqué a notre cas, ca donnerait : je ne serais pas contre, si jlai.lu mettait hexbear et lemmygrad en ban recommandé opt-in. Je serais contre les mettre en opt-out, mais cela ne me pousserait pas a quitter l'instance et j'attendrais d'avoir des "preuves" sures avant de militer activement contre. Je ne serais également pas contre (et limite pour) que chaque instance de toxicité observée dans l'autre fil résulte en l'ajout de son auteur/ice sur la liste des bans recommandés ici (et cette fois-ci peut-être plus opt-out qu'opt-in).

Je trouve que ca permettrait d'exprimer une certaine conséquence forte (et donc appropriée face a la toxicité qu'il y a eu lieu) sans pour autant consigner d'avance toutes les utilisateur/ices de hexbear presents et futurs.

[–] Jayjader@jlai.lu 5 points 1 week ago* (last edited 1 week ago) (3 children)

Après davantage de réflexion, je pense pouvoir donner un debut de "solution" qui me conviendrait. Malheureusement il me semble que ce n'est pas possible avec Lemmy actuellement. Tout de meme : ajouter un niveau supplémentaire entre "federation totale" et "défédération totale".

Un example concrèt serait que les admins d'une instance peuvent maintenir une liste de ban "recommandés" d'instances (et pourquoi pas, d'utilisateurs). Ces admins pourraient ensuite decider de rendre cette liste "opt-in" ou "opt-out" pour l'ensemble des utilisateurs de leur instance. On pourrait également documenter, de facon similaire aux modlog ou la liste acutelle de défédés, les changements de status vis-a-vis de cette liste.

Ce qui m'interese par cet exemple, c'est sa capacité améliorée de feedback mutuel par rapport a la simple binarité de la fédé/défédé. Quand on défédere, on perd énormément en capacité d'observer si la "peine" a eu un impact positif sur les utilisateurs de l'instance défédérée. A l'inverse, l'ajout sur une liste de bans "recommandés" permettrait par exemple d'avoir des jlailutin/es qui individuellement tolèrent plus les ours de pouvoir témoigner de leur evolution au reste de jlai.lu sans quitter notre instance. Ca permettrait également aux ours qui ne nous supportent pas de ne pas avoir a individuellement nous block ou ban. Etc.

Le seul bémol que j'y vois est qu'actuellement bloquer un compte utilisateur et/ou une instance n’empêche pas comportement d’être exposé a leurs agissements sur le fédivers (de ce que je comprends). Il faudrait que ca le soit pour que ma proposition ait du sens.

Bien sur, la défédé totale doit rester dans la boite a outils des admins, ne serait-ce que pour les instances qui partagent des contenus illégaux (et donc trop risqué de laisser leurs servers envoyer le moindre octet chez eux). Il faut juste d'autres nuances ou degrés en plus. VRChat a un systeme avec 5 niveaux de "confiance" que chaque utilisateur peut accorder aux autres, ainsi que définir un degré qui est appliqué par défaut a tous les autres utilisateurs. C'est d'autant plus pertinent pour eux car les avatars de certains peuvent plier en deux ton client si ta machine est trop legere.

[–] Jayjader@jlai.lu 1 points 1 week ago

cacher does, but cache as in "cache-toi !" (go hide!) and "je me cache" (I'm hiding) are pronounced "cash".

Besides, "correct" pronunciation in a different language is pretty meaningless. The word may have come from French but we're speaking English, not French.

Also, it might not be a loan word so much as a legacy-of-foreigners-taking-over word (c.f. the Normand invasion of Britain), which doesn't tend to help the language's users care about respecting the "original" pronunciation. I'm not certain when exactly cachet entered English.

 
 

J'ignore comment rendre justice à l'expérience qu'à été ma lecture de ce livre.

Dévoré en quelques jours. Le dernier tiers en particulier m'a retenu éveillé jusqu'à 3h du matin, le récit tellement fort que je ne pouvais me convaincre d'attendre le lendemain pour le terminer.

Un certain ressenti de découvrir le livre que j'aurais écrit, dans une autre vie, si j'avais choisi un parcours "littéraire" et non "scientifique". Un renouveau de rage écologique maintenu sous contrôle, presque étouffé, par un calme fataliste qui n'est pas pour autant un lâcher-prise. Si Les Soulèvements De La Terre était une religion ceci serait sans doute un de leurs textes sacrés, et Powers un de leurs prophètes (bien que Bouddha serait plus apte comme label). Heureusement, ce n'est pas une religion, et ce livre n'est pas un texte divin. Au contraire, je le trouve profondément profane, et humain.

Au-delà du "contenu" (cad les thèmes abordés, les arcs narratifs et péripéties suivi(e)s) la forme est remarquable. Powers écrit avec un style de narration qui, tel la conduite d'une auto à boite de vitesse dans une contrée vallonnée, change de trajectoire et d'allure dès qu'on a avancé une centaine de mètres. Et tout comme cette conduite, l'expérience qui en ressort n'est pas une succession d'interruptions qui nous laisse sur le qui-vive, mais un état de conscience profonde qui s’imprègne simultanément de chaque détail séparé et du mouvement de l'ensemble. Il y a des phrases qui donnent l'impression que le livre entier a été écrit et construit autour d'elles.

https://fr.wikipedia.org/wiki/L%27Arbre-monde

 
 

cross-posted from: https://jlai.lu/post/10771034

n’hésitez-pas à me demander de traduire certains passages de mon post en français si besoin

Personal review:

A good recap of his previous writings and talks on the subject for the first third, but a bit long. Having paid attention to them for the past year or two, my attention started drifting a few times. I ended up being more impressed with how much he's managed to condense explaining "enshittification" from 45+ minutes down to around 15.

As soon as he starts building off of that to work towards the core of his message for this talk, I was more-or-less glued to the screen. At first because it's not exactly clear where he's going, and there are (what felt like) many specific court rulings to keep up with. Thankfully, once he has laid enough groundwork he gets straight his point. I don't want to spoil or otherwise lessen the performance he gives, so I won't directly comment on what his point is in the body of this post - I think the comments are better suited for that anyways.

I found the rest to be pretty compelling. He rides the fine line between directionless discontent and overenthusiastic activist-with-a-plan as he doubles down on his narrative by calling back to the various bits of groundwork he laid before - now that we're "in" on the idea, what felt like stumbling around in the dark turns into an illuminating path through some of the specifics of the last twenty to forty years of the dynamics of power between tech bosses and their employees. The rousing call to action was also great way to end and wrap it all up.

I've become very biased towards Cory Doctorow's ideas, in part because they line up with a lot of the impressions I have from my few years working as a dev in a big-ish multinational tech company. This talk has done nothing to diminish that bias - on the contrary.

 

cross-posted from: https://jlai.lu/post/10771035, https://jlai.lu/post/10771034

Personal review:

A good recap of his previous writings and talks on the subject for the first third, but a bit long. Having paid attention to them for the past year or two, my attention started drifting a few times. I ended up being more impressed with how much he's managed to condense explaining "enshittification" from 45+ minutes down to around 15.

As soon as he starts building off of that to work towards the core of his message for this talk, I was more-or-less glued to the screen. At first because it's not exactly clear where he's going, and there are (what felt like) many specific court rulings to keep up with. Thankfully, once he has laid enough groundwork he gets straight his point. I don't want to spoil or otherwise lessen the performance he gives, so I won't directly comment on what his point is in the body of this post - I think the comments are better suited for that anyways.

I found the rest to be pretty compelling. He rides the fine line between directionless discontent and overenthusiastic activist-with-a-plan as he doubles down on his narrative by calling back to the various bits of groundwork he laid before - now that we're "in" on the idea, what felt like stumbling around in the dark turns into an illuminating path through some of the specifics of the last twenty to forty years of the dynamics of power between tech bosses and their employees. The rousing call to action was also great way to end and wrap it all up.

I've become very biased towards Cory Doctorow's ideas, in part because they line up with a lot of the impressions I have from my few years working as a dev in a big-ish multinational tech company. This talk has done nothing to diminish that bias - on the contrary.

 

cross-posted from: https://jlai.lu/post/10771034

Personal review:

A good recap of his previous writings and talks on the subject for the first third, but a bit long. Having paid attention to them for the past year or two, my attention started drifting a few times. I ended up being more impressed with how much he's managed to condense explaining "enshittification" from 45+ minutes down to around 15.

As soon as he starts building off of that to work towards the core of his message for this talk, I was more-or-less glued to the screen. At first because it's not exactly clear where he's going, and there are (what felt like) many specific court rulings to keep up with. Thankfully, once he has laid enough groundwork he gets straight his point. I don't want to spoil or otherwise lessen the performance he gives, so I won't directly comment on what his point is in the body of this post - I think the comments are better suited for that anyways.

I found the rest to be pretty compelling. He rides the fine line between directionless discontent and overenthusiastic activist-with-a-plan as he doubles down on his narrative by calling back to the various bits of groundwork he laid before - now that we're "in" on the idea, what felt like stumbling around in the dark turns into an illuminating path through some of the specifics of the last twenty to forty years of the dynamics of power between tech bosses and their employees. The rousing call to action was also great way to end and wrap it all up.

I've become very biased towards Cory Doctorow's ideas, in part because they line up with a lot of the impressions I have from my few years working as a dev in a big-ish multinational tech company. This talk has done nothing to diminish that bias - on the contrary.

 

Personal review:

A good recap of his previous writings and talks on the subject for the first third, but a bit long. Having paid attention to them for the past year or two, my attention started drifting a few times. I ended up being more impressed with how much he's managed to condense explaining "enshittification" from 45+ minutes down to around 15.

As soon as he starts building off of that to work towards the core of his message for this talk, I was more-or-less glued to the screen. At first because it's not exactly clear where he's going, and there are (what felt like) many specific court rulings to keep up with. Thankfully, once he has laid enough groundwork he gets straight his point. I don't want to spoil or otherwise lessen the performance he gives, so I won't directly comment on what his point is in the body of this post - I think the comments are better suited for that anyways.

I found the rest to be pretty compelling. He rides the fine line between directionless discontent and overenthusiastic activist-with-a-plan as he doubles down on his narrative by calling back to the various bits of groundwork he laid before - now that we're "in" on the idea, what felt like stumbling around in the dark turns into an illuminating path through some of the specifics of the last twenty to forty years of the dynamics of power between tech bosses and their employees. The rousing call to action was also great way to end and wrap it all up.

I've become very biased towards Cory Doctorow's ideas, in part because they line up with a lot of the impressions I have from my few years working as a dev in a big-ish multinational tech company. This talk has done nothing to diminish that bias - on the contrary.

 

cross-posted from: https://jlai.lu/post/10083697

Haven't bought the game yet, but these instructions seem legit. I found this link in a ProtonDB comment who claims to be its author/hoster: https://www.protondb.com/app/1934680#WRxwBwtv-Y.

 

Je n'ai pas encore acheté le jeu, mais les instructions m'inspirent confiance. J'ai trouvé ce lien dans le commentaire d'une personne sur ProtonDB qui prétend en être l'auteur (ou au moins l’hébergeur) : https://www.protondb.com/app/1934680#WRxwBwtv-Y.

Par hasard, il-y-aurait des jlailutines ou -lutins qui ont le jeu et sont sur Linux qui pourraient témoigner ?

 

What?

I will be holding the fifteenth of the secondary slot/sessions for the Reading Club, also on "The Book" ("The Rust Programming Language"). We are using the Brown University online edition (that has some added quizzes & interactive elements).

Last time we began chapter 7 (Managing Growing Projects with Packages, Crates, and Modules), and read up through section 7.3 (Paths for Referring to an item in the Module Tree). This time we will start at section 7.4 (Bringing Paths Into Scope with the use Keyword).

Previous session details and recording can be found in the following lemmy post: https://jlai.lu/post/8006138

Why?

This slot is primarily to offer an alternative to the main reading club's streams that caters to a different set of time zone preferences and/or availability.

(also, obviously, to follow up on the previous session)

When ?

Currently, I intend to start at 18:00 UTC+2 (aka 6pm Central European Time) on Monday (2023-07-01). If you were present for a previous session, then basically the same time-of-day and day-of-week as that one was.

EDIT: here's the recording: https://youtu.be/RI4D62MVvCA

Please comment if you are interested in joining because you can't make the main sessions but would prefer a different start time (and include a time that works best for you in your comment!). Caveat: I live in central/western Europe; I can't myself cater to absolutely any preference.

How ?

The basic format is: I will be sharing my computer screen and voice through an internet live stream (hosted at https://www.twitch.tv/jayjader for now). The stream will be locally recorded, and uploaded afterwards to youtube (for now as well).

I will have on-screen:

  • the BU online version of The Book
  • a terminal session with the necessary tooling installed (notably rustup, cargo, and clippy)
  • some form of visual aid (currently a digital whiteboard using www.excalidraw.com)
  • the live stream's chat

I will steadily progress through the book, both reading aloud the literal text and commenting occasionally on it. I will also perform any code writing and/or terminal commands as the text instructs us to.

People who either tune in to the live stream or watch/listen to the recording are encouraged to follow along with their own copy of the book.

I try to address any comments from live viewers in the twitch chat as soon as I am aware of them. If someone is having trouble understanding something, I will stop and try to help them get past it.

Who ?

You! (if you're interested). And, of course, me.

 

What?

I will be holding the fourteenth of the secondary slot/sessions for the Reading Club, also on "The Book" ("The Rust Programming Language"). We are using the Brown University online edition (that has some added quizzes & interactive elements).

Last time we completed chapter 6 (enums & pattern matching). This time we will begin chapter 7 (Managing Growing Projects with Packages, Crates, and Modules).

Previous session details and recording can be found in the following lemmy post: https://jlai.lu/post/7773753

Why?

This slot is primarily to offer an alternative to the main reading club's streams that caters to a different set of time zone preferences and/or availability.

(also, obviously, to follow up on the previous session)

When ?

Currently, I intend to start at 18:00 UTC+2 (aka 6pm Central European Time) on this day (2023-06-24). If you were present for a previous session, then basically the same time-of-day and day-of-week as that one was.

Here's the recording: https://youtu.be/pUqVmPRLhNE

Please comment if you are interested in joining because you can't make the main sessions but would prefer a different start time (and include a time that works best for you in your comment!). Caveat: I live in central/western Europe; I can't myself cater to absolutely any preference.

How ?

The basic format is: I will be sharing my computer screen and voice through an internet live stream (hosted at https://www.twitch.tv/jayjader for now). The stream will simultaneously be recorded locally and uploaded afterwards to youtube (also, for now).

I will have on-screen:

  • the BU online version of The Book
  • a terminal session with the necessary tooling installed (notably rustup and through it cargo & "friends")
  • some form of visual aid (currently a digital whiteboard using www.excalidraw.com)
  • the live stream's chat

I will steadily progress through the book, both reading aloud the literal text and commenting occasionally on it. I will also perform any code writing and/or terminal commands as the text instructs us to.

People who either tune in to the live stream or watch/listen to the recording are encouraged to follow along with their own copy of the book.

I try to address any comments from live viewers in the twitch chat as soon as I am aware of them. If someone is having trouble understanding something, I will stop and try to help them get past it.

Who ?

You! (if you're interested). And, of course, me.

view more: next ›