thanks for the pointers. I think I implemented some of those changes but I need to double check some of the new API endpoints. for now notifs aren't native to android, which makes them a bit Shakey, but the perk is there are no f-droid blockers for publishing so I'm planning that
check v0.5.0 to see latest improvements and ui nitpicks i ironed out!
v0.6.0 just cut, quite happy with the swipe gestures for replying, as well as some better caching / offline behavior on app cold start.
🔥 That’s great! also, new endpoints:
/feeds/latest/conversations
/feeds/hot/conversations
/activities/for-you/conversations
/activities/to-me/conversations
If u check the webapp you’ll see that now conversations are threaded with recent replies revealed and posts expandable to reveal even more from that thread. These new endpoints deliver all that, so we move from strictly chronological to more “recent discussion” based views. Just more work for the next versions :) lmk if you need smthAs a suggestion, could we stick to either first or second person for those sections and links. ie: either "to me" and "for me" or "to you" and "for you". One of each just adds cognitive load.
it was semi-intentional, here are the complete sentences you can imagine:
“here are posts for you” (site talking)
“these posts are addressed to me” (me talking)
Sure, but why is one statement the site talking and the other one me talking? It's just arbitrary and adds a moment of confusion. Maybe I'll run a poll to see if it's just me.
Wouldn’t it be more confusing if there were two tabs with repeating pronouns? Idk I’m not settled on this. I just picked whatever felt better. They’re more visually different.
Repeating pronouns would not be confusing for me. It would serve to indicate that it's the prepositions which are the important part (which they are). Anyway the poll is now live at so we can see what the majority think.
Side note: is there a better way to refer to one post in another like this than putting the whole URL in there?
Fantastic! About the post linking, I’ve thought about it and can’t come up with a good solution. For now it’s getting shrinked visually to
/post/123 because it’s the app domain. Any suggestions here?I can't really think of anything better off-hand. You could overload the # some more and just follow it with the post number but then there would be chaos if anyone wanted a fully numerical hashtag which is going to happen at some point (new year, for instance).
I like that it shortens it in the rendering as it stands - that's good enough for me. :)
Let’s use tilde ampersand, check .
That works nicely. Although again you will get unintentional usage because
~ followed by a number is often used to mean approximately that number. eg: "we're expecting ~100 people". You are also using it for strikethrough formatting.
Looking at my keyboard the least ambiguous/overused symbol is probably the & - but I'm not sure if that's better overall.I think the ampersand is ok. It's doesn't much historical use for these things and being feels more like an append behavior than movement to or continuation of a conversation.
>_2596, branded but looks and feels awkward
>2596 or >>2596, I like the directionality and punch.