Conversation:
Notices
-
@sim @takeshitakenji @hakui @maiya @doze49 @dogjaw The law specifically forbids the "transmittal" of that kind of imagery. It's vague and intentionally so, really.
-
@sim @moonman I do actually plan to add a method to allow or disallow attachments, based upon user, group a user belongs to, hashtag, or instance of origin, I just haven't gotten that far yet. I have a long list of things I want to do with postActiv (some of which is here: https://git.postactiv.com/postActiv/postActiv/issues )
-
@sim @moonman I actually plan this to be something you can do both user level (so if you don't like Mastodon for instance, you could just disallow that instance as a user), and on the server level (so I could disallow images or links from smuglo.li as an example, to be able to open up federation without having to worry about legal reprecussions)
-
@moonman @sim This is actually the genesis of postActiv - this idea. It wasn't something Mikael was keen on writing himself, so I forked GNU social to work on the codebase myself. And then all the other ideas I've had have also happened and I've been picking away piece by piece at progress as I can.
-
@moonman @sim The rendering engine rewrite is the primary prerequisite to this, because there is just /no way/ you are doing this in the existing GS rendering engine without HUGE performance hits, but Smarty can do this quick and easily as long as enough information is exposed to it.
-
@sim @moonman I will make it transparent on the server side, as much as possible, but I do not think I will make the social graph transparent as to individual user choices, as per @verius' concern about this being used to network block bots (and it could also subject people to harassment over blocks, mutes, etc)
-
@sim @verius @moonman A server sanction affects everyone, so they have a right to know its in place. No one really has a right to know any more about how you're choosing to associate personally any more than you choose to say to them, however.