Notices tagged with gnusocial, page 97
-
It just did this again, had to clear out 59 rows where transport=xmpp. The "xmpp-out" transport queue items go through no problem. Need to figure out where this transport=xmpp is coming from because it backs up the whole queue when it happens. !gnusocial
-
@cyberczar And why do you think !gnusocial was waiting for your porn instnace? On the internet there are thousands of porn sites, why do you flood a network of volunteers who love their hobby of free software?
-
@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…
-
And what about the !gnusocial admins that don't want my node's porn? Shouldn't they have the right to restrict content from my node?
-
@cyberczar Can you (you're not the only one so don't take it personally) please stop mentioning the #GNUsocial group wiht a bangtag in all the posts of that thread about blocking full instances?
It keeps bumping up in my home timeline and I don't really think that every new post there carries enough weight in the discussion to bump up it up ;)
-
!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.
-
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.
-
Sure, if you knew the IP address of the offending node, but what if you have more than one node on the same server? (Shared hosting maybe)? Or there are multiple IP addresses? Or what about nodes that are behind Tor hidden services? !gnusocial
-
@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.
-
!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.
-
When ISIS/ ISIL/ Daesh or the next extremist group stands up their own !gnusocial instance and starts to federate with the rest of the network, you're going to wish admins had the ability to block whole nodes.
-
@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
-
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
-
!gnusocial why is /statuses/public_and_external_timeline not listed in the api docs?
-
@orobouros of course instance admins have the right to do what they like with their individual instances. should !gnusocial, though, facilitate widespread censorship?
-
@attila !gnusocial do you mean something like this? "uri":"tag:quitter.se,2016-02-28:noticeId=4867065:objectType=note"
-
Maybe this explains it better: *Nobody has the right to an audience.* /cc !gnusocial
-
To be more clear: data sent back per dent by e.g statuses/friends_timeline.json !gnusocial
-
Am I right in concl. that the data sent per dent does not have info to find what instance the poster is on? !gnusocial #late2party
-
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
orphean
Hiker
Bob Jonkman
Michael Collins
MMN-o ✅⃠
lnxw48 (Linux Walt)
saul st john
vloev
attila
All Hacker Poesy content and data are available under the