If you give your wife a node, there's a good chance that one day she'll come home from work in an already sour mood, her phone will auto-reconnect to her node (which she's still not convinced needs to be kept in her purse), and will then get hammered with public channel notifications. If your wife is like mine, the ultimatum will be something like "fix this or I'm deleting the app." Apparently, this is the fix 🤣
In this episode of Verses We Missed, host Steve Webb reflects on Romans 16:22 and the overlooked figure of Tertius, the scribe who physically wrote Paul’s letter to the Romans. Through historical context, biblical insight, and personal reflection, the episode explores how God values faithful, unseen service and reminds listeners that work done in the margins is never invisible to Him.
Disagree about 'the hard part of nostr'.
I think zaps and relay connections create the most confusion because they seem to be the least consistently reliable elements.
If you zap someone and it fails, you don't always get an explanation for why. And at the risk of sounding like a dick, I don't really have time to care. Just tell me if the problem is on my end. If not, convert the zap to a like and let's move along.
Flakey relay connections are also a problem because they make nostr feel like X or FB when it's temporarily unavailable for a large geographic area.
Example: let's say I check Joe's profile at 3:00 for new content and it's still nothing but yesterday's stuff. I check again at 6:00 and suddenly I see notes that Joe posted at 1:00. Why didn't those notes show up when I checked at 3:00?
Meshtastic Observation/Question:
If I understand correctly, setting your roof node to client_base and favoriting your client_mute handheld causes the roof node to re-broadcast messages sent by the handheld without it counting against your hop count.
I assume this doesn't work in reverse though because when I connect my phone directly to the roof node I see messages in its public channel that never made it to the handheld node.
Also the public channel on my handheld regularly gets messages which seem like they were meant to be a reply to some other message that it never received.
Not sure if something is misconfigured on my end or if this is due to an abundance of high-altitude nodes and people setting hop counts too high.