Ademan

Public Key

npub19jescdjr3wk552j3q77f3awwhe4qy2ds24xce773exd28nr7emqsm2pt7r

Profile Code

nprofile1qqszevcvxepcht229fgs00yc7h8tu6sz9xc92nvvl0gunx4re3lvasgprpmhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmdqyt8wumn8ghj7un9d3shjtnwdaehgu3wvfskueq9ywecr

Publishing to

relay.noswhere.com

relay.nostr.band

relay.damus.io

Author Public Key

npub19jescdjr3wk552j3q77f3awwhe4qy2ds24xce773exd28nr7emqsm2pt7r

Show more details

Last Notes

2024-08-04 21:59:30

We had some sprite left over from independence day and I watered it down with a lemon sparkling water. If it wasn't for the sugar I'd drink this every day.

2024-06-20 20:03:37

I feel like this has been done, but has anyone named a nostr client something like "Nosferatu"? If not I call dibs on "Nosbooratu"

2024-06-09 13:56:19

- reply

I am working on something incredibly stupid
https://image.nostr.build/8272c03c3c8c2f9053e71568be9d68de4788301139c0c92402681cc2a54153f9.jpg
https://image.nostr.build/77318b58e23d3c7555331d30b05d8656ce8982e47504fe54513221cd3838afac.jpg

2024-06-08 05:21:07

#test
This is a test

2024-06-07 18:55:49

- reply

The liquidity ads spec isn't complete yet is it?

2024-06-06 23:32:15

- reply

Ah that's true.
At the very least, supporting *emphasis* **emphasis** and block quotes in addition to the preformatted text you already do (on opt-in posts) would be nice. Since you're fiatjaf anyway you can overrule fiatjaf's fiat ruling on no-rich-text ;-)

2024-06-06 23:02:46

- reply

I mean I think every client is already processing image embeds anyway. markdown tables are human readable (nice to look at in plain text, even!).
Link aliases is probably the one that shouldn't be supported.

2024-06-06 21:53:29

- reply

It's definitely no longer plain text, if you interpret it as a code snippet/preformatted text.
But as hodlbod pointed out that line has kind of already been crossed with link previews, event and npub references, so *shrug*.
Might as well go full markdown imho. Would be easy to have a content type flag to say "this was MEANT to be markdown". Since markdown is perfectly readable as plain-text too, I think it's reasonably backwards compatible.

2024-06-05 20:26:33

- reply

Whoa, backticks work on kind 1s in coracle? I thought any kind of rich text in kind 1 was heavily discouraged, or has everyone just decided to do it anyway?

2024-06-05 19:39:37

@nprofile…tg2c did you ever consider inverse labels for NIP-32?
Something like
['L', '#t'], ['l', '-sfw-photography', '#t']
to remove an event from a hypothetical #sfw-photography hashtag
I have a couple of use cases but moderation is probably the primary one.

2024-06-05 17:38:55

- reply

oh right #asknostr

2024-06-05 17:32:54

Why do nostr events carry their own id? It's derived from the rest of the event, isn't it?
That's 72 wasted bytes on every event as far as I can tell, which isn't *that* much, but I don't understand why it's there at all.

2024-05-29 02:00:51

- reply

Yeah, he's also just wrong about the privacy point.
He's right about custody though imho. OP's attempt to show ECash isn't custodial feels tortured.

2024-05-15 04:10:21

- reply

Bad news about OP_VAULT https://twitter.com/reardencode/status/1756185478716657830
(I have not checked Brandon's work on this, but you can see that I had the intuition about it independently)
https://image.nostr.build/d4c019e99aa6587b5f34906e2547ca4a47f06a16a45cc4a5b04c54d258a86231.jpg

2024-05-15 02:21:57

- reply

closed source? egh

2024-05-14 19:11:15

- reply

What paper are you referring to? The original uses descending timelocks for updates unless I'm missing something.
Regardless, a simple coinpool like tr(<everyone>, {<ctv unroll tx>}) with channel opens for leaves meets the only definition of channel factory that I'm familiar with, and does not require APO (or similar) at all, only CTV.

2024-05-14 00:10:09

- reply

The original channel factory paper definitely doesn't. It doesn't even require CTV. What are you talking about specifically?

2024-05-13 15:47:07

- reply

Timeout trees can be used for lightning channels but it's not really their only use.
Lightning's biggest problem actually IS channel opens right now, it would take ~5.5 years to open 1 billion lightning channels right now. Whereas you could (in theory, but there are practical limits much lower) open 1 billion lightning channels in one transaction with CTV.
*Then* the problem becomes uncooperative closes (force closes and attempted thefts). If you have a billion people competing for block space to handle closes, that could get messy too.
But if we can use CTV to increase channel open capacity, and we can limit the need for uncooperative closes, then overall capacity dramatically increases.

2024-05-13 15:39:48

- reply

Channel factories can be done with just CTV. LNHANCE includes CTV of course.

2024-05-13 00:16:34

- reply

CTV enables coinpools, giant channel factories, Ark, and timeout trees. Each of these offer 10x-1000x scalability improvements (with different tradeoffs). The good news is we don't need to handle billions yet, but CTV gets us close (or maybe over!) the first Billion.

2024-05-12 20:16:51

Does anyone following me have a technical/incentives concern with CTV?

2024-05-10 20:07:47

- reply

Have you looked at https://github.com/braidpool/braidpool ?
It's not a substitute for Sv2 but it's an interesting p2pool revival.

2024-05-08 20:49:54

- reply

> my points were all objective and yours are all subjective, you didn't deny my criticisms
you were talking out of your ass and making shit up, verifiably.
As for subjective things like performance, any claims of performance problems ring completely hollow when I run my instance on a tiny underpowered VPS and it runs circles around every nostr client I've tried.
> you just let it slip your bitterness and resentment against Nostr
I don't hate nostr. I want nostr to get better, and I said outright I think it can.
I'm annoyed because nothing you said was true and you accused me of "bullshit".
The search and remote interaction points are verifiably wrong. Here's some screenshots in case there's a third party confused who is "bullshit"ing and who isn't.
https://image.nostr.build/27cb8d9a3efc732ccd2df332ec967d1646ae7438004e7ccafe2289c19c3d3c4e.jpg
https://image.nostr.build/d1fed5bdcaf096b8ee81c560a5369da68990131125b0dbfa5dbf142da20986d8.jpg
These features have been present since 2017. Here's a github issue about search from 2017 that establishes search was present before this PR was submitted. https://github.com/mastodon/mastodon/pull/1582
Here's a PR for remote following from 2017 https://github.com/mastodon/mastodon/pull/898
Here's a PR for remote interaction with individual posts from 2017 https://github.com/mastodon/mastodon/pull/8202
There's receipts, now please GTFO my notifications.

2024-05-06 23:03:12

- reply

everything you just mentioned is as bad as or 100x worse on nostr
> reply and like counts where always wrong
10000x worse on nostr are you kidding me? There isn't even a canonical version of a thread to know if the count is correct.
> threads never loaded completely
same, except you'd never even know on nostr.
> everything was slow as hell
Maybe *only* 100x worse on nostr
> DMs suck
Nostr DMs weaken the security of your key dude
> no search
Factually incorrect, even in 2017.
> following people if you had their name/address was often cumbersome
Allow me to introduce you to non-human-readable pubkeys for identifiers
> sometimes you're just browsing on other servers, not your home server, for some reason, and there is no way to go home so you can interact
That's wrong, there literally is an "interact on my home server" button. But that's an admittedly clunky UX.
And in closing, mastodon is not the only fediverse server software. Pleroma is what I recommend, with the soapbox frontend. I genuinely have no idea what instance you used, or when, my only conclusion is it was misconfigured. Even in 2017 mastodon's UX was far better.

2024-05-06 22:10:37

- reply

It's (mostly) not inherently better, it's mostly a maturity issue. The current version of the fediverse has been around since 2017.
My preferred fediverse UI will be coming to nostr eventually via @nprofile…qdcn although I think there's a primal-style intermediate server involved.
Most of the more "inherent" problems are solved by some kind of intermediate caching server (local relay might address this). I really don't like the way most clients seem to fetch everything and keep very little state, notes end up loading slowly, out of order and popping in.
markdown notes are great on fedi, I hope they will also come to nostr (there are already markdown kinds, but I'm not sure if there are any markdown "note" kinds)
discoverability is just awful on nostr, feels like I'm shouting into the void here, I'm shadowbanned on twitter and have better reach, and far better than either on fedi.
the instance model in the fediverse has some nice benefits in community, discoverability, moderation, but there's downsides too, obviously.
silly thing, but the fediverse's custom emojis create fun for people (and fun matters).
That doesn't add up to a million x but I hope you'll forgive the hyperbole lol
I think I'm bullish on nostr long term but things are still rough imho

2024-05-06 21:48:34

- reply

I've been running a fediverse instance as a backup for several years now. nostr is more resilient but I think fedi is resilient enough (and the UX is a million times better)

2024-05-03 23:48:56

As far as I can tell the "script restoration project" is literally blowing the doors open on all of the open ended, bad behavior with unknown incentives we've been worrying about for the past 6 years (or since Satoshi disabled the opcodes in the first place if you'd like). WTAF?

2024-04-22 15:34:38

- reply

https://rubin.io/bitcoin/2022/09/14/drivechain-apo/

2024-02-01 20:38:01

OP_CAT enables recursive covenants https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-February/019976.html
Reject CATs as-is.

2024-01-05 04:09:29

- reply

Can't compete on TH/$ up front cost, but the bitaxe is actually more efficient, at least by the raw numbers https://opensourceminer.com/products/bitaxe-201 and it's available today.

2023-12-21 06:09:51

- reply

the kind number lines up

2023-11-16 18:44:03

- reply

test

2023-11-16 18:43:36

- reply

Right, my point was "rejection" might be the wrong way to show 500 errors in the UI.

2023-11-16 18:35:10

- reply

Funny, I ended up with two rejections too, but they're different relays. I wonder if 500 errors end up being shown as rejections in coracle...
https://image.nostr.build/177af3671ff9ade52335ee5e554bb439d2a18b147b8f636514c3338ade943f94.jpg

2023-11-16 18:32:56

- reply

That's a new one, rejected your note?... was it spicy or do you think it was a technical issue?

2023-10-03 22:40:07

Side note, I'm convinced nobody at all sees my posts, and nobody did on my previous account either. It would be nice if I could generate a proof of work to improve my visibility.

2023-09-19 19:23:53

- reply

If the HW device doesn't simply use the provided nonce as-is (seems undesirable due to sensitivity of nonces), can't the HW device still grind it's portion of the nonce to exfil?
It seems like an extra round of communication is unavoidable? (but likely worthwhile!)