Avatar
Peter K
f962906847bbc3de198e685342f117206ec09d7115adf10c947f23a681b3fbb4
Software engineer, outdoor enthusiast, occasional ham radio operator, aspiring hunter and homesteader, bitcoiner, neopagan druid, used to race sailboats, too many hobbies to list. Based in Northern Virginia. I don't like, only zap.

It should span all clients, but like everything noatr-related, it depends on it getting relayed correctly. And clients supporting it.

Today I was supposed to go to a friend's house for a crawfish boil, but they had to cancel, so we are having a lazy day around the house. Hopefully I'll have some time to work on some nostr related projects, but just spending time with the kids and having dinner I actually cook are going to be wins.

#grownostr

Remember how earlier this week I said I had to plan my D&D game for tonight? Yeah, well, that didn't happen. Guess I'll just wing it. Wish me luck!

#grownostr, #dungeonsanddragons, #accidentallyImprovDM

OK, new nostr proposal.

IF a client supports muting of hashtags per NIP-51, AND it supports NIP-36 content warnings, then it SHOULD treat any blocked hashtag as if they had the content-warning tag with the name of the hashtag as the reason. Unless there's actually a content-warning tag already, in which case that takes precedence.

Guessing no clients would be impacted by this? Is this something that should make it into a NIP?

Having thought more about this, I think clients that implement Mute lists from NIP-51, handle hashtag muting, and also implement NIP-02 contact lists (pretty much all of them) should provide either a switch to determine which takes priority, or clearly document which takes priority.

A potential enhancement to the protocol would be to add a "Prioritized Mute" and "Prioritized Contact" list types, that include a numeric priority, and allow them to be shuffled together in a way that makes sense. But that's really complicated from both a client and a user's perspective, and has some potential confusing side-effects while we wait for all clients to support it.

Another possibility I thought of while typing this up is for a client to show all content for any followed user or hashtag, but if it contains a hashtag that's blocked, treat it as if the content-warning tag was applied (which I guess warns you or blurs it out rather than show it by default?) I don't actually know how, or how many, clients implement the content warning functionality. I may see if I can test it.

Ah, nope, not there. Closest I've been was hiking the Haute route through France/Switzerland.

Good almost noon, Nostr.

I'm being really productive at work, which means I'm not being very attentive to Nostr. But I jumped on before lunch, to just look around.

Following up on my fitness comments from yesterday, I'm feeling pretty solid about my plan, and I think I'll be able to get in shape for my hike in August (leg 2 of the GR5 in France). Last year, for the first leg, I was in great shape, but I hadn't been running, so it was... different. This year, I'm going to have my kids on the weekend more, so I won't be able to bomb out to the Appalachian Trail to hike as often, so I have to make up for it with local/weekday training. I enjoyed the running, when I was doing it a lot, so that's a good option. I've also got a home bike trainer that I'm trying to use on weekends when I can't hike.

#grownostr, #hiking, #trekking, #fitness, #running

According to NIP-51, it should be possible, but it would be up to clients to implement it, and it's not 100% obvious how follow and hashtag block would interact.

Morning,

I'm on a bit of a fitness kick lately, having started a guided 5k (running) program via my Garmin watch, plus spending some podcast time at home on my indoor bike trainer.

I've always known that it gets harder as you get older, but for whatever reason today's run, only the second of the program, made that hit harder. 3x5/5 minute run/walk intervals, and I only managed to run the first two straight through, walking about 1:45 of the last one. Back in 2020, I was running half marathon distances without stopping. Just goes to show, if you get yourself into decent shape, stay there.

Hopefully I'm well on my way back to that sort of shape, now I just need to get out and swing my sword again (#HEMA), to get that upper body in the mix.

#grownostr, #quantifiedlife, #fitness, #running

Are you using the Alby extension, and logged in? I'd be curious what it looks like if you pull up the extension while you're on the primal.net page, that might give you some hint. Maybe it's not prompting for permissions for some reason, but you can explicitly grant it?

Thanks for the reminder. I'm about 3 addresses behind on updating my license, I guess I should do that.

I've been falling down keeping up with #grownostr lately. Today I'm WFH, which isn't standard for me, so I can take a moment to post something between tasks for work.

I ended up having to go out for coffee this morning (milk had spoiled, and I didn't realize till it was too late). As I got back, it was raining, and I realized that my carport has a tin roof. I may have to see if I can hang a hammock in the carport for days like this.

Today's tasks:

- Figure out what's wrong with a really complicated deployment process for one of our software applications

- Submit patches for the two things I've already determined are wrong with another of our complicated software deployment processes for another

- If I have time, plan my Friday D&D game

#devops, #devopshell, #dungeonsanddragons