Conversation

Notices

1. Embed this notice
   Alexandre Oliva (lxo@snac.lx.oliva.nom.br)'s status on Monday, 27-Jan-2025 21:12:34 JST Alexandre Oliva

   • The Real Grunfink
   @grunfink@comam.es thank you for snac, I've just set up my own instance with it, and I'm loving it
   
   there are a couple of features from GNU social that I'm missing, and that I'd like to implement, namely:
   
   * some means to open a thread or a post from my timeline in a new browser tab, so that I can interact with it later, or keep up with a conversation without having to search for it in the timeline again. I'm thinking of turning the "date / udate" field into a link to it/them, though ATM I don't quite see what to link to. I suppose a search might work to find a single post, but there's no existing way to link to a local view of a thread AFAICT. any objections to adding these?
   
   it would be nice if I could like/boost/mute/etc without reloading the page, let alone be taken to the first timeline page. I'd like to be able to middle-click on these buttons so that they'd take action on another tab, and I could keep on scrolling on the current tab without waiting for it to reload, or bringing new posts, or getting back to the initial timeline page, even if we currently try* to get back to the same spot
   
   * indeed, it would be desirable IMHO for these actions to not always take you back to the admin and timeline page, but rather to the same page you're on, so that, if you're e.g. interacting with a bookmark or a search result or any other way to show a post or a thread, you remain on that page
   
   - I liked the way notifications are marked as seen, and I'd love something like that for the timeline as well. I'm thinking I'd enjoy a view that showed me not the latest posts in the timeline, but the oldest posts more recent than the latest one marked as seen, with a button/link to mark those as seen and show another such page. then I could catch up roughly in order, rather than in reverse order. (this reminds me that diaspora had a nice feature of generating timestamp-based "earlier posts" links, so that there wouldn't be repeats as I paged over posts while new posts came in.
   
   are any of these features something that you definitely wouldn't want to integrate into snac? or does any of these need further details for you to tell?
   
   thanks again!
   
   • Embed this notice
     The Real Grunfink (grunfink@comam.es)'s status on Tuesday, 28-Jan-2025 00:17:44 JST The Real Grunfink

     in reply to
     Hi. You're welcome!
     
     Regarding your first point (saving a thread for later replying or reacting): I use bookmarks for that.
     
     Regarding the page reloading after actions, I'm afraid it's not possible without the use of JavaScript, which is a no/no for this project. The action requires a trip to the server, and a response back with the same (or the most similar) content you were previously shown.
     
     And with regard the mark of "below this line, you've already seen this": it has been on my mind for long time, but due to implementation details, it's trickier than it seems. I will implement it eventually, because it's something that I deeply need 😆
     
     Thanks for taking a chance on #snac.
     
     
   • Embed this notice
     Alexandre Oliva (lxo@snac.lx.oliva.nom.br)'s status on Tuesday, 28-Jan-2025 02:29:39 JST Alexandre Oliva

     in reply to

     • The Real Grunfink
     thanks for your prompt response
     
     I figured bookmarks could be used to that end, but they also cause a separate page to be loaded. and that's fine. the problem IMHO is that there's not an option to open that page on another tab, rather than replace the current one. don't get me wrong, I don't want JavaScript, that's one of the reasons I'm in love with snac. but I know it's possible to send actions to the server by opening links on another tab. I don't know why the action buttons in snac don't work that way. maybe it's a GET/POST thing?
     
     I'm glad we're on the same page WRT wanting/needing the "already seen" marker.
     
     is this a good place to discuss future features? or is there a mailing list or somesuch? I generally like to get agreement on feature designs before setting out to implement them, and I've historically participated in projects that used mailing lists quite heavily, even for patches.