Drive-by contributions scratching an itch may be the inroad to contributing code, but drive-by contributions in UX are not something that happens, that's not how UX works as a field.
For my first post today, I want to send a bouquet to Nolan, the developer of the Pinafore web app for Mastodon and Pleroma. Thanks for creating such a brilliant freedom-respecting UX!
@arcans > more like 1-to-1 IM that have the options to create and invite people to a chatroom
The #UX of most Jabber apps are like that yes. But #Riot (Matrix client) is more like ...
> chatroom-oriented from which you can have 1-to-1 conversations
Either way, the protocols don't determine that. It's totally up to the apps devs. #Pattle (another Matrix client) is more like IM. #Movim (Jabber client) is designed as a social media app, as is Salut-a-Toi.
@kavbojka > 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.
I just forked a thread on #Loomio for the first time. I proposed the feature back when the app was still in beta, so it's great to see it implemented by the Loomio team. The #UX is a little bit non-intuitive though.
@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.
@rek2 you left out #Jami, which has a much more consistent #UX across platforms than #Tox (eg none of the Tox mobile apps I've tried support group chat). You also left out #BigBlueButton, which I keep hearing is much less of a resource hog on the server-side than #JitsiMeet, and I can confirm JM is a massive resource hog on the client-side. I haven't used #Discord but I've heard #Riot (#Matrix client) is a pretty good substitute?
#ShowerThoughts among the plethora of decentralized software out there, two things are being designed and built; #UX (User eXperiences), and protocols for the exchange of data to make those experiences possible. I suspect that the maturing of (re-)decentralized tech will involve natural selection among the protocols until only a small subset are left in common use (standards are a natural monopoly), and the re-engineering of most of the UX on top of those protocols.
Worked perfectly, super easy to use. I was able to choose whether to record my screen and webcam, or just the screen, and which elements of the screen to record (whole screen or particular window?). After asking the web browser for permission to use the mic. and access the screen, it recorded with my voiceover, and presented the result as an embedded video. Then I had the option to download the video, or close and try again. 10/10 #UX
No worries π It's an elegantly simple #UX once you get your head around it. A really well thought out design all round. Because the #Guppe server only boosts posts that mention its group users, rather than storing posts itself, I imagine an instance is fairly @lightweight to run (pardon the pun)
@mmin I think there is a variation of #ZookoTriangle here. Out-of-the-box, Riot is decentralized and user-friendly, but not encrypted. Turn on encryption, it's still decentralized, but not user-friendly. Same is true of #Jami, #Tox clients, and every other decentralized chat app I've tested that has encryption out-of-the-box, #UX hell. All the user-friendly systems I've seen that have encryption turned on out-of-the-box are centralized ones like Signal and Wire. @lnxw48a1