social.coop

0 posts0 participants0 posts today

Jupiter Rowland@<a href="https://m.ocsf.in/@think" rel="nofollow noopener noreferrer" target="_blank">Kellam⚙️Бур</a> This may come as a surprise, but: <a href="https://joinfediverse.wiki/Nomadic_identity" rel="nofollow noopener noreferrer" target="_blank">Nomadic identity</a> is not an abstract concept or a science-fiction idea for the Fediverse. It is reality. It exists. Right now. In stable, daily-driver software that's federated with Mastodon. And it has been for over a decade. I'm literally replying to you here from a nomadic channel that simultaneously exists on two servers. Nomadic identity was invented by @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin 🖥️</a> (formerly American software developer of about half a century who has been living in rural Australia for decades now) in 2011 and first implemented in 2012. Almost four years before Mastodon was first launched. In 2010, he had invented the Facebook alternative <a href="https://joinfediverse.wiki/Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a>, originally named Mistpark and based on his own DFRN protocol. Over the months, he witnessed lots of privately operated public Friendica nodes shut down with or without an announcement and the users on these nodes lose everything. He added the possibility to export and import Friendica accounts. But that would only help if a permanent shutdown was announced. It did not protect you against shutdowns out of the blue. There was only one solution to this problem. And that was for someone's identity to not be bound to one server, but to exist on multiple servers simultaneously. The whole thing with everything that's attached to it. Name, settings, connections, posts, files in the file storage etc. etc., everything. So in 2011, Mike designed a whole new protocol named Zot around this brand-new idea of what he called "nomadic identity" back then already. In 2012, Mike forked Friendica into something called Red, later the Red Matrix, and rebuilt the whole thing from the ground up against Zot. Red was the first nomadic social networking software in the world, almost four years before Mastodon. In 2015, ten months before Mastodon was first released, the Red Matrix became <a href="https://joinfediverse.wiki/Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a>, the Fediverse's ultimate Swiss army knife. I am on Hubzilla myself. <a href="https://hub.netzgemeinde.eu/channel/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">This channel of mine</a> is constantly being mirrored between its main instance on <a href="https://hub.netzgemeinde.eu" rel="nofollow noopener noreferrer" target="_blank">https://hub.netzgemeinde.eu</a> and its clone on <a href="https://hub.hubzilla.de" rel="nofollow noopener noreferrer" target="_blank">https://hub.hubzilla.de</a>. Anything that happens on the main instance is backed up on the clone. I can also log into the clone and use that, and whatever happens there is backed up on the main instance. <a href="https://hub.netzgemeinde.eu" rel="nofollow noopener noreferrer" target="_blank">https://hub.netzgemeinde.eu</a> could go down, temporarily, permanently, doesn't matter; I still have my channel, namely the clone. And I can declare the clone my new main instance. Well, Mike didn't stop at Hubzilla and its original version of the Zot protocol. He wanted to refine it and advance it, but in ways that wouldn't be possible on daily-driver software. Zot went through several upgrades: Zot6 in 2018 (backported to Hubzilla in 2020, along with OpenWebAuth magic single sign-on). Zot8 in 2020. Zot11 in 2021 which had become incompatible with Zot6 and therefore was renamed to Nomad. Today's Nomad would be Zot12. Also, in order to advance and test Zot, Mike created a whole bunch of forks and forks of forks. Osada and Zap for Zot6 in 2018, followed by another short-lived Osada in 2019. A third Osada, Mistpark 2020 (a.k.a. Misty) and Redmatrix 2020 in 2020 for Zot8. Roadhouse for <del>Zot11</del> Nomad in 2021. All Osadas, Zap, Misty, Redmatrix 2020 and Roadhouse were discontinued on New Year's Eve of 2022. The most recent software based on Nomad is from October, 2021. It can be found in <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">the streams repository</a>. It is officially and intentionally nameless and brandless, it has next to nodeinfo code that could submit statistics, and it is intentionally released into the public domain. The community named it <a href="https://joinfediverse.wiki/(streams)" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> after the code repository. I also have two (streams) channels, one of which is cloned so far. The newest thing, and that's what the Friendica and Hubzilla veteran @<a class="" href="https://hub.tschlotfeldt.de/channel/ts-new" rel="nofollow noopener noreferrer" target="_blank">Tim Schlotfeldt ⚓?️‍?</a> referred to, is nomadic identity using nothing but ActivityPub, no longer relying on a special protocol. This was not Mike Macgirvin's idea. This came from @<a href="https://mitra.social/users/silverpill" rel="nofollow noopener noreferrer" target="_blank">silverpill</a>, the creator and developer of the microblogging server application <a href="https://codeberg.org/silverpill/mitra" rel="nofollow noopener noreferrer" target="_blank">Mitra</a>. He wanted to make Mitra nomadic, make it resilient against server shutdown. But he didn't want to port it to Nomad. He wanted to achieve it with nothing but ActivityPub. So he hit up Mike. The two came to the conclusion: This is actually possible. And they began to work on it. Amongst the results were several FEPs coined by silverpill. This time, Mike did not create another fork to develop nomadic identity via ActivityPub. He did it all on the nomadic branch of the streams repository while silverpill did his part on a special development branch of Mitra. In mid-2024, after enough sparring between (streams) instances, between Mitra instances and between (streams) and Mitra, Mike was confident enough that his implementation of support of nomadic identity via ActivityPub was stable enough. He merged the nomadic branch into the dev branch which ended up being merged into the stable release branch in summer. Now, at this point, (streams) didn't use ActivityPub for nomadic identity. It still used the Nomad protocol for everything first and foremost, including cloning. But it understood nomadic identity via ActivityPub as implemented on experimental Mitra. However, while it worked under lab conditions, it blew up under real-life conditions. At this point, (streams) had to handle so many different identities that it confused them, and it couldn't federate with anything yet. In mid-August, while trying to fix the problem, Mike eventually forked the streams repository into <a href="https://codeberg.org/fortified/forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a>. It got a name again, it got a brand identity again, it got its nodeinfo back, it was put under the MIT license again. But most importantly: Any and all support for Nomad was ripped out, also to get rid of a whole number of IDs, namely those for Nomad-actually-Zot12 and for Hubzilla's Nomad-actually-Zot6. Forte only uses ActivityPub for everything. And so, Forte also had to fully rely on ActivityPub for nomadic identity, cloning and syncing. For almost seven months, Forte was considered experimental and unstable. For most of the time, the only existing servers were Mike's. But on March 12th, 2025, <a href="https://fediversity.site/item/b69ce5a0-0c22-4933-8393-dce7100f4584" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin released Forte 25.3.12</a>, the first official stable release of Forte. This is what Tim wrote about. Because this actually made it into Fediverse-wide news. Not because it's nomadic. Nomadic identity has been daily-driven for over a decade now. But because it uses ActivityPub for nomadic identity. Which means that you can theoretically make any kinds of Fediverse software nomadic now, all without porting it to the Nomad protocol first. For the future, Mike and silverpill envision a Fediverse in which one can clone between different server applications. A Fediverse in which one can have one and the same identity cloned across multiple servers of Mastodon, Pixelfed, PeerTube, Mitra, Forte, Mobilizon, Lemmy, BookWyrm etc., all with the same name, all with the same content and settings (as far as the software allows; you will certainly not be able to clone your PeerTube videos to Mastodon and Lemmy). Even if you don't intend to clone, it will make moving instances and even moving from one software to another dramatically easier. If you're concerned about your privacy, let me tell you this: Hubzilla's privacy, security and permissions system is unparalleled in the Fediverse. Except for that on (streams) and Forte which is another notch better. I can define who can see my profile (my default, public profile on Hubzilla where each channel can have multiple profiles). I can define who can see my stream and my posts when looking at my channel. I can define who can see my connections (Hubzilla, (streams) and Forte don't distinguish between follower and followed; they aren't Twitter clones). I can define who can look into my file space (individual permission settings per folder and per file notwithstanding). I can define who can see my webpages on Hubzilla (if I have any). I can define who can see my wikis on Hubzilla (<a href="https://hub.netzgemeinde.eu/wiki/jupiter_rowland" rel="nofollow noopener noreferrer" target="_blank">no shit, I've got wikis on my Hubzilla channel</a>). On Hubzilla, I can define individually for any of these whether it's <ul><li>everyone on the Internet</li><li>everyone with a recognisable Fediverse account</li><li>everyone on Hubzilla (maybe also on (streams); anyone using ActivityPub is definitely excluded here)</li><li>everyone on the same server as myself (AFAIK, only main instances of channels count here, clones don't)</li><li>unapproved (= followers) as well as approved (= mutual) connections</li><li>confirmed connections</li><li>those of my confirmed connections whom I explicitly grant that permission by contact role</li><li>only myself</li></ul> <a href="https://help.hubzilla.hu/en/usermanual/permissions_channel_roles.html" rel="nofollow noopener noreferrer" target="_blank">There's a whole bunch more permissions than these</a>. And they all have seven or eight permission levels (depending on whether the general non-Fediverse public can be given permission). On (streams) and Forte, I can define whether things are allowed for <ul><li>everyone on the Internet (where applicable)</li><li>everyone with a recognisable Fediverse account</li><li>all my approved connections</li><li>only me myself plus those whom I explicitly grant that permission in the connection settings</li></ul> Yes, connection settings. Hubzilla, (streams) and Forte give you various ways of configuring individual connections, much unlike Mastodon. This includes what any individual connection is allowed to do. Hubzilla uses so-called "contact roles" for that, presets with a whopping 17 permissions to grant or deny for any one individual connection. That is, what the channel generally allows, a contact role can't forbid. (streams) and Forte still have 15 permissions per contact, but they lack some features which Hubzilla has permissions for. These permissions can be set individually for each connection, or you can define permission roles that cover all 15 permissions to make things easier. Okay, how about posting in public vs in private? And when I say "private", I mean "private". It's "private messages" on Hubzilla, (streams) and Forte, not "direct messages". Hubzilla, (streams) and Forte let you post <ul><li>in public</li><li>only to yourself</li><li>only to your connections ((streams) and Forte only; Hubzilla requires a privacy group with all your connections in it for this)</li><li>to all members of one specific privacy group (Hubzilla)/access list ((streams), Forte); that's like being able to only post to those on one specific list on Mastodon</li><li>to everyone to whom one specific non-default profile is assigned (Hubzilla only)</li><li>to a specific group/forum (I'll get back to that later)</li><li>to a custom one-by-one selection of connections of yours</li></ul> Now, let's assume I have a privacy group with Alice, Bob and Carol in it. I send a new post to only this privacy group. This means: <ul><li>Only Alice, Bob and Carol can see the post and the conversation.</li><li>Alice can reply to me, Bob and Carol.</li><li>Bob can reply to me, Alice and Carol.</li><li>Carol can reply to me, Alice and Bob.</li><li>Nobody else can see the post. Not even by searching for it. Not by hashtag either. Not at all.</li><li>Nobody else can see any of the comments.</li><li>Nobody else can comment.</li></ul> If one of them was on Mastodon, they'd see my post as a DM, by the way, and they could only reply to me. But that's Mastodon's limitation because it understands neither threaded conversations nor permissions. Or how about reply control? This is something that many Mastodon users have been craving for quite a while now. Hubzilla, (streams) and Forte have them. Right now. And they work. They have since 2012. Hubzilla optionally lets me disallow comments on either of my posts. Users on Hubzilla, (streams) and Forte won't even be able to comment; they won't have the UI elements to do so. Everyone else is able to comment locally. But that comment will never end up on my channel. It will never officially be added to the conversation. And at least users on Friendica, Hubzilla, (streams) and Forte will never fetch that comment from my channel as part of the conversation, i.e. never at all. (streams) and Forte can go even further with all available options. They can disallow comments like Hubzilla. But in addition, they can allow only the members of one particular access list to comment, regardless of who can see the post/the conversation. On top of that, comments can be closed at a pre-defined point in the future. And then you even have a channel-wide setting for how long people can comment on your posts. Oh, and there's even a setting for who is generally permitted to comment on your posts. And you can additionally allow specific connections of yours to comment on your posts. Lastly, I've already mentioned groups/forums. Like, you know, Web forums or Facebook groups or subreddits or whatever. Like Guppe Groups on a mountain of coke and with moderation and permission control and optionally private. Hubzilla has them, and it has inherited them from Friendica. (streams) has them. Forte has them. They're basically channels like social networking channels, but with some extra features. This includes that everything that's send to a group/forum as what amounts to a PM is automatically forwarded to all other members. On Hubzilla, a forum can be gradually made private by denying permission to see certain elements to everyone but its own members (= connections): the profile, the members, what's going on in it. Depending on what you want or do not want people to see. On (streams) and Forte, you have four types of forums: <ul><li>public, and members can upload images and other files to the forum channel</li><li>public, but members cannot upload images and other files to the forum channel</li><li>like above, but additionally, posts and comments from new members must be manually approved by the admin(s) until their connections are configured to make them full members</li><li>private, non-members can't see the profile, non-members can't see the connections, non-members can't see what's going on in it, but members can upload images and other files to the forum channel</li></ul> In addition, on all three, a group/forum channel can choose to hide itself from directories. This is always an extra option that's independent from public/private. What we have here is the most secure and most private Fediverse software of all. And, once again, at its core, this is technology from 2012. It pre-dates Mastodon by almost four years. Finally, if you want to know how Hubzilla and (streams) compare to Mastodon: <a href="https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392" rel="nofollow noopener noreferrer" target="_blank">I have made a number of tables that compare Mastodon, Friendica, Hubzilla and (streams).</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mitra" rel="nofollow noopener noreferrer" target="_blank">Mitra</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Friendica" rel="nofollow noopener noreferrer" target="_blank">Friendica</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forte" rel="nofollow noopener noreferrer" target="_blank">Forte</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ActivityPub" rel="nofollow noopener noreferrer" target="_blank">ActivityPub</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zot" rel="nofollow noopener noreferrer" target="_blank">Zot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zot6" rel="nofollow noopener noreferrer" target="_blank">Zot6</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Zot8" rel="nofollow noopener noreferrer" target="_blank">Zot8</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Nomad" rel="nofollow noopener noreferrer" target="_blank">Nomad</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=NomadicIdentity" rel="nofollow noopener noreferrer" target="_blank">NomadicIdentity</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Security" rel="nofollow noopener noreferrer" target="_blank">Security</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseSecurity" rel="nofollow noopener noreferrer" target="_blank">FediverseSecurity</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Privacy" rel="nofollow noopener noreferrer" target="_blank">Privacy</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediversePrivacy" rel="nofollow noopener noreferrer" target="_blank">FediversePrivacy</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener noreferrer" target="_blank">Permissions</a>

Asheville Charlie<a href="https://mastodon.social/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Google</a> Assistant recently turned into Google <a href="https://mastodon.social/tags/Gemini" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Gemini</a> and you may want to check your <a href="https://mastodon.social/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a> because I found this all allowed and I don't do that..<a href="https://mastodon.social/tags/privacy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#privacy</a>

Hacker Public RadioNew Episode: hpr4328 :: Use SELinux the easy wayYou don't have to be an expert on SELinux to use it effectivelyHosted by Klaatu on Wednesday, 2025-03-05 is flagged as Clean and is released under a CC-BY-SA license.Tags: <a href="https://infosec.exchange/tags/linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#linux</a>, <a href="https://infosec.exchange/tags/selinux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#selinux</a>, <a href="https://infosec.exchange/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a>. Today on the <a href="https://infosec.exchange/tags/HackerPublicRadio" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HackerPublicRadio</a> <a href="https://infosec.exchange/tags/Community" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Community</a> <a href="https://infosec.exchange/tags/Podcast" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Podcast</a><a href="https://infosec.exchange/tags/HPR" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#HPR</a> ❤️ <a href="https://infosec.exchange/tags/CreativeCommons" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CreativeCommons</a><a href="https://hackerpublicradio.org/eps/hpr4328/index.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hackerpublicradio.org/eps/hpr4328/index.html</a>

2meterdba | Reitse EskensBlog alert!Valerie and I dug into <a href="https://mastodon.nl/tags/DataMasking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DataMasking</a> for <a href="https://mastodon.nl/tags/MicrosoftFabric" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#MicrosoftFabric</a> and found some interesting things about <a href="https://mastodon.nl/tags/Permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Permissions</a> as well!<a href="http://sqlreitse.com/2025/03/04/dp-700-training-data-masking/" rel="nofollow noopener noreferrer" translate="no" target="_blank">http://sqlreitse.com/2025/03/04/dp-700-training-data-masking/</a>

Jupiter RowlandHere's another thing that you may not know about <a href="https://hubzilla.org" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> and <a href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> yet: Not only do they have quote-posts, but they also have pretty effective anti-quote-post defences. Hubzilla Hubzilla has a permission setting named "Can source/mirror my public posts in derived channels". It has been there since 2012 when Hubzilla was still a fledgling project named Red, that's 13 years now. Whether someone may quote-post ("share") your public posts depends on the setting in the channel role. If your channel is set to "Public", I think everyone is allowed to share your public posts. If it's set to "Private", you can (and have to) grant that permission to your connections individually by contact role. Those whom you aren't connected to are not allowed to share any of your posts. The "Custom" channel role lets you choose between granting that permission, one out of 17 permissions, to: <ul><li>everyone in the Fediverse</li><li>everyone on Hubzilla and (streams)</li><li>everyone on your home hub</li><li>unconfirmed and confirmed connections</li><li>confirmed connections</li><li>only those whom you individually grant that permission</li><li>nobody but you</li></ul> (streams) (streams) goes even further. As far as I know, it doesn't give you the option to let everyone quote-post any of your posts in the first place. Not only are you always opted out to the point that only you yourself may quote-post your posts, but you can't even fully opt in. No matter if your channel type is "Social - Public" or "Social - Restricted", the only ones who are allowed to quote-post even only your public posts are those of your connections who get the permission from you. Unlike on Hubzilla, however, you don't have to fumble around with permission roles, although you may do so to speed things up. You've also got a dedicated switch for this permission on each connection labelled "Grant permission to republish/mirror your posts". The effect This permission has its strongest effect on Hubzilla, (streams) and Forte: If one of their users is not allowed to share one of your posts, the Share button is missing altogether. And there's no real way around the Share button. In fact, the Repeat button is missing, too. If you aren't allowed to quote-post it, you aren't allowed to boost it either. This permission is not about how you may forward someone's content, but whether you may forward it. Unfortunately, Fediverse users probably everywhere else are not affected by this permission. Users of Pleroma, Misskey and their respective forks can still quote-post you to their heart's content. And I've got my doubts that Mastodon will understand this permission when it introduces quote-posts. Then again, it's highly likely that Mastodon's quote-post opt-in or opt-out won't work outside of Mastodon either. Privacy as an extra line of defence If you really want to be safe, you've additionally got the option to not post in public. Any post that isn't public can neither be repeated (boosted) nor shared (quote-posted). Both Hubzilla and (streams) give you the option to send a post to the members of a privacy group/access list (think Mastodon list on coke and 'roids), to a specific group/forum or to any individual selection of connections of yours. (streams) also has Mastodon's option to send a post to all your connections; Hubzilla can emulate that with a privacy group with all your connections in it. Okay, your post will lose a whole lot of reach. But this is a trick that even Mastodon understands in a certain way: If a post from Hubzilla or (streams) has a restricted audience, Mastodon takes it for a PM. And you can't boost PMs, can you? #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePost" rel="nofollow noopener noreferrer" target="_blank">QuotePost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePosts" rel="nofollow noopener noreferrer" target="_blank">QuotePosts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweet" rel="nofollow noopener noreferrer" target="_blank">QuoteTweet</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTweets" rel="nofollow noopener noreferrer" target="_blank">QuoteTweets</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToot" rel="nofollow noopener noreferrer" target="_blank">QuoteToot</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteToots" rel="nofollow noopener noreferrer" target="_blank">QuoteToots</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoost" rel="nofollow noopener noreferrer" target="_blank">QuoteBoost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteBoosts" rel="nofollow noopener noreferrer" target="_blank">QuoteBoosts</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotedShares" rel="nofollow noopener noreferrer" target="_blank">QuotedShares</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuotePostDebate" rel="nofollow noopener noreferrer" target="_blank">QuotePostDebate</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=QuoteTootDebate" rel="nofollow noopener noreferrer" target="_blank">QuoteTootDebate</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Pleroma" rel="nofollow noopener noreferrer" target="_blank">Pleroma</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Akkoma" rel="nofollow noopener noreferrer" target="_blank">Akkoma</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Misskey" rel="nofollow noopener noreferrer" target="_blank">Misskey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkey" rel="nofollow noopener noreferrer" target="_blank">Forkey</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Forkeys" rel="nofollow noopener noreferrer" target="_blank">Forkeys</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener noreferrer" target="_blank">Permissions</a>

TechHelpKB.com 📚Google Chrome is now testing a new feature called “PermissionsAI”, which is designed to handle all the annoying pop-ups asking you questions. You know the ones.<a href="https://mastodon.social/tags/google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#google</a> <a href="https://mastodon.social/tags/chrome" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chrome</a> <a href="https://mastodon.social/tags/browser" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#browser</a> <a href="https://mastodon.social/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a> <a href="https://mastodon.social/tags/ai" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ai</a> <a href="https://www.tomsguide.com/ai/annoying-browser-pop-ups-could-become-a-thing-of-the-past-thanks-to-googles-new-ai" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.tomsguide.com/ai/annoying-browser-pop-ups-could-become-a-thing-of-the-past-thanks-to-googles-new-ai</a>

Ben HardillI have a strange situation. I have a PV mounted in a Pod, on that PV there is a file with permissions 0600. If I scale the Deployment the Pod is part of to 0 and then back to 1 the file permission changes to 0660.Doing a rollout restart deployment doesn't appear to trigger it (at least for me)The Pod is running a node:alpine container and the app that is running doesn't change the permissions.Anybody got any suggestions as to why and how to stop it.<a href="https://bluetoot.hardill.me.uk/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#kubernetes</a> <a href="https://bluetoot.hardill.me.uk/tags/k8s" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#k8s</a> <a href="https://bluetoot.hardill.me.uk/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a>

AmereyConcessio - convert between symbolic and numeric representations of UNIX file permissions <a href="https://fosstodon.org/tags/file" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#file</a> <a href="https://fosstodon.org/tags/unix" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#unix</a> <a href="https://fosstodon.org/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a> ➡️ <a href="https://github.com/ronniedroid/concessio" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/ronniedroid/concessio</a>

bijram<a href="https://mastodon.thenewoil.org/@thenewoil" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@thenewoil</a> Another <a href="https://graz.social/tags/malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#malware</a> the user has to install and grant several very sus <a href="https://graz.social/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a> to it though

W3C DevelopersOrganizers Ian Jacobs and <a href="https://mamot.fr/@tidoust" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@tidoust</a> reported on last month's <a href="https://w3c.social/tags/w3cTPAC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#w3cTPAC</a> breakouts: ▶️ <a href="https://www.w3.org/blog/2024/reflections-on-tpac-2024-breakouts/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.w3.org/blog/2024/reflections-on-tpac-2024-breakouts/</a>📈 A record-breaking 87 sessions, compared with 69 in 2023!Key themes included: <a href="https://w3c.social/tags/AI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AI</a>, <a href="https://w3c.social/tags/identity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#identity</a> <a href="https://w3c.social/tags/Wallets" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Wallets</a> <a href="https://w3c.social/tags/WebApps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebApps</a> <a href="https://w3c.social/tags/WebComponents" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WebComponents</a> Feature lifecycle, <a href="https://w3c.social/tags/Permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Permissions</a> and <a href="https://w3c.social/tags/Realtime" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Realtime</a> Web.Check out the agendas, minutes, and slide decks, avail. from the breakouts page: ▶️ <a href="https://www.w3.org/2024/09/TPAC/breakouts.html" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.w3.org/2024/09/TPAC/breakouts.html</a>

Dr. Juande Santander-VelaToday I learned that you can check if groups of people, or particular individuals, can view a particular page in Confluence. You just need to use the horizontal ellipsis menu (\cellip), and select the option People who can view this page (see first image). You can then search (second image) for particular individuals.<a href="https://astrodon.social/tags/TIL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TIL</a> <a href="https://astrodon.social/tags/TodayILearned" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#TodayILearned</a> <a href="https://astrodon.social/tags/Confluence" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Confluence</a> <a href="https://astrodon.social/tags/Permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Permissions</a>

Jupiter Rowland@<a href="https://social.coop/users/J12t" rel="nofollow noopener noreferrer" target="_blank">Johannes Ernst</a> Not even Hubzilla and (streams) offer the option to allow everyone on the Internet to like or dislike stuff, and they certainly have the option to grant certain permissions to people without user accounts. If that isn't implemented, it probably isn't implemented for a reason. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener noreferrer" target="_blank">Permissions</a>

Andy Miller📣 Using custom permissions for is_staff and is_superuser 📄 Another experiment in slimming down the User model 🔗 <a href="https://softwarecrafts.co.uk/100-words/day-176" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://softwarecrafts.co.uk/100-words/day-176</a> <a href="https://indiehackers.social/tags/100_words" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#100_words</a>,<a href="https://indiehackers.social/tags/django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#django</a>,<a href="https://indiehackers.social/tags/auth" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#auth</a>,<a href="https://indiehackers.social/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a>

Kushal Das :python: :tor:Saturday 11pm and I am trying to find and read every blog / article about <a href="https://toots.dgplug.org/tags/django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#django</a> <a href="https://toots.dgplug.org/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a>.

Kushal Das :python: :tor:Spending the evening in the bit of confusing land of <a href="https://toots.dgplug.org/tags/django" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#django</a> <a href="https://toots.dgplug.org/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a>.

Jupiter Rowland@<a class="" href="https://zotum.net/channel/norvegan" rel="nofollow noopener noreferrer" target="_blank">NorVegan</a> <blockquote>Just to make sure I understand correctly, embedded inline images are not remeved all together, but rather moved to the bottom of the post? ...but only 4 images, the rest is actually removed. Did I get that right?</blockquote> What actually happens is that Mastodon's "code sanitiser" strips everything out that Eugen Rochko doesn't deem old-school, original-gangsta, Twitter-like microblogging. Except a little text formatting since Mastodon 4. But this includes in-line images which Mastodon removes. In order for images in posts to make it to Mastodon in some way, Friendica, Hubzilla and (streams) make copies of inline images as file attachments because Mastodon does not strip file attachments away. File attachments are how Mastodon does images. But even then, Mastodon only supports a maximum of four file attachments, even in incoming posts. Everything that goes beyond that is discarded entirely. <blockquote><blockquote>I've set my channel up in such a way that I have to confirm all new connections.</blockquote> How do you do this?</blockquote> It's a default setting in Hubzilla. It can be found in the privacy settings. Or rather, the opposite can, namely that anyone can follow your channel just like so, without your explicit consent. <blockquote>So if you manually confirm new connections, it'll appear to them like you follow them back, but if they're confirmed automatically it will not appear that way?</blockquote> It doesn't just appear so. If someone tries to follow me, all that happens is that I receive a notification. But they don't actually follow me. They aren't permitted anything, not even to receive my posts. In order for them to actually follow me, I have to confirm their follow request. But in doing so, I automatically follow them back. Hubzilla doesn't do that Twitter/Mastodon shtick of having followers on the one hand and followed on the other hand, and these are two different things, and if you follow one of your followers, congrats, you're mutuals. Normally, Hubzilla works like Facebook. You're connected bidirectionally, mutually, or you aren't connected at all. Only that Facebook calls it "friend", and Hubzilla calls it "contact" or "connection". Okay, but there's still that switch that I've mentioned above. It allows others to follow you without your consent. I've never tested this switch. None of my Hubzilla channels is experimental enough for me to try it. But thinking about it, I guess it should establish a bidirectional connection, too. Again, I don't know for sure. This switch does not make much sense for a personal channel. It's much more useful for a public, anyone-can-join forum channel. Now comes the extra trick that I've pulled, the thing that I mean with "I don't actually follow you back". Most of my connections are Mastodon users who have absolutely nothing interesting to say. Not within the scope of my channel (primarily OpenSim, secondarily the Fediverse beyond Mastodon). Some followed me because they took me for a Fediverse guru and nothing else because they had judged me by that one single post or comment they discovered from me. Others, especially from 2023 on, followed me because they found me on the federated timeline on mastodon.social, and they followed everyone whom they found there so they had their timeline abuzz with uninteresting cruft just like on Twitter. If I actually followed them back like you'd expect me to follow them back, they'd completely and utterly soak my stream with what I consider totally uninteresting cruft, completely drowning out the interesting posts, even more so if I even let their boosts through. On the one hand, I want to let them follow me. On the other hand, I don't want them to drown me in all that off-topic rubbish. I tried filtering when the channel was new. All of a sudden, my stream was nicely quiet. Problem, however: Hubzilla can't apply a per-connection whitelist filter including a keyword list only on posts and neither on comments nor on DMs. At least once, I haven't received a DM because the filter blocked it, because it didn't contain any of the keywords that were required for any content to come through. So what I did was: <ol><li>I edited all my contact roles and explicitly allowed sending me posts in them.</li><li>I made two new contact roles that don't allow sending me posts.</li><li>I assigned these new contact roles to all contacts that I didn't expect to post anything interesting.</li><li>Lastly, I edited my channel role and turned off the permission to send me posts.</li></ol> Step 1 ensured that everyone who had one of my old channel roles assigned was still allowed to send me posts even after step 4. Step 2 and 3 made sure all those whom I wanted silenced were silenced when step 4 happened, and those were the majority of my connections. Again, my stream was not nearly as busy as it would have been if everyone was permitted to send me their posts. To reduce the cruft even further, I applied boost filters to those whose posts I allow, but who boost a lot of rubbish. And I also try to filter out specific uninteresting things from very busy connections which, at the same time, are unlikely to send me DMs by blacklisting certain keywords. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Filters" rel="nofollow noopener noreferrer" target="_blank">Filters</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener noreferrer" target="_blank">Permissions</a>

FoxApache2 permissions “hack” It’s not stupid if [the last part] works, right? Right? 1. We need a new group: website 2. We need a user: frank 3. Simple website where everything is put into /var/www/html/ sudo addgroup website sudo adduser frank website sudo adduser www-data website Let’s see if Frank belongs to the right groups: groups frank The result should look so… --- <a href="https://3xn.nl/projects/2024/08/04/apache2-permissions-hack/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://3xn.nl/projects/2024/08/04/apache2-permissions-hack/</a> --- <a href="https://cytag.nl/tags/apache2" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#apache2</a> <a href="https://cytag.nl/tags/chown" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#chown</a> <a href="https://cytag.nl/tags/html" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#html</a> <a href="https://cytag.nl/tags/newgrp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#newgrp</a> <a href="https://cytag.nl/tags/ownership" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ownership</a> <a href="https://cytag.nl/tags/permissions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#permissions</a>

Jupiter Rowland@<a class="" href="https://hub.kliklak.net/channel/jrp" rel="nofollow noopener noreferrer" target="_blank">_jayrope</a> That's because Mastodon users were generally promised paradise when they were still on the Birdsite. And they got used to being mollycoddled all around. Give them tools of self-empowerment, and they won't use them and demand to be coddled some more. I mean, it isn't like Mastodon gives you no means of self-defence at all. But some people don't even seem to be able or willing to mute or block anyone. And I'm not convinced that they're all stuck with a mobile app that only offers the absolute bare basics. And then there are those who came via Friendica to Hubzilla or (streams). Give them a dozen permission settings and a half, and they'll go to the code repository and ask for more. #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener noreferrer" target="_blank">Permissions</a>

Jupiter Rowland@<a href="https://stefanbohacek.online/@stefan" rel="nofollow noopener noreferrer" target="_blank">Stefan Bohacek</a> @<a href="https://blahaj.zone/@jdp23" rel="nofollow noopener noreferrer" target="_blank">Jon</a> Such safety improvements cannot and must not come from within Mastodon. For if they did, it would be non-standard, proprietary, undocumented, Mastodon-exclusive solutions that anything that isn't vanilla Mastodon or a soft fork would hardly be able to adopt themselves and oftentimes not willing either. Fediverse devs are turning away from allowing Mastodon to take control over the development of the Fediverse by introducing more and more non-standard, Mastodon-exclusive stuff. Even worse: If these were Mastodon-only solutions, they might lead to two possible outcomes. One, since the rest of the Fediverse won't support them, the rest of the Fediverse would easily be able to circumvent them. Routinely even. See "quote-toot opt-in". Remember that almost everything in the Fediverse that's an alternative to Twitter and/or Facebook has quote-posts readily available and can quote-post any Mastodon toot right now. Two, an unbridgeable rift through the Fediverse as Mastodon splits <del>everything that isn't Mastodon</del> itself off. This could be because Mastodon makes itself incompatible with everything else in the Fediverse by introducing new mandatory features that everything else doesn't support. Or it could be because new rules come with new features that demand the use of these features at instance level, and instances that don't use these features will be Fediblocked. Only that nothing that isn't vanilla Mastodon is even able to use these features. For these reasons, such safety advancements must never be Mastodon developments. Instead, they must come from the ActivityPub side. And there are things in development right now which, if actually implemented, will increase security in the Fediverse tremendously. Specifically, what I mean is what @<a class="" href="https://fediversity.site/channel/mikedev" rel="nofollow noopener noreferrer" target="_blank">Mike Macgirvin 🖥️</a> is working on right now, the guy who invented Friendica, nomadic identity and Hubzilla, and who has created and is maintaining [#^<a class="" href="https://codeberg.org/streams/streams" rel="nofollow noopener noreferrer" target="_blank">https://codeberg.org/streams/streams</a>]the streams repository[/url] which contains the probably most advanced Fediverse server application of all. He wants to bring not only nomadic identity to native ActivityPub, but also (streams)' extensive, fine-grained, powerful system of permissions which would then be understood not only amongst (streams) and Hubzilla, but all across the Fediverse amongst those projects that implement them. Imagine being able to post only to the members of a specific list. Imagine these posts being unable to ever leave the list, save for copy-pasting or screenshots. Imagine being able to choose which ones of your connections shall be allowed to see your posts. Or send you posts. Or reply to your posts. Or send you DMs. Or see your followers and followeds. Imagine being able to define permission roles, pre-configured sets of permissions, and assign one of these to each one of your connections. Imagine being able to set your entire account to post only to your followers by default. Imagine being able to deny everyone the permission to reply to a certain post of yours. Imagine being able to only allow your connections to reply to a certain post of yours. Imagine being able to limit the timespan within which a post of yours can be replied to. Only if that post isn't a reply itself, but still. Imagine being able to wall up your account, but without walling it up against everyone by only walling it up against certain people. Sounds like utter science-fiction. But all this is available on (streams) right now. Granted, it does not provide absolute, 100% water-tight safety against everything. Like comparable with a shielding that wouldn't even let one neutrino through in ten billion years. But as much such perfect security is desired, as impossible it is. Not unless e.g. the Black community creates an exclusive, walled-garden safe space whose aspiring members must be validated by meeting an admin or moderator in real life, eye to eye, to prove that they're actually Black. Sorry, but everything else can and will be circumvented to attack and harass them. Also, yes, this permission system is not as easy-peasy to handle as the official Twitter mobile app. And it currently comes with a fairly cumbersome UI. That's because, as of now, it only works with (streams)' Nomad protocol and, within certain limitations, the Zot6 protocol used by Hubzilla which has a similar set of permission controls. I mean, I'd love to see a "Black (streams)" come into existence with a bunch of instances of its own and flourish. For one, (streams) has better chances to be a (fairly) safe haven than Mastodon. Besides, this would give (streams) the publicity it so much needs, especially if Black (streams) started thriving after Black Mastodon has failed so spectacularly. But let's face it, it's more cumbersome to use in comparison with Mastodon than Mastodon is in comparison with Twitter, also because (streams) is the descendant of a Facebook alternative rather than a Twitter clone. And if you're on a phone, it's either a PWA or a Web browser because there's no (streams) app. Good news, however: As far as I can see, Mike's goal is to implement all this in ActivityPub with FEPs so that any pure ActivityPub project can adopt it. Friendica can adopt it, fairly easily even because Friendica is (streams)' earliest predecessor. Misskey and its forks can adopt it, and these projects are chock-full of LGBTQIA+ people. Everything can adopt it. Unfortunately, implementing it in ActivityPub so it works nearly the same as on (streams) will be easier than pressuring Mastodon into implementing that stuff. Lastly, there's one feature of Hubzilla and (streams) that won't make it to ActivityPub because it can't. And that's the ability to turn ActivityPub support off altogether, both for users at channel level and for admins at instance level. One flick of a switch, and the entirety of Mastodon is blocked. All of it. As is Threads. As are the various Mastodon forks, Pleroma, Akkoma, Misskey, the various Misskey forks, Mitra, micro.blog, Socialhome, Pixelfed, the entire Threadiverse etc. etc., and if you're on (streams), even Friendica and GoToSocial. But if you are on ActivityPub, that wouldn't make any sense to be able to do. CC, FYI because you've participated in the thread: @<a href="https://mastodon.social/@ErickaSimone" rel="nofollow noopener noreferrer" target="_blank">Ericka Simone</a> @<a href="https://hachyderm.io/@tehstu" rel="nofollow noopener noreferrer" target="_blank">Stu</a> @<a href="https://hachyderm.io/@leoncowle" rel="nofollow noopener noreferrer" target="_blank">Leon Cowle</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Long" rel="nofollow noopener noreferrer" target="_blank">Long</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=LongPost" rel="nofollow noopener noreferrer" target="_blank">LongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLong" rel="nofollow noopener noreferrer" target="_blank">CWLong</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWLongPost" rel="nofollow noopener noreferrer" target="_blank">CWLongPost</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediMeta" rel="nofollow noopener noreferrer" target="_blank">FediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseMeta" rel="nofollow noopener noreferrer" target="_blank">FediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=CWFediverseMeta" rel="nofollow noopener noreferrer" target="_blank">CWFediverseMeta</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Fediverse" rel="nofollow noopener noreferrer" target="_blank">Fediverse</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Mastodon" rel="nofollow noopener noreferrer" target="_blank">Mastodon</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Hubzilla" rel="nofollow noopener noreferrer" target="_blank">Hubzilla</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Streams" rel="nofollow noopener noreferrer" target="_blank">Streams</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=%28streams%29" rel="nofollow noopener noreferrer" target="_blank">(streams)</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=ActivityPub" rel="nofollow noopener noreferrer" target="_blank">ActivityPub</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=Permissions" rel="nofollow noopener noreferrer" target="_blank">Permissions</a> #<a class="" href="https://hub.netzgemeinde.eu/search?tag=FediverseSafety" rel="nofollow noopener noreferrer" target="_blank">FediverseSafety</a>

Recent searches

Search options

Administered by:

Server stats:

#permissions