This noob is testing the interconnectivity of the #Fediverse:
The word out there on the Fediverse make it seem as if all the different tools (Mastdn/P-tube/Lemmy/etc.) can interact with one another. But this is not the case, as some work both ways, whilst others only one way, or at all.
a) Using #Bridgyfed, to test between AT ( #BlueSky ) & AP protocols (Mastodon, etc.)
b) Meta's #Threads for testing with Mastodon.
c) Starting to test #Nostr with its peer-to-peer network.
TL;DR:
The #Fediverse holds a lot of promise, but it the ideal level of interconnectivity isn't there yet. (And yes, not all of them need to be able to connect and interact on the same level of details as with the others, as they are different tools.)
For our first article on #Nostr, we wrote a crash course guide on the protocol and the network, along with what it is, how it works, and how you can get started.
#JackDorsey verse 5 millions de $ pour soutenir le développement du réseau social décentralisé #nostr. Cela confirme qu'il le préfère à bluesky, dont il vient de quitter le comité de direction.
With major companies like Meta realizing the future potential of decentralized social media, connecting across protocols has never been more important.
#Nostr users can soon follow anyone on Threads via the Mostr bridge as Meta adds support for Activity Pub. This opens up a massive base of mainstream users, breaking down the #networkeffect barrier that new protocols struggle to overcome. This is hugely important for user retention.
Hopefully, once Threads users discover Nostr through our bridged interactions, they will realize what they're missing out on by staying under the control of Meta! #GrowNostr
Post from @rabble on why he's chosen to use #Nostr and not #ActivityPub and the #Fediverse. He makes some compelling points. Personally I am not too worried about the server admin parts of his argument (I have enough control, even if I don't control the server), but I agree that this isn't ideal:
Digging around in the #Fediverse (Looking for a good solution to host what amounts to a #PodCast) I found something that looks REALLY interesting. #Nostr . Looking into this now:
My 8th grade science teacher taught me the most important lesson I've ever learned: If you're doing something wrong, don't draw attention to yourself. It's not about getting away with breaking the rules. It's about presenting yourself in a way that only attracts the attention you want to get.
It's essentially the dark forest theory. By announcing your presence in a dark forest, you attract anything in your vicinity to interact with you, and if you can't defend yourself, you will be devoured.
It's the same on Nostr. By designing for self-sovereignty at the key-pair level, you allow each participant to project power on every other participant on an even playing field. And announcing your presence invites anyone who notices you to interact with you based on how you present yourself on your profile and in your notes.
You DO have power over what people send to you by building a profile that invites the kind of engagement you want to receive. If you do whatever you want without considering that, you're going to get engagement you don't like. Monsters exist in the forest, and you cannot reason with them.
A rant about social protocols Introduction
Recently, I read an article that talked about that someone, tried to do a new platform called “Content Nation”. This is a German platform that allows people to write content (to be honest, I don’t really know what it does.) and publish it. And recently, the creators tried to implement the ActivityPub protocol. They did so by using the official documentation provided by @w3c.
The problem was that the last time the official documentation was updated, was in 23 January 2018. So, this means that a lot of new standards that other platforms like Mastodon, Misskey, etc... use are not written in there. But this isn’t the fault of the service developers, this is the fault of the W3C that hasn’t been an update to the protocol officially to support the new standards in the industry such as Webfinger, SharedInbox, Privacy Scopes, and Opt-Out for Search…
The thing, is that this led to a lot of people thinking that this site was some kind of scraper and started making the crawler crash or, even worse, someone tried to load CP inside the platform. BlueSky
Recently, BlueSky opened its AT protocol for everyone to use and federate, due to this, there has been a bit of a discussion inside these platforms. This made me think, why did BlueSky feel the necessity to make another protocol? If there is one already, why do we need another one that competes, wasn’t the objective of protocols to allow interoperability?
So, I did a bit of digging and I found two things. The first one is that they wanted so solve a few things that AP does not support officially (here are the main points, not all of them):
Account portability. A person’s online identity should not be owned by corporations with no accountability to their users. With the AT Protocol, you can move your account from one provider to another without losing any of your data or social graph.
Algorithmic choice. Algorithms dictate what we see and who we can reach. We must have control over our algorithms if we're going to trust in our online spaces. The AT Protocol includes an open algorithms mode so users have more control over their experience.
A lot of these problems are already present on ActivityPub for a long time. The account portability of ActivityPub let’s say it’s not intuitive. You have to do a lot of things and even then, there are some things like the posts that you make or the favourites that don’t transfer (in the case of favourites you need to transfer them manually, the same for blocks and mutes).
Also, right now 99% if not all software that uses ActivityPub, does not have an algorithm that orders content for you to see, but shows you everything in chronological order (I don’t know if its intentional or if it’s a limit of AP) and the only thing you have to discover topics is trough hashtags that maybe someone forgot to tag.
Furthermore, not to mention that on ActivityPub, you are at the mercy of the server moderators, so this means that if you know someone that is on an instance that is blocked by yours, you won’t be able to talk to them unless you change the instance, which in a way it’s not very decentralized. The other protocols
By doing research, I realized that there are a lot of other protocols (for example Nostr) that have its own implementation of things maybe there are some that are bridged and other not.
Such protocols have different features, for example Nostr allows you to suggest content edit to other people’s posts, move your content easily, etc. How can we solve this?
First, we have to know why all these other companies make their own. I must say, that most of them probably do because AP does not allow customization of posts or the adding of new features for everyone and the fact that it’s not been updated for 6 whole years makes matters worse.
What the developers want, is a protocol that lets them create wherever they want and add everything the want, for example the edit thing that I said the Nostr supports, the only way to add it to AP, would be or only on your software or find another software that is willing to implement that feature, the rest of the market is left behind as well as the users that depending on what it is, they don’t understand.
My solution to this problem would be to add some kind of per user plugin system directly to the AP that allows for devs to implement add-ons that do with the JSON strings that add buttons or scripts at least to send and receive data. As well as to add some kind of CSS support for the posts and profiles. Of course, the point of these is that if you make a platform, and you are the only one using these characteristics, well… but in case that everybody wants to use it and everybody makes their own plugins it would be chaos.
For this, the solution I proposed would be like something you add while the W3C updates the protocol to support a very popular feature. #socialprotocols#nostr#activitypub#W3C#ATprotocol#rant#blogpost#ContentNation