20% of my feeds are like this:
b.c7.ee/u/andrewismusic/rss.xml (instance not open to the public any more):
◸―――――――――――――――――――――――――――――――――――――◹ ···< | 500. That's an error. | >··· ◺―――――――――――――――――――――――――――――――――――――◿ ╱ Are you visiting this website? Not sure what's going on? ╲ ╲ You might want to come back later. ╱ TypeError: Cannot read property 'split' of null on line 2 at eval (eval at wrap (/app/node_modules/pug/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:10:23) at eval (eval at wrap (/app/node_modules/pug/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:30:4) at template (eval at wrap (/app/node_modules/pug/node_modules/pug-runtime/wrap.js:6:10), <anonymous>:53:7) at TimelineEntry.fetchFeedData (/app/src/lib/structures/TimelineEntry.js:285:17) at processTicksAndRejections (internal/process/task_queues.js:93:5) at async Promise.all (index 9) at async Timeline.fetchFeed (/app/src/lib/structures/Timeline.js:97:3) at async /app/src/site/api/feed.js:61:19
/u/andrewismusic seems to be up to date with ig. On the RSS client side though, /p/CLckMv0hY66 is the last post received.
The feed seems to work on snopyta.
I'm using docker, I removed the container, nuked the db, and started it again. The issue persists on the same feeds.
Same result with atom feeds.
Nice, didn't know that. Haven't used sh for anything other than tickets. Pardon for my knowledge.
I have for this in GitLab, and hoped it would appear in GitHub.
Tracking progress, and listing everything deemed useful has been usually done in Etherpad.
I would suggest a 'whiteboard', what's editable by everyone (or only contributors, edit history should be enough to prevent abuse).
It's a great way to keep people working on the ticket from reading everything again; a summary, current status (collaborative checkboxes are on GL), and more can be accumulated there.
The current description could move to author's first comment, possibly highlighted.
Quite frustrating to lose all the user has written after doing a check 'did I just file a duplicate' (no you did not..), or adding additional details, refrencing other tickets.
One way to do this would be to also submit the ticket title and description with the search, include the title and description with search results. I have seen browsers retain the text content themselves as well. Don't know too much about it.
Light JS is also an option.. ..probably rather not.
Comment threads would be nice, keeping discussion organized, easy to start reading from zero (40 comments!), and if reply is in a thread, don't send everyone a notification.
Having other 'reactions'/'emojis'/etc doesn't really server purpose.
A simple +1 and -1 for the ticket would be nice.
Helps avoid 'me too'; indicating the count on ticket list provides developers a quick overview of demand.
Comments could have +1/-1 as well, maybe in the future, maybe never.
Pasting it gets the following preview:
Bibliogram Post by Tennyson Gallery of 2 images. @disclosure Hey Howard! Cooked somethin’ up for ya! feat. @erezzobarymusic #BeGuy
There are 2 videos.