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 :)
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.
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?
Mbin is a decentralized content aggregator, voting, discussion and microblogging platform running on the fediverse network. It can communicate with many other ActivityPub services, including Kbin, Mastodon, Lemmy, Pleroma, Peertube. It is an open source alternative to other link aggregator services like Reddit. The initiative...
You can try out #Mbin, it's #Kbin fork, it has issues too, but at leave there's multiple devs and all of them are active.(And anyone can become a dev, and actually send pull requests that will get merged)
Flipboard has recently begun federation, starting with 25 accounts. These accounts can be viewed from Kbin with their posts showing up as microblog posts....
Given this is a software-the-instance-is-running request rather than an instance request as such, you might be better off posting on the (centralized 😅) mbin repo or perhaps asking about it on the mbin Matrix if they accept that kind of thing there.
Not just speaking technically but economically. As user number mount up their post is just going to add up. I know instaces may distribute user, but server space isn’t going to go down for anyone. It just seems like built to fall.
theres a great crew in the devs/other admins of mbin on matrix, and i am always happy to help if you ever decide to give it a go.
you can probably do it very cheaply. i went the most expensive route, and im payin ~$1.00/day. not using aws, you could maybe that down to $0.25
one thing to keep in mind, once your instance is up with a domain name (myinstance.mydomain.com) it cant really be changed.
im an old sysadmin, i hate social media... i just like looking at the numbers..keeping things running. my hate for the new reddit has overtaken my hate for social media.
#Flathub deserves a set of more performant and native applications than being attributed to a page in #Discord's playbook. Stay with me: are we really just going to blindly accept #privacy flaws of this messenger and promote it at the same time?
The fact that it only has got to the head of Discord it's long overdue to verify this popular #Flatpak distribution, I think, is worth a comment on itself, but I'll digress. It is nice that #OpenSource enthusiasts made arrangements for this verification and I have zero disagreements with the result. I'm just stupified that, in all this effort, Discord is treated like some spoon-fed royal baby - at least, according to reactions I see.
So, what was it... Flathub already had a library of nice actively developed #FOSS#applications before these news. I don't see the point in exaggerating the scales on some centralized chat thingabob with well-known #ToS and #telemetry problems, that's all. Thank you for visiting my #dRBBoard talk! ❤
Mbin is alive and kicking! A community-focused fork of Kbin, which has tons of improvements, features and bug fixes. Mbin is a federated content aggregator, voting, discussion and microblogging platform.
Feel free to host your own instance on the fediverse! If you are already running Kbin; migrating is straightforward towards Mbin and experience the benefits yourself.
@kreynen We try indeed to keep the issue list as short as possible atm. We are aware of many bugs and improvement proposals, including the one you mentioned. Kbin has like 480+ issues, which isn't helpful at all for the community. At this stage of development PRs are more helpful if you can imagine.
That all being said, feel free to discuss this in the matrix community rooms: https://matrix.to/#/#mbin:melroy.org We can discuss it there, we could even start a poll for it.
great questions! i think the good thing (or maybe bad, depends on who you ask i suppose...) is there isn't one person or owner of mbin. as of today, there are 10 owners/members of the project with merge privileges on the repo; however, we each need to get approval from at least 1 other project owner to "merge it" into the "main" branch.
github and the associated mbin matrix rooms are where most of the discussion about features and direction takes place among contributors, but i will try to make it a point to keep everyone here informed when a major change take place. right now we're trying to catch-up on the backlog of pull requests and enhancements that have been stagnating for months over in the kbin repo. @melroy is also pretty good about keeping the masses up-to-date on recent events if you want to follow him as well.
finally, one way to look at mbin is viewing it as a superset of kbin, that is, unless the kbin codebase changes dramatically or some other crazy thing happens like a change in license (which wouldn't be a good thing for kbin), it should be relatively easy to port over upstream changes from kbin that we want to see in mbin. my sneaking suspicion is that mbin will quickly surpass kbin in every way since we don't have a massive money pit like kbin.social holding us back, the focus is purely on the development of the code base and listening to community feedback/inputs. :-)
@reiver@weex follow up. The fork is in place and it's seem like a success already. This model based on trust is basically an experiment, let's see how it evolves. See: https://github.com/MbinOrg/mbin
Whenever you visit #dRBB, you will see slight changes in the #Kbin header. I moved instance's home link to the right to prevent any accidental exits. And there is now a solid icon just in case.
If you have any suggestions, feel free to leave a reply.
After some work by contributors of #Mbin to introduce an indication of magazine in the top bar, I'm happy to say that it's more clear now WHERE on the site you happen to be. Happily, my little CSS trick has adapted to it quickly, but I made #dRBB icon smaller to prevent it stealing space.
Again, thanks to the Mbin contributors! There is a lot of work done already, and I feel confident with this fork of #Kbin to improve one of the store fronts of Fediverse.
Terms "thread" and "post" are often used interchangeably on #Kbin and across the #Fediverse, but, as a reader, you still would like to have some guideline.
Threads are a primary tool of presenting information on Kbin. Think of a thread as a magazine clipping: you cut it out and proudly place on your wall. All you see from afar is a title and some preview image (if any). As you skim over the magazine and click on one such clipping, the entire thread opens before you, now including comments.
Posts are a secondary thing on Kbin. But don't let it fool you: before long, you'll have a microblog of things to share. Yes, posts are usually viewed in the context of Microblog, the section adjacent to Threads. One can call post a micro-thread, of sorts. Unlike your run-of-the-mill thread, a post can present text without any pretence. Reader scrolls through Microblog and they can see contents/replies right away. While lengthy discussions may be collapsed to 1-2 recent replies, it's made so to let other posts shine. As a reader, you don't have to change pages to expand the post.
Use Threads to present a pertinent material.
Use Microblog to share any updates, tips and little stories.
Has anyone found a clever way to host 2 separate activotypub servers under the same domain name so that they share accounts, e.g. I could log into an Mbin instance and a Mastodon instance with the same user credentials. Or is that not possible?
Mbin is a fork of kbin: a decentralized content aggregator running on the Fediverse network (lemmy.ml)
Mbin is a decentralized content aggregator, voting, discussion and microblogging platform running on the fediverse network. It can communicate with many other ActivityPub services, including Kbin, Mastodon, Lemmy, Pleroma, Peertube. It is an open source alternative to other link aggregator services like Reddit. The initiative...
Do any of you have that one service that just breaks constantly? I'd love to love Nextcloud, but it sure makes that difficult at times (lemmy.world)
How do we feel about Flipboard federating?
Flipboard has recently begun federation, starting with 25 accounts. These accounts can be viewed from Kbin with their posts showing up as microblog posts....
Seeing lots of posts from centralized instances (e.g. lemmy.world) (fedia.io)
I have ensured that I am not subscribed to any mags on centralized instances. E.g....
Do you think lemmy will sustain scalability?
Not just speaking technically but economically. As user number mount up their post is just going to add up. I know instaces may distribute user, but server space isn’t going to go down for anyone. It just seems like built to fall.
[NEWS] kbin.run has completed migration to mbin codebase (kbin.run)
Hi everyone,...