Conversation:
Notices
-
Agreed. User definitely needs to be in control, but so does the Admin. The admin needs, and must, have ultimate control, because it's the admin that's footing the bill most often, and the one that's going to be held accountable for the content that appears. If a node popped-up in … let's say … Texas … that was speficically for neo-nazis and white supremacists preaching …
-
!gnusocial really needs the ability for users and admins to block all content coming from a specific server. Blocking a user still shows their posts in /main/all … Definitely need the ability to block a hub as well as a user. Yes it's censorship. The right to speak freely must not impugn the rights of others not to be forced to hear/ read speech they might find offensive.
-
@vinzv I feel you, and I certainly don't want my users' content appearing anywhere it's not wanted or shouldn't. !gnusocial
-
@drymer Not everybody uses Qvitter. :-) !gnusocial
-
@vinzv One of the things you can do is this:
php scripts/setconfig.php public localonly true
Which will only show your nodes' local content on the public timelines. !gnusocial
-
a #statement 4 'self' censorship! think on #wauholland ' s #word RT @cyberczar Agreed. User definitely needs to be in control, but so does the Admin. The admin needs, and must, have ultimate control, because it's the admin that's footing the bill most often, and the one that's going to be held accountable for the content that appears. If a node popped-up in … let's say … Texas …
-
@cyberczar I confirm this #bug: Posts of blocked accounts still show up in Classic, not as single posts, but as part of conversations and in WholeKnownNet → @mmn !gnusocial
-
!gnusocial Also thinking that it should probably be transparent. Either in the "Statistics" plugin, or somewhere else. Something like: "The admin of this node has chosen to block all content originating from the following nodes: • http://status.hackerposse.com/url/9206 • shitposter.club • freezepeach.xyz" That way users who sign-up for an account can be forewarned that …
-
@benediktg !gnusocial It's my experience that setting that option only affects /main/all … it doesn't affect anything else.
-
@orobouros@loadaverage.org !gnusocial > "At the same time, I don't know where you get the idea that there's any right to not be exposed to offensive ideas." A preacher has every right to proseletyze on a street corner. He does not have the right to force me to listen to his drivel. I have the right to walk on the other side of the street to avoid him. He does not have the righ…
-
@utzer !gnusocial Except: a) When most speech originating from the node is illegal (a neo nazi node spouting holocaust denial propaganda to a German node, or take IamOver18 and a node that's in Saudi Arabia where the mere existence of pornography is highly illegal)… b) An admin might run a node specifically for a target demographic (let's say kids) and doesn't want NSFW conte…
-
In my opinion, I don't think it would be necessary (or good even) for Alice's "blacklist" to be made public. I would consider that to be private information.
That said, an admin/ node-level site-wide "blacklist"/ "whitelist" should very much be public. !gnusocial
-
Maybe this explains it better: *Nobody has the right to an audience.* /cc !gnusocial
-
@orobouros of course instance admins have the right to do what they like with their individual instances. should !gnusocial, though, facilitate widespread censorship?
-
Absolutely. An admin must have full and complete control over what happens on his or her server. Full stop.
The day some outside entity forces me to do something on my server against my will is the moment I turn it off. (I would assume the same applies to most other admins.) !gnusocial
-
@cyberczar no one's talking about forcing admins to do anything-- we're talking about whether additional development to !gnusocial in order to support some admin's desire for enhanced censorship functionality is warranted and appropriate
-
!GNUsocial is !FreeSoftware. If the current contributors don't bake in the ability to block users/groups/tags/instances then someone else will fork the code and do it. And as long as it stays Free Software someone else can fork that code and remove it again.
-
@cyberczar @betafive @orobouros @bobjonkman2 @dragnucs I'm pretty sure there is some instance-blocking functionality already in !Gnusocial. Back when Evan's company was the primary host of !StatusNet, some spammer instances arose that started randomly mentioning people by their full #webfinger addresses. After a short time, this stopped happening. That tells me that the spammers' instances were blocked.
-
Freedom of speech does not grant one freedom of an audience.
!GNUsocial admins should have the ability to decide the content and audience of their node.
-
@lnxw48 #XMPP servers generally already support blocking other nodes by domain name. It's maybe more sensitive in a public environment like this, but rather than "opposing networks" (in a way that's correct though) I think end-users will be encouraged to have multiple accounts in various sub-fediverses :)
-
@hikerus The point of my !FreeSoftware message is that applying a technical means to enforce a moral standard will not work. If an admin objects to offensive content in the timeline they can write "censorship code" to keep it out. If someone objects to "censorship code" in the software, they can just remove it, and run their instance without it. Censorship will happen, whether ou…
-
@hikerus The Terms of Service may provide justification for an admin banning a user, but another instance with different ToS may not be compatible with my instance's ToS, and any federated messages originating on one instance may violate the ToS of another instance. Never mind that most people don't read the ToS anyway, so even a local user on my instance can post content contrar…
-
@hikerus I think you should probably read what @bobjonkman2 writes again, perhaps try to think of it from a different perspective. He's not actually saying anything that opposes your statements.
-
@hikerus So the TL;DR is: ToS or not, "censorship code" or not, people will do what they like. Now that's freedom.
-
@cyberczar It doesn't if you just unsubscibe does it? !gnusocial
-
@cyberczar @martin !gnusocial IPTABLES is your friend.
Michael Collins
majestyx
mcscx2old is still alive (famous last words)
saul st john
Bob Jonkman
lnxw48 (Linux Walt)
MMN-o ✅⃠
admin
All Hacker Poesy content and data are available under the