Every so often I “seat down” and reflect upon my past and think about what to focus on in the future. Now is such time, a lot of things to reflect upon, and a lot to think over. We can’t predict the future, but we can certainly prepare for the likely outcomes.

Seems that while I was asleep, the world was enjoying yet another cloudflare outage. The main nostr.build services were not impacted by it. On the other hand, blossom.band (a nostr.build blossom linker) was impacted. This was mainly due to it seating on top of CF’s infra as a thin layer to redirect to the actual links and proxy the uploads to the main backend. Since blossom, unlike nip96, requires for the domain sharing of the uploads and downloads, we are forced to host it at CDN. I’ll think about other ways to work around that limitation, so stay tuned. If you have experienced inconveniences during that time, we apologize for this, I know we should do better. 🫡🙇‍♂️

Nostr is engagement protocol, not observer protocol. Want to see more, engage more! 🫡 (Subscribe for future advices 🤣)

GM, day 2 and still trending 🤣

gn

There is comfort to be found in the fact that we don’t know what we don’t know. - Anon

I love that some of my dumb joke replies or posts spur a healthy conversation about some of the technological challenges. Internet never ceases to amaze me 🫂🫡🤯

I like ho bitcoiners start with 1BTC == 1BTC, and then when the conversion price becomes disadvantageous, everyone panics 😂🤣😂