Avatar
frphank
47be0b2a89faaa66bc57f5c679203486da45660295cb3db3c2f38f4be8d8816e
Autopoietic. Scratching things from chaos. Homesteading the noösphere. Opportunity farmer: Reading things that are not yet on the page. Haskell. Dollars only, thanks.

Sounds like a plan. Maybe comment on the issue?

Interest rates give a pretty good answer.

We've got repudiation through key rotation, in theory.

Replying to Avatar rabble

Jack got bluesky funded when he was CEO Twitter, it’s an independent public benefit corporation which has since received VC investment. As far as I know Jack never contributed code to bluesky. I do know that from our Odeo days many eons ago, that he’s an incredibly talented programmer. He’s CEO of a publicly traded company and that requires a lot of meetings and interruptions of your work day which makes coding hard.

When it comes to Nostr? He’s also not contributed any code that i’m aware of. His github account doesn’t show any activity, which we’d see if he contributed code to Nostr. https://github.com/jackjack

What he has contributed to Nostr is both immaterial and material. Jack’s attention on Nostr helped elevate it from a project a few bitcoiners and enthusiasts of social media protocols knew about to something that Elon tried to block and a lot of people started paying attention to. Then Jack started providing material support with funds to fiatjaf to share with the community, funding the conferences, and endowing the OpenSats fund with money to pay developers. This support’s been a huge boost to making sure Nostr matures and develops by providing time for developers and designers to really focus on Nostr projects.

I spent years working on Secure Scuttlebutt which was an inspiration for Nostr, and it didn’t have funding to support the developer community. We’d constantly get great dev’s, designers, and community members in who would contribute for a while, then have to quit in order to work to support themselves. Earlier this month one of the cores of the community, Andre Staltz had to stop working on it in order to focus on doing dev contracts to pay his bills.

https://www.manyver.se/blog/2024-04-05

Nostr doesn’t suffer from that cycle of burnout, and it’s amazing.

Contributing code would require some sort of skill wouldn't it.

Do we have evidence of any of nostr:npub1sg6plzptd64u62a878hep2kev88swjh3tw00gjsfl8f237lmu63q0uf63m 's contributions anywhere?

Is your income going up as much as CPI is? If not you might have a problem with your income, not with inflation.

> 2. Database is solved. Users will choose their relays. You don't need to put anything up. There is no need to spend hours specing out your database tables, mapping them into objects, and then making all the data access layers. No liabilities, no operational costs, no risks, and, more importantly, no long-term commitment to secure and keep the data available to your users.

It's bizarre how this implementation detail occupies the mind of nostr "architects" out there. Clients should cache things (and are in the case of local relay) but in the end that's an implementation detail. Client, cache, local relay, relay are all just terms for "peers" and any peer should be able to talk to any other peer.

Yes even relays should talk to one another and already are in the case of "boostr". Aren't they.

Your idiosyncratic terminology isn't helping things.