Last Notes
Ok, I am officially on vacation. Tomorrow: Mount Rainier! I'm going to attempt to be extremely unavailable for the next two weeks, so hopefully I will fail to respond to any DMs, mentions, or emails. Don't burn down the place while I'm away!
So weird! I will see if I can track it down.
Coracle does allow you to compose notes and choose where the images show up
They only exist in Coracle. Use them, talk about how cool they are, and soon other clients will adopt them.
Just added it to coracle!
https://i.nostr.build/lLZ3n.png
None of that looks like it would be related to the problem, can you do a screenshare of what happens when you try to disable those buttons?
Open the note in Coracle 😉
People are using Coracle's custom feeds! Here are some interesting ones:
#naddr1qv…revn
#naddr1qv…5qk5
#naddr1qv…hdms
#naddr1qv…jnjg
I encourage you to try it out — create your own and paste its address into a reply to this note to share it.
I don't know about that. It looks to me like the cert lasted exactly the expected 90 days.
https://i.nostr.build/BRWln.png
https://i.nostr.build/oM5m5.png
🤔 Thanks, I'll take a look
Yeah, give him a hard time
There will be a sudden spike in people starting streams shortly before RHR ends
Ah, that explains it. I was imagining standard filter behavior, but this is totally reasonable. It is, however, an instance of negative filtering, which some people are rabidly against. It's just baked into the spec rather than included in a filter object.
Yet another great post from my favorite substack, "It's only dark":
> The most famous Mandela Effect is also the least interesting. Did you know it’s spelled “Berenstain Bears” and not “Berenstein Bears?” There are people who will kill you with rocks for suggesting that they remember it being “Berenstein” because that’s by far the more common spelling and not because they shifted timelines, or the simulation glitched, or some great and terrible They changed it.
https://itsonlydark.substack.com/p/consider-the-cornucopia
That would be four weeks from now I believe
Any chance you can take a screenshare or send a screenshot of the dev console?
I just post a note with a link. Some people reposted. I'll try to do it more in advance next time.
I did one last week, it was pretty last-minute. I'll do another one 3 weeks from now
HONEYPOT
brb adding the relay
Derek standing over Pablo like
https://media.giphy.com/media/vzmo81htIGJTMKaMWC/giphy.gif
What is wrong with coffee shops, they're currently playing a soft rock cover of Never Gonna Give You Up
Wouldn't that require current implementations to ignore events with an `h` tag? Seems like you'd want to exclude notes belonging to a group. Of course, NIP 72 has the same problem currently.
If you un-select the read/write/inbox chips, next time you come back to the page those cards will be gone.
@nprofile…ss4n myrelay.page is currently down it looks like.
Store them locally, allow users to persist them manually or in batches. I don't think drafts benefit that much from interoperability.
I used to go through periodically and close some, I should probably do another pass. The surprising thing is probably 80% of the open PRs are still worth having, since they represent unresolved issues or different ways of approaching things. Nostr protocol development is chaos and we basically just have to get used to it.
> we’re not problem solving together, and each of us get tangled in our own patch of technical weeds.
Lots of ways to fix this:
- Dev standup calls
- nostrtalk.org
- NIPs repo
- Using nostr
But I think pitching in to existing projects could be the best of all, because it avoids creating yet another isolated patch of weeds, and contributing energy towards projects that already have momentum. It allows for collaboration on design as well as implementation too. The main downside is competing visions, but if you have suggestions for improving invite links in coracle I'm all ears.
That's defined here: https://github.com/nostr-protocol/nips/pull/933
It's an attempt at interoperable read receipts for notifications. I've had trouble getting them to work smoothly though, so I'm not sure I'll keep them.
As usual 😅
I know we talked about this at one point, but I don't remember the details. How would I send e.g. a calendar event to a NIP 29 group? Just `h` tag it? I thought the purpose of the new kinds was to namespace content so that it doesn't leak outside the group. You'd need the same mechanism for every kind, which seems like @nprofile…2kfz 's preferred approach. I think a repost-like event with the standard event stringified in the content would be an easy way to support any event kind within a group.
Click through and find out which relays are failing to connect/authenticate or are very slow. Lemme know if there's a bug and everything is actually ok.
I'd be inclined to ignore them, because it violates the plaintext rule (the event requires parsing to correctly display), but I don't think it's too important either way.
Coracle has this, called invite links
I am an experienced hiker 💪
But don't worry, we're not doing any mountaineering
😅
We'll be sticking to the lower elevations and thawed parts of the trail, so hopefully we won't hit anything too gnarly. But yeah, planning to prepare well.
Just booked my wilderness pass for Mount Rainier this morning! Going to spend two nights out near Olallie creek, and hike some of the Cowlitz divide. This is the first time I've gone backpacking just with my oldest son, and I am stoked for it.
I think what he did was ensure Dan will never join 😂
Thanks, that's actually really helpful. Coracle sort of has all those things, but differently configured than you probably expect (and with more burden on the admin vs mods, which Coracle doesn't really support). For 1 and 4 you can set the group description. 2, 6, and maybe 3 can be covered by custom feeds. But obviously designing those things in a more purposeful way would be worthwhile.
Don't know, the article doesn't say
Not today, people were saying every week seemed a bit much. Planning another one for late July, but there's no reason other people can't pick up the baton
https://github.com/hzrd149/blossom
https://blossom.hzrd149.com/
Yep, his programming talks are second to none. If you squint, the things that make nostr cool are actually functional programming concepts.
This is hilarious, love micro apps
lol. lmao, even
https://sansec.io/research/polyfill-supply-chain-attack
I credit Rich Hickey for making me capable of being a nostr developer.
Just a sparrow, learned about @nprofile…z4g5 just last week — might put one together at some point
Proud of my son. He decided over a year ago he wanted to buy a kayak. He sold worms last summer on the side of the road, and cookies this summer at the farmer's market until this past weekend he was able to pay $150 cash for a kids' kayak.
He earns bonus points because he's now (temporarily) on zero fiat, but owns a decent amount of bitcoin (for an 8 year old).
It's a fork of some foss video conferencing software, with nostr sign in
Wait, you're unicycling 900 miles?
Click on the buttons at the top. The three dots allows you to load saved feeds and browse uther peopke's feeds (under manage). The filters button lets you customize feeds.
Yeah, confirmed this is an opengraph thing, or at least a linkpreview.net issue
I think it's good, we're done here.
There is a cache invalidation bug in Coracle that I haven't figured out yet. Sometimes all saved events get dropped for some reason. It could be indexeddb being finicky, or a bug in my code, not sure yet.
Ha weird, I'm seeing that too. My guess would be a lack of opengraph data resulting in a weird thumbnail?
Congrats Will, you deserve it!
You're making us watch a disney movie?
Same, come hang out with me and my son. We're going caving at some point.
Always a bad idea to release an update on Friday afternoon, but I'ma do it anyway.
Coracle 0.4.8 is out — this fixes a few bugs that were reported this week, but it also adds support for kind 10050 inbox relay lists, and adds a prompt in feeds to donate to support development. This is dismissible, but let me know if it becomes too annoying.
Hope everyone has a great weekend!
# Changelog
- [x] Add support for kind 10050 relay lists
- [x] Toggle nip44 messages based on 10050 signaling
- [x] Fix settings being stale until reload
- [x] Fix WoT not being applied to mute replies
- [x] Add developer donation prompt
- [x] Add WoT information to feed cards and search
- [x] Fix group updates not getting saved
- [x] Add relay hints to group/community tags
Wow, what amazing timing. Glad to hear she's through.
Sorry, I don't mean "yeah" you contradicted yourself, we were just talking past each other for a while.
Yeah, when I asked that I was fishing for the answer I eventually gave that you have to start with anchors into the real world not based on simple trust attestations. I just wanted to hear how you solved the infinite regress problem of closed systems, because it sounded like you were claiming your algorithm covered that. Eventually you agreed that in order to bootstrap someone with zero followers or attestations, you need to anchor those in the real world. So, it was a circuitous route but we got there eventually.
Yep, completely agree with that. My point is that there are different onboarding scenarios, and non-wot approaches need to be part of a comprehensive onboarding strategy. In a bootstrapping scenario, 1-hop wot and grapevine are equally useless. This isn't to say that there aren't appropriate scenarios for either solution.
This sums up the difficulty with interoperability, and is true of nostr development as well. Everyone wants their products to work seamlessly, but at the end of the day it's a lot easier to implement your splashy new feature without regard to the rest of the ecosystem.
Well, not really, but you don't seem to understand what bootstrapping means. It's short for "pulling yourself up by your own bootstraps", meaning you have no one to help you. Saying there's no bootstrapping problem _if_ you have one follower is a contradiction in terms.
There are ways around this, but no direct-propagation-based web of trust algorithm can do it, by definition.
This wouldn't fare any better than a straightforward wot threshold of 1, unless I'm actively looking for new follows. This is fine for that. But it still doesn't solve WoT bootstrapping, because you're assuming a social onboarding. Not everyone has an initial follow.
Where do these high quality data points come from, and how do they bootstrap their own reputation?
I agree social onboarding is the ideal, but I don't think it will apply to everyone. Platforms following new users (like Tom from Myspace!) is a nice idea, but all it would really do is make those follows meaningless. A similar option would be a site that only follows a given pubkey if they're able to do "KYC" of some form — solve a captcha, have a human conversation, reveal their SSN, etc. That way, you can choose what kind of verification you want to do, and bring that with you as long as the verifying party is trustworthy.
Is this something X had/has? I'd be interesting in a screenshot
And I completely agree that that's a problem worth solving.
LIVE STREAMING the TGFN podcast with Riverside and zap.stream!
https://zap.stream/naddr1qqjxvwp5xcmnzwf494jx2drp956rsvnr943xzct995cnzvfcxcervve58qunvqg4waehxw309aex2mrp0yhxgctdw4eju6t09upzpn6956apxcad0mfp8grcuugdysg44eepex68h50t73zcathmfs49qvzqqqrkvuyqk3l8
It might be harder than you think
Sweet, glad to have a new user! You can use it as a PWA on Android, and I'm slowly working on Google's play store requirements to get it on there.
I time connections out after a minute of inactivity. When I re-connect to pyramid, it refuses the connection. You can see the 1.3 minute connection in the middle here, with two retries (one minute after the first one, then again one minute after that):
https://i.nostr.build/8G8nJ.png
A low-data client with a good ux would be awesome. Gossip does some of this, but it's desktop
This is coming to Coracle and Gossip at least. It's been talked about, just needs some time to bake.
How many of your NIPs have been adopted and merged? I know Vitor has picked up a few, but most NIPs emerge out of developers solving their own problems, not other people offering solutions.
I began my nostr journey by writing my own protocol. Fiatjaf dismissed me as an academic, until I gave up on my ivory tower and started writing real software - on nostr, because I realized I couldn't build a protocol on my own. I think he was right to do so.
Sort of interesting to wonder why influencers do these exclusive deals. It must be mutually beneficial. The benefit to the platform is obvious, they attract users because the users want access to the content. For content creators I'm less certain. Is it that they get to ride the wave of the platform's marketing machine? Or do they just get paid more by the platform? In either case, is this something nostr can compete with? I suppose the users we attract will be a result of the content creators we attract. And those people will not be here for the money, but out of principle, or because they have nothing to gain from big platforms. Which means we get the best, the weird, and the small. Which is ok, but doesn't really set nostr up to steamroll platforms, at least until interop and UX become so much better that users begin leading creators.
Please do, writing specs only goes so far, it's much better to back them up with real world use cases.
Formatting isn't perfect, but it works on mobile too
https://v.nostr.build/aQWwZ.mp4
Opportunity cost can be painful
Ah, a contrarian opinion! I will at the very least allow you to opt out.
Nah, it's just like any other list item. The editor would be annoying, but it's really not central to this.
Bro were you not alive in the 2000s this is a classic
How annoying would it be if one of these showed up every 100 or so posts?
https://i.nostr.build/jY2vg.png
But boy does it have blockers
Bounties I think have some utility, but they've mostly been abandoned. We mostly work on what we want, and either apply for bounties or try to build a business (no one's been successful yet). There's some collaboration, some competition, and a lot of chaos, because we're all building different products on one protocol.
Thanks, I'll look into it!