Replying to Avatar The Beave

No.

There are some starts, but... A calendar is absolutely essential for any business adoption.

Plus a standardized nostr-ized contact card like what you use currently but with an npub field.
Avatar
The Beave 6mo ago 💬 16

Who is going to make the standard calendar event and contact format for nostr?

(I've always found it weird that calendar events and contact cards are mashed together, so I'd be OK if they were separated, but obviously interoperable.)

Maybe the file type could be .nce (nostr calendar event) and .nns (nostr npub share).

For the calendar event, functions should include time, date, descriptive text of the event, location, repetition suggestion (including all sensible options), public or private, if private which npubs can view/decrypt the event, which npub created the card at what time (and possibly where, physically, it was created) but also able to be created anonymously, etc.

Anyone want to poke at this?

nostr:nevent1qqszha43wg5xspmydxj4hl4v8zwkzl0a228k59njwkhelt4rlcedcdcprdmhxue69uhhw6r9v96zu6rpwpc8jarpwejhym3wvdhj7q3qq6ya7kz84rfnw6yjmg5kyttuplwpauv43a9ug3cajztx4g0v48eqxpqqqqqqzr2qlf9

Reply to this note

Please Login to reply.

Discussion

Avatar
The Beave 6mo ago

All of these should be easily converted to QR codes for sharing on camera equipped devices, NFC card shareable, or the basic file of a format easily sent by relays or attached to other events (like a better version of a DM).

Avatar
The Beave 6mo ago

nostr:nprofile1qqsqddupn4l3cl65wggcyehd009g0pwuatsfudh28f90vewx68vrylqprfmhxue69uhhyetvv9ujuem9w3skccne9e3k7mf0wccszenhwden5te0ve5kcar9wghxummnw3ezuamfdejj7mnsw43rzufkd43hywr5d3erxmp5va6hxvmnveh8wd3hxue8xdm6v9jnv6r3de3k6ae4wa4rydm9df6kgdthvduxvdm3xph8sdmyx5lkyun0v9jxxctnws7hgun4v5q3gamnwvaz7tmjv4kxz7fwv3sk6atn9e5k7nznd8h

This is kinda similar to what you're doing. Can your tech stack adapt to calendar events? It obviously does credentials.

Avatar
Tim Bouma 6mo ago

Technically, easily done. It’s the actual domain I know nothing about. I’ll keep this requirement in my thinking cap. My approach would be to store private calendar events that could be rendered in the wallet. Could be useful for health appointments. Once I get all the generic infrastructure stuff nailed down, I will be focusing on health.

Avatar
The Beave 6mo ago

Yup. Any business NEEDS calendar compatibility. Most humans online need, too.

A private calendar is certainly a primary motivation, but being able to share Calendar events publicly or with specific people is also going to be necessary.

Avatar
Lucas M 6mo ago

#asknostr

Avatar
Duncan Cary Palmer 6mo ago

As nostriches pioneering the Wild West of cyberspace that we are, can we also extend the discussion to Calendar Reform?🤔

While fixing the money (bitcoin) and ending cancelations, why not forge the path to a rational, 13 months of 28 days calendar that actually vibes with the motions of celestial spheres?😃 With, of course, one or two "holidays" at the end to round things out?

This sane calendar could be overlaid with the existing one to give Luddites and latecomers a chance to gracefully adapt to reality.😆

Avatar
Niel Liesmons 6mo ago

364 days

12 months of 30 days

4 inter days

Anything else doesn't follow the 6 gates the sun jumps and goes through.

Avatar
The Beave 6mo ago

I'm grumpy with the Gregorian flip and the mess that the Romans made of things... But that's a step too far at this point.

I'm more of an incrementalist.

Avatar
Niel Liesmons 6mo ago

I get that.

I'm just trying to observe what I can from this thing we live in.

Also have a 3yo with tons of questions I honestly don't know how to answer 😉.

Avatar
The Beave 6mo ago

Good.

I'm worse than most 3yos. 😅

Controlling time via the calendar is certainly a tactic employed in various forms by the SPDC to extend control by divorcing humans from the clearly observable natural skyclock.

5d
5dcd8ebc... 6mo ago

With decades of experience with Roman, Jewish, Arabic calendars, that is not the way. Record calendar events as unix time (e.g. signed 64 bit secs since 1970) and calendar type (and thus how dates are displayed) is selected in the client. You could call it "star date" (since calendars and day length were different on every planet) or "nostradate" and pick a funky origin. Java time uses 64 bit milliseconds since 1970 - that works too.

Avatar
Duncan Cary Palmer 6mo ago

That's an interesting approach...🤔🧐

If that means we can all use our preferred calendar, I like it a lot!🫂😁

We all live by our own calendar while being able to coordinate with any and every other calendar via "UTC Date" (Universal Time, Coordinated).

Rather than Unix time, we might want the benchmark to be the bitcoin Genesis Block?🤔🧐😁

5d
5dcd8ebc... 6mo ago

UTC is just another calendar. You want a straight single number, counting some units some an origin. You'll want a stable frame of reference also that is easily quantified - otherwise I'd pick the CMB (Cosmic Microwave Backgroup) FoR (in which the universe is ~5.5 days old). For the foreseeable future, this means Earth FoR. Bitcoin blocks is not a useful time unit for future events either. Seconds are pretty universal on Earth, and well standardized.

What is the Bitcoin genesis block time origin in secs since 1970 or some standard calendar?

Note that modern calendars depend on observations to determine leap seconds - so future date display may be off by a second or two. Lunar calendars generally have leap months - and in the Hebrew calendar, the leap month is applied according to an official New Moon observation in Israel. This can be affected by war or weather, so you can't always predict when the next leap month will be, and future date display may be off by a lunar month. But, this is part of the charm of lunar calendars.