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.
@aktivismoEstasMiaLuo 1) This doesn't answer the question, which is how to use a free code front-end to read content others have put in the FB silo.
2) It really isn't. All #Diaspora can do is public and private posts, and photo uploads. #Friendica, #Hubzilla, or #Zap would be better recommendations for replacing the features people use FB for. They have events calendars and groups, and all federate over #ActivityPub, which Diaspora devs are still refusing to even consider. @paulakreuzer
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.
@tk I liked and was excited about #GPlus when it first came out ( because after all, it was mostly just a #Diaspora clone ). But then came the nymwars and trying to force it down people's throats. And mingling GPlus contacts with my Android contacts ... which was the final straw for me.
@stevenroose I want to say "have you actually used #Diaspora?" then caught myself and realized that could sound more aggressive than intended ;) But that's something people are always saying, and it really isn't true. Diaspora is pretty similar to Friendica, a federated blogging platform with a few options for posting to public/ private/ select subset of friends. It doesn't have any of the feature that make FB distinct; live chat, events invites/ RSVPs, etc.
When I mark a post as "public" on #Friendica or #Diaspora, is it only available to other users logged into federated web apps using compatible protocols, or can it be visited by any web user? If it's the latter, what's the URL for visiting a public feed on these platforms?
Just checking #twitter notifications before work and it's taking far too long because the Twitter UI/UX is utter crap compared to #diaspora#pleroma and #mastodon (no filter options at all!)
@dude Hmm. This complicates the plan to add a #Pleroma instance for !FNetworks before we upgrade to !gnusocial 2.0. I'm not really interested in hosting incompatible services (one reason why planned #Diaspora and #Pump.io instances were abandoned).
@framasky just upgraded #framasphere to debian buster. With that, we now are running postgresql 11 instead of 9.6. Performance improvements can notably be felt, even if the /stream can still take several seconds to load.
I'm proposing a new version of a metadata document specification for servers in the #federated#web. This aims to collect the good and avoid the bad of the previous iterations, and to be flexible enough for a large part of the federated web to implement it.
Comments very much welcome, especially from #developers working on the federated web.