Et pour avoir accès à toute les fonctionalités, on a souvent recours au multicompte.
Pourquoi ne pas avoir une seule appli qui crée un compte maitre sur notre ordi et syncronise tes posts, tes abonnements, tes filtres ? Si l'instance tombe en raison de son budget, problème technique on conserverait nos données et on pourrait migrer facilement.
Cette meme appli pourrait gérer les alias. Et également cross-signer notre identité sur les appareils utilisés ?
Qu'en pensez-vous ? Ya des projets en ce sens ? Quel en serait le risque ou les limites ?
Pour moi l'oblectif est de faciliter la sauvegarde et l'exportation des données.
Pour le coup activitypods.org a l’air pas mal quand même, au-delà de la blague
What is the main shortcoming of ActivityPub ?
ActivityPub wants to make it possible to create decentralized apps. But to post videos, you need an account on a PeerTube instance. And to post images, you need an account on a PixelFed instance. You must thus handle multiple accounts, with their profile, list of followers, etc.
How does ActivityPods solve this shortcoming ?
With ActivityPods, you have only one profile, one outbox, one inbox and one list of followers - all in a single place. Applications connect to your Pod to post activities, read the inbox and fetch data. And of course they can connect to any existing fediverse application !
Have you even tried #Piefed? Piefed.social is:
"A lemmy/kbin clone written in Python with Flask.
-Clean, simple code that is easy to understand and contribute to. No fancy design patterns or algorithms.
-Easy setup, easy to manage - few dependencies and extra software required.
-AGPL.
-First class moderation tools."
It's actually really quite nice, and I don't hear much noise about it. Go give this project a look at https://piefed.social.
Over 8 months ago now, I started using the Fediverse, messing around with different instances.
I'm glad I've found a pretty good instance of Mastodon.social instead of using Lemmy, Kbin / Mbin or other things like PixelFed.
I'm not saying I'll not use these in the future, but I want a main account for the Fediverse to help bring family and friends in as well as learn the basics & complex parts of the fediverse.
@paarth I just added you to the list btw :). That was on my todo list of today haha. Well, the website is mentioning my domain (which is indeed still kbin.melroy.org). I'm planning to setup mbin.melroy.org, the problem is such a simple change is actually non-trivial in the a decentralized network, mbin.melroy.org will be seen as a completely new instance basically. You then need to create a new account, and start again from scratch. But I think it's better to do this ASAP now.
If you haven't heard, sadly, #ChirpSocial, one of the popular #ActivityPub “groups” platform, is shutting down “probably” on February 29th.
In an email they sent to admins, the owner and developer can no longer support https://chirp.social financially as they failed to find a new job after they were laid off by #Google last year.
This reminds us the importance of having a built-in groups feature, and one where the groups feature actually federates.
Back in 2008, when the #Fediverse was born, we did have a built-in federated groups in #Laconica / #StatusNet (today known as #GNUsocial). We used bang (!) instead of at (@). A built-in groups feature is more stable as established instances can host them.
Today, we have #Friendica and #Hubzilla (as well as #Streams-based instances) to fill in that, as groups is a built-in feature in those software products. It's just a matter of finding an instance that's open to hosting groups for any topic for the ActivityPub protocol.
That said, any Friendica, Hubzilla, Streams-based instances you suggest for groups?
Testing out #mbin because I just couldn't stand the timeout errors on #kbin anymore. Does anyone know if mbin pulls in upline changes from kbin, or is it a hard fork at this point?
What it boils down to is having assigned yourself an ownership of the task way forward, resulting in a figurative cookie being licked. Of course, now nobody wants to touch this task/cookie with a 10 m foot pole, because any more collaboration from other parties is essentially obstructed.
I am guilty of trapping myself in a few such situations: job, making and stopping on 90% for a new logo for #Mbin, etc. I wanna learn from these mistakes and give as less cues of ownership as possible. There really isn't much to do to be excellent to each other, unlike to be some hotshot contributor. But as sayings go: the genius is in simple, and one should find beauty in simple.
I already was practicing "non-licking" with licenses on my works: mark all that I want others to move on without hesitation public domain. For logos, I still prefer CC-BY, but I might review some of my reservations (e.g. in lieu of trademark) one day.
Documentation? Absolutely CC0! Why would I need any provenance aside from git logs for some impartial or technical writing?
Overall, just avoiding CC-BY-SA for reusable assets. Saying NO to NoDerivatives, NonCommercial and other shenanigans - they are simply distastefull licenses.
Die ursprünglichen #Forum'e im #Internet gelten schon länger als #veraltet und die scheinbare alternative Lösung #Reddit hat nun #KI integriert und schnuppern die #User aus. Die wahre #Alternative finden wir wieder im Fediverse und sind ua #kbin / #Mbin so wie #Lemmy. Ja das #Fediverse ist viel mehr als nur #Mastodon und Co und kommuniziert nicht nur auf einem Server, sondern in der #Community (ihr kennt es evt schon)
It’s crazy how much of the comments about #Subllinks on the threadiverse are mad that the author is using #Java or just complaining that they chose to build another implementation.
Most of it seems to be #Lemmy users who think that #kbin, #mbin, #piefed, etc don’t exist and no other federated link aggregator should exist.