hexbear
Hexbear Proposals chapo.chat matrix room.
This will be a place for site proposals and discussion before implementation on the site.
Every proposal will also be mirrored into a pinned post on the hexbear community.
Any other ideas for helping to integrate the two spaces are welcome to be commented here or messaged to me directly.
Within Hexbear Proposals you can see the history of all site proposals and react to them, indicating a vote for or against a proposal.
Sending messages will be restricted to verified and active hexbear accounts older than 1 month with their matrix id in their hexbear user profile.
All top level messages within the channel must be a Proposals (idea for changing the site), Feedback (regarding non-technical aspects of the site, for technical please use https://hexbear.net/c/feedback), or Appeals (regarding admin/moderator actions).
Discussion regarding these will be within nested threads under the post.
To gain matrix verification, all you need to do is navigate to my hexbear userprofile and click the send a secure private message including your hexbear username.
view the rest of the comments
I'm sure the API supports it. If there isn't a tool already, someone should make one. For infosec purposes, think of these two things to balanve expectations:
Deleting history to prevent leaking any level of personal info is good, as is rotating accounts, because it limits exposure and makes it harder for someone else to "connect the dots".
You should assume that anything you post to a website is permanently archived somewhere. If a public website like this one, a person could simply archive hexbear once a day with little effort. Federated instances basically do this in real time. Basically every stateful website uses a database and users have no control over what happens to the data in it - we just hope that admins are careful.
It surely supports it, because before we had federation the delete button used to just delete posts and comments but not the account
I'm sure! Deleting or editing any post must go through the API. Just need whatever authentication/authorization mechanism is needed, which for Lemmy (I believe) is a JWT.
Yup.
It's also the part I have never touched and am therefore unsure about.