home.social
Sign in Create account

#permissions — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #permissions, aggregated by home.social.

  1. AskUbuntu @[email protected] ·

    PCSX2 BIOS Not Detecting on Ubuntu After Installation #permissions

    askubuntu.com/q/1566725/612

    #permissions
  2. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  3. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  4. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  5. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #long #lists #groups #cwlong #richtext #hubzilla
  6. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  7. Jupiter Rowland @[email protected] ·
    CW: Uncomfortable truth about the Fediverse that'll totally scare Mastodon users; CW: long (over 2,400 characters), Fediverse meta, Fediverse-beyond-Mastodon meta, quote-post meta, character limit meta
    When you see it, you'll shit brix: The Hubzilla timeline.

    The "it" that you're supposed to see is:
    • The Fediverse did, in fact, not start with Mastodon.
      There was something in the Fediverse before Mastodon: Mistpark was there almost 6 years before Mastodon, Hubzilla was there 10 months before Mastodon.
      Mastodon came into an already existing Fediverse with servers and users and content and a culture.
      The Fediverse has never been only Mastodon. And it will never be.
    • The Fediverse had quote-posts almost 6 years before Mastodon.
      (Accurate implication: The non-Mastodon Fediverse can quote-post any public Mastodon toot with no problems, and it has always been able to do so, for as long as Mastodon has been around.)
    • The Fediverse had groups almost 6 years before Mastodon which still doesn't even support groups.
    • The Fediverse had better lists than Mastodon lists almost 6 years before Mastodon.
    • The Fediverse had reply control almost 6 years before Mastodon where people are still waiting for some kind of reply control.
    • The Fediverse had permissions almost 6 years before Mastodon where the concept of permissions is completely unknown.
    And if you've really paid attention:
    • The Fediverse had no character limit to worry about almost 6 years before Mastodon came along with only 500 characters.
      The Fediverse had 16,777,215 characters almost 6 years before Mastodon had 500 characters.
    • The Fediverse had full rich-text formatting almost 6 years before Mastodon.
      The Fediverse could generate bold type, italics, underline, code blocks, bullet-point lists etc. without any Unicode trickery. Almost 6 years before Mastodon was there. And more than 12 years before Mastodon could even only display that stuff.

    Although it should be blatantly obvious: This here is not a Mastodon toot. This post comes from Hubzilla directly to your Mastodon apps.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mistpark #Friendica #Hubzilla #FediverseCulture #QuotePost #QuotePosts #QuoteTweet #QuoteTweets #QuoteToot #QuoteToots #QuoteBoost #QuoteBoosts #QuotedShares #Groups #FediGroups #FediverseGroups #Lists #ReplyControl #Permissions #CharacterLimit #CharacterLimits #CharacterLimitMeta #CWCharacterLimitMeta #500Characters #TextFormatting #RichText #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwcharacterlimitmeta #characterlimitmeta #fediverseculture #cwfediversemeta
  8. -Fred- :debian: :noai: @[email protected] ·

    Quand tu veux télécharger une #application d'accès à des chronos (#mylaps ; comptage sur des courses de voitures RC) et que tu te rends compte que l'App a été conçue pour #siphonner tout ce qu'elle pouvait comme données.

    Rien dans le descriptif de l'application ne laisse penser qu'elle a besoin de toutes ces #permissions pour fonctionner normalement.

    On va s'en passer je crois... 😅

    Merci à #exodus #privacy pour le travail d'analyse de toutes ces app 👍

    #application #mylaps #siphonner #permissions #exodus #privacy
  9. -Fred- :debian: :noai: @[email protected] ·

    Quand tu veux télécharger une #application d'accès à des chronos (#mylaps ; comptage sur des courses de voitures RC) et que tu te rends compte que l'App a été conçue pour #siphonner tout ce qu'elle pouvait comme données.

    Rien dans le descriptif de l'application ne laisse penser qu'elle a besoin de toutes ces #permissions pour fonctionner normalement.

    On va s'en passer je crois... 😅

    Merci à #exodus #privacy pour le travail d'analyse de toutes ces app 👍

    #exodus #privacy #application #mylaps #siphonner #permissions
  10. -Fred- :debian: :noai: @[email protected] ·

    Quand tu veux télécharger une #application d'accès à des chronos (#mylaps ; comptage sur des courses de voitures RC) et que tu te rends compte que l'App a été conçue pour #siphonner tout ce qu'elle pouvait comme données.

    Rien dans le descriptif de l'application ne laisse penser qu'elle a besoin de toutes ces #permissions pour fonctionner normalement.

    On va s'en passer je crois... 😅

    Merci à #exodus #privacy pour le travail d'analyse de toutes ces app 👍

    #application #mylaps #siphonner #permissions #exodus #privacy
  11. Kent Pitman @[email protected] ·

    Weird as it sounds, I think we need an actual law, like some kind of bill of rights, that says you can't notify me on my phone without offering me highly fine-tuned control of each kind of message.

    Notifications intrude into my life. Sometimes my phone is on waiting for emergencies or other high-priority issues while I sleep. If a friend wakes me, I can have them dialed up or down in priority.

    But Android is designed so Audible won't let me have control of my audiobooks in the lock screen without notifications turned on, yet once I've done that, Audible has no compunction against advertising new book releases in the middle of the night via notifications. I should be able to get cash compensation in court for that.

    And my USB-C cable, once I plug it into my Android phone insists on randomly popping up an utterly inscrutible notification saying "you need to log in if you want to see notifications", or some such, and then when I do there is no notification to see. It was just random.

    And Android Auto likes to give me two completely pointless notifications, one when I plug my phone into the car and one saying Android Auto is available. The first one I don't need a notification about because I just plugged in my phone. But more importantly, the second one is a lie. Android Auto MIGHT be available and it confirms nothing. The handshake may have been done wrong, so all it tells me is the thing I know already, which is that Android Auto is on the phone. But I might have to pull the plug and replug it to be properly connected. So the notification is worse than pointless and just floods my screen with stuff I don't care about that appears to need immediate attention. And then Android asks, as soon as I disconnect it, how my experience was. I always say "Bad" because part of my experience is getting asked that pesky message that I do not want and would happily say "never do this".

    These all seem like technical problems, but they are not. They are reminders that we no longer control our lives, that companies can, at a whim, intrude into our lives with pointless rituals that whittle away our existence. I'm not being metaphorical when I say we need laws on this. I absolutely mean that if we don't write strong law on this, it will only get worse. Or we need to enforce the 4th Amendment on a theory, like Larry Lessig has effectively said in the past, that programmatic code is effectively a kind of government that binds us and our choices in life as surely as legal code does.

    But what DO we get laws about? Having to login to use an operating system so they can track us better, know who we are and where we are at every moment. We need laws against such laws.

    #marketing #notifications #android #ui #ux #settings #design #QualityOfLife #computers #LockScreen #permissions #law #legal #lawsuits #ClassAction #rights #HumanRights #BillOfRights #identity #intrusion #interruption #4thAmendment #government #code

    #marketing #notifications #android #ui #ux #settings
  12. AskUbuntu @[email protected] ·

    Inconsistent access of local WIndows drive #permissions #2404 #files

    askubuntu.com/q/1566076/612

    #permissions #files
  13. AskUbuntu @[email protected] ·

    Permission denied (public key) error i forgot to save the key when i created the Instance #server #permissions #2204 #oracle

    askubuntu.com/q/1566052/612

    #server #permissions #oracle
  14. AskUbuntu @[email protected] ·

    Not letting me move or copy file to desktop #permissions #files

    askubuntu.com/q/1566012/612

    #permissions #files
  15. Jupiter Rowland @[email protected] ·
    But wait, there's more: Even if a Hubzilla channel, upon confirming your follow request, "follows" you back, it doesn't necessarily actually follow you back, as in, let your toots and boosts in.

    Chances are that the Hubzilla channel uses its permissions system to keep your toots and boosts out. Replies are allowed. DMs are allowed. But anything that isn't either is kept out.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #Contacts
    #cwfediversemeta #fediversemeta #permissions #cwfedimeta #fedimeta #hubzilla
  16. AskUbuntu @[email protected] ·

    HP OMEN 16 fan control not working on Ubuntu (ec_sys permission issue) #drivers #permissions #fan #temperature

    askubuntu.com/q/1565799/612

    #drivers #permissions #fan #temperature
  17. AskUbuntu @[email protected] ·

    How do I mount my 8TB hard as my Videos folder with rw permissions? #permissions #mount #harddrive

    askubuntu.com/q/1565789/612

    #permissions #mount #harddrive
  18. Frontend Dogma @[email protected] ·

    Node.js Brotli UAF, by @maitai:

    blig.one/2026/03/29/nodejs-bro

    #nodejs #permissions #brotli #compression #security #claude #ai

    #ai #claude #security #compression #brotli #permissions
  19. AskUbuntu @[email protected] ·

    Change ownership of a volume #permissions #volumecontrol #ownership

    askubuntu.com/q/1565735/612

    #permissions #volumecontrol #ownership
  20. U3dn @[email protected] ·

    Simplified Permission Management for Unity #Permissionmanagement #Unity #Android #Ios #Mobile #Permissions #Api #Editortools #AssetStore

    u3dn.com/packages/simplified-p

    #permissionmanagement #unity #android #ios #mobile #permissions
  21. schuelermine @[email protected] ·

    I think there should be app store guidelines that prohibit apps from having permissions prompts that make it unclear which permissions are required, for what, and that the control about the permissions is exclusively done via system prompts and settings.

    In particular, this would prohibit:
    * Asking for permissions randomly or preemptively. Only ask for permissions on initial setup and after explicit user request of a feature that requires or uses the permission.
    * Showing an app-controlled permissions popup with an option to reject that will trigger a further system popup if the app popup is accepted.

    Here is a shitty example from Spotify.
    The layout makes it look like this screen is asking me to give Spotify the permission. It isn't. It looks like tapping continue, the only obvious choice, will grant the permission. It won't.
    The popup appears even though no functionality related to Bluetooth devices was requested.
    It is not made clear what will happen when the permission is rejected. "Why do you need this?" implies that the user does in fact need the permission. They don't.
    The statement that "You're in control" is not helpful. It directly contradicts "Why do I need this?". It also suggests that the only way to deny the permission is to disable it in system settings. You can just deny the permission in the system prompt.

    #mobileui #permissions #uidesign

    #mobileui #permissions #uidesign
  22. N-gated Hacker News @[email protected] ·

    🎩 GitHub's latest #magic trick: a context-aware babysitter for #Claude #Code. Now you can pretend to be in control of #permissions while your code takes a #coffee #break ☕. Spoiler: #AI is the real boss here, folks! 😂
    github.com/manuelschipper/nah/ #GitHub #HackerNews #ngated

    #magic #claude #code #permissions #coffee #break
  23. Hacker News @[email protected] ·

    A context-aware permission guard for Claude Code

    github.com/manuelschipper/nah/

    #HackerNews #contextaware #permissions #ClaudeCode #security #GitHub #open-source

    #hackernews #contextaware #permissions #claudecode #security #github
  24. Jupiter Rowland @[email protected] ·
    @Stefan Bohacek My own followers. Hubzilla doesn't grant anyone else permission to see the post, much less interact with or reply to it.

    Essentially, here on Hubzilla, "followers only" amounts to posting to a privacy group (think Mastodon list, but more powerful) that contains everyone who follows me. That wouldn't be a public post, though, and Mastodon would understand it as a DM.

    #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Hubzilla #Permissions #FollowersOnly
    #cwfediversemeta #fediversemeta #followersonly #permissions #cwfedimeta #fedimeta
  25. Jupiter Rowland @[email protected] ·
    @Jasper Burns

    Permissions meet groups


    It gets really interesting when the permissions system is applied to groups. As the owner of a Hubzilla forum, you have the following options:
    • You can control who can see the profile of the forum, i.e. what it is all about. For example, you can only allow confirmed members to see it. Or, in fact, you can only allow certain members to see it by assigning a specific contact role to them. Or you could make it Fediverse-specific: Only those who can be recognised as logged-in Fediverse users can see the profile. Or you can hide it altogether.
    • You can control who can see the contacts, i.e. the forum members, all the same. Like, for example, only a chosen inner circle may be allowed to see the list of forum members, but Joe Average Forum Member is not.
    • Likewise, you can control who can see what has already happened in the forum when visiting the group profile.
    • You can choose to hide the whole forum from the directory, the place where people go to find new contacts (the mastodon.social equivalent is https://mastodon.social/directory), to keep the forum secret altogether by keeping people from finding it accidentally or by searching.

    (streams) and Forte have four different types of group channels instead:
    • Normal: public, group members may upload media to the group's file storage
    • Limited: public, but group members may not upload media to the group's file storage
    • Moderated: like Limited, but by default, posts and comments by new group members have to be approved by the admins; members may have their permissions upgraded and post and comment without approval once they've proven themselves worthy
    • Restricted: private, profile is only visible to group members, stream of posts and comments is only visible to group members, posts and comments are only sent to group members, but group members may upload media to the group's file storage
    Whether or not a group is visible in the directory is a separate switch.

    As I've already said, you can grant individual permissions to your contacts on your personal channel. But you can grant individual permissions to forum users on a forum channel just the same. You can have regular users. You can have users with certain extra privileges. You can use the permissions system to silence users without kicking and blocking them.

    And you can use the permissions system to appoint extra forum admins/mods. You can grant contacts permission to administer your forum. Now, this requires for your channel to recognise visitors and their identities to see what permissions they shall have and to grant them these permissions. And this requires OpenWebAuth. So right now, you can only make forum members from Hubzilla, (streams), Forte, Friendica, Mitra and Tootik additional admins/mods. But you can.

    (9/9)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions #Groups #FediGroups #FediverseGroups #PrivateGroups
    #cwfediversemeta #fediversegroups #fediversemeta #privategroups #permissions #cwlongpost
  26. Jupiter Rowland @[email protected] ·
    @Jasper Burns

    Permissions, part 3: At post level


    As I've already said, whenever you write a post to start a new thread, you also define the permissions of this post. Of this post and of all replies.

    Let's translate this to Mastodon again.

    You know the toot visibility button, I guess. Let's assume it looks and works somewhat different. Especially the visibility options.

    "Public" still exists. It does what it says on the button: It makes your toot public. Oh, and now, it also makes all replies public. There's no replying to your toot with a DM.

    The other three don't exist.

    Instead, as the second option, you have "Only me".

    Right below, all your lists are listed up. You can pick one of them. You can send your toot to everyone on one specific list of yours and to only those on that list, all without having to mention them. Better yet: Only those on that list are permitted to see your toot. And only those on that list are permitted to see any reply to your toot. Killer feature: They can see each other's replies, and they can reply to each other.

    Below that, all groups that you follow are listed up. Again, you can pick one of them. This will have the effect that your toot will go to the group, and it will be forwarded by the group to all its members, but it will not go to your followers unless they're also in that group.

    Below that, there's "Custom selection". This opens another window with each one of your lists and each one of your followed accounts, each with a green "Allow" button and a red "Don't allow" button. Here, you can put together a choice of lists and single accounts whom to send your toot to and a choice of lists and single accounts whom not to send your toot to. Again, only those who receive the toot are also permitted to see it, and only them are permitted to see any of the replies, and no-one can ever change these permissions.

    What sense this makes?

    Imagine you have a list with a certain group of friends in it. One of them will soon celebrate their birthday, and you want to organise a birthday surprise for them. So you send a toot to that list with everyone in it, but without that person who'll soon celebrate their birthday so you won't ruin the surprise for them.

    Or: Imagine you have lists according to which languages people speak. Like, you have a German list, and you have an English list. Then you can put together an audience for a German toot from lists and single followed users, but exclude the English list so that those who don't understand German anyway won't receive that toot.

    By the way: This also covers DMs. And this means that DMs are actually private.

    As Mastodon is right now, you can DM Alice, you can have a conversation with Alice, but Alice could mention Bob and pull him into the conversation. This also gives Bob the opportunity to read the whole thread because he has access to it now. Mastodon only defines to whom a message is sent, but not who is allowed to see it.

    In this version of Mastodon, when you DM Alice, you only grant Alice permission to see your toot and everything else in the thread. Now, Alice can mention Bob all she wants, but she can't pull him into the thread. Bob won't even receive the toot with his mention in it. He is not permitted to see it. You have not granted him permission to see the start toot, and thus, you have not granted him permission to see any of the replies, including the one in which Alice mentions him. Alice cannot change any permissions in the thread. Neither can you, by the way. The moment you send the start toot, all permissions are permanently set in stone for the whole thread.

    This also makes dogpiling by extra mentions in DMs impossible.

    Also, this provides for very effective quote-post control. It isn't allowed to boost posts that aren't public, including replies. It isn't allowed either to Mastodon-style-quote, as in quote-post, posts that aren't public, including replies.

    These DMs have another advantage of DMs on Mastodon-as-it-is-now: If you send a DM to Alice and Bob, Bob receives Alice's replies, and Alice receives Bob's replies, and the two can reply to one another.

    Oh, by the way, there's another nifty button. A speech bubble. With this button, you can allow or disallow replies to your post. Mind you, again, this only works when you start a thread. You cannot allow or disallow replies to a reply that you post.

    Now, how does Mastodon-as-it-is-now handle DMs from Hubzilla, (streams) and Forte? It sees them as Mastodon DMs, and it treats them like Mastodon DMs. The downside is, if I send a restricted-permission post to Alice on Mastodon and Bob on Mastodon, both perceive it as a Mastodon DM. Both can only reply to and converse with me. They can't see each other's replies, and they can't reply to each other.

    (8/9)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions #ReplyControl
    #cwfediversemeta #fediversemeta #replycontrol #permissions #cwlongpost #cwfedimeta
  27. Jupiter Rowland @[email protected] ·
    @Jasper Burns

    Permissions, part 3: At contact level


    Let's go one level further down. The second level of Hubzilla's permission system is per contact. On Mastodon, that'd be those whom you follow.

    If Mastodon was like Hubzilla, you'd have the possibility to create permission templates which you can then assign to those whom you follow. (Hubzilla calls them "contact roles", by the way.)

    Like, you could make one template for those whom you really trust. You grant all permissions in that template.

    Then you could make one that's more privacy-oriented. You only grant permission to send you toots, fave and reply to your toots and send you DMs.

    In theory, you could also make one for those whom you absolutely must follow, but whose toots you don't want. In this one, you only grant permission to fave and reply to your toots and send you DMs. This, however, only makes sense on something that works like Facebook, something like Hubzilla, where you can only confirm follow requests by also following back because connections are always mutual by default.

    Then you could go to your list of followed accounts. And you could edit and configure them, one by one. You could choose which of these permission templates is assigned to them and thereby what you allow them to do. While you're already there, you could also, for example, add them to lists or remove them from lists.

    There's one catch, though: If you grant a permission for your whole account, you automatically grant it to everyone whom you follow. You cannot forbid one of your followed something your account generally allows. So if you want to be able to choose whether someone is allowed to do something or not, you must not allow it for your whole account, and instead, you must allow it followed by followed.

    (streams) and Forte make things a great deal easier than Hubzilla, by the way: They don't require such templates anymore. Instead, when you go edit a contact, you'll see one on-off switch for each permission, and you can turn each permission on or off right there, right then (provided it isn't inherited from the channel). You still have such templates, but they only serve to grant the same set of permissions to a whole lot of contacts without having to click single permissions on or off for all of them.

    (7/9)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions
    #cwfediversemeta #fediversemeta #permissions #cwlongpost #cwfedimeta #permission
  28. Jupiter Rowland @[email protected] ·
    @Jasper Burns

    Permissions, part 2: At channel level


    The top level of Hubzilla's permissions system is the whole channel. On Mastodon, that'd be your account and everything that happens on it.

    Translated to Mastodon again, for each of the above permissions, your account would have seven or eight choices whom to grant the corresponding permission:
    • Anyone on the internet (only available where this makes sense, it's mostly viewing permissions, but it also includes "Can fave and reply to your toots")
    • Anyone in the Fediverse
    • Either anyone on Mastodon or anyone using ActivityPub*
    • Anyone on the same server as you (mastodon.social in your case)
    • Anyone who follows you**
    • Any mutual followers
    • Only those of your mutual followers whom you've explicitly granted that permission
    • Nobody but you yourself

    *It's unclear what exactly this option means. See, Hubzilla is not based on ActivityPub. It is based on its own protocol, Zot. When it was created, it was the only server software that used Zot, so limiting permissions to Hubzilla and limiting permissions to whatever uses Zot had the same effect, seeing as Hubzilla could and still can also connect to a whole lot of other things using a whole lot of other protocols. So nowadays, "Anybody in this network" may mean anybody using Zot which means anybody on Hubzilla or (streams), or it may mean anybody on Hubzilla which means just that, excluding (streams).

    **This translates to Mastodon badly. Basically, Friendica, Hubzilla, (streams) and Forte know three states of connection. Either a Mastodon follow request, that's a "contact". Or a mutual follower, that's a "confirmed contact" because it's listed on your connections page, and you have control over that connection. Or only you follow someone, that's a "confirmed contact", too, because, again, because it's listed on your connections page, and you have control over that connection. The concept of confirmed follower doesn't exist because confirming a connection request will automatically make it a mutual connection. Remember we aren't talking about Twitter followers and Twitter followed, but about Faceboook friends.

    The choices on (streams) and Forte, translated to Mastodon, are:
    • Anyone on the internet (only available where this makes sense, it's mostly viewing permissions, but it also includes "Can fave and reply to your toots")
    • Anyone in the Fediverse
    • Any mutual followers
    • Only you and those of your mutual followers whom you've explicitly granted that permission

    To stick with Mastodon equivalents, there are a few more settings on Hubzilla (as for (streams) and Forte, I've covered them in the previous comment already).

    I guess you already know the switch that hides your account from Google and other search engines and the switch that makes your account automatically accept follow requests.

    You know that you can mention anyone out of the blue on Mastodon, regardless of whether they follow you or you follow them or not, and they're always notified? Imagine this being notified is optional. And off by default. On Hubzilla, both is the case.

    Okay, so, next, you don't allow anyone on the internet to reply to your toots. But there's an option that "half-allows" this: Anyone on the internet can send replies to your toots, even if they don't have any Fediverse account at all. Now it comes: You have to approve these replies. You have a green button that you can click, and the reply becomes visible, and it's added to the thread to which it belongs. Before then, nobody can see the reply but you. You also have a red button, and when you click it, the reply is rejected and deleted.

    There are two clear use-cases for this. One is when you want absolute control over who replies what to you. Then you don't allow anyone to reply to your toots, but you activate this option. When someone does reply, you can choose whether to let the reply through or delete it.

    The other one is a use-case that doesn't work on Mastodon, namely when you want to run a Hubzilla channel as a fully public long-form blog with a target audience that isn't limited to the Fediverse, and you want everyone to be able to comment on your posts, even without having some Fediverse account and following you first, but you want to keep spam out.

    Lastly, there's the option that if you don't allow everyone to see your images and other media at https://mastodon.social/@jasperb/media, these images and other media can still be seen attached to toots by those who are allowed to see the toots that they're attached to.

    (6/9)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions
    #cwfediversemeta #fediversemeta #permissions #cwlongpost #cwfedimeta #permission
  29. Jupiter Rowland @[email protected] ·
    @Jasper Burns

    Permissions, part 1: Introduction


    Now allow me to explain Hubzilla's permissions system to you. From a Mastodon point of view again.

    Hubzilla's permission system works on three levels. In Mastospeak, the first level is your entire account.

    The second level is everyone whom you follow, individually. Like, you can go to your list of followed accounts and click on them and configure them. Among other things, you can assign to them a set of permissions that, usually, you'll first define. You'll probably have multiple such sets of permissions.

    (Yes, this completely leaves out those who only follow you, and whom you don't follow back. Such a thing does not exist on Friendica, Hubzilla, (streams) and Forte. That is, it does, but you don't have a list of these, and you can't configure these, because they can't do much anyway as long as you don't follow them.)

    And the third level is each toot that is not a reply, and then that toot forces its own permissions hard upon all toots that reply to it. If you reply to someone else's toot, your toot will have the same permissions as the start toot with no way for you to change them.

    Translated to Mastodon, Hubzilla offers the following permissions:

    • Can see your toots when visiting your Mastodon account at https://mastodon.social/@jasperb
    • Can send their toots onto your timeline (I'm being serious here, you can literally follow someone and forbid them to send you their toots)
    • Can see your profile
    • Can see your lists of followers and followed when visiting your Mastodon account at https://mastodon.social/@jasperb
    • Can see both the images and other media in your toots and the images and other media you've tooted at https://mastodon.social/@jasperb/media
    • Can fave and reply to your toots (those of your toots that aren't replies)
    • Can send you DMs

    In addition, there are more permissions that don't translate to Mastodon because they cover features that Mastodon doesn't have:
    • Can upload images and other files and modify existing files at https://mastodon.social/@jasperb/media
      (because https://mastodon.social/@jasperb/media is not a managed cloud file storage, and the only way to add images or other media there is by you tooting them)
    • Can see the webpages you've built on your account
      (because Mastodon doesn't have webpages)
    • Can see the pages in the wikis you've built on your account
      (because Mastodon doesn't have wikis)
    • Can edit the webpages you've built on your account
      (because Mastodon doesn't have webpages)
    • Can edit the pages in the wikis you've built on your account
      (because Mastodon doesn't have wikis)
    • Can send you a toot by visiting your Mastodon account at https://mastodon.social/@jasperb and using the toot editor that's present there to send a toot straight to your "wall"
      (because Mastodon doesn't have a wall, Mastodon doesn't have a toot editor on your account page for people who aren't you, and Mastodon doesn't have this entire feature)
    • Can like or dislike any element in your profile at https://mastodon.social/@jasperb
      (because liking or disliking things in profiles is not possible on Mastodon)
    • Can chat with me
      (because Mastodon doesn't have a chat)
    • Can automatically repost my toots through their account
      (because Mastodon doesn't have this feature either)
    • Can do absolutely anything on my account that I can, just by visiting https://mastodon.social/@jasperb
      (not possible for a whole lot of reasons)

    Translated to Mastodon again, (streams) and Forte offer the following permission settings, some of which are yes/no switches, some are numbers or text fields:
    • Automatically confirm follow requests (yes/no)
    • Allow replies on your start toots from
    • Manually allow disallowed replies (yes/no)
    • Only allow replies on your start toots for so many days (number)
    • Allow DMs from
    • Allow to see your followers and followed
    • Allow to full-text search your account
    • Allow non-followed-non-followers to fave your toots (yes/no)
    • Be notified about non-followed mentioning you (yes/no)
    • Not if at least so many accounts are mentioned (number) (this is spam prevention)
    • Receive toots from non-followed if they contain any of these hashtags (same as following hashtags, only that this is one text field and not a bunch of followed "accounts")
    • Not if at least so many hashtags are in the toot (number) (again, this is spam prevention)
    • Don't allow replies to replies from non-followed (yes/no) (reply guy filter)
    • Show a timeline of your own toots (yes/no)
    • Add your account to the directory (yes/no)
    • Hide your account from Google and other search engines (yes/no)
    • Delete toots and their replies from your timeline if you haven't interacted with them after so many days (number)
    • Allow toots from your followed accounts that are replies in threads starting with toots from accounts that you don't follow

    Again, there are permissions that don't translate well to Mastodon:
    [list]
  30. Manually allow toots from those who request to follow you
    (Doesn't make sense on Mastodon because if someone wants to follow you, you do not have to follow them back; on (streams) and Forte, confirming a follow request does make you follow them back)
  31. Show links to all clones of your account in your profile
    (Mastodon doesn't have nomadic identity)
  32. Don't show whether you're online
    (Mastodon doesn't show whether you're online anyway, it doesn't even have this feature)[/list

    That said, some of these permissions don't make sense from a Mastodon point of view, namely those that handle what people can see when visiting your profile at https://mastodon.social/@jasperb. There would have be some way to identify them to grant them the permissions you've given them.

    Hubzilla has such a way, as do (streams) and Forte. It's OpenWebAuth, a "magic sign-on" system created by the creator of these four for a Hubzilla fork that was backported to Hubzilla and inherited by (streams) and Forte. These three can recognise logins to grant guest permissions, and their logins can be recognised. There are a few more Fediverse applications whose logins can be recognised. This was actually also developed for Mastodon and ready to be merged in, but the patch was actually silently rejected.

    (5/9)

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Privacy #Security #Permission #Permissions
#cwfediversemeta #fediversemeta #permissions #cwlongpost #cwfedimeta #permission
  • Jupiter Rowland @[email protected] ·
    @Jasper Burns
    I'd like to see more of that in the fediverse features like events, groups, moderation, different roles, permissions etc. complemented by secure communication!

    The Fediverse has literally got just about of this right now. Mastodon doesn't. But the Fediverse does because there's stuff in the Fediverse, as in federated with Mastodon, that has it. And it has had all of this for longer than Mastodon has even existed.

    Friendica


    Friendica has
    • federating events
    • groups (which are special accounts)
    • private groups
    • hidden groups
    • moderated groups
    • groups with multiple moderators on the same server
    • a permissions system
    • DMs that are actually private because they're covered by the permissions system rather than just handling who receives a message
    • etc.

    Friendica is from May, 2010, over five and a half years older than Mastodon.

    It was made as an alternative for Facebook right away. It was not meant to be a Facebook clone, though, but better than Facebook while also covering all long-form blogging features.

    And Friendica is fully federated with Mastodon. You can follow Friendica accounts from Mastodon, and Friendica users can connect to your Mastodon account from Friendica.

    Hubzilla


    Hubzilla has
    • federating events (in addition to a non-federating CalDAV calendar server)
    • groups (which are special channels; Hubzilla calls them "forums")
    • various independent options of making groups private that can be combined
    • hidden groups, groups with multiple admins/moderators anywhere on Hubzilla or (streams) or Forte
    • the second-most advanced permissions system in the Fediverse on three levels (entire channel, individual contacts, content) with 17 different permissions and seven or eight channel-wide permission levels for each
    • DMs that are actually private because they're covered by the permissions system rather than just handling who receives a message
    • optional additional encryption (only works within Hubzilla)
    • optional non-federating articles
    • optional planning cards
    • optional webpages
    • optional wikis
    • nomadic (fully portable, decentralised, distributed) identity
    • etc. etc.

    Hubzilla is from March, 2016, ten months older than Mastodon. It was created by Friendica's creator by rebuilding and repurposing a fork of a fork of Friendica.

    It is considered a "decentralised social content management system" that can be just about anything you want it to be because it's so modular. Basically, what's incomplete and unstable at best and an unfulfilled promise at worst on Bonfire has been readily available and rock-solid stable for over 10 years on Hubzilla. And even more on top of that.

    Red, the Hubzilla precursor, was the first software to establish nomadic identity, something that Bluesky claims to be in the process of inventing from scratch. And that was as early as 2012.

    Hubzilla was the very first software to implement ActivityPub. And unlike Mastodon, Hubzilla implemented ActivityPub by the book and largely still does so.

    And Hubzilla is optionally fully federated with Mastodon. In fact, this comment that you're reading right now comes from Hubzilla. Like, you're directly speaking with someone on something that has absolutely everything you wish for the Fediverse to have, and that has had all of it for longer than Mastodon has existed.

    (streams), Forte


    (streams) and Forte have
    • federating events (in addition to a non-federating CalDAV calendar server)
    • groups (which are special channels)
    • private groups
    • hidden groups
    • groups with multiple admins/moderators anywhere on Hubzilla or (streams) or Forte
    • groups with moderated posting and commenting (as in posts and comments from new members will have to be confirmed by the moderators in order to be visible)
    • the most advanced permissions system in the Fediverse on three levels (entire channel, individual contacts, content) with 15 different permissions and three or four channel-wide permission levels for each
    • DMs that are actually private because they're covered by the permissions system rather than just handling who receives a message
    • nomadic (fully portable, decentralised, distributed) identity
    • etc.

    (streams) is from October, 2021. It was created by Friendica's creator as a fork of a fork of three forks of a fork (of a fork?) of Hubzilla.

    Forte is from August, 2024. It was created by Friendica's creator as a fork of (streams).

    Forte was the first software to establish nomadic identity via ActivityPub.

    And both are fully federated with Mastodon; (streams) optionally so, but it is by default.

    I've made a document with a series of tables which directly compare the features of Mastodon, Friendica, Hubzilla, (streams) and Forte:

    https://hub.netzgemeinde.eu/item/0a75de76-eb27-4149-b708-f20b2f79d392

    In fact, this document is on the very same Hubzilla channel that I'm commenting from right now.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #NotOnlyMastodon #FediverseIsNotMastodon #MastodonIsNotTheFediverse #Friendica #Hubzilla #Streams #(streams) #Forte #Calendar #Events #Groups #FediGroups #FediverseGroups #PrivateGroups #Permission #Permissions
    #mastodonisnotthefediverse #fediverseisnotmastodon #cwfediversemeta #notonlymastodon #fediversegroups #fediversemeta
  • Jupiter Rowland @[email protected] ·
    @Rob Ricci @caterpillar @Stefan Bohacek @Ericka Simone This is exactly the problem.

    I'm on both Hubzilla and (streams) with multiple channels, and I've been on Hubzilla under various guises for longer than the vast majority of Mastodon users have been on Mastodon. I guess you can say that I know both very well.

    I can tell you that the possibilities of Hubzilla's permissions system are staggering. It works on up to three levels: for the entire channel (that's "account" in Mastospeak), for individual connections (that's "followers and followed" in Mastospeak), for individual content (posts and and entire conversations, but also images and other uploaded files and documents).

    For example, you can grant or deny permission to
    • see your public profile (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
    • see your connections (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
    • see your public posts in your stream (this requires OpenWebAuth magic sign-on which Mastodon has rejected)
    • send you their posts (this means public posts that aren't replies because replies are not posts on Hubzilla)
    • like (that's "fave" in Mastospeak; you know, the star), dislike and comment on your posts
    • send you DMs
    • see your uploaded files (this requires OpenWebAuth magic sign-on which Mastodon has rejected, but this also extends to images and other media embedded into posts, comments and DMs)

    All in all, Hubzilla has 18 such permissions, but these are the ones that matter from a Mastodon point of view. They can be granted or denied for your entire channel at seven or eight levels, and if they're denied at channel level, they can be granted for individual connections. Imagine that, on Mastodon, you could allow only certain followers to see your profile and your toots. Or you could only allow certain followed accounts to send you their toots. All of this is reality on Hubzilla right now.

    Better yet: You know that you can send toots only to mentioned accounts on Mastodon. Hubzilla exceeds and improves upon this in three ways. First of all, you can send posts to individual connections. Or to a certain privacy group (from a Mastodon POV, that's a list on steroids). Or to a custom selection of individual connections and privacy groups while even being able to exclude certain other connections or privacy groups. This goes way beyond Mastodon's "mentioned = allowed to see".

    But this doesn't only define who will receive your post. It also defines who is permitted to see your post.

    And: The permissions of a post are inherited by the entire conversation. Comments always have the same permissions as the top post. There's no restricting the permissions in a comment, and there's no relaxing the limitations of a comment. It's impossible to pull other Fediverse users into a private conversation by mentioning them if the top post wasn't targetted at them.

    Even better yet: You can allow or disallow comments on individual posts (remember that a post on Hubzilla is only a post if it starts a conversation, not if it's a reply).

    On top of all this, Hubzilla's filters are both vastly more powerful than Mastodon's filters and easier to use. Mastodon requires you to set up one new filter for each word that you want filtered. It's always blocklisting. And it's always account-wide.

    Hubzilla covers Mastodon's entire filter functionality with one or two text fields. You have one blocklist for the whole channel. And you have an optional extra feature named "NSFW" with its own filter list that generated individual, reader-side content warnings for you. The equivalent of defining a new filter on Mastodon is to add a new line to one of these filter lists. Want to back them up? Just copy-paste them into a text file.

    But wait, there's more: Hubzilla also has a channel-wide allowlist. If you only want to see certain content in your stream, you can allowlist certain keywords.

    Hubzilla even optionally has one blocklist and one allowlist per connection. Imagine you could filter individual followed accounts on Mastodon.

    Hubzilla's filter lists support regular expressions. There is also a "filter syntax" that lets you filter by whether a message is a top post or not, whether a message is public or private, whether it's a repeat (that's "boost" in Mastospeak or "retoot" for those of you who still have Twitter on the brain). The filter syntax even lets you use Boolean operators.

    (streams) and Forte are similar. Their permissions are somewhat different (you don't need permissions for wikis and websites if you don't have wikis and websites). The permissions system is vastly easier to use because it's no longer template-based. You can simply switch permissions on and off for your channel as well as for connections. And you can choose to have even more options for reply control.

    Again, all this exists in the Fediverse right now. And most of it has existed for longer than Mastodon. Some of this dates back to the earliest days of Friendica in May, 2010.

    Unfortunately, next to nobody knows.

    For most Mastodon features, the features that Mastodon has are the features that the Fediverse has. If Mastodon doesn't have it, the Fediverse doesn't. Not only is Mastodon the default, but there's nothing that strays from this default. That's why Mastodon users keep wishing for "the Fediverse" to introduce features which Friendica has had for almost 16 years already. Or which Hubzilla has had for over a decade.

    In addition, probably not even 10% of all Mastodon users have ever heard of Hubzilla. Probably not even 1% of all Mastodon users know what Hubzilla can do. And even only the existence of (streams) and Forte is almost entirely unknown outside of (streams) and Forte themselves and Hubzilla.

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #CW #CWs #CWMeta #ContentWarning #ContentWarnings #ContentWarningMeta #Hubzilla #Streams #(streams) #Forte #Permission #Permissions #ReplyControl #ReplyControls #Filter #Filters #MastodonCentricism #MastodonNormativity
    #mastodonnormativity #contentwarningmeta #mastodoncentricism #cwfediversemeta #contentwarnings #contentwarning
  • N-gated Hacker News @[email protected] ·

    🚫 Oh, the irony! In a riveting twist, our tech wizards decided to jump ship from #OpenBSD to #FreeBSD for firewalls—only to lock themselves out of their own blog post. 🔒 Maybe next time, consider #permissions before making grand announcements? 🤦‍♂️
    utcc.utoronto.ca/~cks/space/bl #firewalls #techhumor #irony #HackerNews #ngated

    #openbsd #freebsd #permissions #firewalls #techhumor #irony
  • The Eclectic Light Company [Unofficial] @[email protected] ·

    Big guns for Tahoe problems: which radical fixes still work?

    fed.brid.gy/r/https://eclectic

    #macs #technology #launchservices #lsregister #macos26 #nvram
  • The Eclectic Light Company [Unofficial] @[email protected] ·

    Explainer: Permissions, privacy and TCC

    fed.brid.gy/r/https://eclectic

    #macs #technology #acls #permissions #privacy #sandbox
  • The Eclectic Light Company [Unofficial] @[email protected] ·

    Should you repair permissions?

    fed.brid.gy/r/https://eclectic

    #macs #technology #cfprefsd #defaults #permissions #preferences
  • N-gated Hacker News @[email protected] ·

    🚨 Oh no, the internet police are here! 🚨 #Cloudflare wants you to apply for permission to exist online, transforming the web into a bureaucratic dystopia where filling out forms becomes the new CAPTCHA. 📝 Good luck getting on the "cool list" while you dodge the wolves in Wi-Fi clothing! 🐺💻
    positiveblue.substack.com/p/th #internetpolice #bureaucraticdystopia #permissions #onlinefreedom #WiFiwolves #HackerNews #ngated

    #cloudflare #internetpolice #bureaucraticdystopia #permissions #onlinefreedom #wifiwolves
  • Habr @[email protected] ·

    Почему не работает ping внутри пода в Kubernetes?

    Привет, Хабр! Меня зовут Никита Бахилин, я студент DevOps-курса YADRO. Во время обучения мы с сокурсником Даниилом Уткиным столкнулись с неочевидной проблемой при развертывании кластера Kubernetes. Не могли сделать пинг внутри пода K8s. Материалов, которые полноценно описывали бы проблему, я не нашел, поэтому мы написали эту статью. Надеемся, она поможет тем, кто только начинает работать с известным оркестратором.

    habr.com/ru/companies/yadro/ar

    #kubernetes #linux #capabilities #ping #icmp #permissions #crio

    #crio #permissions #icmp #ping #capabilities #linux
  • Jupiter Rowland @[email protected] ·
    @Kellam⚙️Бур This may come as a surprise, but: Nomadic identity 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 @Mike Macgirvin 🖥️ (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 Friendica, 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 Hubzilla, the Fediverse's ultimate Swiss army knife.

    I am on Hubzilla myself. This channel of mine is constantly being mirrored between its main instance on https://hub.netzgemeinde.eu and its clone on https://hub.hubzilla.de. 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.

    https://hub.netzgemeinde.eu 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 Zot11 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 the streams repository. 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 (streams) 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 @Tim Schlotfeldt ⚓?️‍? 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 @silverpill, the creator and developer of the microblogging server application Mitra. 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 Forte. 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, Mike Macgirvin released Forte 25.3.12, 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 (no shit, I've got wikis on my Hubzilla channel).

    On Hubzilla, I can define individually for any of these whether it's
    • everyone on the Internet
    • everyone with a recognisable Fediverse account
    • everyone on Hubzilla (maybe also on (streams); anyone using ActivityPub is definitely excluded here)
    • everyone on the same server as myself (AFAIK, only main instances of channels count here, clones don't)
    • unapproved (= followers) as well as approved (= mutual) connections
    • confirmed connections
    • those of my confirmed connections whom I explicitly grant that permission by contact role
    • only myself

    There's a whole bunch more permissions than these. 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
    • everyone on the Internet (where applicable)
    • everyone with a recognisable Fediverse account
    • all my approved connections
    • only me myself plus those whom I explicitly grant that permission in the connection settings

    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
    • in public
    • only to yourself
    • only to your connections ((streams) and Forte only; Hubzilla requires a privacy group with all your connections in it for this)
    • 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
    • to everyone to whom one specific non-default profile is assigned (Hubzilla only)
    • to a specific group/forum (I'll get back to that later)
    • to a custom one-by-one selection of connections of yours

    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:
    • Only Alice, Bob and Carol can see the post and the conversation.
    • Alice can reply to me, Bob and Carol.
    • Bob can reply to me, Alice and Carol.
    • Carol can reply to me, Alice and Bob.
    • Nobody else can see the post. Not even by searching for it. Not by hashtag either. Not at all.
    • Nobody else can see any of the comments.
    • Nobody else can comment.

    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:
    • public, and members can upload images and other files to the forum channel
    • public, but members cannot upload images and other files to the forum channel
    • 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
    • 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

    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: I have made a number of tables that compare Mastodon, Friendica, Hubzilla and (streams).

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #Fediverse #Mastodon #Mitra #Friendica #Hubzilla #Streams #(streams) #Forte #ActivityPub #Zot #Zot6 #Zot8 #Nomad #NomadicIdentity #Security #FediverseSecurity #Privacy #FediversePrivacy #Permissions
    #fediversesecurity #fediverseprivacy #cwfediversemeta #nomadicidentity #fediversemeta #activitypub
  • scholar_farmer @[email protected] ·

    I am now in an argument with an administrator over whether or not I can see the documents in a locked folder.

    No. No I can't. All your wishing in the world doesn't change that. I showed you a snip.

    Believe me when I tell you that all I see is "No files have been added to this section."

    DUH

    #permissions #LockedOut

    #permissions #lockedout
  • scholar_farmer @[email protected] ·

    I am now in an argument with an administrator over whether or not I can see the documents in a locked folder.

    No. No I can't. All your wishing in the world doesn't change that. I showed you a snip.

    Believe me when I tell you that all I see is "No files have been added to this section."

    DUH

    #permissions #LockedOut

    #permissions #lockedout
  • scholar_farmer @[email protected] ·

    I am now in an argument with an administrator over whether or not I can see the documents in a locked folder.

    No. No I can't. All your wishing in the world doesn't change that. I showed you a snip.

    Believe me when I tell you that all I see is "No files have been added to this section."

    DUH

    #permissions #LockedOut

    #permissions #lockedout
  • scholar_farmer @[email protected] ·

    I am now in an argument with an administrator over whether or not I can see the documents in a locked folder.

    No. No I can't. All your wishing in the world doesn't change that. I showed you a snip.

    Believe me when I tell you that all I see is "No files have been added to this section."

    DUH

    #permissions #LockedOut

    #lockedout #permissions
  • scholar_farmer @[email protected] ·

    I am now in an argument with an administrator over whether or not I can see the documents in a locked folder.

    No. No I can't. All your wishing in the world doesn't change that. I showed you a snip.

    Believe me when I tell you that all I see is "No files have been added to this section."

    DUH

    #permissions #LockedOut

    #permissions #lockedout
  • Nicolas Fränkel 🇪🇺🇺🇦🇬🇪 @[email protected] ·

    What is #GoogleZanzibar?

    permit.io/blog/what-is-google-

    #permissions #RBAC #ABAC

    #googlezanzibar #permissions #rbac #abac