(More precisely it's one way among others to reinforce learned helplessness, especially as a catalyzer for depression. Inbox flood, senseless notifications flood should the profile be especially active, showing potential for deeper isolation and more contents generation, are other examples.)

Sorry, misclicked. Anyway, here's the link I've meant to insert inline : https://domesticviolence.org/cycle-of-violence/.

As I've said earlier, media should either be click to download or shown in full height (prroportional to the screen width obviously). Forcing people to click to access to media is one way among many others to make vulnerable people more vulnerable. It's predation.

@BonfireBuilders #bonfire_feedback +Bonfire_Feedback

3% of battery. A limit for artists with Instagram is that they can't display several projects on a single account, like they would at a local art market. They generally end up managing one account per project, which is exhausting.

They may pin stories on their profiles with the model "one story = one projects", but they can't show them to non-followers.

@BonfireBuilders #bonfire_feedback

3% of battery. A limit for artists with Instagram is that they can't display several projects on a single account, like they would at a local art market. They generally end up managing one account per project, which is exhausting. They may pin stories on their profiles with the model "one story = one projects", but they can't show them to non-followers. @BonfireBuilders #bonfire_feedback

Hi, maybe we could subscribe to public block lists (e.g. fediblock) if they were formatted in a public open document format like toml, especially if we could for example fetch new versions via Atom feeds or ActivityPub itself?

Eventually an entire extension would be ideal, just like I could reply to tasks, I’d like to be able to reply (if the instance policy lets me do it) to instance block announcements, if possible directly, as a mod, from the social extension; I’d like as well to be able to share these instance blocks to different circles by boundary, as usual, and for example to let a large circle of instance roles follow my instance blocks, and a smaller circle of instance roles comment or interact with these instance blocks (otherwise than by clicking on the "block" button).

The main difference would be, I suppose, that these boundaries would be set by a specific role on behalf of the instance and that you wouldn’t manage the permissions user by user, but instance role by instance role, e.g. if you have moderators and new_followers_monitors on instance A and B, then you let all the moderators on instance A follow the instance blocks, but you’re free to assign different permissions to the moderators on instance B.