Threads is officially starting to test ActivityPub integration
7heo @ 7heo @lemmy.ml Posts 21Comments 603Joined 2 yr. ago
7heo @ 7heo @lemmy.ml
Posts
21
Comments
603
Joined
2 yr. ago
- 1999, XMPP is born. 👶
- 2005, Google launches "Talk", touted as a "great victory for XMPP", with "large-scale XMPP services".
- 2012, Google encourages "Talk" users to switch to "Hangouts".
- 2013, Google drops open XMPP interoperability with other servers.
- 2015, Google begins shutting down "Talk" clients.
- 2017, previous phase is now complete, XMPP is virtually unheard of.
- 2022, Google shuts down all XMPP integration. XMPP is, for all intents an purposes, dead. 🪦
- 2016, Mastodon is born. 👶
- 2023, Meta launches "Thread", touted as a great victory for Mastodon. ← You are here.
- 2030, Meta encourages "Thread" users to switch to "Fabric".
- 2031, Meta drops open ActivityPub interoperability with other servers.
- 2033, Meta begins shutting down "Thread" clients.
- 2035, previous phase is now complete, Mastoson is virtually unheard of.
- 2040, Meta shuts down all Mastodon integration. Mastodon is, for all intents an purposes, dead. 🪦
N.B.: The delays in the timeline were copied over verbatim. Historical conditions have to be taken into account, as the popular adoption of internet began in the late 2000s. So it is likely for the "extinguish" phase of Mastodon to happen much faster. I give it 5 years tops. And by 2030, we will all remember it as we now remember XMPP.
Yep, I've been enraged by this decision from day one. This is depressingly amateur. Let people join, let other developers make very cool apps, and then introduce a deeply breaking change in a minor version, and deploy it on the most active instance, with mere days of warning. Or "How to destroy all the progress made by Lemmy, in one small change".
I get it if the devs and admins of Lemmy.ml are paying too much out of their own pocket, and if they want users to literally go away, to mitigate that cost.
But doing it in such an in such an insidious, demoralizing way, as opposed to being transparent with the costs and announcing (drastic) measures to mitigate that cost, is literally destroying most of the progress made so far, and driving most users back to reddit.
As of today, the list of most active servers of the fediverse has only one Lemmy server (Lemmy.world), in ninth position, and that is the only Lemmy server in that list, over four pages... The Lemmy instances used to be in the middle of the first first 10 instances, with Lemmy.ml leading the way.
Now, I guess the devs didn't want to take those drastic measures, and tell people to they would be closing down their accounts, ordered by creation date, until the costs become bearable again. Because that would mean "admitting the Lemmy.ml experiment to show the world that people are, when given the opportunity, rising to the challenge, and putting in the effort, in true communist fashion, is actually a failure". People aren't ready for communism. Communism requires education, intelligence, and empathy/compassion. Our western societies are fostering the opposite traits. When we become educated, intelligent, and empathic or compassionate, it is in spite of our societies, not thanks to them.
Now, a few people opened instances, but it wasn't enough, and fast enough, when the "reddit migration" happened, to absorb the insane influx of users to Lemmy.ml.
So I guess it is what it is, but it's still sad and depressing...
I had SSDs go bad, and mechanical hard drives too. The major plus for me is that with HDDs, it is somewhat predictable, while with SSDs it has always been sudden (in my experience, at least).
However, there are more parameters to consider. The storage temperature, the relative humidity, to backup frequency, etc. In the end, if you want a 100% time proof solution without caring for the costs, engraving a crystal, storing it underground in a lead-lined container, is probably the surest way to go. Everything else is a compromise.
It depends how critical the data is.
SSDs and flash are great for speed, but as other comments have mentioned, they can eventually lose data more than other mediums. However this reportedly isn't likely to happen over the normal rated timespan of the devices, unless there is a critical defect.
Magnetic storage will likely last longer, and as it is a much older tech, is less likely to have firmware bugs and other problematic surprises. Plus, as you can see on https://diskprices.com/, the cheapest medium per TB remains magnetic storage.
Then there are tapes. The drives sure cost a hefty sum, but if you have loads of data to backup, this is likely the cheapest option.
Finally, optical. Optical is great in the sense that is is physically a ROM, so data cannot get compromised by mishandling or other staff mistakes; but it still can have issues with the reflective layers peeling away from disks.
So, in the end, I would personally not recommend using SSDs for data backups, out of precaution. Sure, SSDs will likely retain all data just fine for years to come, but I want to be able to store data for as long as possible, with the peace of mind that only magnetic storage will afford me. Plus, if your data is worth backing up, it is worth whatever extra price or effort you will have to do with.
As for the other options, well, they all have their use case, but I don't see much advantage for them in the general use cases. Just make backup copies of your data on magnetic drives, in a few physically different locations, with proper access control.
This is just pointless drama. It's an emotional shitshow with way too much ego from all participants. The reaction from the Dev is actually bad, but the OG CVE is equally bad.
On one hand, I don't expect an app to let me inject code even as an admin. That's just very bad form, and asking for trouble.
On the other hand, arguably, if an attacker has admin access, you're toast. So that's also hardly a CVE.
Now, all the involved people have terrible written expression, poor grammar, and are even omitting entire chunks of sentences.
And then there's the content... Nah, this is just noise. Absolute junk. Sorry, but IMHO this has nothing to do in this community.
Please stop posting paywalled articles. Neither 1ft.io/12ft.io nor archive.ph could get the full text out of that one...
Could you post the full article here?
- Learn basic freecad
- Learn basic openscad
- Learn how to use openscad in freecad
- Iterate
Side note, freecad is CPU bound, so use a good CPU.
Still better than Jakøff. Heard he is a total wanker...
01000110 01101001 01110010 01110011 01110100 00100000 01101111 01100110 01100110 00101100 00100000 01111001 01101111 01110101 00100000 01101111 01101101 01101001 01110100 01110100 01100101 01100100 00100000 01110100 01101000 01100101 00100000 01110011 01110000 01100001 01100011 01100101 01110011 00101100 00100000 01110111 01101000 01101001 01100011 01101000 00100000 01110011 01110101 01100011 01101011 01110011 00100000 01110001 01110101 01101001 01110100 01100101 00100000 01100001 00100000 01100010 01101001 01110100 00100000 00101000 01100101 01110011 01110000 01100101 01100011 01101001 01100001 01101100 01101100 01111001 00100000 01100011 01101111 01101110 01110011 01101001 01100100 01100101 01110010 01101001 01101110 01100111 00100000 01110100 01101000 01100101 00100000 01110011 01100101 01100011 01101111 01101110 01100100 00100000 01110000 01101111 01101001 01101110 01110100 00101001 00101110 00100000 01010011 01100101 01100011 01101111 01101110 01100100 00101100 00100000 01111001 01101111 01110101 00100000 01100110 01101111 01110010 01100111 01101111 01110100 00100000 01110100 01110111 01101111 00100000 01101100 01100101 01100001 01100100 01101001 01101110 01100111 00100000 01111010 01100101 01110010 01101111 01100101 01110011 00101100 00100000 01101111 01101110 01100101 00100000 01100001 01110100 00100000 01101111 01100110 01100110 01110011 01100101 01110100 00100000 00110000 01111000 00110011 00110000 00100000 01100001 01101110 01100100 00100000 01101111 01101110 01100101 00100000 01100001 01110100 00100000 01101111 01100110 01100110 01110011 01100101 01110100 00100000 00110000 01111000 00110100 01000101 00101110 00100000 01000001 01101110 01100100 00100000 01110100 01101000 01101001 01110010 01100100 00101100 00100000 01110100 01101000 01100001 01110100 00100111 01110011 00100000 01101110 01101111 01110100 00100000 01101111 01101110 00100000 01111001 01101111 01110101 00101100 00100000 01100010 01110101 01110100 00100000 01100001 01110000 01101111 01110011 01110100 01110010 01101111 01110000 01101000 01100101 00101101 01110011 00100000 01100100 01100101 01101110 01101111 01110100 01100101 01110011 00100000 01110100 01101000 01100101 00100000 00101010 01110000 01101111 01110011 01110011 01100101 01110011 01110011 01101001 01110110 01100101 00101010 00101100 00100000 01101110 01101111 01110100 00100000 01110100 01101000 01100101 00100000 01110000 01101100 01110101 01110010 01100001 01101100 00101100 00100000 01100001 01101110 01100100 00100000 01001001 00100111 01101101 00100000 01100001 01100010 01110011 01101111 01101100 01110101 01110100 01100101 01101100 01111001 00100000 01110011 01101001 01100011 01101011 00100000 01100001 01101110 01100100 00100000 01110100 01101001 01110010 01100101 01100100 00100000 01101111 01100110 00100000 01110011 01101111 00100000 01100011 01100001 01101100 01101100 01100101 01100100 00100000 00100010 01101110 01100001 01110100 01101001 01110110 01100101 00100010 00100000 01000101 01101110 01100111 01101100 01101001 01110011 01101000 00100000 01110011 01110000 01100101 01100001 01101011 01100101 01110010 01110011 00100000 01110100 01101000 01100001 01110100 00100000 01101000 01100001 01110110 01100101 00100000 01100001 00100000 01110111 01101111 01110010 01110011 01100101 00100000 01000101 01101110 01100111 01101100 01101001 01110011 01101000 00100000 01110100 01101000 01100001 01101110 00100000 01101101 01100101 00100000 00101101 00100000 01100101 01110101 01110010 01101111 01100110 01100001 01100111 00100000 01110111 01101000 01101111 00100000 01110011 01110000 01100101 01100001 01101011 01110011 00100000 01110100 01110111 01101111 00100000 01100001 01101110 01100100 00100000 01100001 00100000 01101000 01100001 01101100 01100110 00100000 01101100 01100001 01101110 01100111 01110101 01100001 01100111 01100101 01110011 00101100 00100000 01110011 01101111 00101100 00100000 01100001 01110010 01100111 01110101 01100001 01100010 01101100 01111001 00101100 00100000 01101100 01100101 01110011 01110011 00100000 01110000 01110010 01101111 01100110 01101001 01100011 01101001 01100101 01101110 01110100 00100000 01100001 01110100 00100000 01100001 01101110 01111001 00100000 01101111 01101110 01100101 00100000 00101101 00100000 01100001 01101110 01100100 00100000 01110111 01101000 01101111 00100000 01100011 01100001 01101110 00100111 01110100 00100000 01100101 01110110 01100101 01101110 00100000 01101101 01100001 01101110 01100001 01100111 01100101 00100000 01110100 01101111 00100000 01110011 01110000 01100101 01100001 01101011 00100000 01101010 01110101 01110011 01110100 00100000 01001111 01001110 01000101 00100000 01101100 01100001 01101110 01100111 01110101 01100001 01100111 01100101 00100000 01100011 01101111 01110010 01110010 01100101 01100011 01110100 01101100 01111001 00101110 00100000 01010100 01101111 00100000 01101101 01100001 01101011 01100101 00100000 01101101 01100001 01110100 01110100 01100101 01110010 01110011 00100000 01110111 01101111 01110010 01110011 01100101 00101100 00100000 01101001 01110100 00100000 01101001 01110011 00100000 01101111 01101110 01100101 00100000 01101111 01100110 00100000 01110100 01101000 01100101 00100000 01110011 01101001 01101101 01110000 01101100 01100101 01110011 01110100 00100000 01101100 01100001 01101110 01100111 01110101 01100001 01100111 01100101 01110011 00100000 01101111 01101110 00100000 01110100 01101000 01100101 00100000 01100110 01110101 01100011 01101011 01101001 01101110 01100111 00100000 01110000 01101100 01100001 01101110 01100101 01110100 00101100 00100000 01100010 01100101 01101001 01101110 01100111 00100000 01101000 01100101 01100001 01110110 01101001 01101100 01111001 00100000 01100011 01101111 01101110 01110100 01100101 01111000 01110100 01110101 01100001 01101100 00100000 01100001 01101110 01100100 00100000 01110100 01101000 01100101 01110010 01100101 01100110 01101111 01110010 01100101 00100000 01100011 01101111 01101110 01110110 01100101 01111001 01101001 01101110 01100111 00100000 01100001 00100000 01110011 01101001 01100111 01101110 01101001 01100110 01101001 01100011 01100001 01101110 01110100 00100000 01110000 01100001 01110010 01110100 00100000 01101111 01100110 00100000 01101001 01110100 01110011 00100000 01101101 01100101 01100001 01101110 01101001 01101110 01100111 00100000 01101001 01101101 01110000 01101100 01101001 01100011 01101001 01110100 01101100 01111001 00101110 00100000 01000001 01101110 01100100 00100000 01110100 01101111 00100000 01100001 01100100 01100100 00100000 01101001 01101110 01110011 01110101 01101100 01110100 00100000 01110100 01101111 00100000 01101001 01101110 01101010 01110101 01110010 01111001 00101100 00100000 01110100 01101000 01100101 00100000 01100100 01101001 01101101 01110111 01101001 01110100 01110100 01100101 01100100 00100000 01001111 01010000 00100000 00101010 01100001 01101100 01110011 01101111 00101010 00100000 01100111 01100001 01110100 01100101 01101011 01100101 01100101 01110000 01110011 00100000 01110000 01100101 01101111 01110000 01101100 01100101 00101100 00100000 01100011 01100001 01101100 01101100 01101001 01101110 01100111 00100000 01110100 01101000 01100101 01101101 00100000 00100010 01101001 01100100 01101001 01101111 01110100 01110011 00100010 00100000 01101111 01110110 01100101 01110010 00100000 01110000 01100101 01110010 01110011 01101111 01101110 01100001 01101100 00100000 01110000 01110010 01100101 01100110 01100101 01110010 01100101 01101110 01100011 01100101 00101110 00101110 00101110 00100000 01000101 01101110 01101111 01110101 01100111 01101000 00100000 01110111 01101001 01110100 01101000 00100000 01100111 01101100 01101111 01110010 01101001 01100110 01111001 01101001 01101110 01100111 00100000 01100011 01101111 01101110 01110100 01100101 01101110 01110100 00100000 01100110 01110010 01101111 01101101 00100000 01110000 01100101 01101111 01110000 01101100 01100101 00100000 01110111 01101111 01110100 01101000 00100000 01110010 01101111 01101111 01101101 00101101 01110100 01100101 01101101 01110000 01100101 01110010 01100001 01110100 01110101 01110010 01100101 00100000 01001001 01010001 00101110 00100000 01000110 01000110 01010011 00101110
expired
Because in spite of the question ("private host" as opposed to "privacy friendly host"), people have commented in the context of privacy (probably because of the community we're on); and in that context, the mere mention of github or gitlab is met with downvotes.
IMHO using github or gitlab for that isn't much of a concern privacy wise (at least not more than browsing a website from the companies behind those services), but it surely is when it comes to data integrity (which is a totally separate concern, but people often confuse it with privacy, like they also do with security). I would not trust either service with that.
The state before Google was "up and coming solution for federated chat"
The state after Google was "impractical solution that does not federate¹ properly, and is hard to set up²".
Those are not the same.
1: because of Google.
2: because of Google.