I asked and enough of you answered that allowing to federate with threads.net even for the lolz would be considered too risky for y'all.
So I've gone ahead and added threads.net to our blocklist.
this post was submitted on 11 Jul 2023
627 points (98.6% liked)
/0
1560 readers
1 users here now
Meta community. Discuss about this lemmy instance or lemmy in general.
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, I still remember early days of building something for the internet and you know what held back development easily by years: Internet Explorer. Big corporations even back then were playing that same shitty game of EEE, trying to lock people down and not caring at all about standards. Standards are why we have an internet at all.
Yeah, all the EEE talk made me reminisce a day or so ago about how IE was intentionally breaking standards and how dumber IT types fell for it and used it because "It's more compatible!".
and then they had their software and some others spit out .htm files instead of .html files because it would cause just enough issues to let them still claim they were in support with the standard yet somehow weren't....
And defederating threads would not be considered „locking down“?
It's not. It's a choice that instances make, not a change to the protocol. You can always change your instance or host your own and as long as Threads conforms to the activitypub protocol you can interact with it. Locking down cannot happen as long as majority of participants adhere to an open protocol. It is what happens when a major player makes proprietary changes to how interaction works. Please study how EEE works, there are numerous examples in the past. Defederation is not that.
Well I believe we will come to no agreement then. To my understanding, locking down is both, proprietary software and the decision to defederate. Because both have the same result.