Avatar
Tanner Silva
2ef0fccfd5a55e36bc8be3a525c1ce97f20eabaa94e69d82febfd641d9480c35
Strategic software architect and lead nostr developer for CakeWallet. Building topaz (and other solutions) with nostr-kit. Photographer shooting Leica M digital. Watch collector. Follower of Christ.

I think everyone that dives into LMDB deeply enough ends up walking away with this impression.

If I could only have one library to use for the rest of my career, it would be LMDB. Without question. nostr:note1fayzzfmv63r22l5e3ghnj4zdwhgh0ldfw8sqnf92k0j0jgqaeh3s7pt72j

Damus only showing reposts in the replies feed is a downright crime.

NTP? Idk

Certain users in my timeline reliably make posts that my client perceives as “future” by just a few seconds.

Nostr is absolutely not a synchronized protocol, nor does it need to be. I believe the docs encourage for clients to stay within ~10 minutes or something like that.

That said, I think it’s perfectly reasonable not to relay newly created events in real time to my client if I’m filtering UNTIL some date that’s clearly not present time.

I feel like any use of UNTIL that is past current system time should be considered backdated and future events not broadcasted.

It’s used primarily as a means of hosting centralized directories, possibly for secure applications. Access control, authentication, etc.

OpenLDAP is used today because it’s been around forever, and used by a wide range of hosts in various industries.

Replying to Avatar PABLOF7z

ANNOUNCING:

https://kind3.xyz

the fastest way to possibly destroy your nostr experience

😂

Kind3 allows you completely replace your follow list and follow someone else's.

Of course, it also allows you to create a backup of your list before doing so and restoring that backup in 1-click.

Use at your own risk 😂

https://pablof7z.com/rec.mov

This will be very helpful for my client testing. Thanks!

A nostr client with user-configurable regex filters on the timeline? 🤔

Amen brotha, have an excellent day 🍻

SwiftNIO absolutely smokes 🔥💨

topaz will ALWAYS show the correct (relative) time on events. always. it’s impossible for a date not to be accurately shown.

its shocking how many clients are chill showing a date that is actually completely incorrect.

if you’re gonna show a date, the date needs to be correct. it’s simple 🧠

TIL that NIP-69 (Polls) is a thing

Ok, sure. Didn’t think I had the reach for a nostr post, and never heard of bountstr.

But certainly, open to throwing this job at the community first

I really wanna see NIP-42 get implemented in strfry and thinking I’ll need to throw down and pay some credentialed indie on Upwork to implement it.

Never used Amethyst but it seems kinda less than ideal?

È ancora in fase di sviluppo, ma il TestFlight sarà presto disponibile.

(Blindly translated from ChatGPT; should basically say “coming soon”)