One drawback of POSSE is that you’re bolstering the value of the silos. Instagram grows more powerful with your pictures on it and GitHub thrives on your repos.
Sandra, I'm really glad I had the opportunity to catch your review, or rather, observation of POSSE, especially the long term ramifications from the PoV of #DeSoc.
For quite some time now, I've been advocating for something that describes a not so dissimilar modus operandi for extricating subjugated chattel from that of the #Borg_Collective.
POSSE has merit, being a partial design for disrupting the deprecated monolithic silos, but IMO actually falls short by only seeking to coexist with it, instead of completely obviating them.
As a dedicated FOSS and Privacy Advocate, here's my take on how we can follow a best practices modus operandi, achieving what can eventually relegate today's monolithic silos into the marginalized zone, sending them into the abyss of downtrodden insignificance.
The model can work from any Fediverse platform, but platforms that support a rich feature set with longform authoring capabilities work best, having the greatest impact. For those stuck using masto for the time being, their impact will be less dramatic, but nonetheless still valid.
The model I've been advocating goes like this:
) Create original content on Fediverse enabled properties you own, or cite (link to) content NOT residing in the deprecated silo space (Twitter, Medium, TikTok, InstaSPAM, YouTube, Faceplant, Reddit, Linkedin, Etc.). You can do this from pretty much any Fediverse platform - even masto, with its paltry 500 character limit. A paragraph or so as a rule of thumb, just a teaser/headline to create interest for the reader to follow the link.
) Optional: For added impact and if you have any, from your traditional silo account(s), as well as from less capable clones like masto, offer up a teaser, perhaps a paragraph or so, with a link to the URL of this original content.
) If you're merely pointing to an article or resource created by someone else that exists independently, that's it. Well done! If you created your original content in long form on a more capable Fediverse platform than masto - there are many excellent Fediverse platforms for doing this. A few of those are:
) Endeavor to never publish any actual content (articles, news, photos, videos) on platforms in the deprecated monolithic silo space. Instead, it is preferable to publish your photos, videos on demand, and textual content on a Fediverse Platform well suited to this. i.e., PeerTube for VoDs, Pixelfed for images, and one or more of the platforms mentioned above for textual or multimedia based content such as news articles, HowTo's, tutorials, recipes, Etc.
) Occasionally, you may find it necessary to link to content in the deprecated silo space - a video on YouTube, for example. You may be able to clone videos (depending on licensing) to a PeerTube server, but if not, then make sure you sanitize those videos by using tools such as Invidious that shield the viewer from tracking and other privacy disrespecting constructs built into those silo systems.
The philosophy here is to ensure that anything posted into the deprecated monolithic silo space entreats the reader/viewer to leave that space in order to consume the content.
This practice insures that the consumer of that information does so in a protected, privacy respecting place, presumably built on FOSS, and in the Fediverse. It further serves to familiarize the consumer in an easy and unassuming way, with Fediverse platforms that do not track them or mine their privacy.
For the Fedizen however, it provides a one way transit - anyone seeing a teaser/headline/intro on say, Twitter or Faceplant, is immediately catapulted away from those denizens of commodification that packages and inventories the consumer as the product for sale, depriving those platforms of the necessary revenue that sustains them - death by atrophe. No blissful coexistence, every single post inside the deprecated monolithic silo space is in fact an egress point bringing the consumer into a free and privacy respecting environment.
Obviously, an article on the New York Times website isn't ideal, but it isn't strictly one of the monolithic silo systems listed above either. In this case specifically, it's a walled garden however, so you're directing the consumer to a place where they'll be privacy mined anyway, which offers three other possibilities:
You can, and should unless you feel you absolutely must, elect not to send someone to that resource
You can, under certain circumstances, copy that data verbatim elsewhere and provide a link to that place where you copied the data.
You can also probably check with the AP, since we're talking about a newspaper outlet, most of which actually pull their news from the Associated Press and other similar networks that provide free access, which you can link to instead.
There's simply no way to completely ensure being so mindful of your consumers without precluding yourself from linking to some forms of interesting content - but the point here is that almost without exception, you're not sending anyone into the deprecated monolithic silo space - you're sending them into the Fediverse, where they'll begin to become comfortable with, eventually creating their own accounts here.
I recently had some discussions with a few folks who completely turned their back on things like Twitter, which is good because it is one of those social networking systems that engages in tracking and privacy mining. Those individuals have made it easy for themselves by simply putting the existence of those privacy disrespecting resources completely outside the real of consideration - it's not like anyone is going to suffer because they didn't visit Faceplant. They may suffer a bit of withdrawals, but bear the following in mind:
There are liquor stores on virtually every corner in the real world. They sell booze at liquor stores. An alcoholic must come to terms with this and learn to live with this fact, making a conscious choice to buy, or not to buy booze in those stores, or even go outside where the temptation is even greater.
That's not the greatest metaphor I know, or maybe I just didn't deliver it well. Either way, I hope that in understanding this death by atrittion model, that people can make better informed decisions about privacy for themselves and others.
I'd love to hear your comments and thoughts on the matter, and any tools that help assist folks in addressing privacy concerns. Please feel free to share this by boosting to raise awareness within the Fediverse (and beyond) of all the excellent platforms available to everyone in the Fediverse. I realize I left out large sectors of the Fediverse that can be factored into this formula - the link aggregators and forums like #NodeBB, #Lemmy, #Kbin, #Mbin, #Discourse, and more. I didn't even directly address the purpose built single user instance platforms. Maybe we can give them some coverage in a later edition :)
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.
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.
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.
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)
Come say hi at the Mastodon stand in #fosdem ! We are in the basement of Building H
I will be there all afternoon, with some nice Elephant-themed merch! Mugs will probably be out of stock in the next hour, dont wait if you want one 👀
@renchap I got my #mastodon muck! Nice talk with @Gargron@andypiper about activitypub and integration with other protocols and software like #mbin and ap groups.
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.
Ok now I’m a little sad. I just recently found the Artifact app, and now it’s shutting down. What app do you all use to read various types of news on all kinds of topics?
Could someone recommend a working and well-maintained #kbin or #mbin instance to me? I deleted my Lemmy account because of reasons and I thought kbin looked pretty nice, so I signed up to kbin.cafe only to realise that the last few federated posts are from 2+ weeks ago, lol.
An update regarding the future of m/AskKbin (heading towards Mbin)
Hello everyone!...
I think we should slightly rethink how login works on most Fediverse apps (Mastodon, Lemmy, but not only)
A while ago I posted a thread back on the...