Currently between olives

  • 47 Posts
  • 473 Comments
Joined 6M ago
cake
Cake day: Jun 01, 2023

help-circle
rss

It’s not like an average person would be unable to use their laptop and some media player, regardless of which OS they use; the fact that I use a weird-ass player doesn’t mean it’s the only option available on a laptop. It just seems pointless to get another gadget to do the same thing you can do on a gadget you own (assuming you have a laptop, of course.)




I guess those devices make more sense if you don’t have a laptop. I only have a laptop (well, that and a Steam Deck which counts as mobile Linux I guess) so I just plonk it into the HDMI port



I may be an anomalous IT professional, but despite being a coder and generally a ginormous nerd, I’ve never really understood why people buy “smart” devices. This isn’t a criticism; I honestly just don’t understand why they’re popular. The amount of convenience they provide really doesn’t seem like it’s worth it at all, to me



Algorithm-free

I’m not sure you understand what an algorithm is. They’re simply a sequence of steps you apply to get some end result, comparable to eg. a recipe in baking.

Lemmy still has multiple ways for you to choose how posts are sorted; “hot”, “active”, “new” etc. Each of those is an algorithmic sorting, and there’s literally no other option except to have an algorithm that is used to determine which posts you see

edit: I think many people who think Lemmy is “algorithm-free” may mean that it has a transparent algorithm for post selection. It’s still an algorithm, but we can all go look at source code and documentation to be able to know exactly how it works – with eg. Facebook the exact workings of the post sorting algorithm is secret





I’ll be treating the freebie as a limited collectable in a video game

Ah so you’ll be using it impulsively on the first thing that crosses your mind, only to regret what you did just moments afterwards?

and never use it fearing that I’ll waste it

Oh I see



Conservatives generally have an astonishing skill at coming up with the weirdest bullshit to justify their hate of anyone progressive.


Are you trying to convince yourself or the person you’re replying to?


IBM sold machines to the original Nazis, so I guess this time around they at least want to keep up the appearance of giving a shit where their money comes from


Because no way could I dislike modern PHP. Maybe you just have low standards when it comes to programming languages?


I’m not sure which thought is scarier: that you don’t know what you’re signing up for, or that you do know and you enjoy fixing undecidable formatting fuckups manually


Bit unfair to compare them to the Ferengi.

At least the Ferengi have redeeming qualities


That’s a good point about the synergies, something like eg. a type system that’s expressive enough to be Turing-complete is going to have some effects. You’re right that it might just feel like a “kitchen sink language” due to complexity of the features it has, but then again I suppose it’s sort of one and the same where a language’s complexity comes from.

But it’s no Swift, at least; now that language really does have everything and the kitchen sink.


Semantic whitespace problems can easily be literally impossible to solve automatically. One of the dumbest fucking ideas anybody ever came up with in computing and its inventor if anyone belongs in YAML Hell. As a fuckup it’s not quite as bad as null, but that ain’t exactly a high bar


The guy in the blog says mb (millibits)

a) does anybody actualy use that? How many people reading this thread can say they’ve actually seen that in real use or used it?

b) I’m fairly convinced you knew what was meant because it’s not like it’s uncommon to use a minuscule m for “mega” in colloquial usage

Weird performative pedantry or a joke that flew over my head? I give about a 0.5 probability for both


I mean, wouldn’t it essentially have to be storing every possible move (well, state) for as many rounds as you want for the player to be able to play at most? And I’m not sure he can take advantage of the fact that you can end up in the same state from multiple other states, which would remove a lot of the redundant ones


There’s a special place in hell for the inventor of semantically significant whitespace.

YAML itself is one of the circles of hell. You have to copy-paste YAML from web etc sources with dubious formatting for all eternity, and the editor doesn’t have YAML support. Also you can only use Python


It already feels like Twitter.

Still full of Nazis then, I take it?


It was an analogy for how something infinite doesn’t necessarily contain everything you can think of, not meant to be taken absolutely literally (hence the word “analogy” there). Also I got this from some physicist so I didn’t pull it out of my own butt, I’ll try find a source


I think it’s the PHP, makes people doubt your soul’s status that you’d subject yourself willingly to it


“Sufficiently powerful” is a bit of an understatement when it comes to Scala. Honestly may have a bit too many features for my taste, it’s not a small language


I’ve been meaning to give F# a go but I never seem to get around to it. Seems like an interesting language



Captain Buzzkill here, but an infinite number of universes wouldn’t necessarily guarantee that every possible scenario happens.

As an analogy, there’s an infinite amount of integers, but you’re not going to find 1.5 in them.


Affordable and available housing has everything to do with homelessness though, it’s one of the best ways to actually keep people from becoming homeless in the first place. If more people can afford a place to live, less people will be homeless. Won’t fix all of it but a huge chunk anyhow

I have no idea if or how much old Eastern Bloc countries lied about the number of homeless. I wouldn’t be surprised at all, but I haven’t seen any studies or statistics about this so I can’t assume they were all lying or that the situation was universally worse than in Western countries.


That was well said. Recontextualization is exactly the thing; it’s not that I think the Soviet Union was absolute evil with zero redeeming features. They got more right during the early years although I’m not necessarily a huge fan of that period either, and to a large extent it was Stalin who fucked them up pretty severely with the frankly sociopathic system that the Union turned into.

Russian political culture has been outright brutal for a long time. Eg. these KGB-like secret police organizations have been around for a while and have invariably had brutal methods of dealing with politically displeasing individuals or just who-the-hell-ever in many cases. This, coupled with the cultural ethos that Russia and Russians – and specifically meaning ethnic Russians – are superior to anyone outside their borders and a tendency for imperialism, means that Russian rule has nearly invariably been a shitty time, with Finland being one of the few exceptions as we mostly faced little repression or cultural erasure compared to other Russian “colonies” and this was done intentionally; most of the Russian Emperors during our time as a Grand Duchy in some ways thought of Finland as way to show the European powers that they can run things in a “western” way, and to work as a kind of window to the West. For the last 20 or so years they did try to Russify us, which we – being stubborn fucks – did not take well. We also kept our previous Parliament for the most part even though even starting from Alexander I the Emperors wanted to have autocratic rule, but – again in parts thanks to us being stubborn fucks – it took something like 4 emperors for it to happen. Their other historical or the currently existing colonies (nobody seems to think of Russia as a colonialist empire because their colonies are inside contiguous borders) weren’t quite so lucky, as Russification and “Russian supremacy” has been the standard.

This political culture played a large part in the problems with the Union. It was nominally multicultural (and korenization was briefly a thing until they went back to Russification as usual) but it wasn’t exactly unclear who were ultimately in charge.

And before some smartass barges in asking me why it’s OK if the US/UK/France/whoever does this stuff: I don’t like imperialism any more regardless of who’s doing it.


I’m a leftist but I’m not much of a fan of the Soviet Union. I’m Finnish and middle-aged so I know a bunch of people who had to escape from there and I’ve heard first-hand stories about the shit that went on, and I’ve visited Soviet Estonia who got the short end of the stick with Russian imperialism compared to us. At least we stayed independent although had to grant a lot of power over eg. our foreign policy to the Russians – ie. Soviets, but it’s not like it wasn’t essentially a Russian project since they pretty quickly forgot about korenization and went for Russification instead – to keep them from invading (again…)


Interesting. How are things in the year 2033? Could you tell us about the technology you’re using to communicate with us?


More likely outcome: he takes a person in strange clothing appearing from thin air only to set his book on fire with a magical implement as clear proof of witchcraft existing and posing a huge danger. Get ready for turbo witch hunts on crack


Heh, an optimist here assuming Chrome will work with 8Gb RAM in 2033



No duh, they were built to be very affordable so you wouldn’t have as many homeless people. It’s incredible that you thought that answer was somehow insightful


Oh neat. That definitely qualifies under infinite curiosity.


But the anthropic principle doesn’t imply an intention either, though. Much the opposite: it’s all just dumb luck, but for us to be here right now observing it, some of that luck had to go a certain way (eg some physical constants had to get the values they have or matter wouldn’t exist etc).

In some ways this really isn’t even in question, an example being the apparent “fine-tuning” of physical constants so that there’s stable matter than can form more complex compounds, and that stars can exist, etc. That “fine-tuning” itself is pretty clear, ie we can calculate that if this or that constant was 0.000004% off then everything would go to shit.

But it’s only apparent tuning: it just boils down to the fact that those constants have to be the way they are, or we wouldn’t be able to be here as observers: if even one thing was slightly different then eg hydrogen would be the most complex chemical in the universe or something like that. Ain’t no observers emerging out of nearly perfectly homogenous hydrogen soup. Or a universe that collapsed into a singularity and disappeared into whatever the hell is on the other “end” of black holes a Planck time after the big bang, because instead of bonds being too hard to form they were too easy.

Now the AP just then takes that idea and runs off with it, with the strong principle ending up with the conclusion (and this is much simplified) that we’re the only ones out here due to the amount of “fine tuning” required, and the weak being less, well, chauvinistic 😁

Some people think that the “fine-tuning” of physical constants means the universe was made for us, when the truth is closer to the opposite of that, with us sort of being made for the universe. Again without intention or a Maker, but simply meaning that with these “universe settings / seed”, something similar to our current universe is what you get

edit: this Douglas Adams quote on rationalwiki is a great distillation of the AP but in a humorous way:

Imagine a puddle waking up one morning and thinking, ‘This is an interesting world I find myself in, an interesting hole I find myself in, fits me rather neatly, doesn’t it? In fact it fits me staggeringly well, must have been made to have me in it!’ This is such a powerful idea that as the sun rises in the sky and the air heats up and as, gradually, the puddle gets smaller and smaller, it’s still frantically hanging on to the notion that everything’s going to be alright, because this world was meant to have him in it, was built to have him in it; so the moment he disappears catches him rather by surprise. I think this may be something we need to be on the watch out for.



By https://www.gocomics.com/sunny-street
fedilink




In today's episode of "weird shit I stumbled onto on the internet", I bring you: nuclear-powered pacemakers. ![](https://beehaw.org/pictrs/image/2127db05-d1ac-47ef-a8d2-9f70ca204024.webp) Some of the earlier pacemakers made in the US, around the 70's, were powered by a very small amount of plutonium. If you've ever heard of the term radioisotope thermoelectric generator or RTG in relation to eg. satellites, that's what the pacemakers used. The upside of using an RTG was that the device could run for decades without needing to get its power source replaced. The downside is that you now have plutonium sown in to your chest cavity – which actually isn't as bad as it sounds considering the amounts used, but it's still a highly radioactive element and presents some fun challenges, some of which are discussed in the article. Here's an article on the technical details on how they, and thermoelectric kajiggers in general, work https://blog.plover.com/tech/seebeck-effect.html
fedilink


The image has a stock photo of a chemist with Samuel L. Jackson's head photoshopped on, and he appears to be looking a graduated cylinder with some colored liquid in it. Near the bottom there's the text "ah, yes". Below it are two rows that look like they were copied from the periodic table, with atomic numbers at the top, then the abbreviation in the middle and the full name of the element at the bottom. The first row of elements is Mo, Th, Er (molybdenum, thorium, erbium) The second row of elements is F, U, C, K, Er (fluorine, uranium, carbon, potassium, erbium) **edit**: corrected term to "atomic number"
fedilink



> Democracy remains popular across the world, but faced with a global array of challenges from inequality to the climate crisis, young people are far less likely than their elders to believe it can deliver on what concerns them. > > According to a major international survey of 30 countries published on Tuesday, 86% of respondents would prefer to live in a democratic state and only 20% believe authoritarian regimes are more capable of delivering “what citizens want”. > > However, only 57% of respondents aged 18 to 35 felt democracy was preferable to any other form of government, against 71% of those over 56, and 42% of younger people said they were supportive of military rule, against just 20% of older respondents. I wish I could say I was surprised. Here in Finland we had a parliamentary election earlier in the year and ended up with the most right-wing government we've ever had, with zero leftist or centrist parties in the government. One fresh minister had to quit his post due to being a neo-Nazi, and the extremist party whose ministerial post it currently is replaced him with a _pedophile_ neo-Nazi (who won a vote of confidence, so apparently that's not a problem to anybody but leftists.) Almost half of the under-25's voted for right-wing parties. The most popular one was an extremist right-wing party (multiple neo-Nazis, politicians who openly fantasize about eg. murdering gay people, the works), and 2nd most popular was the "fiscally conservative" party (who really aren't much better than the extremists, and in many ways actually worse).
fedilink

Drawing, vaguely 50's retro style. In the center is an anthropomorphic egg character, dressed in a "sailor hat", a shirt and a tie, and shorts. The character is walking in a sort of jaunty-looking fashion, but on closer inspection the poor egg is looking a bit ragged, with a large network of cracks on its shell right next to its hat, a missing tooth, and bags under its eyes. The character is surrounded by the text "one minor hiccup away from losing my shit"
fedilink

4 panel comic. In the top left panel there's a slightly antropomorphic tortellini that has eyes, and it has a thought bubble reading "I wish I was skinnier". Next to it is a similarly antropomorphic spaghetti thinking "I wish I wasn't so skinny". In the top right panel there's a small macaroni thinking "I wish I was bigger" and a ravioli thinking "I wish I was smaller". In the bottom left panel there's a… uh… tube-shaped pasta that I think is a rigatoni thinking "I wish I wasn't hollow inside", and a clam-shaped pasta (lol I give up with the names) thinking "I'm just an empty shell". In the bottom right panel we can see part of a plate that has the antropomorphic pasta on it, and then the top half of the face of a female-presenting person with dilated pupils, peering over a table edge looking at the plate thinking "I wish I wasn't tripping so hard".
fedilink

Meme (??) image. On the left side there's a picture of a cylindrical metallic container with the text > DANGER > RADIATION > ☢️ (radioactivity warning symbol) > DROP > & > RUN > > Co 60 > 3540 > CURIES > 7-1-63 And below it the top part of a similar container is just visible. On the right side next to the first container are 4 lines that look like they measure out portions of the container, each with the text "mmm tasty." Then below those lines, "measuring out" the empty space between the two containers is the text "sadness", and then below it where the next container starts is the text "another :D yeey". (This might possibly be the worst description of a meme ever, but goddamn was this not easy 😅 Corrections / edits welcome)
fedilink
2

Screenshot of a social media post – maybe Mastodon? – by "Cuttlefish Brand Ambassador" @Sir__Ian. It has the text "Upstaged by cuttlefish yet again" and below it a screenshot of a preview of a news article. It has a photo of a pair of cuttlefish and below it the headline reads "Cuttlefish have ability to exert self-control, study finds"
fedilink
2

Screenshot of a Mastodon post by @nikitonsky@mastodon.online. The post has text on top and an image on the bottom. The text reads: > "How are you gonna watch Oppenheimer?" > "In Emacs" > "You mean IMAX?" > "No" Below the text is what looks like a screenshot of Emacs. There are a couple of text panes open with indistinct green text on black background, and one pane is playing Oppenheimer.
fedilink

meme image. Top part has text on white background: >Android: file saved successfully. >Me: and where exactly it is saved >Android: Below that is a black and white picture of a chimpanzee (or is that a bonobo?) dressed in a long sleeve shirt and smoking a cigarette, with the caption "who the fuck knows"
fedilink

In a comment on my "right to be forgotten" proposal I mentioned causality tracking (so eg. figuring out whether event A happened before or after event B) in distributed networks as an example of a hard problem, and I figured I'd share a blog post (not mine) on one of the more modern techniques that's still very much underutilized. This class of algorithms is called [logical clocks](https://en.wikipedia.org/wiki/Logical_clock), and the first of them was the [Lamport timestamp](https://en.wikipedia.org/wiki/Lamport_timestamp) by [Leslie Lamport](https://en.wikipedia.org/wiki/Leslie_Lamport). Note that many of these algorithms can be used for tracking version changes and not just logical time, often with some changes like in the case of interval tree clocks. In many cases just plopping a timestamp on a message and using that to establish causality isn't good enough. If you rely on clients to attach that timestamp, you have to trust that their clocks are correct, or that they don't simply lie about the time for whatever reason (although of course that's a problem with logical clocks too.) Also, you might not want to base your causality on when a message was sent but on when it was _received_; even if message A is sent before message B, there's no telling whether A actually makes it to your system before B does. These are just a few common reasons for needing logical clocks, and they're necessary in a surprising amount of cases when you deal with distributed systems. The advantage of interval tree clocks compared to eg. [vector clocks](https://en.wikipedia.org/wiki/Vector_clock) is that they're designed to work well in networks where participants are constantly leaving and coming back online and where you can't know the number of nodes in the network beforehand. These are cases most other algorithms don't deal with too well. Of course this means more complexity in the algorithm, but this is a case of "them's the breaks" as the problem is definitely not a simple one to solve.
fedilink

Data protection, the right to be forgotten, and federation
cross-posted from: https://beehaw.org/post/923434 I hope this isn't too technical for this community. I'm looking for feedback on an idea, and figured !chat might also be a good place to ask. (TTL stands for "time-to-live", which should be fairly self-explanatory) ## Original post Hey fellow nerds, I have an idea that I'd like to discuss with you. All feedback – positive or negative – is welcome. Consider this a baby RFC (Request for Comments). So. I've been having a think on how to implement the right to be forgotten (one of the cornerstones of eg. the GDPR) in the context of federated services. Currently, it's not possible to remove your comments, posts, etc., from the Fediverse and not just your "home instance" without manually contacting every node in the network. in my opinion, this is a fairly pressing problem, and there would already be a GDPR case here if someone were to bring the "eye of Sauron" (ie. a national data protection authority) upon us. Please note that this is very much a draft and it does have some issues and downsides, some of which I've outlined towards the end. ## The problem In a nutshell, the problem I'm trying to solve is how to guarantee that "well-behaved" instances, which support this proposal, will delete user content even in the most common exceptional cases, such as changes in network topology, network errors, and server downtime. These are situations where you'd typically expect messages about content or user deletion to be lost. It's important to note that I've specifically approached this from the "right to be forgotten" perspective, so the current version of the proposal solely deals with "mass deletion" when user accounts are deleted. It doesn't currently integrate or work with the normal content deletion flow (I'll further discuss this below). While I understand that in a federated or decentralized network it's impossible to guarantee that your content will be deleted (and the Wayback Machine exists), but we can't let "perfect be the enemy of *good enough*". Making a concerted effort to ensure that in most cases user content is deleted (initially this could even just be a Lemmy thing and not a wider Fediverse thing) from systems under our control when the user so wishes would already be a big step in the right direction. I haven't yet looked into "prior art" except some very cursory searches and I had banged the outline of this proposal out before I even went looking, but I now know that eg. Mastodon has the ability to [set TTLs on posts](https://fedi.tips/deleting-posts-automatically-in-mastodon-after-a-certain-time-period/). This proposal is sort of adjacent and could be massaged a bit to support this on Lemmy (or whatever else service) too. ## 1. The proposal: TTLs on user content 1. Every comment, post etc. (*content*) **must** by default have an associated TTL (eg. a `live_until` timestamp). This TTL can be long, on the order of weeks or even a couple of months. Users can also opt out (see below) 2. well before the content's TTL runs out (eg. even halfway through the TTL, with some random jitter to prevent "thundering herds"), an instance asks the "home instance" of the user who created the content whether the user account is still live. If it is, great, update the TTL and go on with life 1. in cases where the "home instance" of a content creator can't be reached due to eg. network problems, this "liveness check" **must** be repeated at random long-ish intervals (eg. every 20 – 30h) until an answer is gotten or the TTL runs out 2. information about user liveness ***should*** be cached, but with a much shorter TTL than content 3. liveness check requests to other instances **should** be batched, with some sensible time limit on how long to wait for the batch to fill up, and an upper limit for the batch size 4. in cases where the user's home instance isn't in an instance's linked instance list or is in their blocked instance list, this liveness check **may** be skipped 3. when a user liveness check hasn't succeeded and a content's TTL runs out, *or* when a user liveness check specifically comes back as negative, the content **must** be deleted 1. when a liveness check comes back as negative and the user has been removed, instances **must** delete the rest of that user's content and not just the one whose TTL ran out 2. when a liveness check fails (eg. the user's home instance doesn't respond), instances **may** delete the rest of that user's content. Or maybe **should**? My reason for handling this differently from an explicit negative liveness check is to prevent the spurious deletion of all of a user's content in cases where their home instance experiences a long outage, but I'm not sure if this distinction really matters. Needs more thinkifying 4. user accounts **must** have a TTL, on the order of several years 1. when a user performs any activity on the instance, this TTL **must** be updated 2. when this TTL runs out, the account **must** be deleted. The user's content **must** be deleted if the user hasn't opted out of the content deletion (see below) 3. instances **may** eg. ping users via email to remind them about their account expiring before the TTL runs out 5. users **may** opt out of the content deletion mechanism, both on a per-user basis or on a per-content basis 1. if a user has opted out of the mechanism completely, their content **must not** be marked with a TTL. However, this does present a problem if they later change their mind ## 2. Advantages of this proposal 1. guarantees that user content is deleted from "well behaved" instances, even in the face of changing network topologies when instances defederate or disappear, hiccups in message delivery, server uptime and so on 2. would allow supporting Mastodon-like general content TTLs with a little modification, hence why it has TTLs per content and not just per user. Maybe something like a `refresh_liveness` boolean field on content that says whether an instance should do user liveness checks and refresh the content's TTL based on it or not? 3. with some modification this probably could (and should) be made to work with and support the regular content deletion flow. Something for draft v0.2 in case this gets any traction? ## 3. Disadvantages of this proposal 1. more network traffic, DB activity, and CPU usage, even during "normal" operation and not just when something gets deleted. Not a huge amount but the impact should probably be estimated so we'd have at least an idea of what it'd mean 1. however, considering the nature of the problem, _some_ extra work is to be expected 2. as noted, the current form of this proposal does not support or work with the regular deletion flow for individual comments or posts, and only addresses the more drastic scenario when a user account is deleted or disappears 3. spurious deletions of content are theoretically possible, although with long TTLs and persistent liveness check retries they shouldn't happen except in rare cases. Whether this is actually a problem requires more thinkifying 4. requires buy-in from the rest of the Fediverse as long as it's not a protocol-level feature (and there's more protocols than just ActivityPub). This same disadvantage would naturally apply to all proposals that aren't protocol-level. The end goal would definitely be to have this feature be a protocol thing and not just a Lemmy thing, but one step at a time 5. need to deal with the case where a user opts out of having their content deleted when they delete their account (whether they did this for all of their content or specific posts/comments) and then alter changes their mind. Will have limitations, such as not having any effect on instances that are no longer federated with their home instance ### 3.1 "It's a feature, not a bug" 1. when an instance defederates or otherwise leaves the network, content from users on that instance will eventually disappear from instances no longer connected to its network. This is a feature: when you lose contact with an instance for a long time, you have to assume that it's been "lost at sea" to make sure that the users' right to forgotten is respected. As a side note, this would also help prune content from long gone instances 2. content can't be assumed to be forever. This is by design: in my opinon Lemmy shouldn't try to be a permanent archive of all content, like the Wayback Machine 3. content can be copied to eg. the Wayback Machine (as noted above), so you can't actually guarantee deletion of all of a user's content from the whole Internet. As noted in the problem statement this is absolutely true, but what I'm looking for here is best effort to make sure content is deleted from compliant instances. Just because it's impossible to guarantee total deletion of content from everywhere does not mean no effort at all should be made to delete it from places that are under our control 4. this solution is more complex than simply _actually_ deleting content when the user so wishes, instead of just hiding it from view like it's done now in Lemmy. While "true deletion" definitely needs to _also_ be implemented, it's not enough to guarantee eventual content deletion in cases like defederation, or network and server errors leading to an instance not getting the message about content or a user being deleted
fedilink

Data protection, the right to be forgotten, and federation
Hey fellow nerds, I have an idea that I'd like to discuss with you. All feedback – positive or negative – is welcome. Consider this a baby RFC (Request for Comments). So. I've been having a think on how to implement the right to be forgotten (one of the cornerstones of eg. the GDPR) in the context of federated services. Currently, it's not possible to remove your comments, posts, etc., from the Fediverse and not just your "home instance" without manually contacting every node in the network. in my opinion, this is a fairly pressing problem, and there would already be a GDPR case here if someone were to bring the "eye of Sauron" (ie. a national data protection authority) upon us. Please note that this is very much a draft and it does have some issues and downsides, some of which I've outlined towards the end. ## The problem In a nutshell, the problem I'm trying to solve is how to guarantee that "well-behaved" instances, which support this proposal, will delete user content even in the most common exceptional cases, such as changes in network topology, network errors, and server downtime. These are situations where you'd typically expect messages about content or user deletion to be lost. It's important to note that I've specifically approached this from the "right to be forgotten" perspective, so the current version of the proposal solely deals with "mass deletion" when user accounts are deleted. It doesn't currently integrate or work with the normal content deletion flow (I'll further discuss this below). While I understand that in a federated or decentralized network it's impossible to guarantee that your content will be deleted (and the Wayback Machine exists), but we can't let "perfect be the enemy of *good enough*". Making a concerted effort to ensure that in most cases user content is deleted (initially this could even just be a Lemmy thing and not a wider Fediverse thing) from systems under our control when the user so wishes would already be a big step in the right direction. I haven't yet looked into "prior art" except some very cursory searches and I had banged the outline of this proposal out before I even went looking, but I now know that eg. Mastodon has the ability to [set TTLs on posts](https://fedi.tips/deleting-posts-automatically-in-mastodon-after-a-certain-time-period/). This proposal is sort of adjacent and could be massaged a bit to support this on Lemmy (or whatever else service) too. ## 1. The proposal: TTLs on user content 1. Every comment, post etc. (*content*) **must** by default have an associated TTL (eg. a `live_until` timestamp). This TTL can be long, on the order of weeks or even a couple of months. Users can also opt out (see below) 2. well before the content's TTL runs out (eg. even halfway through the TTL, with some random jitter to prevent "thundering herds"), an instance asks the "home instance" of the user who created the content whether the user account is still live. If it is, great, update the TTL and go on with life 1. in cases where the "home instance" of a content creator can't be reached due to eg. network problems, this "liveness check" **must** be repeated at random long-ish intervals (eg. every 20 – 30h) until an answer is gotten or the TTL runs out 2. information about user liveness ***should*** be cached, but with a much shorter TTL than content 3. liveness check requests to other instances **should** be batched, with some sensible time limit on how long to wait for the batch to fill up, and an upper limit for the batch size 4. in cases where the user's home instance isn't in an instance's linked instance list or is in their blocked instance list, this liveness check **may** be skipped 3. when a user liveness check hasn't succeeded and a content's TTL runs out, *or* when a user liveness check specifically comes back as negative, the content **must** be deleted 1. when a liveness check comes back as negative and the user has been removed, instances **must** delete the rest of that user's content and not just the one whose TTL ran out 2. when a liveness check fails (eg. the user's home instance doesn't respond), instances **may** delete the rest of that user's content. Or maybe **should**? My reason for handling this differently from an explicit negative liveness check is to prevent the spurious deletion of all of a user's content in cases where their home instance experiences a long outage, but I'm not sure if this distinction really matters. Needs more thinkifying 4. user accounts **must** have a TTL, on the order of several years 1. when a user performs any activity on the instance, this TTL **must** be updated 2. when this TTL runs out, the account **must** be deleted. The user's content **must** be deleted if the user hasn't opted out of the content deletion (see below) 3. instances **may** eg. ping users via email to remind them about their account expiring before the TTL runs out 5. users **may** opt out of the content deletion mechanism, both on a per-user basis or on a per-content basis 1. if a user has opted out of the mechanism completely, their content **must not** be marked with a TTL. However, this does present a problem if they later change their mind ## 2. Advantages of this proposal 1. guarantees that user content is deleted from "well behaved" instances, even in the face of changing network topologies when instances defederate or disappear, hiccups in message delivery, server uptime and so on 2. would allow supporting Mastodon-like general content TTLs with a little modification, hence why it has TTLs per content and not just per user. Maybe something like a `refresh_liveness` boolean field on content that says whether an instance should do user liveness checks and refresh the content's TTL based on it or not? 3. with some modification this probably could (and should) be made to work with and support the regular content deletion flow. Something for draft v0.2 in case this gets any traction? ## 3. Disadvantages of this proposal 1. more network traffic, DB activity, and CPU usage, even during "normal" operation and not just when something gets deleted. Not a huge amount but the impact should probably be estimated so we'd have at least an idea of what it'd mean 1. however, considering the nature of the problem, _some_ extra work is to be expected 2. as noted, the current form of this proposal does not support or work with the regular deletion flow for individual comments or posts, and only addresses the more drastic scenario when a user account is deleted or disappears 3. spurious deletions of content are theoretically possible, although with long TTLs and persistent liveness check retries they shouldn't happen except in rare cases. Whether this is actually a problem requires more thinkifying 4. requires buy-in from the rest of the Fediverse as long as it's not a protocol-level feature (and there's more protocols than just ActivityPub). This same disadvantage would naturally apply to all proposals that aren't protocol-level. The end goal would definitely be to have this feature be a protocol thing and not just a Lemmy thing, but one step at a time 5. need to deal with the case where a user opts out of having their content deleted when they delete their account (whether they did this for all of their content or specific posts/comments) and then alter changes their mind. Will have limitations, such as not having any effect on instances that are no longer federated with their home instance ### 3.1 "It's a feature, not a bug" 1. when an instance defederates or otherwise leaves the network, content from users on that instance will eventually disappear from instances no longer connected to its network. This is a feature: when you lose contact with an instance for a long time, you have to assume that it's been "lost at sea" to make sure that the users' right to forgotten is respected. As a side note, this would also help prune content from long gone instances 2. content can't be assumed to be forever. This is by design: in my opinon Lemmy shouldn't try to be a permanent archive of all content, like the Wayback Machine 3. content can be copied to eg. the Wayback Machine (as noted above), so you can't actually guarantee deletion of all of a user's content from the whole Internet. As noted in the problem statement this is absolutely true, but what I'm looking for here is best effort to make sure content is deleted from compliant instances. Just because it's impossible to guarantee total deletion of content from everywhere does not mean no effort at all should be made to delete it from places that are under our control 4. this solution is more complex than simply _actually_ deleting content when the user so wishes, instead of just hiding it from view like it's done now in Lemmy. While "true deletion" definitely needs to _also_ be implemented, it's not enough to guarantee eventual content deletion in cases like defederation, or network and server errors leading to an instance not getting the message about content or a user being deleted
fedilink

The good people of Finland decided to elect the most right wing government in the history of the country just a couple of months ago. The government is a coalition of an extreme right wing party, a right wing christian party, the Swedish People's Party (nominally centrist) and a "fiscally conservative" party – ie. they _mostly_ leave saying the bigoted shit out loud to the other two parties, but occasionally eg want to fund a Waffen SS volunteer "memorial organization" with government money, to spread "true information" about the SS volunteers who totally weren't ideologically motivated and totally didn't participate in the Holocaust (they absolutely did and we have archived war diares as proof, but it hurts the neo-nazis' feelings if you say that out loud.) The parties finally managed to come up with a plan on how to run things 10 days ago (hint: not well), and the extremist party has already gotten into multiple PR fuckups due to being full of neo-nazis and neo-nazi sympathizers, and now one of the newly minted ministers had to resign _officially_ due to making a "joke" (ie. it's not a joke until it gets him in trouble, and then it's a joke) about how climate change could be solved by forcing Africans to abort children. The _actual_ reason is that the fresh minister in question also made a speech at a neo-nazi rally and made "jokes" about HH / 88, made a klansman snowman complete with a noose, hired a senior adviser who is a literal neo-nazi and has made eg. social media posts admiring Hitler, lied about almost literally every achievement in his life – university, multiple years of work experience, etc – and the list just goes fucking on and on. And don't get me started on what these people are doing to the country's public sector funding. Education is fucked, public healthcare is double fucked, welfare is extra triple fucked with fuck on top.
fedilink

I'm a layperson when it comes to physics, and I've always been a bit confused about what virtual particles actually are, especially since the terminology is often downright misleading – "virtual particles in and out of existence", other particles "exchanging virtual particles" etc. This blog post by theoretical physicist Matt Strassler was really helpful in explaining the concept (as far as it _can_ be explained without going elbow deep into math, I guess)
fedilink

Source: NASA's [Astronomy Picture of the Day](https://apod.nasa.gov/apod/ap230630.html). > Explanation: Are asteroids dangerous? Some are, but the likelihood of a dangerous asteroid striking the Earth during any given year is low. Because some past mass extinction events have been linked to asteroid impacts, however, humanity has made it a priority to find and catalog those asteroids that may one day affect life on Earth. Pictured here are the orbits of the over 1,000 known Potentially Hazardous Asteroids (PHAs). These documented tumbling boulders of rock and ice are over 140 meters across and will pass within 7.5 million kilometers of Earth -- about 20 times the distance to the Moon. Although none of them will strike the Earth in the next 100 years -- not all PHAs have been discovered, and past 100 years, many orbits become hard to predict. Were an asteroid of this size to impact the Earth, it could raise dangerous tsunamis, for example. To investigate Earth-saving strategies, NASA successfully tested the Double Asteroid Redirection Test (DART) mission last year. Of course, rocks and ice bits of much smaller size strike the Earth every day, usually pose no danger, and sometimes create memorable fireball and meteor displays.
fedilink


Work-Efficiency vs. Step-Efficiency (in parallel processing)
Good explanation of the difference between work efficiency and step efficiency when talking about parallel algorithms.
fedilink




Dr. Angela Collier plays the Binding of Isaac: Rebirth and talks at length about what went wrong with string theory, and how that affected science communication.
fedilink




Description of ActivityPub protocol?
Hey does anybody know if there's a description of ActivityPub available that isn't just [the spec](https://www.w3.org/TR/activitypub/)? I realized I don't actually know how the protocol works, and I'd be interested in learning more. May have to just bite the bullet and dive into the spec – it doesn't actually look too bad based on a quick glance – but a summary would be cool
fedilink


Original [here](https://www.facebook.com/groups/376947332744820/permalink/1765469683892571/)
fedilink


I've lived in Finland for most of my 40-odd years but I can never get over how weird the nightless nights feel at the beginning of every summer. It's 3am and this is as about as dark as it gets. That just ain't right, it ain't natural. Makes a person wish for thicker curtains
fedilink

I had many expectations for today, but learning that mushrooms sweat wasn't one of them. > The scientists are still unsure why fungi might want to keep cool. > In their paper, the authors speculate that it might have something to do with creating optimal conditions for spore formation, or it may help fungi spread their spores — by altering the temperature, they might be causing tiny winds that can blow the spores around. > It’s also possible that this phenomenon is due to something else entirely. For example, evapotranspiration also increases humidity, and when asked if it’s possible that the fungi are trying to keep humid, and the cooling is simply a by-product, Casadevall said it was conceivable.
fedilink

MIT 22.01 Introduction to Nuclear Engineering and Ionizing Radiation course on YouTube
I'm 24 lessons in at this point and it's been absolutely fascinating. Highly recommended if you're interested in learning about how nuclear anything works.
fedilink