home.social

#permission — Public Fediverse posts

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

  1. State by State Pending and recently passed #AntiProtestLaws: #Mississippi

    SB 2343: Requiring state #permission for protests near statehouse and other state government buildings

    The law requires that organizers obtain written permission from state law enforcement before holding a protest near the Mississippi #statehouse or other state government buildings. As a result, state officials will be able to approve or disallow protests at the statehouse, including rallies and demonstrations against the actions of state officials. The permit requirement broadly applies to protests near state-owned buildings or any other property that is “occupied by any [state] official” or entity. It applies to protests on the streets and sidewalks “immediately adjacent” to such locations, as well as those that can be “reasonably be expected to block, impede, or otherwise hinder” access to such locations. The process for obtaining a permit is not stated in the law, but is to be determined by rules issued by the state law enforcement agency. Organizers of protests in Jackson, Mississippi, where the statehouse and most state government buildings are located, must already obtain a municipal permit to hold most protests; the law creates an additional state permitting requirement. The law also expands the jurisdiction of state law enforcement over infractions that may occur during nonviolent protests throughout the capitol city of Jackson: The law authorizes state police to make arrests for violations not only of state law, but of Jackson city ordinances “related to disturbance of the public peace” that may occur.
    Full text of bill: billstatus.ls.state.ms.us/2023

    Status: enacted
    Introduced 16 Jan 2023; Approved by the Senate 8 February; Approved by the House 8 March; Signed by Governor Reeves 21 April 2023.

    HB 1243: New Penalties for Protests Near Critical Infrastructure

    Creates new potential penalties for protests near oil or gas pipelines and other infrastructure facilities, including those under construction. The law establishes two new offenses: "critical infrastructure trespass," and "impeding critical infrastructure." Critical infrastructure trespass is defined in the law as knowingly entering onto infrastructure property without authorization or not leaving once notified to depart; the offense is a misdemeanor punishable by up to one year in jail and a fine of $1,000. "Impeding" critical infrastructure is defined to include "preventing legal access to" a critical infrastructure property or construction site. Under the law, such impediment is punishable by 7 years in prison and a $10,000 fine if the impediment results in $1,000 worth of damage or economic loss. If the damage or loss is less than $1,000, the offense is punishable by six months' imprisonment and a $1,000 fine. The law also provides that an organization "that aids, abets, solicits, compensates, hires, conspires with, commands or procures" someone to impede critical infrastructure is subject to a $100,000 fine and liable for a civil action by the infrastructure facility. "Critical infrastructure facility" is broadly defined and among many other things includes oil and gas #pipelines, refineries, water treatment plants, cell phone towers, and railroad tracks-as well as "[a]ny site where the construction or improvement of any [referenced] facility... is ongoing."
    Full text of bill: billstatus.ls.state.ms.us/2020

    Status: enacted.
    Introduced 19 Feb 2020; Approved by House 4 March 2020; Approved by Senate 15 June 2020; Signed by Governor 25 June 2020.
    Issue(s): Civil Liability, Protest Supporters or Funders, Infrastructure, Trespass

    #FirstAmendment #CriminalizingDissent
    #Authoritarianism #Fascism #Clampdown #CriminalizingProtest
    #CharacteristicsOfFascism #USPol #AntiProtestLaws #PipelineProtests

  2. @The Nexus of Privacy And why fork Mastodon, the most lack-lustre, underwhelming, underequipped and out-dated of all Fediverse projects, if the Fediverse already offers what you're looking for?

    Because it does.

    Imagine something that gives you the power to adjust things like
    • who can see your posts
    • who can send you their posts
    • who can see your profile
    • who can see your connections
    • who can comment on or fave your posts
    • who can send you DMs (yes, this is a separate setting)
    • who can quote or boost your posts
    • and many more

    Now imagine these permissions can be given to, depending on the setting, seven or eight different subsets of users, including but not limited to:
    • only yourself
    • only your own confirmed connections (yes, their logins will be recognised)
    • only those of your connections whom you explicitly grant that permission by adding them to a privacy group which grants that permission

    It gets even better: If something is not allowed, it isn't just deleted from your timeline. It is rejected at server level.

    Mind-blowing? Maybe.

    Utter science-fiction? No. Fediverse reality since 2012, almost four years longer than Mastodon has existed.

    Okay, let me add some more stuff on top.

    How about a character limit of not 500, not a few thousand, but infinite?

    How about the option of being safe from instance shutdowns because all your content, your posts, your contacts in both directions, your files, your settings, your everything simultaneously exists on multiple independent server instances?

    Now this has to be a fever dream, right?

    Nope. Reality since 2012 when @Mike Macgirvin 🖥️, already creator of the Facebook alternative Friendica, started developing more and more advanced and powerful Fediverse server applications, from 2013's Red Matrix to 2015's Hubzilla (which still exists, which I'm using) to 2018's Zap and finally to the most recent and most advanced incarnation, established in October, 2021 and still advancing ever since.

    The streams repository.

    Whatever you may want to add to Mastodon, (streams) very likely already has it implemented right now.

    Whatever marginalised, harassed groups may wish the Fediverse to have, (streams) very likely already has it implemented right now. Plus stuff they wouldn't even dare to dream of.

    It has been developed, improved and advanced for 14 years, longer than any other Fediverse project, by someone who, in these 16 years, created three Fediverse protocols and about a dozen Fediverse projects, every last one of them vastly more powerful than Mastodon or any of its forks would ever dare to be.

    I'll let Mike speak for himself:

    Mike Macgirvin 🖥️ schrieb den folgenden Beitrag Fri, 12 Jan 2024 23:38:02 +0100

    A brief overview of the streams repository.

    The streams repository is a fediverse server with a long history. It began in 2010 as a decentralised Facebook alternative called Mistpark. It has gone through a number of twists and turns in its long journey of providing federated communications. The fediverse servers Friendica and Hubzilla are early branches of this repository.

    The first thing to be aware of when discussing the streams repository is that it has no brand or brand identity. None. The name is the name of a code repository. Hence "the streams repository". It isn't a product. It's just a collection of code which implements a fediverse server that does some really cool stuff. There is no flagship instance. There is no mascot. In fact all brand information has been removed. You are free to release it under your own brand. Whatever you decide to call your instance of the software is the only brand you'll see. The software is in the public domain to the extent permissable by law.  There is no license.

    If you look for the streams repository in a list of popular fediverse servers, you won't find it. We're not big on tracking and other spyware. Nobody knows how many instances there are or how many Monthly Active Users there are. These things are probably important to corporations considering takeover targets. They aren't so important to people sharing things with friends and family.

    Due to its origins as a Facebook alternative, the software has a completely different focus than those fediverse projects modelled after Twitter/X. Everything is built around the use of permissions and the resulting online safety that permissions-based systems provide. Comment controls are built-in. Uploaded media and document libraries are built-in and media access can be restricted with fine-grained permissions - as can your posts. Groups are built-in. "Circles" are built-in. Events are built-in. Search and search permissions? Yup. Built-in also. It's based on Opensearch. You can even search from your browser and find anything you have permission to search for.  Spam is practically non-existent. Online harrassment and abuse are likewise almost non-existent. Moderation is a built-in capability. If you're not sure about a new contact, set them to moderated, and you'll have a chance to approve all of their comments to your posts before those comments are shared with your true friends and family. For many fediverse projects, the only way to control this kind of abusive behaviour is through blocking individuals or entire websites. The streams repository offers this ability as well. You'll just find that you hardly ever need to use it.

    Because federated social media is a different model of communications based on decentralisation, cross-domain single sign-on is also built-in. All of the streams instances interact cooperatively to provide what looks like one huge instance to anybody using it - even though it consists of hundreds of instances of all sizes.

    Nomadic identity is built-in. You can clone your identity to another instance and we will keep them in sync to the best of our ability. If one server goes down, no big deal. Use the other. If it comes back up again, you can go back. If it stays down forever, no big deal. All of your friends and all your content are available on any of your cloned instances.  So are your photos and videos, and so are your permission settings. If you made a video of the kids to share with grandma (and nobody else), grandma can still see the video no matter what instance she accesses it from. Nobody else can.

    Choose from our library of custom filters and algorithms if you need better control of the stuff that lands in your stream. By default, your conversations are restricted to your friends and are not public. You can change this if you want, but this is the most sensible default for a safe online experience.

    There are no inherent limits to the length of posts or the number of photos/videos you can attach or really any limits at all. You can just share stuff without concerning yourself with any of these arbitrary limitations.

    Need an app? Just visit a website running the streams repository code and and install it from your browser.  

    Nobody is trying to sell you this software or aggressively convince you to use it. What we're trying to do is show you through our own actions and example that there are more sensible ways to create federated social networks than what you've probably experienced.

    You can find us at https://codeberg.org/streams/streams

    A support group is provided at @Streams

    Have a wonderful day.

    Mike Macgirvin 🖥️ schrieb den folgenden Beitrag Sun, 14 Apr 2024 23:13:02 +0200 Here is what we've created:

    Conversations: communicate directly with the people in the conversation, not have completely isolated conversations with your followers and their followers shouting at each other -- and neither audience seeing the responses of the others.

    Permissions: If you haven't been given permission to speak, you aren't part of the conversation.  If you have not been granted permission to view a photo or video, you won't see it.

    Audience: Your choices go far beyond public and not public. Yes, we have groups. We also have circles. You can also just select a dozen people right now and have a conversation only with them.

    Nomadic identity, amalgamated identities and single sign-on: Site and project/product boundaries don't exist. It's one big space and you are you - no matter what service or services you use.

    Post limits, photo limits, poll limits: None.

    Rich content: Use markdown, bbcode, or HTML. Any of them or all of them.

    Rules: You make them.

    Algorithms: You can install them if you want. You can remove them. You control them and can tweak them.

    And much more.

    We are the streams repository.

    https://codeberg.org/streams/streams


    So why does it absolutely have to be Mastodon if the Fediverse has something so much better to offer, readily available in a stable release right now?

    #Long #LongPost #CWLong #CWLongPost #FediMeta #FediverseMeta #CWFediMeta #CWFediverseMeta #FediverseSafety #Permission #Permissions #NomadicIdentity #Streams #(streams)