I love how @dansup is building a platform with @pixelfedlabs, and building a product of said platform with @pixelfed itself. I hope one day a platform that uses some incarnation of #ActivityPub, #Matrix, #Zot & legacy support for email for the ultimate decentralized, client-side encrypted, real time & social media communication tool
He started it!
"We have cross-posting tools for copying our posts from the #fediverse to Titter or vice-versa, and the same with the #IndieWeb (#BridgyFed). Maybe we could also have cross-posting tools for communicating between #ActivityPub and #XMPP (#Movim and #SalutAToi), #Diaspora, and #Zap, and any other federated social web servers that don't bridge to AP (eg any that get built using #Matrix)?"
what if mastodevs or activitypubdevs (or whoever) become the police of the internet? what if they are the ones who decide what counts as hate speech or fake news or whatever?
what is the point of decentralizing if the actual power becomes centralised anyway?
everybody is allowed to speak. we don't have to listen.
If I make a federated old-school forum bulletin board (no upvotes, time based bumps) over #ActivityPub, I am thinking of giving users, admins and mods complex tools to form "policies", which would be building blocks like "allow federation", "deny federation", "if user is", "if instance is", etc. The instance's applies first, then individual users'.
The instance policy would be public and applied first. The user's is private and applied second.
Diffu is a Free Software allowing authors to publish all kinds of texts or articles and to aggregate the reactions they generate on social networks, especially through #ActivityPub such as #Mastodon, #PeerTube, #Pleroma, #PixelFed, #Funkwhale, #Hubzilla, #GNUSocial ...
Diffu is a kind of free and federated alternative to #Medium or other applications that are not always easy to install.
ReToot are welcome 😉 !
One area of agreement I have with some of the folks who are not in favor of the #ActivityPub client to server protocol is that it's not just a small change from server to server (S2S) to Client to Server (C2S). There's a sizable chunk of the requirements that's just the C2S stuff.
I also agree that the C2S stuff should ideally have been in a separate document. There's a lot of overlap but having them both in the one spec makes it harder to read.
code here https://humungus.tedunangst.com/r/honk
Although, to be fair, the Diaspora work was *before* they documented the federation protocol. #ActivityPub is in *theory* documented. As the spec is more a framework, getting federation working requires a lot of reverse engineering to happen, though in theory it's "documented".
This is not all a bad thing. At least it leaves room for implementers.
Let's try this and see what happens:
#AskFedi What #ActivityPub #Fediverse platform do you think is best for a paradigm similar to #Facebook, but not necessarily with a similar UI? Intended use being to connect IRL friends and family together, share links and personal events to said friends without risk of privacy leak (posts being shared by others unless permitted).
Federated code hosting
Are you interested in #federated#codehosting? This term means a site like #GitHub, #GitLab, #Cogsor #Gitea- but instead of all servers being an individual part of the #web, they talk to each other just like servers in the #fediverse. Imagine being able to open issues, make pull requests and engage in discussion, to any other repository from your own personal code hosting server? https://friendica.feneas.org/display/76158462-195d-2249-980a-3f8962540417
Friendly neighborhood instance block notification + addressing Gab and free speech fetishists
Ah yes, and:
A GNU Social site that bills itself as offering "absolutely no censorship" except for illegal activity. The admin publicly states white supremacy is not "censored". I consider this a "Free speech fetishist" instance on the fediverse and have chosen to preemptively block it as it adds no value.
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.
Historically, Eugen has called it the Mastodon Network and has made no attempts to correct other people who misunderstand. The federative protocol underlying the Fediverse is owned by no one and shared by all.