128 bits is an awful lot, you’re not really saving any bytes vs string names at that point
Conversation
Notices
-
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:04 JST
Ademan
-
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:04 JST
Sexy Moon
@ademan @rieger_san @benjaminbellamy yeah. my first version was actually just a 16 bit integer id, if we exceed 65k activity types lets just change the protocol then and not worry about it now lainy likes this. -
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:05 JST
Ademan
At least with names you probably need to be engaging with similar problems to run into a name collision
-
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:05 JST
Sexy Moon
@ademan @rieger_san @benjaminbellamy yeah true. i was experimenting last year a bit and also settled on numbers but what i did was hash a name+versionid to 128 bits if i revisit it i will revise it to also hash your author id into it so there's not likely to ever be a collision. 128 bits is a lot though -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:06 JST
Sexy Moon
@ademan @rieger_san @benjaminbellamy yeah it rubs me the wrong way even though theres nothing stopping two implementors on fedi from giving their new activity the same name and confusing servers -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:07 JST
Sexy Moon
@ademan @rieger_san @benjaminbellamy i got a little hung up over evend kind ids being seemingly centrally defined unless you literally can just pick a number and start coding a new event -
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:07 JST
Ademan
Since it’s opaque to relays you can do whatever, but I don’t like kind ids being numeric because collisions are going to be common between people experimenting. You need to coordinate it somehow.
(Also encoding persistence behavior into numeric ranges is super dumb)
-
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:08 JST
Ademan
or if they want to implement it out of spec…
-
Embed this notice
Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:16 JST
Sebastian Rieger
@Moon @benjaminbellamy @ademan that’s true! Everyone can create a NIP and the community then discuss the pros and cons.
There is no roadmap or something like this.
When a NIP is finalized everyone can decide if he want to implement it or noy
-
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:17 JST
Sexy Moon
@rieger_san @ademan @benjaminbellamy but a random guy on nostr insisted to me that nostr development is not centrally controlled -
Embed this notice
Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:18 JST
Sebastian Rieger
@ademan @benjaminbellamy @Moon
Nostr is an open protocol that only exists because of the nips.
There is reference implementation, which means the specs are the only source of truth -
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:19 JST
Ademan
specs aren’t always followed in practice, especially when things are rapidly changing, and that seemed to be what was happening from what @Moon said, but it turned out not to be the case.
-
Embed this notice
Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:20 JST
Sebastian Rieger
@ademan @benjaminbellamy @Moon nips are the protocol spec’s! They are up to date ?
-
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:21 JST
Ademan
I wonder how horribly out of date the NIPs are then https://github.com/nostr-protocol/nips/blob/master/57.md Granted I just skimmed it but it looked like lnurl was integral to the process
-
Embed this notice
Ademan (ademan@thebag.social)'s status on Wednesday, 01-Mar-2023 16:36:22 JST
Ademan
zaps require lnurl? gross
In conversation permalink -
Embed this notice
Sexy Moon (moon@shitposter.club)'s status on Wednesday, 01-Mar-2023 16:36:22 JST
Sexy Moon
@ademan @rieger_san @benjaminbellamy i've received sats using plain old ln address In conversation permalink -
Embed this notice
:pci: Benjamin Bellamy 🇺🇸 (benjaminbellamy@podcastindex.social)'s status on Wednesday, 01-Mar-2023 16:36:28 JST
:pci: Benjamin Bellamy 🇺🇸
@rieger_san
https://github.com/nostr-protocol/nips/blob/master/57.mdIn conversation permalink Attachments
-
Embed this notice
Sebastian Rieger (rieger_san@mastodontech.de)'s status on Wednesday, 01-Mar-2023 16:36:29 JST
Sebastian Rieger
@Castopod everyone who voted with no has not heard of zap’s! They are a game changer for content creators!
In conversation permalink -
Embed this notice
Castopod :podcasting2: (castopod@podlibre.social)'s status on Wednesday, 01-Mar-2023 16:36:30 JST
Castopod :podcasting2:
Hmmm… Maybe too soon… ??
#nostrIn conversation permalink Attachments
-
Embed this notice