elsirion

https://sirion.io

Freedom loving #Bitcoiner, anti-statist, researcher and builder.

Public Key

npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5pa

NIP-05 Address

_@sirion.io

NIP-57 Address

elsirion@sirion.io

Profile Code

nprofile1qqsfu8jfssstclp470360rfqq3d5eq6rnpk6ujrnjavmeje2yl5gc5cpzdmhxue69uhhqatjwpkx2urpvuhx2ue0qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz76xk46u

Publishing to

purplepag.es

nostr.oxtr.dev

relay.nostr.band

Author Public Key

npub1nc0ynppqh37rtulr57xjqpzmfjp58xrd4ey8896ehn9j5flg33fszrz5pa

Show more details

Last Notes

2024-08-29 21:04:16

- reply

Great watch indeed, I got the Instinct 2x solar tactical and the built-in flashlight is just so useful! Also 40d battery life if I go outside often enough 🤩

2024-08-29 20:54:14

- reply

Outbox is a great model! Basically Mastodon, but you can easily migrate your account because it's just a private key with a lightly coupled "home relay".
How does it deal with threads? I guess my home relay has to keep track of replies to my posts? Spam will be an interesting problem to solve since suddenly my relay has to accept third party data. Maybe micro payments are the way to go?
I guess there will also be "index relays" eventually that keep the entire global routing table (which would be in the 10s of GB once nostr is successful)?

2024-08-29 10:24:48

On why I think protocols ought to be designed carefully from the beginning (in particular re scalability) if we want to preserve certain properties like decentralization in the success case:
#note1h2p…qdyy

2024-08-29 10:21:06

- reply

Protocols != Businesses
A business that has lots of demand can buy its way out by raising money and directing lots of resources towards solving the problem. It also has the benefit of typically controlling all the infrastructure, so is able to replace the entire underlying stack.
A protocol cannot do that, it's dependent on volunteers, grants or companies that, often against their commercial interest, keep improving it in a mostly backwards compatible way. The amount of resource that can be mobilized is smaller and the upgrade process harder (a whole ecosystem has to move).
The most likely outcome imo is that companies will build very sophisticated scaling technology, that will likely not be open source so they can have a moat, and then dominate the end user market. Us nerds can still use the core protocol, but might not even be able to communicate with the majority of users.
E-mail is a cautionary tale, try hosting your own and still reaching gmail users reliably. Or try getting ICS files for flight bookings, airlines just set the google calendar metadata since ~everyone uses GMail+GCal. It's a bit different since the centralizing force for e-mail was spam and not scaling, but I think it's a close enough analogy.
Or look at the web stack, it historically evolved to become such a bloated monstrosity (because the inventors designed a document standard and we shoehorned it into becoming an application framework) that these days only companies with millions to burn can keep up with maintaining browser engines (and Google pretty much defines the direction of travel because Chrome is number one).
So when I worry about scalability it is out of a deep care for decentralization and not seeing all that energy invested go to waste by ultimately ending up in the same place we started at. If we don't consider decentralized scaling from the beginning, the non-ideological VCs pouring money in once it gets traction certainly won't.

2024-08-28 20:31:57

- reply

There have been many, quite sophisticated attempts at building less centralized social media/web applications in general (Secure Scuttlebutt, Freenet, Web5, …). There's lots of theory to catch up to, but maybe keeping the protocol insultingly simple at the beginning, getting lots of people (especially devs) excited and involved and then fixing all the shortcomings using the community momentum will be the winning strategy.
I just hope it won't end up like the web: a platform full of historically grown, accidental complexity and insane quirks and limitations that still everyone has to interact with.

2023-04-15 06:37:11

- reply

(The thing you meant, simplicity)

2023-04-15 06:36:44

- reply

There will be a talk about this at BTC++ by Christian Lewe ;)

2023-03-19 07:04:48

- reply

Lol, you just proved how nieche nostr still is 🤣

2023-03-18 13:59:02

- reply

Keine Ahnung was für ein Wahnsinn in Deutschland wieder los ist, aber der Vorteil von Wärmetauscher basierten Systemen ist, dass sie (zumindest theoretisch, also Augen auf beim Kauf) auch umgekehrt zum kühlen im Sommer genutzt werden können. Da höre ich gewisse Kreise schon jammern 😄

2023-03-18 09:27:16

I want a *symmetric* GBit connection again 😭
https://nostr.build/i/nostr.build_48455ad3eea5ed9c30c757577434a80e248b7b13728d070af83095c2fbeb9225.jpg

2023-03-16 15:57:59

- reply

Trying to pump up the Nostr engagement numbers? 😜
More seriously, if rust tells you you are doing something wrong it's typically correct about it. Not great for random hacking around without a plan, but awesome for building and maintaining reliable systems. The main problem I feel is finding good developers (that aren't already working on something super awesome).

2023-03-15 06:38:33

- reply

Obsidian has the sameproblems for me, was also wondering.

2023-03-14 06:40:51

- reply

Tbh I don't know how I made do with 16G till only a few years ago anymore. It's crazy how software extends to the amount of memory you give it.

2023-03-13 21:24:15

- reply

Closing tabs is not an option! 🤣
#[0]

2023-03-13 21:23:27

After discovering that my laptop used like 20GB of swap space a few days ago I finally upgraded from 32G to 64G RAM, let's hope CLion, Firefox and rustc will stay in these bounds for a bit, I only got one potential doubling left 😬

2023-03-13 21:13:30

Fedimint dev call be like
https://i.imgur.com/U7vkLUM.jpg

2023-03-13 21:04:42

- reply

Looking at BIPs: for small numbers just put them into the markdown spec doc, for big numbers/large vectors add a file of appropriate encoding (here a list of json and info on if its valid or what is wring with it I guess) and reference it. Not sure about specifics, not an expert in speccing, just a consumer of specs.

2023-03-13 06:11:14

- reply

Do you happen to know why it begins downloading stuff like mad and supposedly runs out of memory eventually (rather quickly on a GBit backed WiFi)?

2023-03-13 06:06:22

- reply

Idk why, but viewing your profile made Amethyst crash more than once for me 😬 maybe related?

2023-03-12 21:50:13

One of the most important but likely most underrated things happening in Nostr right now. Building distributed systems is hard. #[0] https://github.com/nostr-protocol/nips/pull/355/files

2023-03-12 21:31:27

- reply

That could hide unintentional implementation or configuration errors 😬 better to be explicitly about where money goes.

2023-03-12 21:07:20

- reply

Didn't think about it that way before, but does it mess with #hashtags ?

2023-03-12 16:19:23

- reply

Having test vectors people can easily test against and maybe a more machine readable spec (e.g. JSON schema) would help with that. My experience with Nostr and LNURL has been one of reverse-engineering and trying to understand the author's intentions so far (human language sucks for specs).
There's only so much time people spend on spec compliance if it works(tm), being compliant should be the easiest path to "it works".

2023-03-12 13:38:28

Is there a NIP for LaTeX math support? 🤪

2023-03-12 13:37:31

- reply

For that it works surprisingly well 😅 also, I don't get the md hate, super easy to support in nearly any language and not too bad to read without rendering (unlike LaTeX).

2023-03-12 07:50:27

- reply

This is so awesome! 🔥
#[1]

2023-03-12 07:48:18

- reply

Wow, Amethyst supports nearly everything 😲
https://i.imgur.com/K2i6mDY.jpg

2023-03-12 07:45:07

Do any nostr clients support rudimentary markdown like:
* Lists
* *italic* and **bold** typefaces
* [Hyperlinks](https://bitcoin.org)
* `innline code`
```rust
// Code blocks
let foo = "bar";
```
## Subheadings
And finally footnotes [^1]
[^1]: lmk if anything works :)

2023-03-11 20:35:50

Props to #[0] for being the only org I've seen so far generating their `.well-known/nostr.json` on the fly using the `?name=…` parameter and not just listing everyone with a NIP-5 handle under the domain.
Is there some open source server for that? Not that it'd be hard to implement, but why re-invent the wheel …

2023-03-11 20:28:42

- reply

If it ever becomes significant I'll probably turn it off again. Kinda sad, becauseits *is* a lot of fun throwing around sats and seeing others doing so 🥲

2023-03-11 20:01:45

- reply

Every day I'm amazed how such an under-engineered protocol can work so well in practice and just keeps getting better 🤯
The extensibility and scriptability (you can sign a message with a key? => you can post!) makes it even more exciting!

2023-03-11 19:53:06

Did anyone think about that leaving cryptographic evidence of having received money, in form of zap notes signed by the *recipient*, isn't the best idea re taxes 😬
If you are receiving significant amounts might be worth reconsidering.

2023-03-11 19:34:58

- reply

5
(assuming the imaginary post before #[2]'s was also 1)

2023-03-11 15:49:39

- reply

Do I want to know how it ran before or would that give me nightmares? 😅

2023-03-11 14:19:45

- reply

Plugins are awesome!
They allow following the Unix philosophy of tools doing one thing and doing it well and then composing these tools to accomplish specific taksks.
#[0]

2023-03-11 14:16:34

After some more hacking with #[0] I finally got Zaps to work properly with my Core Lightning node. All you need is two plugins:
* clnurl: LNURL server with Nostr support https://github.com/elsirion/clnurl
* cln-zapper: Broadcast zap notes when invoices are paid https://github.com/thesimplekid/cln-zapper-rs

2023-03-06 22:31:16

Are there any mobile nostr Clients with good Tor support?

2023-03-05 16:55:26

- reply

The results are in, it takes ~170 lines of #rustlang code and half a day of work if you implement a LNURL server for Core Lightning. Deployment was a ~25 line diff to my nix-bitcoin config.
I think #[1] nerd-sniped me 😅
Added benefit: now I can zap around on nostr like all the cool kids 😁
https://github.com/elsirion/clnurl
#[0]

2023-03-04 11:44:17

- reply

I think you missed his point unfortunately. He argues forthee adoption of more private protocols where this isn't even possible.

2023-02-06 19:13:07

- reply

The thing is we can't really do anything effective against it, especially not in an ethically consistent manner as Andrew puts it quite well, so all the outrage seems not really helpful.
https://i.imgur.com/c09mqoE.jpg

2023-02-06 04:45:37

What gives me hope for nostr is the same reason that gives me hope for mixnets:
Hardware performance has gotten to a point that we can be ridiculously inefficient at solving simple tasks without it being perceptible. This makes fundamentally less efficient protocols viable.
But it also means that app developers will have to work twice as hard to make the UX slick, you can only spend your performance budget once after all. I'm excited to see where this goes!

2023-02-06 04:24:33

- reply

Not on iOS myself, but I hear it's the best client 😃

2023-02-05 23:54:53

Amethyst is the first nostr client that makes me consider it as a serious Twitter alternative. Still lots of optimization to do, but the out-of-the-box experience is better than I anticipated.

2023-02-01 02:31:47

- reply

👋

2023-01-30 21:41:36

#[0] Verifying My Public Key: "EricSirion"

2023-01-30 21:41:01

#[0] Verifying My Public Key: "EricSirion"

2023-01-30 21:35:28

@npub1teawtzxh6y02cnp9jphxm2q8u6xxfx85nguwg6ftuksgjctvavvqnsgq5u Verifying My Public Key: "EricSirion"

2022-01-06 22:10:08

- reply

🔥🔥🔥 LFG