Avatar
Constant
5ea4648045bb1ff222655ddd36e6dceddc43590c26090c486bef38ef450da5bd
Writing a book about Nostr Ceterum censeo NIP-03 omnibus esse utendum

Will take a while, both my sinterklaas and christmas avatar remixes have laser eyes.

Replying to Avatar Duchess

———INGREDIENTS——-

Filling Ingredients

* 6 shredded organic carrots (you can add more if you like)

* 2 organic white onions (you can add more if you like)

* 1 teaspoon of brown sugar

* Pepper (to taste)

* Salt (to taste)

* Olive oil (for sautéing)

* Fresh herbs (like organic dill or organic parsley) - finely chopped, for garnish

Optional Garnish:

• Grated hard-boiled eggs (to sprinkle on top)

• Additional fresh herbs or scallions

Mayo Icing Ingredients

* 250 ml of olive oil

* 1 spoon of salt

* 1/2 spoon of sugar

* 1/2 spoon of mustard

* 2 spoons of fresh lemon or lime juice

* 1 organic egg

Liver Blini Ingredients

* 4 organic eggs

* 1 1/2 cups of raw organic milk

* 1/2 kg of grass-fed cow liver

* 2-3 spoons of flour (I used Einkorn)

* Olive oil (for frying)

———TOOLS ——-

Filling Tools:

* Peeler (to peel carrots)

* Grater (like a cheese grater, for shredding carrots)

* Knife (to chop onions)

* Sauté pan

* Spatula

Mayo Icing Tools:

* Hand blender

Liver Blini Tools:

* Blender

* Mixing bowl

* Blini pan

* Ladle spoon

* Long spatula

———DIRECTIONS ——-

Filling Instructions:

1. Prepare the Carrots:

• Wash and peel the carrots using a peeler.

• Grate the carrots using a grater until finely shredded.

2. Prepare the Onions:

• Peel the onions and finely chop them with a knife.

3. Cook the Filling:

• Heat olive oil in a sauté pan over medium heat.

• Add the chopped onions and cook until they are soft and transparent, stirring occasionally.

• Stir in the shredded carrots, mixing well with the onions.

• Add salt & pepper to taste, along with the teaspoon of brown sugar.

• From time to time, add a small amount of water to the pan to help soften the carrots and prevent them from burning. Sauté until the carrots are tender and fully cooked.

4. Set Aside:

• Remove the filling from heat and let it cool slightly. Reserve it for assembling the cake layers.

Mayo Icing Instructions:

1. Combine Ingredients:

• Pour 250 ml of olive oil into a tall mixing cup or container.

• Add 1 spoon of salt, 1/2 spoon of sugar, 1/2 spoon of mustard, 2 spoons of fresh lemon (or lime) juice, and 1 organic egg.

2. Blend:

• Insert the hand blender into the cup, ensuring the blades are fully submerged in the mixture.

• Blend at a steady speed until the mixture emulsifies into a thick and creamy mayo-like consistency.

3. Adjust Seasoning (Optional):

• Taste the icing (mayo) and adjust seasoning (e.g., add more salt, sugar, or lemon juice) to suit your preference.

4. Set Aside:

• Transfer the mayo icing to a bowl and set aside until it’s time to assemble the cake.

Liver Blini Instructions:

1. Prepare the Liver:

• Peel the liver (if necessary).

• Chop the liver into small strips or pieces for easier blending.

2. Blend the Mixture:

• In a blender, combine the liver and raw organic milk. Blend until the mixture is completely smooth.

• Pour the blended mixture into a mixing bowl.

3. Add Remaining Ingredients:

• Into the liver mixture, whisk in the eggs and gradually add the flour (2-3 spoons, depending on desired consistency). Mix well until fully combined.

4. Cook the Blini/crepes:

• Heat a small amount of olive oil in a blini pan (or non-stick frying pan) over medium heat.

• Pour a thin layer of batter into the pan, swirling to spread evenly, creating a pancake or crepe-like texture.

• Fry for about 1–2 minutes on each side until golden and cooked through. Repeat until all the batter is used.

5. Cool and Set Aside:

• Once cooked, stack the blini on a plate (you can assemble the cake in the end if you are working alone).

Once everything is prepared you can start assembling the layers of the liver blinis with the filling, stacking them to create a “cake.”

Assembling the Liver Cake

Directions

1. Layer 1:

* Place a liver blini on your serving plate.

* Spread a thin layer of mayo icing on top.

* Over the mayo icing, add a layer of the carrot and onion filling, spreading it evenly.

2. Repeat:

* Continue layering by alternating liver blinis, mayo icing, and carrot-onion filling until all the blinis are used.

3. Finish with Garnish:

* On the top layer, spread a final layer of mayo icing.

* Garnish with fresh herbs, grated hard-boiled eggs, or any other preferred toppings.

4. Serving:

* This dish can be served warm, as the flavors are fresh and vibrant. (I prefer it warm)

* Alternatively, you can chill the cake before serving to allow the flavors to meld together. (Most people prefer it chilled)

Where did you conjure this recipe from?

Replying to Avatar ynniv

> Now, if we just put the whole thing on a blockchain that would totally solve that problem.

I would be very surprised if this were true, as I have failed to find a sound use of a blockchain outside of a fungible currency.

The problems are always deciding whether a change is valid, and enforcing the on-chain information. With Bitcoin a change is valid if it sends value less than what's in a wallet to somewhere and is signed by the corresponding private key. The change is also respected because now the wallet doesn't have control of the value, and (probably) someone else does. Both of these are automated and verifiable by anyone.

When you put something else on the chain, say the deed to a house, miners can't validate the change unless it's an ordinal. Fair enough, we can assign an ordinal. But they also can't enforce the effect: only the government decides who owns a house. Once you identify this part which isn't automated, you might as well replace the blockchain with a database.

So, on the one hand, it seems that they did the right thing and avoided using a blockchain in a way that doesn't make sense. But on the other, it's presumably because only one group can determine whether a change is valid, which means it was never distributed in the first place.

Identity is a surprisingly difficult problem. Nostr gets most of it right, except for combining identity and authorization into a single key. No reasonable system still uses "$username:$password" as their session id.

You are confusing things. Blockchains indeed dont work irt 'physical' things. But 'identity' is just an abstract notion. Its just a registration of names and pointers, and signatures determine validity. So that should work fine.

The problem is that blockchains dont scale well on the one hand and you have an incentive problem on the other.

So Alex is correct in this statement: we know how to do decentralized global state, and we barely know and for the most part are still finding out over time if it works for money, let alone something else.

Accepting that, leaves us with putting keys at the center of the system, and as such you have no option other than 'combining identity and authorization'. Your complaint against that is the same old trap that makes people want to look at blockchains or whatever, because you need a registry linking the two if you dont want to combine them.

If your conclusion is that putting keys at the center of things (not an unreasonable possition btw) is unwise/wont work, then give up on Bitcoin and give up on Nostr.

Sir, von neumann was a mistake. HDL or nothing

Glühwein @ sinterklaas #luxemburg

Nostr is the real World Computer

I guess censorship as a result of what a client dev decided is hard to solve for if all devs decide to do such a thing.

But why would any dev start to do such a thing in the first place? Why would users addopt it secondly? And subsequently, if the clients are opensource it would be trivial to fork take it out. And lastly you'd think there would be clients not doing such things out there.

Lastly:

Hardcoded censorsing on a client level is just bad tech btw, terrible way of doing things.

Say you have really good reasons to want to make sure your users dont get into contact with someone; blocking that person hardcoded in your client wont help your users in all their other clients.

When your sleep schedule is all fucked up, but you are sleeping over at people who have normal lives with corresponding normal bedtimes, and their house in on an alarm so you are also trapped.

Was planning on writing the FOSDEM talk proposal, but meh.

No, larger unit selection groups would favor zerg too much. With remastered they barely touched the game itself which is good. They made the engine handle more stuff and fixed some minor things.

You are wrong, but i already explained how all of this works in another post here.

So let me just ask you:

How would that work?

First up: are you 100% sure that you dont share a relay with those people?

Its inherrent to the 'protocol'/ a fact of life.

Say Alice post on her personal relay, and non of her posts ever make it to other relays.

Alice and Bob know eachother, so Bob checks Alice's relay from time to time to see if perhaps Alice responded to any of Bobs posts.

You know Bob, but how would you know of Alice her reply to Bob? That event is only on a relay you dont even know exists.

It is only after Bob then replies to Alice, that there is an event you can see, that contains a reference to Alice, allowing you to find alice her relay and therefor her posts.

'Big central relays' are fine, they are usefull for discovery purposes. After that the outbox model takes over and you don't rely on that relay for that particular person any longer.

To 'find' someone you either need common relays or a suggestion/hint of existence.

To 'follow' someone you dont, because you know where to look.

On the one hand its cool Blizzard came with remasters of Warcraft I & II. But it is a shame they don't just open source these things and throw them into the public domain (I wonder if it would even impact sales all that much, maybe). Practically speaking these things have been leaked or reverse engineered already anyway. From what I gather from one reviewer is that those communities in a lot of aspects do a better job than what Blizzard themselves did with these remakes.

I am also afraid they going to use their posts for training LLMs.