Nigerian Official pretends to faint after he is questioned about missing funds đ
https://video.nostr.build/9dde1d488101803031acffb34b41edc365d79935978aec77083d3c359d368b5f.mp4
Maybe SBF should have tried that.
A shot of whisky.
For those who weren't following the adventure in real time on Telegram, here's a nice writeup about a recent incident that has some lessons for anyone running a Lightning node: https://medium.com/@goryachev/bitcoin-node-security-case-study-e1ca00a378b5
What are you listening to on this Friday night?
Dean Martin for us.
(Donât mind nostr:npub1hu3hdctm5nkzd8gslnyedfr5ddz3z547jqcl5j88g4fame2jd08qh6h8nh asking about asparagus in the background)
#waxstr #vinyl #grownostr https://v.nostr.build/reqw.mp4
Enjoying this classic: https://youtu.be/5O9hr5LBeWg
Sure. All I'm saying, and I think what Semisol was saying, is that pure altruism isn't enough. Developers have to eat, too. In the case of Linux, after the first 5 years Linus' own work was supported by a job at Transmeta, then later indirectly by other companies via funding of the Linux Foundation. IIRC, there was also a gift of some Red Hat stock when they IPOed.
Even in the 90s, contributions were happening as a side effect of Linux use by companies and big organizations. For example, the Ethernet drivers I used on all my servers in the late 90s were written by someone at NASA (probably as part of their work on Beowulf clusters). My company (an ISP) didn't write much code, but we gave modest $ support to open source projects, mirrored repositories, etc., because we knew OSS was crucial.
A lot of folks working on Linux are supported by companies that rely on Linux, though. They do something else that they can monetize, and they contribute to Linux and other OSS because (1) their business succeeds when Linux succeeds and (2) contributing is a badge of honor while not contributing might get them shamedâIOW, the culture of OSS expects/demands it.
How do we create/maintain the same culture for nostr? What business models will align incentives?
Some aspects of the ecosystem are more easily monetized than the software development: operating relays, image hosting, etc. I could imagine a viable model where the branded version of the software ships posting to a set of relays that require payment, etc., by default. Newbies will naturally use the paid services, and some of the experts will continue to use them as a way of supporting the developers.
What really mattersâthe war we've been fighting for 2+ decades nowâis that the *protocols* stay open and interoperable. Actually, it also matters that they stay simple enough that core functionality can easily be reimplemented and servers can be run by any reasonably geeky person.
At the end of the day, I think a lot of this comes down to culture. What are the nostr equivalents of a hard supply cap, "not your keys, not your coins", hodl, and the other touchstones of Bitcoin culture that seem to be working so far?
GM đĽ
TradFi: Payments via a blockchain may fail because of bugs. You should stick to tried & true centralized payments systems.
Also TradFi: https://www.cbsnews.com/news/bank-of-america-wells-fargo-banks-direct-deposit-delays/
Plus ça change⌠https://www.atlasobscura.com/articles/staged-train-wrecks
It's a good idea. The funny thing is that from start i have heard some people mock about nostr as a "glorified rss feed"; as a response to that this idea would be really funny on top of actually being useful.
I suspect the nostr -> rss, pipeline could be done on any client. Just like blog -> rss is done. Possibly webb clients are optimal for this. So maybe coracle.social? nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn
I usually compare it to Usenet, but either way it's a compliment, not a putdown! Both are amazing Good Things that centralized services keep trying to destroy. Here's hoping that this time we win the fight for good!
Hmm⌠That makes me wonder, is there a handy tool for turning notes into RSS feeds yet? Not a great solution for DMs, but that would make it easy to integrate public notes into a whole bunch of appsâThunderbird, Zotero, etc.
See, e.g., this, from their FAQ. At the end of the day, it's probably "stuff the FCC doesn't approve of". But my interpretation is that syncing Bitcoin nodes would be OK, since you're not receiving compensation. But routing fees would be verboten, even if encryption were allowed.
What might be interesting would be broadcasting blocks and/or transactions a la Blockstream's satellite service. Or, if that's too bandwidth-intensive, maybe setting up a service where your node could accept transactions submitted via packet.
Now, running a nostr relay over packet radio, *that* might be doableâŚ
Sounds like a good way to lose your ham license. The amateur service bands aren't supposed to be used for commercial activity, and packet radio transmissions have to be in the clear. *Maybe* you could get away with syncing a Bitcoin node over the airwaves, but I can't see, e.g., connecting two lightning nodes that way.
Yes, I was being sarcastic.
Anyone can memorize a strong password and use that to secure their password manager. Most people won't.