Avatar
Danny, the cyber guy
66675158e6338fe89fda418e42a0bf2a7a2b132504dd347f015a18971b644430
Building Arx, because private, sovereign networks matter ------ Developer, protocol tinkerer, neighborhood thought-criminal. When legacy media shouts “conspiracy,” I just call it Tuesday. • Shipping Arx commit by commit, code before commentary • Unapologetic free-thinker & digital-sovereignty maximalist • Bitcoin ⚡ & Nostr native • Living life permissionlessly, no rulers, only protocols ✨

Update on the #mit-bitcoin-hackathon #bitcoindev mailing list project

everything is working mostly

- users can see messages in mailing lists

- can subscribe to multiple mailing lists

- can answer to threads from an email client

- threads support simple markdown, images and non english characters

what's not working right now:

- creating new threads from an email client (will finish this today)

- adding attachments from an email client and linking them to the reply in nostr (I will not be finishing this before the hackathon ends)

(exmple shown from thunderbird, works on any email client that supports IMAP and SMTP)

update:

- looking pretty good, messages are shown in thunderbird, including multiple layers of nesting

- the server mostly seems to be stable

- naturally, we can read the messages

now working on:

- proper message parsing for anything other than 7bit ascii

- basic markdown to html, to allow basic formatting

- SMTP to allow users to reply via an email client, not just via nostr

I decided to join the MIT Bitcoin Hackathon, and the project I'm working on is a nostr to IMAP bridge (and depending on time, SMTP bridge too), in light of what happened recently with the bitcoin devs mailinglist on google groups

this is a regular nostr event (kind 11), being pulled up inside thunderbird (and it will work with any email client)

#mitbitcoin #bitcoindevs

throughout history, those very moments happen when empires are on the verge of failure, when they turn their gaze inward and begin to fear their own citizens more than external threats. fear of losing control, fear of citizens organizing beyond state supervision, fear of the inevitable.

If privacy is outlawed, only outlaws will have privacy.

yes, but not like in your picture. comments to specific commits, especially when linked to specific files and lines is crucial

GM

Let's build communities on nostr, let's make the world decentralized again!

Two words: KISS Launcher, trust me, you'll never look back. I've been using it for years, and there's no Android launcher that's better. No clutter, just a vertical list of apps, a search bar and pinned favorite apps.

LOTR is already one of my favorite movies, but if it were animated, in the style of ghibli or in the style of shinkai, it would be AWESOME

I guess this is going to be my next DnD character

what's this? looks interesting

Replying to Avatar atyh

i started using the Fediverse before it was called the Fediverse. back before Mastodon even existed, when there was just identica and diaspora.

i watched it go from a tiny place for fringe linux nerds, hackers, and artists, to a place for disgruintled corporate journalists and WokeScolds with 15 million daily users.

steady growth was minimal. The major growth happened from mass influxes. Usually from a negative facebook or twitter event, or some famous person talking about the fediverse.

Then 90% of those new people would drop off, and go back to the corporate BS, leaving behind a small increase. Those cycles happened over and over again until there were 10+ million daily users.

I see something very similar happening to nostr. It is very familiar and natural. But it seems like some people have a Silicon Valley VC funded growth from 2012 paradigm of what success it. Nostr is probably not going to happen like that. They dont have a realistic paradigm of how open source, community developed protocols grow over time.

So they keep getting disappointed because their paradigm is unrealistic, and the hype growth they keep telling themselves will happen is really probably not going to. Or to put it another way, 'go fast and break things' is a luxury mentality afforded by VC capital. Go slow and fix things is how real, lasting, open protocols that are worth something develop.

What will happen with people is pretty simple.

Some will leave quietly, some will leave loudly, making sure to dump their disappointment on everyone before they go. But some will just keep rolling, noting, memeing, and building, a peice at a time, until something really unique, robust, and reliable has formed.

stay humble, stack sats, post notes.

Exactly, couldn't have said it better myself

the argument I like to make is that bitcoin isn't volatile at all. it's only volatile when compared to other currencies that are actually volaitle.

the value of bitcoin never actually changes, 1sat = 1sat

it's the value of bitcoin in relation to other currencies that change.

the usd value of bitcoin only changes when either the government starts to make the little printer go brrrr a little more, or when degens trade too much

Closed Community Networks are one of the best use cases for nostr, and will be increasingly important as organizations seek secure, censorship-resistant communication channels

#888888

Congratulations everyone, we did it ~

(It's a Japanese internet thing, because a bunch of eights sounds kinda like パチパチ repeater over and over, which is the onomatopoeia for clapping)

We need to all simultaneously start clapping for the blockchain when that happens, the timechain is asking us to

While I do agree that there's nuance for sure, in the case of what you're referring to it's just a lack of tooling. There's are SOME advantages (mostly in dev simplicity) to having stateless protocols such as HTTP, but the flexibility of reusing a socket can allow building much better (especially better performing) applications.

No matter what there's no case where back and forth HTTP is faster than WebSockets. The only exception would perhaps be extremely well optimized QUIC http servers with literally ideal data sizes (and even then WebTransport or WebRTC would beat QUIC)

Got it, so you're thinking of nostr as just a twitter replacement I'd assume?

If that's the case then maybe I'd agree with you, but that's the network effect, rather than a technical problem, is it not? Twitter had the same problem at the start, "how do we get people to use this, if people aren't using this?"

Nostr is honestly so much more than just twitter, it's honestly better to compare it to a layer on top of http that handles identity, decentralized data publishing and validation, and it just so happens that twitter (kind 1) apps are among the easiest to develop. Personally the microblogging/kind 1 is the least exciting part of nostr to me.

What I meant by that, in case you're not technically inclined, is that many more applications can be built (and are being built) on this protocol, and with the twitter-clones we're just scratching the surface!