Never heard of that tool. Thank you for sharing it!
Just a nerd who migrated from kbin(dot)social.
Never heard of that tool. Thank you for sharing it!
There are dozens of us! Dozens!
PipePipe has even more sources.
Most social media has a leftward bias. Avoiding politics in any form of social media now is like trying to avoid plankton in ocean water - you might be able to do it, but you’ll need a really tight filter.
Hasn’t been my experience, but I’m mostly in a sphere of scientists, creatives, and memes. A couple art museums post some great stuff too.
I don’t remember MSN Messenger being able to handle IRC chats. If it had, I wouldn’t have needed an IRC client. But Threads won’t drown out other voices, they’ll just add voices to the conversation. There’s content on Threads that’s worth following, and I don’t think it’s valuable to lose that because of a few engagement farms that you can either personally block or defederate.
Somewhat selfishly, I’d suggest she try Mbin instead. It allows her to interact with both the microblog side of the fediverse (including bridges) and the thread side, from the same interface.
Threads is a great example of a company acknowledging that the open web exists and bringing content people want to places where they want to be. I’d like to be able to interact with everyone through one or two accounts, not have to maintain a Meta account, an Mbin account, a Google account, and all the rest.
You may not like it, but I believe the open web is about things like Threads being federated - individual platforms interacting freely, no matter who built them.
Oh neat. I’ve been aware of this for a while and I’m glad in an academic sense that it exists. I guess I would need more people that I care about who are on Bluesky.
Now if only there were instances willing to actually host anything worth watching.
Better yet, I’ll request the admin specifically to federate with Threads, so that I can move across the stuff that I care about to mbin from the Threads app.
Thank goodness. PeerTube needs wider adoption. We need creators as much as we need consumers.
Mail clients, torrent clients, and word processors are fundamentally different from browsers. Yes, we can implement their base functions inside a web browser, but that’s not their function, or their core UX principle. Also, you forgot NNTP. Thee is no value in moving away from HTTP(S).
Okay, that’s his opinion. Like his opinions on many things, I feel entirely free to disagree with him.
Absolutely not. It should run on HTTP, as a website. Unless you want to build a client which would be somehow fundamentally different from a web browser somehow (note: Lagrange and Gopher Browser are just browsers), which would somehow be able to display data from every use of ActivityPub / “the fediverse” in a different context from a web browser, then no. What we need to build is website software more in line with kbin / mbin, collecting together all the different information of the fediverse into one interface.
Uh-huh. The error was that they were caught doing it.