Perhaps that was exactly the intent, to ensure that only actual humans read the content?
If that's the case, it has the opposite effect. Humans generally benefit from being able to select text and not just read from an image. It's of course especially important for blind people.
Meanwhile computers can easily read images via OCR algorithms.
I don't agree with the comment there. In my mind, the LTS release would not mean anything. It would just be a label on an arbitrary release every couple of years. I feel it could help the ecosystem align on which MSRV to choose, so that you don't have one crate choosing 1.x, another chooses 1.(x+1) and another chooses 1.(x+5). It would be nice if we just sort of agreed that if you care about your crate being used by somewhat older compilers, use the LTS version and consider the implications if your MSRV go beyond that version.
Of course any crate author is free to completely ignore this and choose whatever MSRV they desire. But perhaps a significant amount of authors would put at least a little effort (but not much) in trying to avoid raising the MSRV above the LTS version, just as authors may try to avoid breaking changes and such. It's just a nudge, nothing more.
An LTS release scheme, combined with encouraging libraries to maintain MSRV compatibility with LTS releases, could reduce this friction.
This actually sounds like a good idea. Currently crates are choosing their MSRV all over the place. If we just got a bit of alignment by calling every ~17th Rust release (roughly 2 years worth of releases) an "LTS" release, then crates could be encouraged to keep their MSRV compatible with that release.
But we also heard a consistent shape of gaps [in core]: many embedded and safety-critical projects want no_std-friendly building blocks (fixed-size collections, queues) and predictable math primitives, but do not want to rely on "just any" third-party crate at higher integrity levels.
I think some fixed-size collections and stuff like that would be super nice in core. Something with simple, predictable semantics, just like Vec has (i.e. no optimizations for certain usage patterns, like small string optimizations and that sort of stuff). With const generics working for integers, fixed size collections in core shouldn't even be that hard (it's certainly been done in many crates already).
I mean, that's still acknowledging that damage is being done, just less than actual graffiti. I'd rather not associate the fediverse with defacing public spaces with half-scraped off stickers.
Again, feel like a t-shirt or a cap is a much better option.
It might be because I am in Denmark which has quite a functioning and lawful system and where I see the most graffiti is in public transport, like on trains and train stations. The transport company spends a lot of money cleaning that graffiti, making public transport more expensive for everyone else (hence antisocial behavior).
So I can understand where you are coming from but my perspective is just different.
I definitely do not find graffiti cool. It's illegal and antisocial behavior. The art can be cool of course (although it very rarely is in my experience), but the illegal act is not.
Isn't this not much better than graffiti? I think advocating for the fediverse is great, but let's not plaster unnecessary and potentially illegal posters/advertisements everywhere.
If you want to display an appreciation for the fediverse, perhaps there are T-shirts with the fediverse logo?
We're actually seeing a rise in new user applications over at Feddit.dk. The hostile behavior of the US has gotten some Reddit users to seek alternatives to american platforms.
Could you elaborate on why that is a bad thing? I'm sort of confused why you wouldn't want everyone to be in on it. To be clear, I don't think we really need to change the goal, I just think the wording is unfortunate.
But again, I think we honestly shouldn't focus on this small disagreement of the words, as long as we agree on the idea itself. We may not agree on feminism or egalitarianism as words, but I think we both agree on the much more important ideas behind it.
It may also be that I'm coming at this discussion from a Danish perspective, which is very different from an American perspective (I'm assuming you're american, sorry if that's not correct). We usually use a word like "ligestilling" which translates as "equality" rather than use a term like feminism.
He had a point but he kinda fucked it up in the third panel.
Tbh I think the term is kind of unfortunate exactly because of this confusion and rebuttal. We would spend less time discussing this if it was actually called egalitarianism or whatever, I feel. People use the "fem" in feminism to make the movement seem unequal. I think the term is just kind of unnecessarily confusing and egalitarianism would be less ambiguous.
But I don't really care that much, the ideas behind are obviously more important than the word we use - but words are also important.
Fediverse platforms are not in competition with each other. In fact, it's more like symbiosis. There's no problem with having 15 or even 100 fediverse platforms.
Why do you need a culture shift if anyone can just pick whatever platform they personally prefer? If you want a certain cultural approach, then feel free to use a fediverse platform with that approach, but there's no need for anyone else to follow the same choice, unless they want to.
I mean okay sure, you can disable these things. But the fact that they are enabled out of the box in the software as written is a huge red flag.