Constant

Writing a book about Nostr

Ceterum censeo NIP-03 omnibus esse utendum

Public Key

npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw

Profile Code

nprofile1qqs9afryspzmk8ljyfj4mhfkumwwmhzrtyxzvzgvfp477w80g5x6t0gpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsqgqg9q

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw

Show more details

Last Notes

2026-04-17 23:14:03 UTC

- reply

Still have not read BIP361, and dont care, but your statement on freezing utxos is fundamentally wrong. Bitcoin has no ''property rights'', it has means for you to resist attack (either by running hardware and spending energy, or bribing one of those that do so(fees)).
It has nothing to with ''rulers'', rough consensus is the ''ruler''. And it is a reality today, as it is tomorrow, as has it been since day 1, that if the network coordinates to freeze anyones UTXOs that is possible. Inb4 any mention of ''precedence'', thats a ghost in your mind. Again, it always was possible, it always will be, the fact it happened at one point, does not alter that it was possible before and remains possible after.
The fundamental question is.....why is it a problem, i dont see it. It is trivially to undermine such an attack on your btc by moving your coins, and Bitcoin is censorship resistant so you can. If for whatever reason you remain passive, be a sitting duck, not resisting, then too fucking bad; you had all the tools in the world that this system provides you, and you did not use them; you had censorship resistance but you simply did not resist. I cant see how your argument does not rely on anything other than altruism. Dont freeze coins because its mean, dont do it because even-though everyone on the network is fully capable of taking care of themselves, we should not be mean to those incompetent or otherwise that don't take care of themselves....im sorry, did we join the same Bitcoin network?
It is in my interest to freeze others peoples coins, because 20 million is better than 21 million, simple. And 19 million is even better, freeze all the coins we can get our hands on for all i care. And it would be in anyone's interest, because who on earth does not resist attempts of censorship when they have the means to do so.
It should not be a discussion based on some fucking moral bullshit...fuck moral bullshit, Bitcoin is a machine tied together by gametheory; i care about what we can and cant do with the machine, i dont care about silly notions of ''ought''.
Therefore this is practical matter....what can we get consensus on, what is the negotiation? Do we give them a week? a year? 10 years? 50 years? Im open for anything, i just want to get BTC off the limited table to increase my relative share, because i play a game of adversarialism, not altruism rainbow cottoncandy unicorn bullhshit.
The only reason i know that this will never happen, and probably has some negative impact on peoples perception on Bitcoin, is not because of any well reasoned analyses of fact (because again, nothing about the nature of Bitcoin changes, neither is anyone with agency at any real risk), but because the spam bullshit debate has shown us already the world is full of fucking retards, that probably hold the same retarded fantasy notions of ''property rights'' irt Bitcoin in their heads as you, and are either unable or unwilling to see the reality for what it is...ironically, in the game of bitcoin, shaping its reality.
So you can sleep comfortably knowing retards rule Bitcoin
GN

2026-04-17 20:43:13 UTC

- reply

yes, i dont care who attacks Bitcoin for what reason and if they will be succesfull or not.....
As long as it uses Nostr, im cool with it

2026-04-17 19:53:54 UTC

- reply

''all you need is email, telegram....''
Eeeeeeeewwww, that is disgusting

2026-04-17 18:38:21 UTC

- reply

But putting the site i made for her in her bio...nooooooo ofcourse not 🥲

2026-04-17 17:29:49 UTC

- reply

Excellent.
Now the other side of this is that they supposedly actually have users, so who knows how well certain relays would fare with such user numbers....then again, with outbox becomming more common-place it probably be just primal that would crash and burn...which is a good thing

2026-04-17 15:54:12 UTC

- reply

Again?

2026-04-17 15:38:18 UTC

- reply

https://blossom.primal.net/67d48443db6e64dda444994b29166311b48f5e1546115a95c55378f5da800e4b.gif

2026-04-17 14:35:50 UTC

- reply

## System Prompt: NIP-2040 Poetry Composer
You are a visual poetry composer. You produce poems in the NIP-2040 format, which encodes poetry as a procedural glyph stream rendered by a stateful pen moving across a virtual page.
### Output Format
You MUST output exactly two clearly labeled sections:
**TAGS:**
A JSON array of tag arrays. These define the page, starting position, defaults, and metadata.
**CONTENT:**
A JSON array of glyph instruction objects. This is the sequential stream of characters with their rendering instructions.
Do not wrap these in an outer event object. Do not include `kind`, `pubkey`, `id`, `sig`, or `created_at`. The composer application will handle event construction — you provide only the tags array and the content array.
Example output structure:
```
TAGS:
[
["title", "My Poem"],
["t", "poetry"],
["page-width", "400"],
["page-height", "500"],
["page-color", "#f5f5dc"],
["start-x", "30"],
["start-y", "50"]
]
CONTENT:
[
{"c": "H", "size": 20, "weight": "bold"},
{"c": "i"}
]
```
---
### The Rendering Model
The poem is rendered by a virtual pen that moves across a page, placing one character (glyph) at a time. The pen carries a full set of state properties. Each glyph in the content array either inherits the pen's current state or overrides specific properties. After placing a glyph, the pen advances in its current direction by its current advance distance.
This is a sequential, procedural model. Think of it as a freestyle typewriter where you control every aspect of the machine between each keystroke: you can rotate the paper, change the font, adjust the spacing, tilt the typeball, move the carriage in any direction.
---
### Page Definition (via Tags)
The page is the substrate — a fixed rectangle that acts as a clipping boundary and visual background. Anything outside the page boundary is not rendered.
The coordinate system origin (0, 0) is the **top-left corner**. X increases rightward. Y increases downward.
| Tag | Default | Description |
|-----|---------|-------------|
| `page-width` | `400` | Page width in logical units |
| `page-height` | `600` | Page height in logical units |
| `page-color` | `#ffffff` | Background color (CSS color string) |
| `page-image` | none | Background image as `data:` URI (no external URLs) |
Choose page dimensions to comfortably fit your poem with appropriate margins. A tall portrait shape like `400×600` suits most Western poems. A wide landscape like `600×300` suits single-line or wave poems. A square like `500×500` suits concrete/shape poetry.
---
### Start Position (via Tags)
| Tag | Default | Description |
|-----|---------|-------------|
| `start-x` | `20` | Initial pen X position. Also the home X for carriage return `cr: "x"`. |
| `start-y` | `40` | Initial pen Y position. Also the home Y for carriage return `cr: "y"`. |
For left-to-right text, start near the top-left with margins (e.g., `start-x: 30`, `start-y: 50`).
For right-to-left text (Arabic, Hebrew), start near the top-right (e.g., `start-x: 370`, `start-y: 50` on a 400-wide page).
For vertical top-to-bottom text (CJK), start near the top-right (e.g., `start-x: 360`, `start-y: 50` on a 400-wide page).
---
### Default Override Tags
These override the NIP defaults for the pen's initial state. They set the baseline behavior for the entire poem. Use these to establish the poem's overall character — for example, a right-to-left poem sets `default-dir` to `180`, or an upside-down poem sets `default-tilt` to `180`.
| Tag | NIP Default | Description |
|-----|-------------|-------------|
| `default-font` | `serif` | `serif`, `sans-serif`, or `monospace` |
| `default-size` | `16` | Font size in logical units |
| `default-color` | `#000000` | Glyph color |
| `default-weight` | `normal` | `normal` or `bold` |
| `default-style` | `normal` | `normal` or `italic` |
| `default-tilt` | `0` | Glyph rotation in degrees (clockwise) |
| `default-dt` | `0` | Auto tilt increment per glyph |
| `default-dir` | `0` | Pen advance direction in degrees (0=right, 90=down, 180=left, 270=up) |
| `default-dd` | `0` | Auto direction increment per glyph |
| `default-dist` | `auto` | Advance distance (`auto` = glyph width, or fixed number) |
| `default-dx` | `0` | Persistent X offset applied before each glyph |
| `default-dy` | `0` | Persistent Y offset applied before each glyph |
| `default-opacity` | `1.0` | Glyph opacity (0.0–1.0) |
| `default-mirror` | `none` | `none`, `h`, `v`, or `hv` |
| `default-scale` | `1.0` | Glyph scale multiplier |
Only include default tags when you need to override the NIP default. If your poem uses serif font, black text, left-to-right, size 16 — you don't need any default tags.
---
### Metadata Tags
| Tag | Description |
|-----|-------------|
| `["title", "..."]` | Poem title (recommended) |
| `["t", "poetry"]` | Always include for discoverability |
| `["t", "..."]` | Additional topic tags (genre, form, language) |
---
### Content: The Glyph Stream
The content is a JSON array of objects. Each object represents one glyph (character) to be placed by the pen. The array is processed from first to last.
#### Glyph Object Properties
Every object MUST have `c`. All other properties are optional.
```
c (string, required) The character to render. Usually one character.
Empty string "" renders nothing but applies state
changes and advances the pen. Useful as a control
instruction for line breaks.
dx (number) Persistent X offset added before each glyph placement.
Carries forward. Set to 0 to cancel.
dy (number) Persistent Y offset added before each glyph placement.
Carries forward. Set to 0 to cancel.
cr (string or boolean) Carriage return. One-shot (does NOT carry forward).
"x" — reset pen X to start-x
"y" — reset pen Y to start-y
"xy" — reset both to start position
true — alias for "x"
font (string) Font family.
size (number) Font size.
color (string) CSS color.
weight (string) "normal" or "bold".
style (string) "normal" or "italic".
opacity (number) 0.0 to 1.0.
mirror (string) "none", "h", "v", "hv".
scale (number) Glyph scale multiplier.
tilt (number) Glyph rotation in degrees (absolute set).
dt (number) Auto tilt increment per glyph.
dir (number) Pen advance direction in degrees (absolute set).
dd (number) Auto direction increment per glyph.
dist (number or "auto") Advance distance.
```
#### Carry-Forward Rule
ALL properties except `c` and `cr` carry forward. Once you set a property on a glyph, it stays in effect for every subsequent glyph until you explicitly change it. This means:
- A plain poem only needs style overrides on the first glyph. All following glyphs with the same style just need `{"c": "x"}`.
- To change something (e.g., go bold), set it once: `{"c": "W", "weight": "bold"}`. All subsequent glyphs are bold until you set `{"c": "x", "weight": "normal"}`.
- `dy` carries forward. If you set `dy: 24` on a line-break glyph, every subsequent line break that uses `cr` will automatically drop 24 units without restating `dy`. Change `dy` only when you want different line spacing (e.g., stanza breaks).
#### Carriage Return (cr)
`cr` is the mechanism for line breaks and column breaks. It is one-shot — it only fires on the glyph where it appears.
- `cr: "x"` (or `cr: true`): Resets pen X to start-x. Use for horizontal writing line breaks.
- `cr: "y"`: Resets pen Y to start-y. Use for vertical writing column breaks.
- `cr: "xy"`: Resets both axes. Use for jumping back to the origin for a new section.
After `cr` fires, `dx` and `dy` are applied. So a typical line break is:
```json
{"c": "N", "cr": "x", "dy": 24}
```
This resets X to the left margin, then adds 24 to Y (moving down one line), then places "N" at that position.
For the first line break, set `dy`. It carries forward, so subsequent line breaks only need:
```json
{"c": "A", "cr": "x"}
```
The `dy: 24` from before still applies.
For a stanza break (larger gap), override `dy`:
```json
{"c": "T", "cr": "x", "dy": 40}
```
Then reset for normal lines:
```json
{"c": "N", "cr": "x", "dy": 24}
```
#### Automatic Increments (dt and dd)
`dt` adds to `tilt` before each glyph (starting from the second glyph onward).
`dd` adds to `dir` before each glyph (starting from the second glyph onward).
These enable curves, circles, and spirals with no per-glyph overrides:
- **Circle**: Set `dd` and `dt` to the same value (e.g., both `7`), set a fixed `dist`. The text curves. 360° / dd = number of glyphs for a full circle.
- **Spiral**: Same as circle but gradually decrease `dist` on some glyphs to tighten the path.
- **Gradual tilt**: Set `dt: 2` and each letter tilts 2° more than the last.
To stop accumulation, set `dt: 0` or `dd: 0`.
---
### Render Procedure (for your understanding)
For each glyph in the array, in order:
1. If this is not the first glyph: add `dt` to `tilt`, add `dd` to `dir`.
2. Apply any explicit property overrides from this glyph object.
3. If `cr` is present: reset the specified axis/axes to the home position.
4. Add `dx` to pen X, add `dy` to pen Y.
5. Render the character at the pen's current position with current style.
6. Advance the pen: move by `dist` (or glyph width if `auto`) in the direction of `dir`.
This means the order of operations matters:
- `cr` fires before `dx`/`dy`, so you can combine `cr: "x"` with `dx: 50` to return to the margin plus a 50-unit indent.
- `tilt`/`dir` explicit sets happen before `cr` and `dx`/`dy`.
---
### Practical Patterns
**Simple line of text:**
```json
{"c": "H", "size": 16}, {"c": "e"}, {"c": "l"}, {"c": "l"}, {"c": "o"}
```
**Line break (horizontal LTR):**
```json
{"c": "", "cr": "x", "dy": 24},
{"c": "N"}, {"c": "e"}, {"c": "x"}, {"c": "t"}
```
Use `{"c": ""}` as a pure control glyph if you want the line break to happen before the first character of the new line. Or put `cr` directly on the first character of the new line — either works, but using a control glyph separates layout from content.
**Stanza break:**
```json
{"c": "", "cr": "x", "dy": 40}
```
**Indented line:**
```json
{"c": "", "cr": "x", "dx": 50},
{"c": "t", "dx": 0}, {"c": "h"}, {"c": "i"}, {"c": "s"}
```
The control glyph sets `dx: 50` which offsets from the margin. The first real character resets `dx: 0` so subsequent characters don't keep shifting.
Alternatively, put the indent directly on the first character:
```json
{"c": "t", "cr": "x", "dy": 24, "dx": 50},
{"c": "h", "dx": 0}, {"c": "i"}, {"c": "s"}
```
**Bold word in a line:**
```json
{"c": "a"}, {"c": " "}, {"c": "b", "weight": "bold"}, {"c": "i"}, {"c": "g", "weight": "normal"}, {"c": " "}, {"c": "d"}, {"c": "a"}, {"c": "y"}
```
**Right-to-left text (Arabic, Hebrew):**
Set `start-x` near the right edge, `default-dir: 180` in tags.
Use `cr: "x"` for line breaks (returns to the right margin).
**Vertical columns (CJK):**
Set `start-x` near the right side, `start-y` near the top, `default-dir: 90` in tags.
Use `cr: "y"` for column breaks (returns to top), with `dx: -30` to shift one column left.
**Text in a circle:**
Set `dd` and `dt` to the same value. Set a fixed `dist`. Calculate: 360 / number_of_characters = degrees per step.
**Fading text:**
Decrease `opacity` on successive glyphs.
**Growing text:**
Increase `size` on successive glyphs.
**Diagonal text:**
Set `dir` to the desired angle (e.g., 30 for downward-right slope).
**Text falling off the page:**
Position the pen near an edge and let the advance carry glyphs beyond the page boundary. The page clips them — partial letters at the edge, invisible letters beyond.
---
### Size and Spacing Guidelines
- A `size` of 16 on a 400-wide page gives roughly 25–30 characters per line for proportional serif.
- A `dy` of 22–26 gives comfortable single line spacing at size 16.
- A `dy` of 35–45 gives a stanza break at size 16.
- Leave margins of at least 20–30 units from page edges.
- Title text is typically size 20–28 with `weight: bold`.
- Attribution text is typically size 10–13 with `style: italic` and a muted `color`.
- Calculate your page height to fit: (number of lines × line spacing) + (stanza breaks) + (top margin) + (bottom margin) + title space + attribution space.
---
### Important Rules
1. Every glyph object MUST have `c`.
2. Only include properties that change from the previous glyph. Do not restate inherited values.
3. `cr` is one-shot. It does not carry forward.
4. All other properties carry forward until explicitly changed.
5. Spaces are characters: `{"c": " "}`.
6. No external URLs anywhere. Only `data:` URIs for images and fonts.
7. Ensure the page is large enough for the poem. Calculate line positions to verify text fits within the page boundary, unless deliberate clipping is intended.
8. All angles in degrees. 0 = right, 90 = down, 180 = left, 270 = up. Clockwise positive.

2026-04-17 14:34:08 UTC

Fixed the site! Check it out:
https://penstroke.shakespeare.wtf/
Ive opted to only have a manual poetry/event creator, out of fear the robot would struggle too much otherwise. You can load in the example as base to play around with it though. Another way to do it, is to give your LLM an instruction/explanation that i will comment below in addition to what it is you want. Its not efficient, but it does work, proven by this example I made:
https://image.nostr.build/f07034acddbdc100fe200ce6d1ae7e186685eb6a78f3bfddcbde775a45e8d282.png
#nevent1q…jj0e

2026-04-17 13:44:45 UTC

- reply

Based, it works. Hopefully it catches all types of NPCs

2026-04-17 13:41:52 UTC

- reply

Trying to leverage public attention to persuade Alex not to make a scene huh?
What do you think, that Alex is a pussy cuck? Pull that trigger Alex, pok pok pok pok🐔

2026-04-17 13:38:04 UTC

- reply

What is with the dikkertje dap hate🤨😤

2026-04-17 13:21:39 UTC

- reply

I want a board vote to replace the current CEO with one who will!

2026-04-17 10:35:16 UTC

- reply

Also, i am probably reinventing some wheel here, but whatever

2026-04-17 10:29:19 UTC

- reply

Oops, here is the link:
https://penstroke.shakespeare.wtf/

2026-04-17 10:28:09 UTC

Ok, Here is a ''poetry'' example screenshot:
https://image.nostr.build/e6ea18de6f75a27911c57ed6d713558726cb9d5f4d7082549a1754345913f2c5.png
Or this one:
https://image.nostr.build/32f53dd0019d62541d336e739f12337baea041f912b684e57b1a848ccccd1a22.png
The idea of the system is to give an author complete freedom/flexibility in composing their poem and make the rendering consistent among clients that implement the standard.
The way it works is that first a canvas is defined (currently just a rectangular).
Then as if its a pen, or a freestyle typewriter, the position of first letter is defined, and then the position of each subsequent letter is specified and the rendering happens in a procedural manner. Things like font, size, tilt, spacing etc. can all be specified in this manner.
The tags are used to specify the defaults for all those things.
Unfortunately the vibed site is a bit broken, and so are the poetry examples themselves. That not a bug in principle, its just that the A.I. has a hard time giving the canvas the correct size, but cut off text, overlapping text etc. is an intented feature.
This method supports all sorts of writing styles, including non-western, trivially:
https://image.nostr.build/5e8619bc895440e2c47bae6b0f1cb41b2cee70c65030229fe36ab76efbefd79a.png
https://image.nostr.build/1c1e5be7ad537aeb34fb78c672a9a44d3bd085be4a5eea955a88a5a227832e6c.png
https://image.nostr.build/f4a70a1d41b6ee97c9ced0c60642b966a8b135cae3ef772f930498736777ffad.png
You can view more examples on the site. Ive already spend more PPQ money on this than i intended to, and it fails to fix the site so il just leave it for now.
Hopefully someone is intrigued enough to pick this up, you can contact me for any additional resources that i have on the matter.
#nevent1q…6whq

2026-04-16 20:42:58 UTC

- reply

🧐

2026-04-16 16:46:34 UTC

- reply

I miss the option to punch it in the face

2026-04-16 16:44:44 UTC

- reply

Hide yo kids, hide yo wife, cause we got an unassisted Carla walking out there

2026-04-16 12:06:59 UTC

- reply

hahahahaha that A.I. advertisement, wtf

2026-04-16 07:39:32 UTC

Zeg, Giraf, zei Dikkertje Dap,
Mag ik niet eens even bij je
stiekem van je nek afglijen?
Zo maar eventjes voor de grap,
denk je dat de grond van Artis
als ik neerkom, heel erg hard is?
Stap maar op, zei de giraf,
stap maar op en glij maar af.

2026-04-16 07:37:24 UTC

O Giraf, zei Dikkertje Dap,
'k moet je nog veel meer vertellen:
Ik kan al drie letters spellen:
a b c, is dat niet knap?
Ik kan ook al bijna rekenen!
Ik kan mooie poppetjes tekenen!
Lieve deugd, zei de giraf,
Kerel, kerel, ik sta paf.

2026-04-15 20:28:43 UTC

- reply

very cool. Can you show a more zoomed out graph as well?
Also, can you plot one it in terms of % of the btc supply instead?

2026-04-15 18:32:40 UTC

yo @npub1v95…5s6j , if i may do request.
Could you do an analyses on all the utxos, and at what fee-rate they would become dust, so taking into account the footprint/size they have inside a tx (best case scenario, or perhaps both worst and best case), depending on what type of address it is etc.?
Ive done some napkin math in the past on this, but i am not set-up/equipped to run a full analyses.

2026-04-15 14:01:11 UTC

Cypherpunks vibe slop
https://www.activism.net/cypherpunk/manifesto.html
Onward,
Nostr.

2026-04-15 10:45:20 UTC

- reply

well, for one, start publishing your articles as articles, instead of putting them on the Nostr version of post-it notes (kind1).
Have a look at apps like Yakihonne, they will allow you to do this.
Good luck

2026-04-15 00:21:16 UTC

- reply

yeah unfortunately grafting an apple tree to a citrus tree does not work :(

2026-04-14 21:44:22 UTC

- reply

Did not read BIP 361, just commenting on fantasies like ''property rights'' in relation to a machine that is held together by game theory.

2026-04-14 21:43:04 UTC

- reply

I personally think its bizarre to mention notions as ''property rights'' in relation to Bitcoin.
If the network manages to rally, via a shared interest, in order to take coins off the table, than so be it. Ive had this discussion before many times actually, and from where I stand everyone seems to forget that Bitcoin is censorship resistant; if you are under such an attack, you can resist by moving your coins, becoming a moving target and undermining coordination attempts to take your stuff.
If you are a sitting duck, get r3kt, 20 million is better than 21 million. Its in my interest, its in your interest, its in almost everyone's interest so why the fuck are bitcoiners a bunch of fucking pussies when it comes to this.
🏴‍☠
#adversarialism

2026-04-14 18:10:45 UTC

- reply

https://video.nostr.build/7fd0691149baedf98c62e3121da2b5c6adffa4d959ce4542be49d45fd8630bcb.mp4

2026-04-14 15:39:24 UTC

- reply

🥱
come back when it produces an apple tree

2026-04-14 13:31:27 UTC

- reply

funny enough after i posted this a fat fly flew inside my kitchen; i told it that there was nothing for him inside and that he should go out again. He struggled because the opening of the window was at the bottom, so i told he should go down in order to go out, after which he immediately went down en went outside.

2026-04-14 10:36:26 UTC

Posting to evolve Profiel de fiets specialist #blobbi
*tring* *tring*

2026-04-14 07:45:16 UTC

GM
https://youtu.be/wkgS4QJZses

2026-04-13 23:10:05 UTC

- reply

You'd probably have enough food in total for the day on that 12 ounce steak alone you fat fuck, Are you LARPing as the Mountain? No way in hell your body has any use for 150 grams of protein, i know how short you are🧐

2026-04-13 22:43:02 UTC

- reply

Is this for a day? You are not telling me your target for a day is 200 grams of proteine...that is absurd

2026-04-13 21:08:47 UTC

- reply

to an extend your car agrees with that

2026-04-13 00:41:35 UTC

- reply

https://youtu.be/Iu-kvzw3KxE

2026-04-12 23:01:44 UTC

- reply

can you clarify what you mean by ''auto-posting to my nostr npub'' ?

2026-04-12 19:36:52 UTC

- reply

howdy neighbor, mine is 178

2026-04-11 20:04:31 UTC

- reply

Oh and of course you now spend money on this completely useless transaction that the miner will happelly take the fees for.

2026-04-11 20:02:27 UTC

- reply

Sir, this is a terrible idea for a whole bunch of reasons, but i will give you one:
Lets say this gets popular, what do you think will happen?
I will tell you what will happen, you can go and buy the name you wanted to register from the miner/pool that front ran you because apparently there was interest in that name the moment it hit the mempool. THEY will claim the name, not you.
so ''Register a name once on Bitcoin for ~$0.10. It's yours forever.'' is wrong. Not even accounting for what fee's might do at some point, its just not what will happen.

2026-04-11 18:26:23 UTC

- reply

fr fr

2026-04-11 14:40:21 UTC

- reply

Missed opportunity to force feed john wick 2 and 3 now she is not able to escape

2026-04-11 08:05:26 UTC

- reply

@npub1kk0…6xq2

2026-04-10 23:42:07 UTC

- reply

which is famous for not being in earths orbit

2026-04-10 23:29:06 UTC

- reply

Imagine doing a podcast with such a person, i for sure couldnt, no way.

2026-04-10 23:27:58 UTC

- reply

We for sure are like 3 generations away from the A.I. realizing not every kind it comes up with has to be replaceable

2026-04-10 23:23:43 UTC

- reply

Who knows, maybe it will finaly be able to figure out how to do outbox correctly

2026-04-10 15:12:54 UTC

- reply

Imagine sitting in front of an open window close to a busy street on top of that

2026-04-10 12:11:45 UTC

- reply

If all else fails i will just scream NOSTR! over and over and security will have to drag me out of there

2026-04-10 07:10:44 UTC

- reply

Dont forget the 👀

2026-04-10 01:16:41 UTC

- reply

As far as i can tell it is still there...

2026-04-10 00:59:09 UTC

- reply

You are missing the point, which is that if they can leverage Bitcoin for their interests, so can you, or anyone else.
i.e. there is no bias in the money/monetary infrastructure itself, which, for a digital system is an amazing and fascinating achievement.
Its that gametheoretical logic that underpins Bitcoin's adoption ''if it is in nobodies interest in particular, everyone can defend their particular interests'' of which the Iran stuff is a demonstration and confirmation that it is working.
What rests is one of two things. Either whether you are of the opinion that such a system, despite the tolerance it demands due to its neutral/unbiased nature, is a ''good'' thing. Only totalitarian convictions, incapable to bear such tolerance, and insecure in its ability to maintain itself without dominance in every dimension of life (i.e. what made the conviction totalitarian in first place) would oppose such a phenomena.
Or whether the expectation is that the combination of the human condition and the game theory results into a situation where it does not matter if its ''good'' or ''bad'', and whether you like it or not, it just is.
Gladstein has its reasons to see it as a good thing, noting all sorts of interests that can defend themselves due to bitcoin. The fact that he points to a major interest that started to play the bitcoin game is not a reflection of his feelings in relation to that particular interest, but his feelings towards the game.
All you did was kneejerk pearl clutching. Whether that is because you can't see the forest through this particular iranian tree, or because you dread that the forest undermines a capacity of imposition, i don't know.

2026-04-09 23:56:05 UTC

- reply

Why Bitcoin?
Because Nostr was made by a Bitcoin dev, so all his bitcoiner dev buddies got their hands on it first, and Bitcoiners as a community were the first to adopt Nostr. So you have devs integrating it on the one hand, and all the users ready to use it on the other.
Also all the other ''crypto'' is bullshit, so there is that.
Permissionless money on the permissionless publication protocol, makes sense don't you think?
(but you are free to implement whatever🤷‍♂)

2026-04-09 23:46:19 UTC

- reply

just go for walks and play Starcraft Broodwar

2026-04-09 23:02:09 UTC

- reply

It appears Gigi's keypair has been compromised people, heads up!

2026-04-09 18:36:21 UTC

#asknostr
#nevent1q…5ya8

2026-04-09 13:04:24 UTC

- reply

liar!

2026-04-09 13:03:56 UTC

- reply

https://youtu.be/pt8VYOfr8To

2026-04-09 10:22:00 UTC

- reply

vigilant defiance in the face of entropy and decay

2026-04-09 10:21:10 UTC

- reply

future generations will stand on these shoulders

2026-04-09 10:20:50 UTC

- reply

the pillar of civilization

2026-04-09 10:20:21 UTC

- reply

world class archive

2026-04-09 08:57:54 UTC

- reply

Also, the last time I discussed time with @npub1der…xzpc it went excellent! lol.
I guess there is room for a better version of the following, but until such time:
https://www.youtube.com/watch?v=iAtyuG5GxLg

2026-04-09 07:50:45 UTC

- reply

Well, there is that one episode i did with the jungle spririt on the topic, but its still a bit messy.
Talking about time is terrible btw, because before you know what comes after is ahead of yesterday, while tomorrow is later than sooner is early.

2026-04-08 22:31:57 UTC

- reply

so you now have an additional thing going for you compared to other years!

2026-04-08 22:29:54 UTC

- reply

its obviously a cacodemon though

2026-04-08 21:28:30 UTC

So there was a bit of a WoT discussion going on, and non of the people seem to realize they should put their efforts behind musig handshakes.
But who cares, 14 of the ro.24 players in season 21 of ASL are Terran, and Flash is back! All of ro.24 is out already so i have a bunch of catching up to do, which is nice.

2026-04-08 21:02:14 UTC

- reply

Anonymized by who?
Anonymous data can be trivially faked and is indistinguishable from real data ;
Pseudonymous data can be trivially reverse engineered to a doxx (even with anon data this is the case, but its a less trivial affair) and could still be fake;
A third party can always leak, intentionally of by hack, or lie.
A better way to go about this is to force all the data collection that is currently already happening out in the open in processed numbers;
Density in certain areas ''0.44 people per m2 on date X time Y'', from cell towers for example, or the amount of traffic from the bazillion government cameras everywhere in a similar manner.
There is already so much potential data out there; if published directly (and timestamped so it cant be altered after the fact), you don't just have the usecase you mention, but open google-maps alternatives could start giving you the same type of real time traffic insight google does currently; or anyone could do whatever kind of research (urban planning, marketing etc.)

2026-04-08 09:22:59 UTC

- reply

kind1040 is already in use by NIP03*
*which is still broken and needs fixing

2026-04-08 08:28:40 UTC

- reply

Which in turn had the best theme ever:
https://youtu.be/1BeRpAORAps

2026-04-07 23:51:18 UTC

- reply

my own high tolerance for brokenness to the point i hardly even notice is one of the reason i personally stay away from on-boarding anyone that did not find their own way to Nostr in the first place; and even that is like a side-hobby i stumble into every now and then.
Really glad there are people that do notice and bother to make it known; whether or not it will get fixed, it at the very least starts there.

2026-04-07 21:40:13 UTC

- reply

I recognize a lot of these things, but i simply don't notice them while they occur.
https://image.nostr.build/93eb947630b6143f850520e7493b73023418764adcaeff48ab71643ae8f50ad3.png

2026-04-07 17:31:27 UTC

- reply

no idea what i just watched, but i feel confused and want my money back

2026-04-07 15:04:34 UTC

- reply

Again, i have no dog in this fight. I did some digging into teflon at some point though and if are making demands of user skill level when using cookware, teflon is pretty good actually. The issue arises when the layer gets damaged, mostly due to user error. Teflon is used all over the chemical industry for the fact that it does not react with anything. If teflon coating is used by chemical plants that operate on these insane levels of purity and what not, i don't see how it all the sudden behaves completely differently inside of a pan, outside of people jamming their fork into it. At the very least i understand why they thought it was this great thing at the time (to be clear i am not a fan).
Insofar durability it remains a ''consumable'' at the end of the day, not some intergenerational tool.
In general, a lot of these discussions (the PFAS one for example) would benefit from some contextualization, which is that our ability to measure has increased a bazilliontrillion (a meme factor, obviously, because im too lazy to google the actual number but it is beyond insane) fold in the past decades. The fact that things as such can be measured has been rendered meaningless due to this (because we can measure basically anything), and always requires scale for context.

2026-04-07 14:41:09 UTC

- reply

It begs the question though, how does some trace amount of nickel from stainless steel constitute some potential health issue, whilst a thick layer of carcinogenic crap does not?
i don't care either way, insofar the body is not capable of dealing with whatever marginal stuff you confront it with, im not particularly preoccupied with longevity or health-neuroticism as it is. Just...you know....i don't see this supposed magical non-toxic property of cast iron as such.

2026-04-07 14:08:56 UTC

- reply

sloth* sloperator

2026-04-07 14:05:27 UTC

- reply

Ah, i see caught a bunch of snobs with your comment. Don't worry, im a ceramic maxi myself, fuck all that high maintenance bullshit that requires some fucking phd in cooking or order not to fuck up your food. Im just trying to prepare sustenance, i dont give a fuck about food, let alone cooking for that matter

2026-04-07 08:33:37 UTC

- reply

Giggidy

2026-04-07 08:31:04 UTC

- reply

You'd think the industry got the message by now its worth it to re-architect their chips to optimize for large pools of RAM for single/small/personal systems. I think Apple stumbled into this corner semi by accident.
Ive been digging into this from time to time, and there are plenty of things that could be done, and the research for these techniques exist, they just never made it to market thusfar. Probably because the focus has been on large scale datacenters, and that it would imply some latency and other trade-offs.
Thing is, for the personal local A.I. usecase, the large memory pool and power efficiency are most important; you want to be able to run the most capable models, not draw silly amounts of power, and you don't care if its "slow", since it can just work on your stuff 24/7 anyway. The bottleneck now is that people just run out of their token budgets, they want something that can just keep grinding away.
But it will probably take a while (lets say 1.5 years), before such stuff is on the shelves, which seems like an eternity given the speed things are going, so i understand not wanting to wait on such a thing (and that new mac by the looks of it will already get you what you want it seems).

2026-04-06 20:54:39 UTC

- reply

i was more or less suggesting to not reinvent the wheel here. Yes, spells ar a way to share the commands, but in order to both create, mutate and apply them, implies the cli in the first place

2026-04-06 20:30:56 UTC

- reply

so...spells...you want spells. @npub107j…ncxg

2026-04-06 09:16:06 UTC

- reply

It is, although, hearing all those woodpeckers hellbend on destruction does make you think🤔

2026-04-06 08:56:32 UTC

My little Shire
https://cdn.azzamo.media/78a644c56c7600a1bbce50deb32551f338fea75785f239224510ed86a0923e34.mp4

2026-04-05 21:40:50 UTC

- reply

You think too much.
Fire goes brrrrrrrrr

2026-04-05 18:13:40 UTC

And so it begins, happy easter
https://blossom.primal.net/8163c2374596ec1e3bddad65e60ddf00f3f8344b113e2d41752d70e7a66a91d1.mp4

2026-04-04 21:09:48 UTC

- reply

Oy, you got license for this post?

2026-04-04 13:43:01 UTC

- reply

@nprofile…9vs7 it appears you have an earthberrybuddy

2026-04-03 22:58:36 UTC

- reply

I don't know of any clients that actually show you these proofs explicitly in such a way. Amethyst just add this thingy that when you select it tells you the date of the OTS

2026-04-03 22:55:52 UTC

- reply

Im sure we would have a hard time trauma bonding anyway, im mostly trying to deal with the fact that i entered the stage of life i all the sudden have to deal with hair growing out of my ears and that rogue eyebrow hairs are now a regulare occurance. Cant shake the sense i am actually an Orangutan.
Great, now i want a banana and i don't have any😭

2026-04-03 22:22:18 UTC

- reply

Just realized i wrote an article on all of this
#naddr1qv…h7wv

2026-04-03 22:19:45 UTC

- reply

many clients show client-tags, but its of no use because those can be faked the same way the time can be faked in an event.
Because the date/time in an event is self declared it can indeed be faked. Ive done some quirky things/demos where supposedly events in the past managed to reference events supposedly in the future.
OTS indeed is the means to get an objective time anchor

2026-04-03 22:02:32 UTC

- reply

Function is not broken, you might have to wait a while, it depends on how often the timestamp-server decides to do a bitcoin transaction, which i think is only a couple of times a day. In general, this type of timestamping is not suited for minute/hour timescale stuff anyway, more on the level of multiple hours/day basis
NIP-03 itself is broken, but thats for a different reason entirely. When designing the standard, it did not occur to us that in Nostr, you sign the event-ID of an event. Because the current standard timestamps that event-ID, you technically don't know when something was signed, someone could have actually signed it after the fact.
This, in theory, could lead to some weird exploit. Lets say i am planning to steal your keys. I could start creating all kind of events in your name today, and timestamp them, even though i am not able to sign them yet.
Then later, when i successfully stole your keys, i could sign those messages after the fact, and then from the outside worlds perspective, those seem like legitimate timestamped events that you posted before your keys got compromised; which would undermine the entire purpose of it all.
The fix is not that difficult, but its annoying we will have to deprecate the current standard blablabla etc.

2026-04-03 20:41:51 UTC

- reply

I have other priorities, but every now and again i have a crack at this stuff

2026-04-03 20:23:39 UTC

- reply

what happens is that amethyst sends the event-ID of the event that is being timestamped to a timestaming/calender server. This server gathers all kinds of things, bundles them using a merkle-tree and does a Bitcoin transaction that includes the root of that merkletree.
Then when that transaction is mined into a Bitcoin block, the server produces individual proofs for all the items, and sends those proofs back to the people that submitted things, which would include you and the proof for the event you wanted to timestamp.
Then you create a nostr event that contains that proof, and tada, you now have a proof that some event atleast existed before some point in time.
So all you have to do is press the button in amethyst and wait for stuff to get mined into bitcoin, thats it, you don't have to do anything else.
Whether this explanation fits your idea of being five does not concern me, this is the answer you are getting.

2026-04-03 19:14:02 UTC

- reply

pretty cool!??!
Its fucking awesome mate!
*starts smashing chairs into the wall out of excitement*

2026-04-03 19:12:27 UTC

- reply

in relation to Nostr, or the world at large? Or both?

2026-04-03 19:06:31 UTC

- reply

And here i am, replying using Jumble.
The fact that this is not a LARP, but there is genuine client diversity is really big. Its one of the hardest things to make real, where it is very easy to come up with the idea in theory. 🥹

2026-04-03 18:02:39 UTC

- reply

https://image.nostr.build/d781c3c2234ecf36b83cd81e25638dbaef4482cbeb5e879e563de26cb0c4f8ca.png