このSNSはなんか使いにくいかもしん…

I want to know too as I’m the founder and was largely responsible for its development 😆

@prologic@twtxt.net @david@netbros.com literally never counted on technicalsuwako’s admin coming to yarn, lol
quite unexpected

@novaburst@twt.nfld.uk I’m quite pleased to be honest 😆 Means we’re doing something right after all 👌

@technicalsuwako@netbros.com / @david@netbros.com What’s the confusing part here? 🤔 Hiw can we improve the UX?

@technicalsuwako@netbros.com Yeah so if you use the “Post Box” at the top, that will create a brand new post. Correct.

If you use “Reply” it will place the Post Box below the Twt you’re replying to (if you have Javascript enabled), “Fork” will for the current Conversation/Thread (we call a Yarn) into a new one.

I’m not sure how else to make this better except to see if @ullarah@txt.quisquiliae.com can do something about hiding the Pos Box at the top behind some kind of HTML section with some CSS and JS. Ideally it would not be visible at all unless you clicked on a button of some kind…

The trick is making this work gracefully so that if you don’t have Javascript enabled, it still works, even if a bit of a degraded UX. The UI/UX of the yarnd Web Interface is designed to be an SSR (Server-Side Rendered) UI with very small use of Javascript with graceful degradation.

@prologic@twtxt.net Maybe having the post box contextual could help? If you are in a thread it will be posting there.

Plus adding a simple label above the post box or in the post button that says “Post in (#THREAD)” or “Reply to @USER” , ecc. can help the UX?

@justamoment@twtxt.net That’s how it behaves now hmmm 🤔 But there are some good points here. @ullarah@txt.quisquiliae.com let’s see if we can make some improvements here when you’re done with the other WIP PR(s) 👌

@prologic@twtxt.net Oh. too bad, I haven’t noticed.

Actually, I had a bit of trouble understanding where a post will go to at first so I spinned a yarn locally with the docker image to try on two accounts created on the spot there to see how it behaved to avoid making mistakes here.

Even when replying on threads I was confused that replying forked with another ID and I couldn’t see it when replying below, I ended up copying manually the current thread id to be sure.😣

@justamoment@twtxt.net We’re going to need your help here to make this a better user experience. Please help us 🤗 I’m biased because I’m used to the current UX, but that doesn’t mean it’s correct or even the best user experience (yet) – I blame myself, I originally built most of it, now thanks to folks like @ullarah@txt.quisquiliae.com it’s getting a lot better 🤗

Hmmm

@prologic@twtxt.net That’s still amazing! 👍

If I can help on the UI/UX then sure!

Except the post box reference the rest is already pretty simple and nice.

A first point I can make is to show a reference of the thread like when you fork in the post box below, that would already make it clear you’re replying there and not globally.

@justamoment@twtxt.net Showing a reference is in the works 👌 Agreed 😅You are welcome to help us improve the UX 🙇‍♀️ Source code is linked in the footer of any pod 👌

@prologic@twtxt.net Okay, I’ll check it out! 👍

Sadly, I don’t know Go Lang though, so my help is limited to the HTML/JS parts. 😁

I can probably contribute the most on the pwa repo.