I just pushed version 2.3.0 of #Friendica Directory.
This release notably adds back support for the zrl query parameter that allows a directory user coming from a Friendica node to be automatically authenticated with remote nodes to make remote follow seamless.
This was a legacy directory feature that had been missing from the new directory ever since it's been initially released.
As usual, please report bugs and feature requests at github.com/friendica/friendica… where I'll safely ignore them for several months before suddenly take care of one of them during an all-nighter coding frenzy!
♲ @heluecht@twitter.com: In #Friendica haben wir die Tage für die kommende Version den Begriff der "Blacklist" durch einen neutralen Begriff ersetzt. Die Benutzung solcher Begriffe geschieht häufig, ohne über die Bedeutung nachzudenken. www.golem.de/news/black-lives-…
♲ @clacke@libranet.de: Finally, thank you to @Mike Macgirvin , @Hypolite Petovan , @Michael Vogel , @Tobias and others who created and maintained Friendica. It was there not long after it all began, and it has been steadfast ever since.
As others waned and waxed, Friendica moved on in its own pace, smoothing out wrinkles, tying things together, offering a different view, a slower view of the Fediverse than the microbloggier nodes.
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.
Back in late 2016 I'm glad the #Fediverse (comprising OStatus/ActivityPub-compatible social networks) and the #Federation (comprising Diaspora-compatible social networks) welcomed me when my #Facebook account was frozen and I was (and still am) too stubborn to give in to their demand to give me back access to it.
I've been contributing to #Friendica ever since, mostly through dogfooding through my own single-user node.
Happy Birthday to us and thank you to everyone who has contributed or still is contributing to this mind-boggling common project.
I'm looking for either a high-level explanation of this system that doesn't seem to rely on the usual "max_id"/'since_id" boundaries, or an actual implementation of it.
Just tried out the AndStatus app on Android. I successfully added accounts for pump.io and Titter, but adding this Mastodon account failed. I tried adding a Friendica account as a GNU social account, since it supports OStatus and I can't see any other way to do it, but that failed. I don't think I have a GNU social account since the Quitter. sites went down, but I'll have to check and maybe set up a new one for testing purposes.
@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
There are different approaches to private social messaging, even within the fediverse. Diaspora was one of the earlier examples, allowing users to give access permission to only one person (like a #DM), some people (like group DMs), a group of people defined by the posting user ("aspects"), or everyone (public). #Friendica does private messages with #DFRN and Dispora, and maybe now AP? Hubzilla and now Zap have been doing federation of private content with Zot, later AP. Consensus is emerging.
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?
Thanks Aaron, I appreciate the compliment, however I can't expect all my contacts on Twitter (this was cross-posted from over there) to move to #Friendica. #Mastodon would still be a nice easier change for them.
Finally flipped the switch! ActivityPub support is very alpha still but far enough that dogfooding is becoming the only efficient way forward.
Plus it's my birthday, so let this be a present to myself, after so much work to make this little project of mine multi-protocol, joining #Friendica and #Hubzilla in having the largest reach in the #Fediverse ;)
The account @jaywink@diaspodon.fr will not get new posts at some point in the future after a few announcements to followers - follow me here! Thanks @{https://diaspodon.fr/@dada} for offering me a home while building my AP support <3