Replying to Avatar Derek Ross

apparently i'm blacklisted from using nostr:npub15xd2mmjnh3caykh77djsv73e0zkrp42jp5mwerx8f4m6su40wdvss7t3l3? LOL!

the last time i logged into Satlantis, a year ago, their calendar events weren't being published to nostr and weren't nostr events. i wanted to see if this changed, since we're talking about calendar events today. i tried to login and check...

why am i banned nostr:npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m?

#FREEDEREK šŸ˜‚šŸ˜‚šŸ˜‚

Yah turns out you’re in the sin bin. We’ve been playing around with WoT filters to make the feeds more appealing to normies, nomads & people from outside our circle. For whatever reason you ended up in the bad boy bucket.

Guess we need to go back to the drawing board šŸ˜…

Try again in 30min. You should be good. And try the app, not the website. App is much nicer now.

——-

Also - we pulled events off the NIP52 spec because it’s shit. We’re building it from scratch & once happy with the events feature, we’ll propose a new NIP with a new, fully fleshed out & battle tested standard. That’s gonna take a few more months - but it will be 100% worth it because Nostr will finally have a really good calendar-events spec

Reply to this note

Please Login to reply.

Discussion

Thanks.

You’re good to go sir

thank you for looking into it and fixing it.

Anytime mofo

Keep posted as u find things, broken or not

Thanks for the heads up on the upcoming nip-52 improvement suggestion from yall

https://github.com/nostrability/nostrability/issues/2#issuecomment-3111752331

What’s the issue with NIP-52?

Poor feature set.

🤣 Terry, who created the NIP:

I’m not saying it to be a dick

But if we’re going to compete on events, we need to do everything Luma does.

I agree. nostr:nprofile1qqsq743lut8a7xqvkyz9s6u4suehngxplh8mcvq6sryz2hen690s88gpydmhxue69uhhyetvv9ujuem0dajx6mmjde5kuemzd96xxmmfdchxxmmd9uq3uamnwvaz7tmjv4kxz7fwwpshgunfvd4h2mrjd93kstnrdakj7qg4waehxw309aex2mrp0yhxgctdw4eju6t09ufll977 and I have both launched calendar apps recently and both of us have features that we are using or will be using that will need to bed added to the NIP to extend functionality.

Please check out https://github.com/patrickulrich/nips/blob/master/52.md and see what you think. I've not submitted this yet while I've been trying things with nostrcal.com but I think you'll find a lot of needs covered. Happy to work together to iron out whatever needs are missing!

Will do

That’s fine, I don’t take it personally. But that’s not really how any of this works. NIPs are documenting what clients currently do. It’s not meant to restrict what you can do. If there’s something missing, you can extend the NIP or do something entirely differently if you think it’s wrong entirely. It’s not clear to me why anything needs to be ā€œpulled off of itā€. Can you extend the NIP to do what you need it to do?

Yah but if we add a bunch of things, does it not defeat the interoperability aspect?

Or will just the feature sets be different but the actual events themselves be visible across all compatible clients ?

clients only see the portions of the event that they support and wouldn't support your enhancements or exctensions as long as you're not changing the structure of the json tags and just adding new ones.

additionally, other clients that support calendar events could adopt your features and become 100% interoperable.

Ok I see.

In that case I believe it’s how it currently works on Satlantis. There’s a bunch of things we added (like co hosts, etc) that is not supported in the spec.

Thanks for understanding. Feel free to propose these updates to the spec. We can encourage interoperability and have more clients do what you’re doing on Satlantis.

Will do for sure

I’m hesitant to propose anything until we’ve figured out the actual product with customers.

Once we know what works & what doesn’t, then I’ll have something more realistic to propose. Stay tuned