(1) #Twitter has millions of users. There is no #ActivityPub nor #OStatus implementation in which an instance hosted on a $5/mo #DigitalOcean / #Linode / #Vultr #VPS could handle the volume of a seamless connection with #Twitter. If they adopted AP OStatus, #Diaspora, or any other current open federation protocol, instances that didn't use firewall blocking would topple once the two userbases had sufficient interconnections (within a few hours or a few days after they started federating).
(2) Twitter's business model is to push ads disguised as tweets. If their users could escape those and still interact with all the same contacts, they would. I'm certain that Twitter's management know this. They also turn all links into tracking links, and sell access to media (images, video, audio) uploads of important news events to news organizations.
(3) Most Fediverse instances are financed out of the admin's pocket. Some have financial contributors, but nothing like Twitter's revenue. As the largest and best-financed instance, they would immediately have to start implementing modifications to make AP or other existing federation protocols useful to them, and those modifications would (as Mastodon's currently do) become unofficially mandatory in order to be compatible.
(4) This isn't the first time that Twitter has considered federation, though this may be the first time they openly discussed it. Back when Identica was still a happening place (during Twitter's fail-whale days), Twitter considered federating. They didn't do it then, and I honestly do not believe they will do it now.
(5) I'd say that Twitter's #BlueSky initiative is more meant to try to get bidirectional connections across #Facebook's moat and wall than it is to surround Twitter with a cloud of #Fediverse instances.
I know this because JoinDiaspora sent me a bunch of notification e-mails about people’s birthdays. (I think it just assigned YYYY-JAN-01 for anyone that didn’t fill out a birthday; as far as I remember, giving that information wasn’t even an option when I joined #Diaspora. I truly think it is betraying the “we’re privacy focused” approach they promised all those years ago. #JD, this should be something that accounts opt into.)
@vegos I agree. To most organizations, their primary concern is reach. So they congregate on big #corpocentric #socnets, even when the central corporation running things is actively hostile to their point of view.
Then they're butthurt when their accounts are shadowbanned.
Years ago, I tried to persuade some local Black churches and ethic-focused organizations to join !GNUsocial and #Diaspora, but was unsuccessful. I think they all joined #Facebook, where their posts are hidden by the algorithms.
♲ @AlexVoss@fosstodon.org: Student of mine is conducting a survey on the barriers to uptake of alternative social media platforms. Your input would be much appreciated. Please boost.
I am conducting an anonymous survey for my MSc dissertation on the barriers to uptake of alternative social media platforms. If you're interested, please click the link below. Your input would be much appreciated!
The #SARS-CoV-2 virus, the #coronavirus that causes #COVID-19, blocks one arm of the body's anti-virus defenses, while stimulating the other. This unique behavior allows unhindered replication while causing inflamation.
@gargron wants to replace the current scope limited #Mastodon fake direct messages with real DMs, E2E encrypted using OLM (an implementation of Signal’s encryption). Good. People have sent personally identifying information and financial data across fake DMs, not aware that others could accidentally see the contents.
Bad: Scope limited posts are going away entirely. SLPs / SLMs are useful. They are just regular messages, but sent only to the @mentioned users. That could be the foundation for something like #Diaspora’s Aspects. If there’s no pretense that they are private, and they are treated and displayed like other posts, they are good.
The issue has always been the name. Pretending SLMs are DMs means people send each other private information. I don’t believe any instance admins would intentionally read them or misuse information in such posts, but having that information in your database could be bad news when “John Q Cracker” breaks into the server.
https://github.com/friendica/friendica/issues/8642 #Friendica Someone that is familiar with #Diaspora is writing a new socnet based on #ActivityPub, wishes to change other #Fediverse software to follow Diaspora's model (viewer's server hijacks hashtags so the #hashtag search points to the viewer's home server, not the original poster's home server). The model that has been followed by almost all federated socnets for over a decade is that hashtag search links are inserted by the poster's server and point back there.
IMO, a remote server changing the links is sketchy as heck*, but if they added local hashtag links in a separate area outside the post itself, that's acceptable. Or if they followed the #Pump.io idea of keeping hashtags completely separate from the basic server, then an external server (e.g. ragtag\.io) would be called to index and link the tag during the posting process, and searches would be performed based on results from the tag server.
Anyway, I can't be bothered logging into Github to comment, but maybe @heluecht and other Friendica devs will see this and take this into consideration.
* Remote servers editing the contents of one's posts is about as sketchy as it gets. There are rare occasions where that may be acceptable (i.e., to insert NSFW tags / image hiding on posts from instances where untagged NSFW content originates), but editing content to hijack hashtag search is about as questionable as one could get.
@simsa03 That's for my account on the #Diaspora network, where most of my real contacts have left years ago, leaving dozens of spammy newsbots squatting on my subscribed hashtags and flooding out real people.
(I'm using "ignore this poster" to manage the most frequent posting bots. They seem to make hashtags useless, because they pollute the stream with peripherally-connected junk articles.)
Under marked otherwise, all posts from this account are #CC#BYSA 4.0. Unless I send a DM, I want all my posts publicly visible, to any web browser, and any other user app or archival/ research system that speaks #ActivityPub (and ideally #Diaspora and #Zot too). I'm happy for them to be indexed by any search system and included in any relevant search. That's why I publish them on the web with Mastodon. When I want to have private discussion, I use DMs. One day the AP-verse will do this better.
@fedilab awesome. Being able to use both #Diaspora and an AP-compatible account within the same client would make me much more likely to use my D* account (which I haven't for ages TBH) @FiXato
@jcgruenhage > that's a lot better than having all conferencing on the whole network go through the central jitsi instance.
True, but not as good as having all the conferencing going through the client apps (as Jami does), with no dependence on servers. Also, as with the attempt to shoehorn #Jabber chat into #Diaspora, it makes hosting a Matrix server even more of a headache if you also have to stand up a Jitsi Meet stack and duct tape the two together.
Over and over I come across people saying that #Diaspora is "like FB". It really isn't. It's more like a federated version of G+. The main thing that makes the UI different from Titter or Mastodon is that by default it doesn't have a character limit, and as well as as public or private, posts can be sent only to a group of users defined by the sender.
@dredmorbius same :) I currently blog on an ancient Wordpress fork hosted by #CoActivate.org, but I'm keen to transition to something that interacts with the #fediverse, as well as publishing to the web. I've considered using apps that allow long form posts and speak a number of federation standards. Eg #Friendica (#OStatus, #Diaspora, #ActivityPub) or #Hubzilla (all those plus #Zot). I'm also watching the tech deployed for @blog (WP + plugins).