> I wish there was a decentralized effort I could help crowdfund.
There are *heaps* of decentralized efforts you could help crowdfund! Jami, for example, is entirely P2P (no servers). I suspect it would be help tremendously to have a paid designer or two to work on the #UX and coordinate formal testing. That way, the engineers could focus their time and energy on improving the performance of the back-end, and adding features.
What do you think @AmarOk ?
Chances are everything Tidelift does could be done without any client-side scripting at all.
@Gargron maybe you could put the signup page on mastodon.social behind a few clicks?
* have a 'new account' button on the front page
* that links to a second page explaining why you'd rather folks join a different instance, and offering a link to joinmastodon.org (and maybe fediverse.party?)
* at the bottom of that page, have 'no I *really* want to be on mastodon.social' link, which links to actual signup form.
I'm looking for some programmers and #devOps types willing to work on a fork of #Loomio, aimed at orgs who might want to self-host a single Loomio group with subgroups, without the overhead of the full multi-group stack. It would need support for #SSO (using open standards like #LDAP etc), so orgs can integrate their Loomio group with other self-hosted tools. Bonus points for achieving #federation between instances. The existing Loomio stack is #RubyOnRails and #Vue:
I spoke too soon ;) I continued testing Jami and hit a number of problems with text messages delivery, even though the other user shows up as online, and with video message delivery. Something to do with the connection between the UI and the network daemon perhaps? Voice message was worked pretty reliably, but now it's giving me an error "unjoinable peer".
@clacke well, it's not possible without the message sync feature. Once that's shipped, I guess we'll find out if they've thought of it ;)
@clacke OK that sounds ... far beyond the skills of the average user. Hopefully once they ship the group chat/ message sync features, they will consider having the mobile app looks for a desktop app on the same account to use, and sync messages from that, and only connecting to the P2P network when that's not available.
@clacke I don't exactly follow what they said, do you?
@clacke the desktop app is worth a play.
> maybe have a true peer in your home and use your phone as a satellite to that peer.
I suggested exactly this the other day. One of the devs replied:
♻️ jami has improved markedly
@clacke I spoke too soon ;) Continued testing and hit a number of problems with text messages delivery, even though the other user shows up as online, and with video message delivery. Something to do with the connection between the UI and the network daemon perhaps? Voice message has worked pretty reliably so far.
@hambibleibt the biggest problem with #Tox from a #UX POV is the fragmentation across OS platforms. Apps for some OS have group chat, while others don't. Anyone could develop an app compatible with the protocol set #Jami uses, but the dev team has an app for each major OS, and features roll out across all of them at the same time. Jami also seems to progress steadily, while Tox dev seems to have been in hibernation for some time.
... and #MachineTranslation:
@feld it's about strategy, not purity. It's worth planting tomatoes for next month even when you can buy them from a corporate big box store today.