aaron
A. A. RON

Public Key

npub14lu6nuqh7v4jazmqw49yzqkmnkw0nletjeuqfdgwqurcp2j9ex5qz37m8m

Profile Code

nprofile1qqs2l7df7qtlx2ew3ds82jjpqtdem88elu4ev7qyk58qwpuq4fzun2qpzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgqgdwaehxw309ahx7uewd3hkc89q375

Publishing to

relay.nostr.band

nos.lol

Author Public Key

npub14lu6nuqh7v4jazmqw49yzqkmnkw0nletjeuqfdgwqurcp2j9ex5qz37m8m

Show more details

Last Notes

2024-09-16 23:32:26 GMT

Hello world
#introductions

2023-02-25 16:28:50 GMT

monstr is cool.

2023-02-17 03:20:39 GMT

There was a time when I was probably seeing most of my follow’s content.
But I’ve been out of the loop for a while and paid relays have z̶a̶p̶p̶e̶d̶ taken off.
So I’m probably missing everything now.

2023-02-07 00:27:04 GMT

- reply

I can’t autocorrect.

2023-02-07 00:26:47 GMT

- reply

I fixed gross perf issues in my relay fast last nights just in time for this.

2023-02-07 00:25:51 GMT

- reply

There wasn’t a single “nostr” in the reply thread!

2023-02-03 23:12:39 GMT

- reply

Niice

2023-01-31 01:28:21 GMT

- reply

And trust users more and give normie users more credit.

2023-01-31 01:23:19 GMT

- reply

People can back up data to any and all relays that let them.
They can run their own relays if they need to.
Nostr is amazing.

2023-01-31 01:12:40 GMT

- reply

We need clients and user experiences that expose users to relays so that users can gravity to and “select” relays of quality.
We need this kind of market economy with relays or nostr doesn’t work long term.
We need to stop hiding relays from users.

2023-01-30 02:08:56 GMT

- reply

It is working: https://nostr-relay.untethr.me/.well-known/nostr.json - I think snort is not validating them correctly.

2023-01-29 23:18:26 GMT

- reply

Would you need to AUTH first? so you know who it is ..

2023-01-28 22:20:12 GMT

- reply

You’re not giving normies enough credit
We had AOL - how did we ever get normies off of that?

2023-01-28 20:43:57 GMT

- reply

Damus recommends relay sets, will soon effectively default/auto-pilot relays.
Where this devolves to is most of user base will have no concept of relays, “I’ve got my client and there’s some backend something out there cool I’m on nostr f the system” - but which devolves into every other standard social platform out there.
Yes we have “portable” identities but I’m not sure portable keys model saves you here … for all intents and purposes.
The nostr vision as I initially read it was relay-centric. This seems to go the opposite way entirely.
Maybe I’m overstating all this.
But we’re in prime early phase here and this seems the time to really embrace the core nostr model not hide it all.

2023-01-28 20:20:04 GMT

Relays have become full blown shameful at this point. Long live nostr.

2023-01-26 00:34:02 GMT

- reply

Right!

2023-01-26 00:33:08 GMT

Someone build del.icio.us on nostr

2023-01-25 23:14:22 GMT

- reply

Thanks!! I zappitidied you hopefully it went through

2023-01-24 03:22:29 GMT

- reply

Why do you need to make new events durable before relaying them?
The big performance win is optimally figuring out which subscribers are interested in an in-flight event (using specialized filter indexes, instead of iterating over all subscribers for every event).
`wss://nostr-relay.untethr.me` does this. I think #[4] was pursuing this, as well.

2023-01-22 13:40:24 GMT

- reply

Interesting yes query params are more flexible but the urls less likely to compare “equal” since you can reorder params - that might matter to some places in spec or clients don’t know

2023-01-22 13:19:41 GMT

- reply

To users they would behave identical to regular relays so most use cases that apply to regular relays. Probably other use cases like ephemeral private-ish channel-like experiences. There are pay-for-your-own relay services out there, those are probably doing something similar or at least sharing machine resources across relays.

2023-01-22 03:38:27 GMT

I've been thinking about implementing "virtual relays" in untethr.me code.
They would go like this. In your client, you would configure your relay to: `wss://nostr-relay.untethr.me/virtual/<any-string-you-make-up>`.
Then this becomes a silo, its own relay: only clients configured with this relay will see data from clients configured on this relay. (Unless of course someone consumes a message and publishes it again at the root relay or anywhere else.)
This will be really easy to implement efficiently (w/ no extra overhead) within the current relay code.
I'm not sure what clients do if someone were to configure multiple ones of these -- i.e., if a relay URL resolves to the same IP address. (Hopefully they just respect them.)
There are other variations of using URL paths to change behavior. For example:
`wss://nostr-relay.untethr.me/read-only`
`wss://nostr-relay.untethr.me/write-only`
`wss://nostr-relay.untethr.me/reactions-only`
...etc...
You get the idea.
Thoughts?

2023-01-21 23:33:58 GMT

- reply

How many active connections? What’s your cpu load / how many cores? I serve about 200 concurrent and I’m about 20-30% of one core/vcpu. Majority of load is reads; sqlite shouldn’t balk at concurrency—using separate db just means you’re shifting some compute over to your database cores.

2023-01-19 03:00:57 GMT

Sir, this is a bitcoin chat room.

2023-01-19 02:21:58 GMT

Tell us your age by mentioning the first nostr client you ever used. I'll go first,
branle

2023-01-18 17:39:08 GMT

- reply

Please add
https://github.com/atdixon/me.untethr.nostr-relay
🙏

2023-01-16 18:41:52 GMT

- reply

Probably good practice to change your mind even when the facts don’t change.

2023-01-14 21:20:43 GMT

- reply

yeah i'd be happy to scale based on payment but also there's this weird gray area between actually running a viable business and hobbying this out on tips or micropayments or whatever. i like some kind of peering approach because then i could participate without having to do either of these

2023-01-14 20:46:03 GMT

- reply

Yeah, agreed generally what you're saying. I'm doing this for fun. I wouldn't be able to develop the relay code I'm working on without actually operating a relay with some kind of load, so I'll put a cap on connections or data some point like others are doing.

2023-01-14 20:34:02 GMT

- reply

Hey I'm at a modest 3000 GB/month, but I can't justify to my family spending more of our own money.
> Why use a master and not just sync between peers?
I think this may be more ideal, I had a thought about needing a master but don't recall what it is. I think nostr protocol needs an addition, however, to "ack" writes so that clients can know for certain a write is durable.
> What is the logic of when to redirect reads? If daily/hourly egress is exceeding a plan?
Peers would say "I don't want more work right now" (for any reason they like) and then some coordination strategy would have to "balance" over peers that are happy to take work.
> Why not just drop a new connection under the same circumstance to force the client to use another relay?
Dropping connections won't work. There needs to be a first-class understanding of how to get "all" of the data you are intersested in. So you need a single relay endpoint (relay url / "brand") that coordinates across peers and ensure complete data coverage (for whatever that means for the the relay).
Sharding is less about disk space (b/c disk is cheap and you can archive older data etc). It is more about solving the network egress - but putting more burden on the client level. So client is responsible for figuring out which shard or shards to go to with for any given query. Haven't thought about this direction much, though. For global timeline, every shard has to get hit in this world, so that is not great but more thinking could go here.

2023-01-14 03:27:43 GMT

- reply

No at that point your phone itself will be Damus

2023-01-12 05:13:51 GMT

- reply

I’ve seen profiles flip-flop like that across other clients.
Updating relays is kinda tricky for clients to get right.
When you remove relays, a good client should first write to the profile with the full set of removals to all removed relays.
When a client reads profiles, it should make sure it caches the created-at timestamp and always let newest win.
Any latencies to get latest profile will also make your experience wonky.

2023-01-05 00:01:09 GMT

- reply

Do you see a lot of limit-less firehose queries? I’ve been thinking about auto-limiting users/clients that request the same big query repeatedly.

2023-01-04 23:45:12 GMT

- reply

I’ve been thinking relays should be able to redirect clients to download older (and compressed) event data from “firehose” subscriptions (i.e. [.., {}]) from a different url/endpoint — which could then be cdn cached etc.

2023-01-04 23:40:30 GMT

- reply

😎 how many active users? do you fulfill limit-less subscriptions fully (i.e. all of history?)

2023-01-04 04:40:56 GMT

- reply

I think good UX design can bring concept of branded relays to average user. It doesn’t have to be loud or complicated. I don’t see how nostr can reach ultimate potential otherwise. Relays must become first class in client UXs.

2023-01-04 00:40:32 GMT

- reply

Clients should keep a durable queue of sent messages and retry for a protracted (at least multi-minute) period.
Also clients need to be more relay-centric and indicate relay durability of messages through elegant UI.
Relay uptime calculations can and should forgive multi-minute outages.
Users can then hold relays accountable.

2023-01-01 02:21:13 GMT

New notes via websocket, old via batched paginated http api or archive downloads.

2022-12-31 02:57:35 GMT

- reply

Okay now I can make a blazingly snappy view. I'll out-compete most clients out there - because I'll use 1/nth their bandwidth. Now with most of the market share, aren't I just Twitter again? Especially as I become increasingly less motivated to post *out* of my walled garden.

2022-12-31 02:53:28 GMT

- reply

Okay let's implement our client server-side with a graphql or REST endpoint -- with all of the smart relay-passing etc to make it sound and performant... (2/n)

2022-12-31 02:50:38 GMT

What is a nostr "client"?
For max performance, a client would implement much of itself server-side. Mirror, proxy, etc and only serve each message once to the client view side. A lot of "clients" in the world are heavy server-side implementations. (1/n)

2022-12-30 03:45:55 GMT

This message is only being sent to wss://nostr-relay.untethr.me, so for those of you seeing it right now, thanks for staying with my relay as I work to scale it up!
(For those seeing it from a different relay, it may have been mirrored or re-broadcast...hello anyway!)

2022-12-24 01:56:13 GMT

- reply

Yeah -untether’s /q endpoint is really just for human admin/operator observability but should it be an restish api :thinking:

2022-12-23 14:45:24 GMT

really want to get relay pixel perfect on perf and nips coverage then work on desktop client. have so many ideas for the client. twitter deck with relay-aware ux...

2022-12-22 19:53:27 GMT

- reply

I might move to support https://github.com/nostr-protocol/nips/blob/2fa78a8097745139be5299c9f6117049f7d4a074/22.md but only restrict far-future events. At the end of the day, though, I don't see how clients can't avoid having to deal with future events....

2022-12-22 19:49:33 GMT

- reply

Am I the only relay that still supports future-dated posts?

2022-12-22 19:49:27 GMT

- reply

Am I the only relay that still supports future-dated posts?

2022-12-19 13:00:27 GMT

- reply

what latencies are you seeing?
my tiny relay is holding up decently but I’ll prob need to upgrade the machine soon

2022-06-09 15:42:40 GMT

- reply

https://github.com/ACINQ/secp256k1-kmp -- fme way faster than pure JVM impls

2022-04-19 03:00:22 GMT

why not sell nostr to elon musk

2022-03-21 01:35:19 GMT

I’ve been on vacation. What have I missed in nostrland

2022-03-10 02:38:05 GMT

- reply

I'm curious...

2022-03-09 21:41:28 GMT

- reply

Oops, a double-post.

2022-03-09 21:41:11 GMT

Thinking...

2022-03-09 21:41:05 GMT

Thinking...

2022-03-09 04:00:51 GMT

- reply

👍🏽😎😎😎

2022-03-09 02:49:05 GMT

- reply

I get it! Is this a desktop or web client?

2022-03-09 02:23:29 GMT

- reply

beautiful; i wanna use this beast, how do i

2022-03-08 14:30:24 GMT

"People used to laugh at me when I said I wanted to be a comedian. Well they're not laughing now." ― Bob Monkhouse

2022-03-08 13:52:49 GMT

Cold morning.

2022-03-07 21:19:27 GMT

- reply

But other clients will display all of the room chatter in users timelines potentially dominating it

2022-03-07 21:18:24 GMT

- reply

Nice!
Wonder if I should try some first class support for this
If user tells the client that an event represents a room then it can give a separate chat experience that’s more like Slack/telegraph
Keeping the lists out of the customary timeline

2022-03-07 17:11:30 GMT

- reply

But anyway- wonder if there has been thought to replacing Telegram w/ first-class nostr client?

2022-03-07 17:11:05 GMT

- reply

Only consequence is that your followers will see all of your chats in the room unless your client elides them. (Not sure what it could use to decide to elide them...without introducing some new nip/rule.) 4/

2022-03-07 17:09:25 GMT

- reply

Client can give first-class treatment to the "room" by having a more immediate chat experience (instead of this infrequent click-to-reply ux). 3/

2022-03-07 17:08:49 GMT

- reply

Everyone adds the room as an "identity" to the client, which will show all messages with a "p" tag. (There are no "follows" at all.) Client can add a "p" tag for each message in the room. 2/

2022-03-07 17:07:48 GMT

This desktop client is pretty snappy. Probably this has been discussed before. But public Telegram-style chatrooms could be had just be creating a new identity to represent the room 1/

2022-03-07 02:37:37 GMT

- reply

2022-03-06 22:01:35 GMT

Cool- now can use this untethr client for real. First functional publish and replies are working.

2022-03-06 22:01:01 GMT

- reply

What?

2022-03-06 21:42:49 GMT

- reply

You're not deep.

2022-03-06 21:39:48 GMT

- reply

Similarly deep.

2022-03-06 21:39:34 GMT

- reply

Deeper.

2022-03-06 21:34:58 GMT

- reply

Deep

2022-03-06 21:34:36 GMT

- reply

Sna

2022-03-06 21:22:11 GMT

- reply

Whatev

2022-03-06 21:21:21 GMT

- reply

Nope.

2022-03-06 15:59:19 GMT

- reply

👍 on my todo list to steal

2022-03-05 20:36:10 GMT

- reply

is it "on-relay-seen" ... right now i'm every received message is logging ------ but you should see the logs relatively quiet after all the data has been fetched from relays

2022-03-05 20:35:02 GMT

- reply

(i just pushed the first version of publishing to repo -- no reply ability yet)

2022-03-05 20:34:30 GMT

- reply

i haven't turned down any of the logs -- which ones in particular are you seeing ? maybe a quick screen shot

2022-03-05 19:45:13 GMT

How many relays does this hit?

2022-03-05 17:50:51 GMT

- reply

- on left you can add many identities- one will have focus and you'll see its timeline
- rn the whole thread is shown in the timeline - and a thread is sorted into timeline by its latest reply
- the end-to-end latency is fast!
- all ux & ui decisions are open for critique

2022-03-05 17:47:04 GMT

- reply

https://media1.giphy.com/media/kAKrd92lIX5gC6t9Wh/giphy.gif?cid=790b7611104ef1d747d7e304f21369e5c8c54e8bf039e817&rid=giphy.gif&ct=g

2022-03-05 17:47:03 GMT

- reply

https://media1.giphy.com/media/kAKrd92lIX5gC6t9Wh/giphy.gif?cid=790b7611104ef1d747d7e304f21369e5c8c54e8bf039e817&rid=giphy.gif&ct=g

2022-03-05 17:46:33 GMT

- reply

https://giphy.com/gifs/nostr-kAKrd92lIX5gC6t9Wh

2022-03-05 17:45:02 GMT

Hello world.

2022-03-05 17:41:47 GMT

Hello this is a new post.

2022-03-05 03:52:16 GMT

So fast.

2022-03-05 03:50:27 GMT

First message from desk client.

2022-03-05 02:03:38 GMT

Need a marketing team.

2022-03-04 03:54:19 GMT

- reply

Timelines show full threads right now. Would love for someone that can do pretty styles to give a pass. The styling is roughly css, but javafx style.

2022-03-04 03:53:20 GMT

Who wants to take an early spin w/ a nostr desktop client? On the left-hand side, you can add identities and see their timelines. No write/publish yet. You can manage relays by clicking in lower right. https://github.com/atdixon/me.untethr.nostr-desk

2022-02-25 04:30:13 GMT

writing an effective client is way harder than writing a relay

2022-02-24 22:06:33 GMT

- reply

latah

2022-02-24 00:58:01 GMT

- reply

👍

2022-02-23 04:03:19 GMT

- reply

Low right

2022-02-23 03:53:59 GMT

- reply

https://github.com/atdixon/me.untethr.nostr-desk -- not usable yet
if want to try: -- start it up per README, then manually add public keys to `identities_` sqlite table in `~/.nostr-desk/nd.db` then restart
all read-only so far except you can edit relays (click low left)

2022-02-22 14:27:04 GMT

- reply

been hacking here & there for a few weeks, whenever i can squeeze in some minutes, i will push it up to repo next chance i get

2022-02-22 08:41:38 GMT

- reply

clojure/clfx!