tallship

mikedev, 17 days ago

My experience is that state actors won't even try to decrypt your communications. That's old school - and a horribly inefficient use of resources. They'll come after you with a keylogger or manufactured legal nightmares or torture - to either or both sides of the communication; depending on the perceived value of your secret.

It all comes down to 4 fundamental questions:

• What is the value of your secret to you
• What resources do you have available to protect it
• What is the perceived value of your secret to your adversary
• What resources do they have available to divulge it

mima, 19 days ago

@youronlyone I don't think they can force the rest of fedi to implement controls on quotes. I do think it's a bad idea to control who can quote post no matter if it's Mastodon or Threads doing it (or even Misskey). But it's just going to be circumvented/ignored easily, like how Masto's "opt-in search" has no effect on Misskey's note search per user.

What fedi really should focus on is controlling replies. And while I have reservations on federating that control, I do believe it's important to give users the power to control how their posts look like in their own instances without having admin privileges. Because it's a (micro)blog.

@vetehinen @tchambers @tokyo_0

tallship, 20 days ago

@darnell I'm sure he's got a hot little yummy Jessica Hahn of his own. At least he doesn't look like that little troll - Jim Baker, or perhaps worse, Sam Kinison, who really sent her onto page 6.

It is page six over there on the other side of the pond, isn't it?

Anyway, I thought she was fantastic in Sam's video cover of "Wild Thing":

yewtu.be/watch?v=3wAm2HAx7i0

A bit of trivia (there's a lot for this vid): Billy idol almost got his ass kicked for dribbling his spit on all the other rockers from that balcony ;)

tallship, 24 days ago

@Sandra

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:

1. ) 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.
2. ) 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.
3. ) 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:

• Streams
• Mitra
• Misskey, Iceshrimp, Cherrypick, Firefish, and Others
• Pleroma, SoapBox, and Akkoma
• Friendica
• Hubzilla
• WriteFreely
• WordPress (with the ActivityPub plugin)
• Ghost (reportedly coming soon)
• GoToSocial
• Socialhome

4. ) 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.
5. ) 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 :)

All the best!

#tallship

⛵

.

tallship, 25 days ago

@jupiter_rowland @danie10 @thenexusofprivacy @mikedev

Okay first I should state that I've never actually said that masto isn't a solid and capable platform. It is, but at a severe cost - the design of masto, notwithstanding the insistence on maintaining a historically lackluster feature set when compared with almost any other Fediverse software, is such that it really isn't built for #DeSoc - it really strives to be some sort of unachievable ideal for the monolithic silo model.

No one but me seems to site this nowadays, but masto doesn't even really shine with respect to cost in terms of system resources and stability until you approach the 20,000 user account mark. What? Why would you do that? Back when these stats were being bandied about, Pleroma was showcasing its new #Gopher protocol (browsing) support, and reminding people that it felt perfectly at home on an #rPi. No such claim was ever made for masto, lolz. That doesn't mean that the other platforms aren't just as capable of scaling vertically... but... why? Who's going to foot the bill? Who's going to manage all of those un-vetted people creating accounts on your machines? Why would someone bother with that in the first place?

Community? Nope - there's no sense of community on masto servers, and I'll get to that later. Because you want to create your own private Idaho? Probably. mastodon.social is one of, if not the, largest deprecated monolithic silos existing in the Fediverse today. Why? What possible benefit could be derived by driving a million people into a single funnel under the auspices of telling them that they're escaping that very same model? It's ludicrous.

No matter what happens in the short term, Eugen is assured of his parachute and comfortable retirement fund, except for the part where he forgot to have his new significant other sign a pre-nup - that might dash his net worth later, but that's another consideration entirely. I hope his marriage is actually a long and fruitful one that lasts forever, he's not a bad guy, he's just been courted and corrupted by the "Ooh shiney" phenomenon of financial entrapments that come with relative success in the media and pop culture.

The reason masto needs to be hard forked (several times, IMO) is not to create a better masto that will lend itself to DeSoc, #smolweb, and self-hosting on people's home networks, but rather, to further dilute the trademark, and especially the brand, effectively killing it if possible, supplanting it with Fediverse instead. People like to bounce around that term inclusivity, well, this accomplishes that.

Forks of masto aren't going to create a better masto. No way. Sure, some improvements on this one, other features on that one, but dilution of the brand until it is only as significant as any other deserving Fediverse platform is and should be the ultimate goal. It's not well suited, architecturally for horizontal scaling anyway, unless you don't mind throwing all those system resources at it that could better serve you elsewhere with something like #GoToSocial or one of the #Misskey and #Pleroma family fork members.

True leaders in the Fediverse will initially be those platforms that have planned ahead and accommodate other DeSoc protocols, arguably Fediverse protocols, at this time, #Diaspora, #OStatus, #Nomad, #Zot, and even others that some #Fedizens turn their noses up at, like #nostr and #Bluesky's #ATP. #ActivityPub is NOT the end-all, be-all for the future. It is the golden calf of today, and just as others that have come before, it will morph and evolve or be obviated by others that will be plugged into the platforms currently running it - #Friendica, #Hubzilla, and Streams are prime examples of this, and Friendica especially, considering it's the only extant original member of the Fediverse for all intents and purposes. One could say that Friendica is the #Slackware of the Fediverse, lolz.

With respect to Friendica in particular, but also Hubzilla and others that have arrived at this obvious conclusion, ActivityPub is merely the major vehicle by which it communicates with other decentralized social communications systems on the Internet. I don't think it has ever lost sight of that, like another of its contemporaries, #GNU_Social did.

Hemming large masses of people onto a single (and at this time appearing to be) and open walled garden has the immediate effect of control over large swaths of population - you can say this, but not that. You can think this, but not that. You can be this, but not that. You can believe this, but not that - under penalty of excommunication.

In reality, we don't have strong friendships with our neighbors - that's why we have fences. We wave to them and say hi, call the cops when their on vacation and see someone suspicious lurking about their property. That's about the extent of being a neighbor. We invite our friends and coworkers over for BBQ's and to swim in our pools, not so much our neighbors.

The current masto social architecture is the antithesis of that, and so is it's physical architecture - put all the lobsters in the same pot of boiling water. Turn on and off their ability to speak all at once. Force them en masse to endure advertising blitzes (Oh, mark my word that's coming) decided upon by the server admin. It's like Baba O'Reilly by The Who - "Meet the new boss, Same as the old boss".

That's not the promise of Fediverse. it's the antonym.

masto also hinders innovation, attempting to define, dictate even, what should and should not be available - Nomadic identity is but one emerging facet of what is fracturing the masto monopolistic initiative - and that's a good thing, because with the help of FEPs, already, others are adopting various cooperative models for this as well, but discussing that now, and here, at this time, is more of a tangent so I'll get back to the point.

Jupiter:
> That's why people still fork Mastodon to add features that are available just about everywhere else.

Indeed it is, and why it has managed to enjoy a reasonable level of notoriety. There's also the wholly undeserved notion of community that actually, in direct opposition to, masto has continually sought to break and in a very big way, break.

There are certainly platforms (mostly forumware) that curate a sense of community, but those days are largely past. Whether it was #gplus, #Myspace, #Faceplant, #InstaSPAM, or #Twitter; because just as it is in real life, #COMMUNITY is that which you define for yourself through your connections - your follows and those who choose to follow your account. The biggest failures in the Fediverse that I've personally observed are those that seek to localize, geographically or by shared interest, a monolithic ivory tower of sameness and similarity amongst people.

I felt so awful for one guy who, so enthusiastically upon discovering the Fediverse, started registering domain names corresponding to several states, thinking that he would be successful in launching a geographically oriented family of masto based servers tending to the shared interests of people by offering them a place to congregate. He quickly discovered the fatal flaw in his model, but was stuck with hefty data center bills to maintain all these masto servers that were largely uninhabited.

Trying to get rid of your masto subscribers when you figure out that you need to egress from it is not an easy task without disenfranchising your user base. I know, because a few years back, not long after @Gled archived his #mastodo fork and urged everyone to adopt Pleroma instead, I face the daunting task of trying to convince my user base to migrate elsewhere - it took more than a year to accomplish!

Danie:
> thing is though there are also many existing alternatives to Mastodon already on the Fediverse, so why fork it?

In a nutshell, because it serves to, at the very least, dilute the masto brand, and more likely kill it. It has served its purpose and now that it has been exposed as a vehicle antithetical to #DeSoc, it's time to deprecate it.

My introduction to the #Fediverse occurred when I stumbled upon an earlier incarnation of #Friendica, started looking at #Red_Matrix, and discovered that the monolithic model, if not having been shown the door, had at least been handed its hat.

The problem at that time, was the effect of Prettiness, and of course, UX. Friendica wasn't too bad in that latter sense, when compared to that of Faceplant, but it sure didn't even come close to being as pretty as Faceplant - or even Myspace, which had only recently fallen into the abyss. That's changed A LOT, even in just the past year, with respect to Friendica and Hubzilla - they're much more intuitive for a layperson parachuting to the ground after jumping from the cesspit over at Faceplant.

I think that more than anything, not being pretty enough for the subjugated chattel coming from Twitter and Faceplant, was the most difficult thing for onboarders to embrace. Mike placed all of his focus on functionality and forward thinking vision with respect to what these and later efforts could provide the masses, but the "prettification" was left to others who didn't step up for the challenge for many years. I'm all for features six-ways to Sunday, but I also feel that many things need to be hidden from the landing page a new user sees upon account creation - the very basics they expect should be there, akin to those available in the deprecated monolithic space; users expect this, but they don't yet know they not only want, but really need all of these other feature sets too, yet some things should left, IMO, to be discovered later by the user.

And in my conversations years ago with Mike, I gleaned as much from him: "Here's this really bitchen gift for the masses, it does all this kewl stuff, now I leave it up to others to make it pretty" (and with a sense of coherency that these former subjugated chattel can initially get their heads around). Putting all that stuff right in their face was awe inspiring, but foreboding at the same time for many.

Well, finally, people are making it pretty :) And they're also moving much of the overwhelming busy-ness elsewhere in the UI. As a result, there's been an explosion of adoption - not even primarily from former masto folks either.

I'd like to touch on the notion of community one more time in closing. It might be convenient for n00bie onboarders to glean a bit about how a particular platform functions, but just like in your own neighborhood where you live, you make friends elsewhere mostly - at work, at functions of the hobbies you engage in, with friends you meet at the grocery store or libraries, and the beaches or on hiking or 4x4 weekend excursions. It's the same way in the Fediverse, you make your friends through connections here and there through people you discover along the way, and 99% of them ARE NOT on your particular server instance.

They don't need to be either, because this is the Fediverse :)

#tallship #FOSS

⛵

.

reidrac, 22 days ago

@tallship makes me wonder who approved this and what was the level of understanding of it 😂