Post AkxXsmC0nkt4fWsQSW by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
 (DIR) More posts by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
 (DIR) Post #AkxXsj4oO4LT0KU8Js by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
       2024-08-12T18:33:33.000Z
       
       0 likes, 0 repeats
       
       Is there a reason why I can't see most profile pics or npub names on next.Nostrudel.ninja for a couple of days, now? I have to go to the profile and refresh and it doesn't stay for long.
       
 (DIR) Post #AkxXskMDcpraybdY5g by 036533caa872376946d4e4fdea4c1a0441eda38ca2d9d9417bb36006cbaabf58@mostr.pub
       2024-08-14T04:42:03.000Z
       
       0 likes, 0 repeats
       
       That's been me for a couple of weeks. I usually have to refresh the page whenever I want nip05 names or profiles to show up. I rarely see pfps. I always have to refresh for content to load.
       
 (DIR) Post #AkxXsl3p0ik39q2N3Q by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
       2024-08-14T04:51:00.000Z
       
       0 likes, 0 repeats
       
       @266815e0 Do you have a ngit repo in GitWorkshop.de, yet? Then I could just create an issue there.
       
 (DIR) Post #AkxXsleKoxwsz57Wy0 by 266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5@mostr.pub
       2024-08-14T04:58:12.000Z
       
       0 likes, 0 repeats
       
       I setup one a few days ago, still learning how it all works
       
 (DIR) Post #AkxXsmC0nkt4fWsQSW by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
       2024-08-14T05:06:42.000Z
       
       0 likes, 0 repeats
       
       Here's an issue for you to try out, then. ☺️https://gitworkshop.dev/r/naddr1qqykum6nw3e82er9dsqs6amnwvaz7tmwdaejumr0dspzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qvzqqqrhny5zxf4f/issues/note1mxvgjuy9c3ytxf8365p6zx2yw2vakz022790rnle97xd50xt6p6svk0c7v/
       
 (DIR) Post #AkxXsmhYuS7mFNdcdU by 266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5@mostr.pub
       2024-08-14T13:08:05.000Z
       
       0 likes, 0 repeats
       
       why are replies kind 1....nostr is never going to work if we keep using kind 1 for every kind of reply...
       
 (DIR) Post #AkxXsnN2QFIkK12kHg by 266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5@mostr.pub
       2024-08-14T13:08:43.000Z
       
       0 likes, 0 repeats
       
       I don't want my replies to git project issues showing up in my social feed... ?
       
 (DIR) Post #AkxXsnsEYGFrsldeuO by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
       2024-08-14T13:15:30.000Z
       
       0 likes, 0 repeats
       
       I thought this was an elegant solution, but it's sort of just stalled.https://github.com/nostr-protocol/nips/pull/1076#issuecomment-1987002929
       
 (DIR) Post #AkxXsoY42jiPyVD46q by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
       2024-08-14T13:22:55.000Z
       
       0 likes, 0 repeats
       
       I like this one.https://github.com/nostr-protocol/nips/pull/1233
       
 (DIR) Post #AkxXspAhj4cjuLHvKy by 266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5@mostr.pub
       2024-08-14T13:34:35.000Z
       
       0 likes, 0 repeats
       
       I's still a fan of using kind+1 for replies but I think I'm in the minority. Still NIP-22 is a better solution than kind 1sanything to stop using kind 1 😀
       
 (DIR) Post #AkxXspijgXqVbtD6Nk by dd664d5e4016433a8cd69f005ae1480804351789b59de5af06276de65633d319@mostr.pub
       2024-08-14T13:36:05.000Z
       
       0 likes, 0 repeats
       
       Kind 1 with a k Tag or a generic comment kind are both "final implementations" (you rebuild it once and you're done). Seems neater than plan Kind 1s, at least.
       
 (DIR) Post #AkxXsqHpa3v1Mjd85I by 266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5@mostr.pub
       2024-08-14T13:44:38.000Z
       
       1 likes, 0 repeats
       
       even kind 1 with a "k" tag wouldn't fix the issue of social clients having to filter out every reply just to show a timelinea generic comment kind would be a clean solution since it would not show up in the social timeline and would allow clients to show just the replieshowever NIP-22 might need to include "p" tags for notifications