We are preparing to release federation support and we want your feedback!
Can you think of any safety, privacy or security features that we haven't announced or already support?
We appreciate any ideas/feedback that can make more safe and secure. #pixelfed
@pixelfed Let's call me a killjoy, but here is an idea of a security posture: letting fellow developers and infosec folks have a look at your code and software in small and/or testing environments before you organize a much hyped upgrade event and have the same unreviewed code handle pictures and data for thousands of users.
Still unhappy that you are not releasing a single line of the code I guess.
The repo (https://github.com/pixelfed/pixelfed/blob/dev/README.md) clearly states
*** do not use this software until there is a stable release ***
And (thousands? really?) users sign up for the pixelfed **beta** and they know this.
Since when is the developer of an open source project not allowed to test their new code before they release it?
(Really, do not try to impose rules upon ppl who devote their time to making things you can pick up for free.)
I am not in a position to impose anything but simply to suggest, and state what makes me unhappy when using and/or trying to contribute to the project.
On « Tweet » sur Twitter ; on « Toot » sur Mastodon. Sur ce réseau social plein de libertés, TeDomum met à disposition une modeste instance. N'hésitez pas à nous solliciter pour la modération ou des ajustements de configuration.