Also:
Again, key factors being: open, customizable, correctable, and serving the user, not serving the platform.
They don't really use the major.minor.bugfix scheme anymore. If they did, they wouldn't be at version 117.
I tend to think of them all as minor updates that add up over time, like a rolling release with numbers.
And even when you can, saving files one by one from Wayback is a lot slower than re-uploading your local copy to a new server
I was expecting this to be a half-baked plan to block something using a less-than-half-baked definition that would also cover security updates.
The fact that someone actually thinks explicitly blocking security updates is a good idea is just appalling.
Even better: the one-star review on the pre-order page complaining that it's not out yet!
Assuming you mean the save-to-read-later functionality, I hear good things about Wallabag. You can even self-host it if you want.
A backpack solves both problems!
KDE Plasma handles the touch screen fine on my PineTab2.
It works in LxQt too, but only in portrait mode (which is the default for this device). I keep meaning to look up how to tell it to rotate the touch coordinates along with the display, and I keep not getting around to it.
But the main issue I've run into is that most GUI apps for Linux are...let's just say they're not designed with touch input in mind.
I've been using the Firefox Translations extension that this is probably building on. Also runs entirely in the client.
Having this built into the browser is going to be a great selling point.
Not much point in writing a PR if the idea has already been rejected (or is still hotly contested) in the issues. Most of the suggestions aren't just write-some-code solutions, they're design decisions, and if the project owner doesn't agree with that decision? Well, you can fork it like glitch-soc or hometown, or you can use another project that already does what you want (but doesn't have as much traction), or you can keep trying to convince the people running the project to accept your idea. Even quote posts, which they're finally coming around to grudgingly accept as a possible feature, involve a lot of decisions on which posts can be quoted, who gets notified, etc.
As others have said: followers yes, posts, no. Some other Fediverse platforms can migrate posts, though, and I believe Firefish (previously known as Calckey) is able to import posts from Mastodon as well as from other instances of itself.
Examples of this might include prioritizing mutual followers on Mastodon, or prioritizing low-traffic subscribed communities on Lemmy so that they don't get lost in the 50 posts from the busier communities.