Notices by 🌈 BarbaPulpe 😇 ᴹᵃˢᵗᵒᵈᵒⁿ (barbapulpe@gayfr.social)

🇫🇷 J'ai activé un robot pour faciliter la création de comptes XMPP à partir de Mastodon (fonctionne aussi depuis Pixelfed). Essayez ! C'est sympa, la messagerie instantanée.

🤖 Suivez ou mentionnez @xmpp_bot pour créer votre compte.

🔄 N'hésitez pas à le faire savoir et à inviter vos potes pour des interactions plus riches !

🇬🇧 I activated a robot to facilitate XMPP account creation from Mastodon (works also from Pixelfed). Try it out! Instant messaging is cool.

🤖 Follow or mention @xmpp_bot to create your account.

🔄 Spead the word and invite your friends to join for richer interactions!

#xmpp #gayxmpp #movim #gaymovim

@dansup @pixelfed @loops
Great news! What are the main backend server requirements? PHP, Postgres, Redis...?

@dansup
Sorry but definitely no, it goes against a philosophy of decentralization and free software. I am happy to volunteer contributions, not to pay a fee to a central authority. Just my pick, sorry if I sound harsh but it's definitely against my principles.

@dansup
And I guess the underlying server dependencies: postgres, redis,...?

@dansup
Great initiative. What is the technical stack used by Loops?

@dansup
I'm more worried about an exploit on a user (pixel, www-data) which is in the redis group.

@dansup
Do we actually need the ability to edit S3 keys? This is a very rare task and multiplying the key storage to several locations does not seem good for security, to enable a task which does not require to be done from the UI in my opinion.

@dansup
Even the S3 portal UI will only show you the secret once (on creation of the API key). Compromising that key leaves all your files open to leakage or deletion, so I'm very cautious in storing it in a redis cache unencrypted.

@dansup @pixelfed
Great!

A higher priority for me is localization: any way we can help in templating and avoiding to have to edit PHP source code to translate all texts? And fear of redoing some of the job when updating.