-
Notifications
You must be signed in to change notification settings - Fork 78
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make replying more intuitive #40
Comments
hmm, how about a "reply" button that opens the thread in a lightbox? or takes you to the thread? |
simple idea: ...why not this way people would click it. I would |
Beyond the UX issue, I've discovered the actual issue here is threads do not work when you're running the lite client at a port and serving it up at a url. When you click a thread, it just opens patchbay in a new browser window. Threads do work when you save the lite client to your desktop. This is also a faster experience because the browser isn't downloading 2mb of javascript every time you reload the page. @benjajuarez are you using the lite client from ssb.evbogue.com or did you download the patchbay-latest html file from my site? |
@evbogue do you have ssb-links and ssb-query installed? |
@dominictarr I didn't have them installed on my server. Installing ssb-links and ssb-query fixed the permalinks issue at http://ssb.evbogue.com/ |
@evbogue aha, I see it. when you click re: link it opens it in a new tab. |
Aha, no, the problem at Which assumes that any http link is external. Instead, we need to check if it's on a different domain, |
fixed in 1.7.6! |
oops, no i broke other stuff... |
okay fixed in 1.7.7 |
confirmed fixed when deployed to ssb.evbogue.com |
I believe 1.7.7 and #41 resolve this issue. |
I've noticed from on-boarding a few people into the lite client that it's not intuitive how to reply to a post in Patchbay. Most people seem to reply with a new message in the stream, which isn't the correct UX for threads.
I don't have any ideas about how to fix this, but I figure I'd open an issue about it.
The text was updated successfully, but these errors were encountered: