Thanks, I appreciate it! It took a stupidly long time. :V
On some level, it’s probably not that important that people understand all this stuff, but I think the most dangerous thing is people believing that their data will be protected if Threads gets defederated. Any other confusion is basically harmless, but that’s the one thing where people have a false sense of security, because Meta has exactly the same access to your data whether or not they get defederated.
No, I don’t want to? Weird take.
Definitely. Meta is studiously only sharing the number of accounts registered. We have no idea how many of those are active. If we go with the old 1-9-90 rule, only about 10 million of those 100 million will become active users. Although, the rule obviously isn’t a universal constant. On the fediverse, for example, it’s closer to ⅓ of registered users that are active.
You already got a solution to this, but an alternative mechanism for people who use uBlock Origin is to add this filter to your custom list:
kbin.social##^style
That assumes you’re on kbin.social, obviously substitute in your home kbin instance.
This is untrue. Threads accounts are reserved for the matching Instagram user, but those users have to actually choose for that account to be opened. If all Instagram accounts were auto-converted to Threads accounts there’d be over 1 billion Threads accounts. The 100 million Threads users are all people who have specifically opted to have a Threads account.
In fairness, I think we might already be the rest who don’t matter. Threads has just passed 100 million users in like three days. The entire fediverse, in about ten years (it’s tough to pin down an exact start date because “When did it become the fediverse?”), has accrued around 12 million users, of which less than 4 million are active. There’s any number of things Meta might want, but I don’t think greater access to 4 million geeks is at the top of their list.
I do think the embrace, extend, extinguish concerns have some merit. Meta isn’t threatened by the fediverse now, but maybe they do want to kill it before it becomes a problem. In the short term, though, we’re not overtaking Threads. Personally, I think another plausible theory is that Threads is using ActivityPub to demonstrate that they’re not running a monopoly or gatekeeping control of social media (which the EU’s new Digital Markets Act now regulates) by pointing to the fediverse–which will soon also include direct competitors Tumblr–and saying “See, we’re all on equal footing! We don’t control social media! Look over there at those 4 million geeks and whatever number of Tumblr users.”
It comes from Fortune, they can’t conceive of something that’s not a business.
Hard to tell. It’s been in decline since January though, so some of it is just Twitter being a place people want to be less and less.
Here’s the graph, as posted by CloudFlare CEO Matthew Prince:
Yeah, they can vote and reply and all of that and others who remain federated will see their interactions, but you or any other server who defederates them won’t.
Yeah, my understanding is that defederation prevents any incoming communication, so you won’t see any posts or comments that come from lemmy.bullshit, however users from lemmy.bullshit will still see all of your comments and posts from lemmy.world unless they choose to defederate you back.
Isn’t that privacy more illusory than actual? You’re not surfacing the web pages which show the votes, but the protocol is openly sharing that info and anybody can still see what your instance’s users have voted on just by looking at them from a different instance. I’m not going to out anybody, but it was trivial for me to find that thread here on kbin.social and see exactly who upvoted it, including a kglitch.social user.
This looks cool and all, but what has it got to do with kbin?
It’s a bit self-serving of me to phrase it this way, but I do think the Reddit debacle shaved off a disproportionately not-terrible segment of the Reddit userbase. I think you could make your comment about Redditors instead and it would still be fair. There’s obviously a lot of Twitter users we don’t want here, but if we got the top 0.1% of Twitter users by quality? That’s not bad.
Busted! I have been thinking about how “threadiverse” is complicated a lot by Threads existing. It could easily mean “the part of the fediverse that is attached to Threads” (uppercase) rather than “the part of the fediverse that revolves around threads” (lowercase). Maybe we already need a new name. Eggheadiverse?
I think the portmanteau “threadiverse” works for this situation and it’s what I’ve been using to refer to anything in the general Lemmy/kbin side of the fediverse, but I think people just referring to the platform is inevitable. People talk about posts “on Mastodon” even though there’s like 15 different services you can use to post to the blogging side of the fediverse, like Pleroma, pump.io, etc. It’s worth thinking about in situations where you’re like “Hi Lemmy” because you’re definitely talking to more than just Lemmy, but any time you’re talking about your personal experience of where you saw a thread I think it’s perfectly accurate to use the name of that platform rather than having to say you saw it “on the fediverse”.
Bit of a downer, but it is an Android news site. kbin currently doesn’t really merit much of a mention in that context. The PWA is nice, but by its nature barely related to Android, since it also runs on Windows, MacOS and everything else under the sun.
People self-host all kinds of things on Raspberry Pis, from web and other servers to home automation hubs. Web serving is extremely cheap in terms of CPU time, even moreso when you’re only hosting for yourself and perhaps family/friends. I wouldn’t recommend running an open web service like a Lemmy instance on a Raspberry Pi, but hosting something like this would have a minimal impact on a Pi. I have a multiple-generations-old Pi 3 which hosts an IRC bouncer, DNS-level ad blocker, Matrix chat bridge, web server and probably more stuff I’ve already forgotten and I can still use it for media playback or retro emulation concurrent to the rest, if the mood strikes.
The recent updates have already made it work as you expect. Upvotes are upvotes. Boosts are still boosts but are also counted as being worth 2 votes.
For the most part, Threads content just wouldn’t appear on Lemmy at all. It’s like how you can’t see Mastodon users’ timelines on Lemmy. e.g. Jeri Ryan from Star Trek is on
mastodon.world, but you can’t read her blog from Lemmy because it just doesn’t display microblog content, only stuff that’s sorted into groups (communities).The one exception is that Jeri Ryan can track down the equivalent group on her Mastodon instance and “microblog” directly into the group. Mastodon has some hacky tweaks to do things like reading the first sentence as a heading, the second line as a URL, and the third line as the post body, so if you’re especially dedicated you can post to Lemmy from Mastodon. If Threads cares enough, they could add similar functionality to Threads to make it technically possible to post to Lemmy as long as you try hard enough, but just regular people’s blog posts on Threads won’t display on Lemmy at all.