Subnostr

Since coming home from Tokyo, work on gossip slowed down quite a bit. I had lost my groove.

I have some excuses or rather explanations. Partly I had cluster headaches (I don't get them as bad as online sources describe, but they definitely come in clusters, feel like stabbing my eye or near my eye, and make it hard to program). Partly I had trouble with jet lag. Partly I had lost my place, having not programmed for 6 days. Partly I was working on my relay. Partly the work needed next didn't seem like fun. Partly I didn't want to step on the toes of my UI team. Partly I felt a sense of urgency and being a rebel at heart I rebel against my own sense of urgency! Partly I felt overwhelmed with all the new information from the conference. Partly I felt overwhelmed with all the NIP changes. Partly I felt overwhelmed with other clients pushing out features far more rapidly than I do. Overall, I had lost my groove.

But I kept at it. Put in the hours. And luckily, over the last few days, somehow, I'm back in the groove. Back to being unable to type as fast enough.

Reply to this note

Please Login to reply.

Discussion

Justin_Tokyo 2y ago

Lost the groove, but found a new rhythm.

💋

Mike Dilger ☑️ 2y ago

In trying to finish the UI for multiple following lists, I'm running into more and more problems that have to be solved first such as

1. Needing a slightly different UI switch widget,

2. More command line functions for debugging,

3. Making the page to list the lists, and

4. Generalizing the Following/Muted list pages to work for any PersonList, then

5. Subscribing to kind 30000 lists and to my chagrin discovering lots of kind-30000 data that other clients created, so then

6. Fixing the menu collapsibility since it is now far too big

7. Adding a list delete that deletes locally and also issues a delete to the relay, but that didn't work, the list just reappeared after I restarted, so..

8. Fixing event deletes on multple fronts, so I can delete these annoying kind-30000 lists that I don't want,

8a. Updating nostr-types to handling deletions by 'a' tag too,

8b. actually deleting local events if they aren't feed-displayable, so they stop interfering (we still keep feed-displayable ones and mark them deleted)

8c. when deleting, delete from all the indexes we can reasonably delete from (without doing an exhaustive scan)

8d. Add a new database to index all the event IDs we have deleted, so we can...

8e. When a new event comes in, check if it is deleted and discard if it is (and is not feed-displayable)

8f. Add another database for indexing all the event addresses that have been deleted, and updating 8e to check that too

8g. Do a migration to populate these new databases, ... but oh shit that requires restructuring everything so you can login BEFORE the migration because the migration needs to index DMs and giftwraps and cannot do that if you are not logged in.

I'm getting a bit tired of this at 8g which is only partly finished.

I'm eliding a lot here too.