@ c631e267:c2b78d3e

Die grauenvollste Aussicht ist die der Technokratie – \ einer kontrollierenden Herrschaft, \ die durch verstümmelte und verstümmelnde Geister ausgeübt wird. \ Ernst Jünger

«Davos ist nicht mehr sexy», das Weltwirtschaftsforum (WEF) mache Davos kaputt, diese Aussagen eines Einheimischen las ich kürzlich in der Handelszeitung. Während sich einige vor Ort enorm an der «teuersten Gewerbeausstellung der Welt» bereicherten, würden die negativen Begleiterscheinungen wie Wohnungsnot und Niedergang der lokalen Wirtschaft immer deutlicher.

Nächsten Montag beginnt in dem Schweizer Bergdorf erneut ein Jahrestreffen dieses elitären Clubs der Konzerne, bei dem man mit hochrangigen Politikern aus aller Welt und ausgewählten Vertretern der Systemmedien zusammenhocken wird. Wie bereits in den vergangenen vier Jahren wird die Präsidentin der EU-Kommission, Ursula von der Leyen, in Begleitung von Klaus Schwab ihre Grundsatzansprache halten.

Der deutsche WEF-Gründer hatte bei dieser Gelegenheit immer höchst lobende Worte für seine Landsmännin: 2021 erklärte er sich «stolz, dass Europa wieder unter Ihrer Führung steht» und 2022 fand er es bemerkenswert, was sie erreicht habe angesichts des «erstaunlichen Wandels», den die Welt in den vorangegangenen zwei Jahren erlebt habe; es gebe nun einen «neuen europäischen Geist».

Von der Leyens Handeln während der sogenannten Corona-«Pandemie» lobte Schwab damals bereits ebenso, wie es diese Woche das Karlspreis-Direktorium tat, als man der Beschuldigten im Fall Pfizergate die diesjährige internationale Auszeichnung «für Verdienste um die europäische Einigung» verlieh. Außerdem habe sie die EU nicht nur gegen den «Aggressor Russland», sondern auch gegen die «innere Bedrohung durch Rassisten und Demagogen» sowie gegen den Klimawandel verteidigt.

Jene Herausforderungen durch «Krisen epochalen Ausmaßes» werden indes aus dem Umfeld des WEF nicht nur herbeigeredet – wie man alljährlich zur Zeit des Davoser Treffens im Global Risks Report nachlesen kann, der zusammen mit dem Versicherungskonzern Zurich erstellt wird. Seit die Globalisten 2020/21 in der Praxis gesehen haben, wie gut eine konzertierte und konsequente Angst-Kampagne funktionieren kann, geht es Schlag auf Schlag. Sie setzen alles daran, Schwabs goldenes Zeitfenster des «Great Reset» zu nutzen.

Ziel dieses «großen Umbruchs» ist die totale Kontrolle der Technokraten über die Menschen unter dem Deckmantel einer globalen Gesundheitsfürsorge. Wie aber könnte man so etwas erreichen? Ein Mittel dazu ist die «kreative Zerstörung». Weitere unabdingbare Werkzeug sind die Einbindung, ja Gleichschaltung der Medien und der Justiz.

Ein «Great Mental Reset» sei die Voraussetzung dafür, dass ein Großteil der Menschen Einschränkungen und Manipulationen wie durch die Corona-Maßnahmen praktisch kritik- und widerstandslos hinnehme, sagt der Mediziner und Molekulargenetiker Michael Nehls. Er meint damit eine regelrechte Umprogrammierung des Gehirns, wodurch nach und nach unsere Individualität und unser soziales Bewusstsein eliminiert und durch unreflektierten Konformismus ersetzt werden.

Der aktuelle Zustand unserer Gesellschaften ist auch für den Schweizer Rechtsanwalt Philipp Kruse alarmierend. Durch den Umgang mit der «Pandemie» sieht er die Grundlagen von Recht und Vernunft erschüttert, die Rechtsstaatlichkeit stehe auf dem Prüfstand. Seiner dringenden Mahnung an alle Bürger, die Prinzipien von Recht und Freiheit zu verteidigen, kann ich mich nur anschließen.

---

Dieser Beitrag ist zuerst auf Transition News erschienen.

@ 6be5cc06:5259daf0

A seguir, veja como instalar e configurar o Privoxy no Pop!_OS.

---

1. Instalar o Tor e o Privoxy

Abra o terminal e execute:

bash sudo apt update sudo apt install tor privoxy

Explicação:

• Tor: Roteia o tráfego pela rede Tor.
• Privoxy: Proxy avançado que intermedia a conexão entre aplicativos e o Tor.

---

2. Configurar o Privoxy

Abra o arquivo de configuração do Privoxy:

bash sudo nano /etc/privoxy/config

Navegue até a última linha (atalho: Ctrl + / depois Ctrl + V para navegar diretamente até a última linha) e insira:

bash forward-socks5 / 127.0.0.1:9050 .

Isso faz com que o Privoxy envie todo o tráfego para o Tor através da porta 9050.

Salve (CTRL + O e Enter) e feche (CTRL + X) o arquivo.

---

3. Iniciar o Tor e o Privoxy

Agora, inicie e habilite os serviços:

bash sudo systemctl start tor sudo systemctl start privoxy sudo systemctl enable tor sudo systemctl enable privoxy

Explicação:

• start: Inicia os serviços.
• enable: Faz com que iniciem automaticamente ao ligar o PC.

---

4. Configurar o Navegador Firefox

Para usar a rede Tor com o Firefox:

1. Abra o Firefox.
2. Acesse Configurações → Configurar conexão.
3. Selecione Configuração manual de proxy.
4. Configure assim:
   • Proxy HTTP: 127.0.0.1
   • Porta: 8118 (porta padrão do Privoxy)
   • Domínio SOCKS (v5): 127.0.0.1
   • Porta: 9050
5. Marque a opção "Usar este proxy também em HTTPS".
6. Clique em OK.

---

5. Verificar a Conexão com o Tor

Abra o navegador e acesse:

text https://check.torproject.org/

Se aparecer a mensagem "Congratulations. This browser is configured to use Tor.", a configuração está correta.

---

Dicas Extras

• Privoxy pode ser ajustado para bloquear anúncios e rastreadores.
• Outros aplicativos também podem ser configurados para usar o Privoxy.

@ c631e267:c2b78d3e

Herzlichen Glückwunsch zum dritten Geburtstag, liebe Denk Bar! Wieso zum dritten? Das war doch 2022 und jetzt sind wir im Jahr 2024, oder? Ja, das ist schon richtig, aber bei Geburtstagen erinnere ich mich immer auch an meinen Vater, und der behauptete oft, der erste sei ja schließlich der Tag der Geburt selber und den müsse man natürlich mitzählen. Wo er recht hat, hat er nunmal recht. Konsequenterweise wird also heute dieser Blog an seinem dritten Geburtstag zwei Jahre alt.

Das ist ein Grund zum Feiern, wie ich finde. Einerseits ganz einfach, weil es dafür gar nicht genug Gründe geben kann. «Das Leben sind zwei Tage», lautet ein gängiger Ausdruck hier in Andalusien. In der Tat könnte es so sein, auch wenn wir uns im Alltag oft genug von der Routine vereinnahmen lassen.

Seit dem Start der Denk Bar vor zwei Jahren ist unglaublich viel passiert. Ebenso wie die zweieinhalb Jahre davor, und all jenes war letztlich auch der Auslöser dafür, dass ich begann, öffentlich zu schreiben. Damals notierte ich:

«Seit einigen Jahren erscheint unser öffentliches Umfeld immer fragwürdiger, widersprüchlicher und manchmal schier unglaublich - jede Menge Anlass für eigene Recherchen und Gedanken, ganz einfach mit einer Portion gesundem Menschenverstand.»

Wir erleben den sogenannten «großen Umbruch», einen globalen Coup, den skrupellose Egoisten clever eingefädelt haben und seit ein paar Jahren knallhart – aber nett verpackt – durchziehen, um buchstäblich alles nach ihrem Gusto umzukrempeln. Die Gelegenheit ist ja angeblich günstig und muss genutzt werden.

Nie hätte ich mir träumen lassen, dass ich so etwas jemals miterleben müsste. Die Bosheit, mit der ganz offensichtlich gegen die eigene Bevölkerung gearbeitet wird, war früher für mich unvorstellbar. Mein (Rest-) Vertrauen in alle möglichen Bereiche wie Politik, Wissenschaft, Justiz, Medien oder Kirche ist praktisch komplett zerstört. Einen «inneren Totalschaden» hatte ich mal für unsere Gesellschaften diagnostiziert.

Was mich vielleicht am meisten erschreckt, ist zum einen das Niveau der Gleichschaltung, das weltweit erreicht werden konnte, und zum anderen die praktisch totale Spaltung der Gesellschaft. Haben wir das tatsächlich mit uns machen lassen?? Unfassbar! Aber das Werkzeug «Angst» ist sehr mächtig und funktioniert bis heute.

Zum Glück passieren auch positive Dinge und neue Perspektiven öffnen sich. Für viele Menschen waren und sind die Entwicklungen der letzten Jahre ein Augenöffner. Sie sehen «Querdenken» als das, was es ist: eine Tugend.

Auch die immer ernsteren Zensurbemühungen sind letztlich nur ein Zeichen der Schwäche, wo Argumente fehlen. Sie werden nicht verhindern, dass wir unsere Meinung äußern, unbequeme Fragen stellen und dass die Wahrheit peu à peu ans Licht kommt. Es gibt immer Mittel und Wege, auch für uns.

---

Danke, dass du diesen Weg mit mir weitergehst!

@ 3b7fc823:e194354f

The Secret to Staying Private in the Digital Wild West: A Guide to Using Encryption

You’re scrolling through social media, and suddenly you realize your phone’s been tracking your location and displaying it on your profile for months. You’re not even sure how that happened. Or maybe you’ve noticed that every time you shop online, the item you looked for follows you around with ads wherever you go. Sound familiar? Yeah, welcome to the digital world—where your data is basically a free buffet for anyone who knows how to ask.

But here’s the thing: you don’t have to sit back and take it. Encryption is like the secret weapon that lets you lock up your data and keep those prying eyes out. It’s not just for hackers or spies—it’s for regular people who want to take control of their privacy in a world that’s increasingly looking like a reality show where everyone’s a contestant.

What Is Encryption, and Why Should You Care?

Encryption is like a secure box that only you can open. When you use encryption, your data is scrambled in a way that’s hard for anyone else to read, even if they try. Think of it as putting on a metaphorical cloak that makes your online activity invisible to just about everyone except the people you want to see it.

For example, when you browse the internet, your connection is often not encrypted by default. That’s why websites start with “https” to indicate a secure connection—it’s saying, “Hey, we’re using encryption here!” Without that little green padlock, anyone on the same WiFi could potentially spy on what you’re doing.

So, encryption isn’t just for tech geeks or government agencies. It’s for everyone who wants to protect their data from being sold, stolen, or misused without their consent. And guess what? You’re already using it without realizing it. Every time you use a password-protected account or send an encrypted message, you’re reaping the benefits of encryption.

The Privacy Advantages of Encryption for Regular People

Let’s break down why encryption is your best friend when it comes to privacy:

1. Financial Transactions
   When you pay online or use a banking app, encryption keeps your financial info safe from hackers. It ensures that only the banks and businesses you’re dealing with can access your money—no one else can.

2. Online Accounts
   Your email, social media, and other accounts often use encryption to protect your login details. That’s why you see those little “lock” icons when you’re logging in. Without encryption, someone could potentially intercept your password and gain unauthorized access to your account.

3. Data Breaches
   Encryption can often prevent data breaches from being useful. Even if hackers manage to steal your information, the encryption makes it unreadable, so the stolen data is basically worthless to the attackers.

4. Location Data
   If you’re worried about apps tracking your every move, encryption can help limit how much of that data is accessible. Some apps use encryption to protect location data, making it harder for companies to sell your movements without your consent.

5. Privacy Protection
   Encryption acts as a layer of protection against invasive technologies. For example, some apps use tracking software that follows you around the internet based on your browsing history. With encryption, these trackers can be blocked or limited, giving you more control over what information is collected about you.

How to Use Encryption Like a Pro

Now that you know why encryption is essential for privacy, let’s talk about how to use it effectively:

1. Use Strong Passwords
   Encryption works only if your passwords are strong and unique. Don’t reuse passwords from one account to another, and avoid using easily guessable information like “password123” or your birth year. Use a password manager if you need help keeping track of them.

2. Enable HTTPS Everywhere
   Install browser extensions like HTTPS Everywhere to automatically encrypt your connections to websites that don’t support encryption by default. This ensures that even if you’re not actively thinking about it, your data is still protected.

3. Look for the Lock Icon
   Whenever you’re on a website or app, look for the lock icon in the URL bar. Make sure it’s encrypted before you input any personal information.

4. Use Encrypted Communication Tools
   For private conversations, use apps like Signal or SimpleX, which are designed with encryption in mind. These tools ensure that only the sender and recipient can read your messages, keeping them safe from prying eyes.

5. Enable Two-Factor Authentication (2FA)
   This isn’t exactly encryption, but it’s a close second. 2FA adds an extra layer of security by requiring you to provide two forms of verification—like your password and a code sent to your phone—to access your account. While not encryption itself, it works alongside encryption to keep your accounts secure.

6. Use Encrypted Storage and Backup
   When storing sensitive files or data, use encrypted cloud storage or external drives. Tools like BitLocker (for Windows) or AES-256 encryption can protect your files from unauthorized access.

7. Stay Updated
   Encryption technology is always evolving, so it’s important to keep your software and apps updated. Outdated systems are often easy targets for hackers, leaving you vulnerable to attacks.

Final Thoughts: Your Data Is Your Power

In a world where data is a commodity, encryption is your weapon against the invasive tactics of corporations and hackers alike. It empowers you to control what information you share and protects you from having it used against you. So, whether you’re shopping online, using your favorite apps, or just browsing the web, remember that encryption is there to help you stay private and in control of your own data.

And if you ever feel overwhelmed by all the privacy stuff, just remember this: you’re not alone. Millions of people are fighting for stronger privacy protections every day. So, do your part by using encryption wisely—your data and your privacy are worth it. Let’s make sure no one can take that away from you.

---

Advocating for privacy does not finance itself. If you enjoyed this article, please consider zapping or sending monero

82XCDNK1Js8TethhpGLFPbVyKe25DxMUePad1rUn9z7V6QdCzxHEE7varvVh1VUidUhHVSA4atNU2BTpSNJLC1BqSvDajw1

@ 378562cd:a6fc6773

Chef's notes

I'm only testing this out right now. I will update the recipe as well as add my own image soon after making this dish again.

Details

• ⏲️ Prep time: 20 minutes
• 🍳 Cook time: 1 hour
• 🍽️ Servings: 4

Ingredients

• 4 to 6 potatoes (size depending)
• 1 lb ground beef
• seasonings
• 2 cans chili beans
• 1 onion
• katsup
• shredded cheese of some kind

Directions

1. saute onion and add ground beef to skillet. Season to liking.
2. peel if you like and thin slice potatoes
3. in a rectangle baking dish, layer potatoes, beans, meat and cheese (like a lasagna) until you have used all your ingredients. Try and make at least 2 or 3 layers with extra cheese on top.
4. Bake at 350 for one hour. Serve and enjoy!

@ 8d34bd24:414be32b

This Sunday our pastor had to give a sermon with very little preparation. He was leading an elders’ retreat and one of the elders was supposed to preach in his place. The elder who had prepared a sermon ended up in the hospital, so our pastor had to prep fast. He did a great thing. He preached on a passage, but also used that passage to demonstrate how he studies scripture. It was a great sermon. The passage he preached on reminded me of a time in my past when I learned some important lessons.

Almost 20 years ago, I was leading a high school girls Bible study. They picked out a book about Mary and Martha to study. Initially, I wasn’t thrilled with their choice, but didn’t have a theological problem with it, so I agreed for us to study this book. (I don’t remember the name of the book and all my books burnt up when my house burnt down almost 10 years ago). In the end, I probably got more out of the study than any of the girls because I have a definite tendency to be a Martha. What was Martha’s error? Let’s check out the passage:

Now as they went on their way, Jesus entered a village. And a woman named Martha welcomed him into her house. And she had a sister called Mary, who sat at the Lord’s feet and listened to his teaching. But Martha was distracted with much serving. And she went up to him and said, “Lord, do you not care that my sister has left me to serve alone? Tell her then to help me.” But the Lord answered her, “Martha, Martha, you are anxious and troubled about many things, but one thing is necessary. Mary has chosen the good portion, which will not be taken away from her.” (Luke 10:38-42 ESV)

Jesus visited two sisters who welcomed Him into their home. Mary sat at Jesus’s feet and listened to His teaching. Martha spent her time serving everyone and taking care of everyone’s physical needs.

Is taking care of their home and the needs of their guests a bad thing? Of course not, but is it the best?

To make things much worse, Martha then got upset because her sister Mary wasn’t helping her. She was just sitting there taking in every word that Jesus said. Most of us would think Martha’s sacrifices to take care of everyone was better than Mary’s choice to just sit at Jesus’s feet, but did Martha really choose the better path?

Martha then showed that her heart wasn’t focused right and she wasn’t putting the most important things first. She complained to Jesus about her sister’s failure to help and even commanded her Creator, “Tell her then to help me.” Instead of focusing on the words of Jesus, her frustration led her to command her God to act in the way she desired. She was so busy with cooking, cleaning, and serving, that she missed the most important things — spending time with and listening to her God, who was right there in her house with her. This was an opportunity that shouldn’t be missed due to busyness.

How often do we all do this same thing? How often are busy doing good things and miss the most important things? How often are we busy doing ministry that we forget about the reason for the ministry? I don’t know about you, but this happens to me a lot more often than I would like to admit. My biggest sins are usually not what most people think of as sins. My biggest sins are getting so busy that I leave God out of my life. I am so busy serving God that I forget to follow His leading. I am so busy doing what most people would consider good things, but if God is not part of them, they are not worth much. Because I am focusing on getting things done, worry and stress overtake me harming my health and my relationship with Jesus.

I don’t think this is taking Scripture out of context:

We have come to know and have believed the love which God has for us. God is love, and the one who abides in love abides in God, and God abides in him. (1 John 4:16) {emphasis mine}

Knowing that God is love, read the following passage replacing love with God.

If I speak with the tongues of men and of angels, but do not have love, I have become a noisy gong or a clanging cymbal. If I have the gift of prophecy, and know all mysteries and all knowledge; and if I have all faith, so as to remove mountains, but do not have love, I am nothing. And if I give all my possessions to feed the poor, and if I surrender my body to be burned, but do not have love, it profits me nothing. (1 Corinthians 13:1-3)

If I do not include God in my every action, “it profits me nothing.”

In reality it shouldn’t be allowing God to join me in my works, but me joining God in His works. It should be me listening to God’s word and the leading of the Holy Spirit, looking and seeing what God is doing around me, and me joining in His great works. It should be me allowing God to use me as a tool.

There are times that God speaks clearly and directly to us about what He desires for our lives, but most of the time, He speaks through His word — the Bible. Knowing the Bible helps us to know His will and His eternal plan, so we can follow Him and join Him in His work. Knowing the Bible helps us to differentiate between what is good and what is God’s best. It helps us to prioritize what is really important.

And this I pray, that your love may abound still more and more in real knowledge and all discernment, so that you may approve the things that are excellent, in order to be sincere and blameless until the day of Christ; having been filled with the fruit of righteousness which comes through Jesus Christ, to the glory and praise of God. (Philippians 1:9-11) {emphasis mine}

We can’t obey God, imitate Christ, or follow Him if we refuse to listen and that means spending time in the Bible and time in prayer with Him.

“Listen to Me, you stubborn-minded, Who are far from righteousness.” (Isaiah 46:12)

Come, you children, listen to me; I will teach you the fear of the Lord . (Psalm 34:11)

“Now therefore, O sons, listen to me, For blessed are they who keep my ways. (Proverbs 8:32)

But seek first His kingdom and His righteousness, and all these things will be added to you. (Matthew 6:33)

Our focus on Jesus/God must go beyond knowing Him. It is equally important to obey.

And He [Jesus] said to another, “Follow Me.” But he said, “Lord, permit me first to go and bury my father.” But He said to him, “Allow the dead to bury their own dead; but as for you, go and proclaim everywhere the kingdom of God.” (Luke 9:59-60) [clarification mine]

Once we know what He wants from us, we need to instantly drop what we are doing and follow Him. We can’t put other things ahead of obeying God.

For amazement had seized him and all his companions because of the catch of fish which they had taken; and so also were James and John, sons of Zebedee, who were partners with Simon. And Jesus said to Simon, “Do not fear, from now on you will be catching men.” When they had brought their boats to land, they left everything and followed Him. (Luke 5:9-11) {emphasis mine}

We should be like these apostles, that, after their most successful catch of fish in their entire career as fishermen, “they left everything and followed Him.” We need to let go of what we think is important and obey Him. We need to change our priorities to match God’s priorities.

That may mean we change careers to one that allows more free time for ministry or even going into full time ministry. It may mean letting go on keeping the perfect, clean house, so there is time for ministry, Bible study, or discipling our kids. It may mean changing your habits from watching TV with your family to reading the Bible with your family. For each of us, it will look different, but we need to be like Mary and choose to sit “at the Lord’s feet and listened to his teaching.” We need to be like the apostles who “left everything and followed Him.” We need to choose to put Jesus’s plans before our own. We need to choose to make God’s values our values.

But this is what I commanded them, saying, ‘Obey My voice, and I will be your God, and you will be My people; and you will walk in all the way which I command you, that it may be well with you.’ (Jeremiah 7:23)

Like so many things, it is simple, but it isn’t necessarily easy. We have to change the way we think in order to obey faithfully.

If anyone serves Me, he must follow Me; and where I am, there My servant will be also; if anyone serves Me, the Father will honor him. (John 12:26)

We have to change our priorities to God’s priorities.

Then Jesus said to His disciples, “If anyone wishes to come after Me, he must deny himself, and take up his cross and follow Me. (Matthew 16:24)

We need to seek God, His word, and His presence.

As the deer pants for the water brooks,\ So my soul pants for You, O God.\ My soul thirsts for God, for the living God;\ When shall I come and appear before God? (Psalm 42:1-2)

We need to be in God’s word daily, so we know who God is and what He desires from us.

How can a young man keep his way pure?\ By keeping it according to Your word.\ With all my heart I have sought You;\ Do not let me wander from Your commandments.\ *Your word I have treasured in my heart*,\ That I may not sin against You.\ Blessed are You, O Lord;\ Teach me Your statutes.\ With my lips I have told of\ All the ordinances of Your mouth.\ I have rejoiced in the way of Your testimonies,\ As much as in all riches.\ *I will meditate on Your precepts*\ And regard Your ways.\ I shall delight in Your statutes;\ I shall not forget Your word. (Psalm 119:9-16) {emphasis mine}

We need to read the Bible cover to cover so we know the whole word of God. Once we have read through the Bible multiple times, we need to spend time studying the Bible in more depth, so we can know the details, see how the different parts relate to each other, and grow in our knowledge of God. We need to study the Bible and use this knowledge to guide every decision in life — big and small.

Yet they did not listen or incline their ears, but stiffened their necks in order not to listen or take correction. (Jeremiah 17:23)

Just reading the Bible or sitting in church listening to sermons will not make a difference if we don’t truly listen and internalize God’s word, so we can apply it in our every day life. God knows what is best for us and we will never be truly at peace or have true joy until we are living our lives in the light of God’s word and direction.

My prayer for you and for me is that we will have the heart of Mary rather than the heart of Martha and that we will faithfully seek and follow God all of the days of our lives.

Trust Jesus.

@ 9e69e420:d12360c2

A new report from the National Sports Shooting Foundation (NSSF) shows that civilian firearm possession exceeded 490 million in 2022. The total from 1990 to 2022 is estimated at 491.3 million firearms. In 2022, over ten million firearms were domestically produced, leading to a total of 16,045,911 firearms available in the U.S. market.

Of these, 9,873,136 were handguns, 4,195,192 were rifles, and 1,977,583 were shotguns. Handgun availability aligns with the concealed carry and self-defense market, as all states allow concealed carry, with 29 having constitutional carry laws.

@ e31e84c4:77bbabc0

Bitcoin and Fixed Income was Written By Wyatt O’Rourke. If you enjoyed this article then support his writing, directly, by donating to his lightning wallet: ultrahusky3@primal.net

Fiduciary duty is the obligation to act in the client’s best interests at all times, prioritizing their needs above the advisor’s own, ensuring honesty, transparency, and avoiding conflicts of interest in all recommendations and actions.

This is something all advisors in the BFAN take very seriously; after all, we are legally required to do so. For the average advisor this is a fairly easy box to check. All you essentially have to do is have someone take a 5-minute risk assessment, fill out an investment policy statement, and then throw them in the proverbial 60/40 portfolio. You have thousands of investment options to choose from and you can reasonably explain how your client is theoretically insulated from any move in the \~markets\~. From the traditional financial advisor perspective, you could justify nearly anything by putting a client into this type of portfolio. All your bases were pretty much covered from return profile, regulatory, compliance, investment options, etc. It was just too easy. It became the household standard and now a meme.

As almost every real bitcoiner knows, the 60/40 portfolio is moving into psyop territory, and many financial advisors get clowned on for defending this relic on bitcoin twitter. I’m going to specifically poke fun at the ‘40’ part of this portfolio.

The ‘40’ represents fixed income, defined as…

An investment type that provides regular, set interest payments, such as bonds or treasury securities, and returns the principal at maturity. It’s generally considered a lower-risk asset class, used to generate stable income and preserve capital.

Historically, this part of the portfolio was meant to weather the volatility in the equity markets and represent the “safe” investments. Typically, some sort of bond.

First and foremost, the fixed income section is most commonly constructed with U.S. Debt. There are a couple main reasons for this. Most financial professionals believe the same fairy tale that U.S. Debt is “risk free” (lol). U.S. debt is also one of the largest and most liquid assets in the market which comes with a lot of benefits.

There are many brilliant bitcoiners in finance and economics that have sounded the alarm on the U.S. debt ticking time bomb. I highly recommend readers explore the work of Greg Foss, Lawrence Lepard, Lyn Alden, and Saifedean Ammous. My very high-level recap of their analysis:

• A bond is a contract in which Party A (the borrower) agrees to repay Party B (the lender) their principal plus interest over time.

• The U.S. government issues bonds (Treasury securities) to finance its operations after tax revenues have been exhausted.

• These are traditionally viewed as “risk-free” due to the government’s historical reliability in repaying its debts and the strength of the U.S. economy

• U.S. bonds are seen as safe because the government has control over the dollar (world reserve asset) and, until recently (20 some odd years), enjoyed broad confidence that it would always honor its debts.

• This perception has contributed to high global demand for U.S. debt but, that is quickly deteriorating.

• The current debt situation raises concerns about sustainability.

• The U.S. has substantial obligations, and without sufficient productivity growth, increasing debt may lead to a cycle where borrowing to cover interest leads to more debt.

• This could result in more reliance on money creation (printing), which can drive inflation and further debt burdens.

In the words of Lyn Alden “Nothing stops this train”

Those obligations are what makes up the 40% of most the fixed income in your portfolio. So essentially you are giving money to one of the worst capital allocators in the world (U.S. Gov’t) and getting paid back with printed money.

As someone who takes their fiduciary responsibility seriously and understands the debt situation we just reviewed, I think it’s borderline negligent to put someone into a classic 60% (equities) / 40% (fixed income) portfolio without serious scrutiny of the client’s financial situation and options available to them. I certainly have my qualms with equities at times, but overall, they are more palatable than the fixed income portion of the portfolio. I don’t like it either, but the money is broken and the unit of account for nearly every equity or fixed income instrument (USD) is fraudulent. It’s a paper mache fade that is quite literally propped up by the money printer.

To briefly be as most charitable as I can – It wasn’t always this way. The U.S. Dollar used to be sound money, we used to have government surplus instead of mathematically certain deficits, The U.S. Federal Government didn’t used to have a money printing addiction, and pre-bitcoin the 60/40 portfolio used to be a quality portfolio management strategy. Those times are gone.

Now the fun part. How does bitcoin fix this?

Bitcoin fixes this indirectly. Understanding investment criteria changes via risk tolerance, age, goals, etc. A client may still have a need for “fixed income” in the most literal definition – Low risk yield. Now you may be thinking that yield is a bad word in bitcoin land, you’re not wrong, so stay with me. Perpetual motion machine crypto yield is fake and largely where many crypto scams originate. However, that doesn’t mean yield in the classic finance sense does not exist in bitcoin, it very literally does. Fortunately for us bitcoiners there are many other smart, driven, and enterprising bitcoiners that understand this problem and are doing something to address it. These individuals are pioneering new possibilities in bitcoin and finance, specifically when it comes to fixed income.

Here are some new developments –

Private Credit Funds – The Build Asset Management Secured Income Fund I is a private credit fund created by Build Asset Management. This fund primarily invests in bitcoin-backed, collateralized business loans originated by Unchained, with a secured structure involving a multi-signature, over-collateralized setup for risk management. Unchained originates loans and sells them to Build, which pools them into the fund, enabling investors to share in the interest income.

Dynamics

• Loan Terms: Unchained issues loans at interest rates around 14%, secured with a 2/3 multi-signature vault backed by a 40% loan-to-value (LTV) ratio.
• Fund Mechanics: Build buys these loans from Unchained, thus providing liquidity to Unchained for further loan originations, while Build manages interest payments to investors in the fund.

Pros

• The fund offers a unique way to earn income via bitcoin-collateralized debt, with protection against rehypothecation and strong security measures, making it attractive for investors seeking exposure to fixed income with bitcoin.

Cons

• The fund is only available to accredited investors, which is a regulatory standard for private credit funds like this.

Corporate Bonds – MicroStrategy Inc. (MSTR), a business intelligence company, has leveraged its corporate structure to issue bonds specifically to acquire bitcoin as a reserve asset. This approach allows investors to indirectly gain exposure to bitcoin’s potential upside while receiving interest payments on their bond investments. Some other publicly traded companies have also adopted this strategy, but for the sake of this article we will focus on MSTR as they are the biggest and most vocal issuer.

Dynamics

• Issuance: MicroStrategy has issued senior secured notes in multiple offerings, with terms allowing the company to use the proceeds to purchase bitcoin.

• Interest Rates: The bonds typically carry high-yield interest rates, averaging around 6-8% APR, depending on the specific issuance and market conditions at the time of issuance.

• Maturity: The bonds have varying maturities, with most structured for multi-year terms, offering investors medium-term exposure to bitcoin’s value trajectory through MicroStrategy’s holdings.

Pros

• Indirect Bitcoin exposure with income provides a unique opportunity for investors seeking income from bitcoin-backed debt.

• Bonds issued by MicroStrategy offer relatively high interest rates, appealing for fixed-income investors attracted to the higher risk/reward scenarios.

Cons

• There are credit risks tied to MicroStrategy’s financial health and bitcoin’s performance. A significant drop in bitcoin prices could strain the company’s ability to service debt, increasing credit risk.

• Availability: These bonds are primarily accessible to institutional investors and accredited investors, limiting availability for retail investors.

Interest Payable in Bitcoin – River has introduced an innovative product, bitcoin Interest on Cash, allowing clients to earn interest on their U.S. dollar deposits, with the interest paid in bitcoin.

Dynamics

• Interest Payment: Clients earn an annual interest rate of 3.8% on their cash deposits. The accrued interest is converted to Bitcoin daily and paid out monthly, enabling clients to accumulate Bitcoin over time.

• Security and Accessibility: Cash deposits are insured up to $250,000 through River’s banking partner, Lead Bank, a member of the FDIC. All Bitcoin holdings are maintained in full reserve custody, ensuring that client assets are not lent or leveraged.

Pros

• There are no hidden fees or minimum balance requirements, and clients can withdraw their cash at any time.

• The 3.8% interest rate provides a predictable income stream, akin to traditional fixed-income investments.

Cons

• While the interest rate is fixed, the value of the Bitcoin received as interest can fluctuate, introducing potential variability in the investment’s overall return.

• Interest rate payments are on the lower side

Admittedly, this is a very small list, however, these types of investments are growing more numerous and meaningful. The reality is the existing options aren’t numerous enough to service every client that has a need for fixed income exposure. I challenge advisors to explore innovative options for fixed income exposure outside of sovereign debt, as that is most certainly a road to nowhere. It is my wholehearted belief and call to action that we need more options to help clients across the risk and capital allocation spectrum access a sound money standard.

Additional Resources

• River: The future of saving is here: Earn 3.8% on cash. Paid in Bitcoin.

• Onramp: Bitcoin, The Emergent Asset Class

• MicroStrategy: MicroStrategy Announces Pricing of Offering of Convertible Senior Notes

---

Bitcoin and Fixed Income was Written By Wyatt O’Rourke. If you enjoyed this article then support his writing, directly, by donating to his lightning wallet: ultrahusky3@primal.net

@ 3bf0c63f:aefa459d

Nostr: a quick introduction, attempt #2

Nostr doesn't subscribe to any ideals of "free speech" as these belong to the realm of politics and assume a big powerful government that enforces a common ruleupon everybody else.

Nostr instead is much simpler, it simply says that servers are private property and establishes a generalized framework for people to connect to all these servers, creating a true free market in the process. In other words, Nostr is the public road that each market participant can use to build their own store or visit others and use their services.

(Of course a road is never truly public, in normal cases it's ran by the government, in this case it relies upon the previous existence of the internet with all its quirks and chaos plus a hand of government control, but none of that matters for this explanation).

More concretely speaking, Nostr is just a set of definitions of the formats of the data that can be passed between participants and their expected order, i.e. messages between clients (i.e. the program that runs on a user computer) and relays (i.e. the program that runs on a publicly accessible computer, a "server", generally with a domain-name associated) over a type of TCP connection (WebSocket) with cryptographic signatures. This is what is called a "protocol" in this context, and upon that simple base multiple kinds of sub-protocols can be added, like a protocol for "public-square style microblogging", "semi-closed group chat" or, I don't know, "recipe sharing and feedback".

@ 5a261a61:2ebd4480

Let’s be real—sticking to anything for 90 days is like trying to herd cats on espresso. You start strong, then life happens: kids, chores, or that one glass of wine that makes you forget foot rubs (#relatable). But here’s the thing: 90-day challenges aren’t about perfection. They’re about bribing your lizard brain with rewards and scaring it straight with punishments.

The Game Plan

First, pick a thing—something that makes you feel like a devoted servant or a slightly frazzled superhero. Daily foot care? Chores with a side of #FLR flair? Cool. Now, break it into chunks: 30 days (survival mode), 60 days (grind phase), and 90 days (victory lap).

Keeping up something for so long is no joke. That's why you need those little checkpoints along the way. Each milestone should feel special—30 days deserves celebration, 60 days something more meaningful, and 90 days? That's your victory dance moment.

Reality check: some days will suck, and you'll want to skip. That's where having everything planned out helps. When your brain is foggy and you're tired, you don't want to be negotiating with yourself about what counts and what doesn't. The hardest part isn't even doing the thing—it's remembering to do it every single day, until it feels wrong NOT to do it.

Why It (Maybe) Works

Three months is long enough for habits to stick, short enough to see the finish line. Plus, tying it to power exchange? Genius. Every foot rub or denied cum becomes a ritual, proof you're leveling up as a sub/human/slightly-messy adult. And let's be honest—nothing fuels devotion like a mix of structure, desperation, and the occasional humiliating punishment.

Current run

My current challenge is to get my wife/godess/object of my insatiable kinky thoughts/partner feet massaged with special cream. It's for making evyrthing soft, help nails and yadayadayada. Basically preping her feet for more instensive worshiping. She doesn't know my hidden agenda and I am not sure if I would really be into it, since I am more into being her devout toy than having foot fetish, but I think it will be all the same if I put myself juuust right. So for my rewards I have planned these? - 30 days: Tiny dopamine hit. (making little photoset of Her feet playing with my hardon… for science.)
- 60 days: Mid-tier flex. (cleaning mushed banana split off Her toes tongue only)
- 90 days: Go nuclear. (a tiny foot spa whirpool because She deserves it, damn it :D and it will create more opportunities for... you know )

As for the hhip part of the sugar duo... It was easy having one for my shaving rutine, but here? Not sure and it's bad that I ave started challenge without having them prepared... May be that warrant more punishment?

TL;DR

90-day challenges are the BDSM of self-improvement: consensual, slightly painful, and weirdly addictive. Fail? Reset, adapt, try again. Win? Congrats, you’re now 10% more disciplined and 100% more bumptious on Nostr.

90days #FLR #LostCauseButStillTrying #femdom

@ 76c71aae:3e29cafa

On social media and in the Nostr space in particular, there’s been a lot of debate about the idea of supporting deletion and editing of notes.

Some people think they’re vital features to have, others believe that more honest and healthy social media will come from getting rid of these features. The discussion about these features quickly turns to the feasibility of completely deleting something on a decentralized protocol. We quickly get to the “We can’t really delete anything from the internet, or a decentralized network.” argument. This crowds out how Delete and Edit can mimic elements of offline interactions, how they can be used as social signals.

When it comes to issues of deletion and editing content, what matters more is if the creator can communicate their intentions around their content. Sure, on the internet, with decentralized protocols, there’s no way to be sure something’s deleted. It’s not like taking a piece of paper and burning it. Computers make copies of things all the time, computers don’t like deleting things. In particular, distributed systems tend to use a Kafka architecture with immutable logs, it’s just easier to keep everything around, as deleting and reindexing is hard. Even if the software could be made to delete something, there’s always screenshots, or even pictures of screens. We can’t provably make something disappear.

What we need to do in our software is clearly express intention. A delete is actually a kind of retraction. “I no longer want to associate myself with this content, please stop showing it to people as part of what I’ve published, stop highlighting it, stop sharing it.” Even if a relay or other server keeps a copy, and keeps sharing it, being able to clearly state “hello world, this thing I said, was a mistake, please get rid of it.” Just giving users the chance to say “I deleted this” is a way of showing intention. It’s also a way of signaling that feedback has been heard. Perhaps the post was factually incorrect or perhaps it was mean and the person wants to remove what they said. In an IRL conversation, for either of these scenarios there is some dialogue where the creator of the content is learning something and taking action based on what they’ve learned.

Without delete or edit, there is no option to signal to the rest of the community that you have learned something because of how the content is structured today. On most platforms a reply or response stating one’s learning will be lost often in a deluge of replies on the original post and subsequent posts are often not seen especially when the original goes viral. By providing tools like delete and edit we give people a chance to signal that they have heard the feedback and taken action.

The Nostr Protocol supports delete and expiring notes. It was one of the reasons we switched from secure scuttlebutt to build on Nostr. Our nos.social app offers delete and while we know that not all relays will honor this, we believe it’s important to provide social signaling tools as a means of making the internet more humane.

We believe that the power to learn from each other is more important than the need to police through moral outrage which is how the current platforms and even some Nostr clients work today.

It’s important that we don’t say Nostr doesn’t support delete. Not all apps need to support requesting a delete, some might want to call it a retraction. It is important that users know there is no way to enforce a delete and not all relays may honor their request.

Edit is similar, although not as widely supported as delete. It’s a creator making a clear statement that they’ve created a new version of their content. Maybe it’s a spelling error, or a new version of the content, or maybe they’re changing it altogether. Freedom online means freedom to retract a statement, freedom to update a statement, freedom to edit your own content. By building on these freedoms, we’ll make Nostr a space where people feel empowered and in control of their own media.

@ d57360cb:4fe7d935

Beauty and art function beyond the mind.

When you’re not thinking, when the mind reaches its natural silence. When it quiets down.

You begin to experience and actually experience how things are.

There is no more narration. Things happen as if by magic. Everything is in its place happening and grooving.

Every act, every movement feels like jazz.

We’re better doers than we are thinkers. But the world thinks otherwise.

@ 3bf0c63f:aefa459d

Drivechain

Understanding Drivechain requires a shift from the paradigm most bitcoiners are used to. It is not about "trustlessness" or "mathematical certainty", but game theory and incentives. (Well, Bitcoin in general is also that, but people prefer to ignore it and focus on some illusion of trustlessness provided by mathematics.)

Here we will describe the basic mechanism (simple) and incentives (complex) of "hashrate escrow" and how it enables a 2-way peg between the mainchain (Bitcoin) and various sidechains.

The full concept of "Drivechain" also involves blind merged mining (i.e., the sidechains mine themselves by publishing their block hashes to the mainchain without the miners having to run the sidechain software), but this is much easier to understand and can be accomplished either by the BIP-301 mechanism or by the Spacechains mechanism.

How does hashrate escrow work from the point of view of Bitcoin?

A new address type is created. Anything that goes in that is locked and can only be spent if all miners agree on the Withdrawal Transaction (WT^) that will spend it for 6 months. There is one of these special addresses for each sidechain.

To gather miners' agreement bitcoind keeps track of the "score" of all transactions that could possibly spend from that address. On every block mined, for each sidechain, the miner can use a portion of their coinbase to either increase the score of one WT^ by 1 while decreasing the score of all others by 1; or they can decrease the score of all WT^s by 1; or they can do nothing.

Once a transaction has gotten a score high enough, it is published and funds are effectively transferred from the sidechain to the withdrawing users.

If a timeout of 6 months passes and the score doesn't meet the threshold, that WT^ is discarded.

What does the above procedure mean?

It means that people can transfer coins from the mainchain to a sidechain by depositing to the special address. Then they can withdraw from the sidechain by making a special withdraw transaction in the sidechain.

The special transaction somehow freezes funds in the sidechain while a transaction that aggregates all withdrawals into a single mainchain WT^, which is then submitted to the mainchain miners so they can start voting on it and finally after some months it is published.

Now the crucial part: the validity of the WT^ is not verified by the Bitcoin mainchain rules, i.e., if Bob has requested a withdraw from the sidechain to his mainchain address, but someone publishes a wrong WT^ that instead takes Bob's funds and sends them to Alice's main address there is no way the mainchain will know that. What determines the "validity" of the WT^ is the miner vote score and only that. It is the job of miners to vote correctly -- and for that they may want to run the sidechain node in SPV mode so they can attest for the existence of a reference to the WT^ transaction in the sidechain blockchain (which then ensures it is ok) or do these checks by some other means.

What? 6 months to get my money back?

Yes. But no, in practice anyone who wants their money back will be able to use an atomic swap, submarine swap or other similar service to transfer funds from the sidechain to the mainchain and vice-versa. The long delayed withdraw costs would be incurred by few liquidity providers that would gain some small profit from it.

Why bother with this at all?

Drivechains solve many different problems:

It enables experimentation and new use cases for Bitcoin

Issued assets, fully private transactions, stateful blockchain contracts, turing-completeness, decentralized games, some "DeFi" aspects, prediction markets, futarchy, decentralized and yet meaningful human-readable names, big blocks with a ton of normal transactions on them, a chain optimized only for Lighting-style networks to be built on top of it.

These are some ideas that may have merit to them, but were never actually tried because they couldn't be tried with real Bitcoin or inferfacing with real bitcoins. They were either relegated to the shitcoin territory or to custodial solutions like Liquid or RSK that may have failed to gain network effect because of that.

It solves conflicts and infighting

Some people want fully private transactions in a UTXO model, others want "accounts" they can tie to their name and build reputation on top; some people want simple multisig solutions, others want complex code that reads a ton of variables; some people want to put all the transactions on a global chain in batches every 10 minutes, others want off-chain instant transactions backed by funds previously locked in channels; some want to spend, others want to just hold; some want to use blockchain technology to solve all the problems in the world, others just want to solve money.

With Drivechain-based sidechains all these groups can be happy simultaneously and don't fight. Meanwhile they will all be using the same money and contributing to each other's ecosystem even unwillingly, it's also easy and free for them to change their group affiliation later, which reduces cognitive dissonance.

It solves "scaling"

Multiple chains like the ones described above would certainly do a lot to accomodate many more transactions that the current Bitcoin chain can. One could have special Lightning Network chains, but even just big block chains or big-block-mimblewimble chains or whatnot could probably do a good job. Or even something less cool like 200 independent chains just like Bitcoin is today, no extra features (and you can call it "sharding"), just that would already multiply the current total capacity by 200.

Use your imagination.

It solves the blockchain security budget issue

The calculation is simple: you imagine what security budget is reasonable for each block in a world without block subsidy and divide that for the amount of bytes you can fit in a single block: that is the price to be paid in satoshis per byte. In reasonable estimative, the price necessary for every Bitcoin transaction goes to very large amounts, such that not only any day-to-day transaction has insanely prohibitive costs, but also Lightning channel opens and closes are impracticable.

So without a solution like Drivechain you'll be left with only one alternative: pushing Bitcoin usage to trusted services like Liquid and RSK or custodial Lightning wallets. With Drivechain, though, there could be thousands of transactions happening in sidechains and being all aggregated into a sidechain block that would then pay a very large fee to be published (via blind merged mining) to the mainchain. Bitcoin security guaranteed.

It keeps Bitcoin decentralized

Once we have sidechains to accomodate the normal transactions, the mainchain functionality can be reduced to be only a "hub" for the sidechains' comings and goings, and then the maximum block size for the mainchain can be reduced to, say, 100kb, which would make running a full node very very easy.

Can miners steal?

Yes. If a group of coordinated miners are able to secure the majority of the hashpower and keep their coordination for 6 months, they can publish a WT^ that takes the money from the sidechains and pays to themselves.

Will miners steal?

No, because the incentives are such that they won't.

Although it may look at first that stealing is an obvious strategy for miners as it is free money, there are many costs involved:

1. The cost of ceasing blind-merged mining returns -- as stealing will kill a sidechain, all the fees from it that miners would be expected to earn for the next years are gone;
2. The cost of Bitcoin price going down: If a steal is successful that will mean Drivechains are not safe, therefore Bitcoin is less useful, and miner credibility will also be hurt, which are likely to cause the Bitcoin price to go down, which in turn may kill the miners' businesses and savings;
3. The cost of coordination -- assuming miners are just normal businesses, they just want to do their work and get paid, but stealing from a Drivechain will require coordination with other miners to conduct an immoral act in a way that has many pitfalls and is likely to be broken over the months;
4. The cost of miners leaving your mining pool: when we talked about "miners" above we were actually talking about mining pools operators, so they must also consider the risk of miners migrating from their mining pool to others as they begin the process of stealing;
5. The cost of community goodwill -- when participating in a steal operation, a miner will suffer a ton of backlash from the community. Even if the attempt fails at the end, the fact that it was attempted will contribute to growing concerns over exaggerated miners power over the Bitcoin ecosystem, which may end up causing the community to agree on a hard-fork to change the mining algorithm in the future, or to do something to increase participation of more entities in the mining process (such as development or cheapment of new ASICs), which have a chance of decreasing the profits of current miners.

Another point to take in consideration is that one may be inclined to think a newly-created sidechain or a sidechain with relatively low usage may be more easily stolen from, since the blind merged mining returns from it (point 1 above) are going to be small -- but the fact is also that a sidechain with small usage will also have less money to be stolen from, and since the other costs besides 1 are less elastic at the end it will not be worth stealing from these too.

All of the above consideration are valid only if miners are stealing from good sidechains. If there is a sidechain that is doing things wrong, scamming people, not being used at all, or is full of bugs, for example, that will be perceived as a bad sidechain, and then miners can and will safely steal from it and kill it, which will be perceived as a good thing by everybody.

What do we do if miners steal?

Paul Sztorc has suggested in the past that a user-activated soft-fork could prevent miners from stealing, i.e., most Bitcoin users and nodes issue a rule similar to this one to invalidate the inclusion of a faulty WT^ and thus cause any miner that includes it in a block to be relegated to their own Bitcoin fork that other nodes won't accept.

This suggestion has made people think Drivechain is a sidechain solution backed by user-actived soft-forks for safety, which is very far from the truth. Drivechains must not and will not rely on this kind of soft-fork, although they are possible, as the coordination costs are too high and no one should ever expect these things to happen.

If even with all the incentives against them (see above) miners do still steal from a good sidechain that will mean the failure of the Drivechain experiment. It will very likely also mean the failure of the Bitcoin experiment too, as it will be proven that miners can coordinate to act maliciously over a prolonged period of time regardless of economic and social incentives, meaning they are probably in it just for attacking Bitcoin, backed by nation-states or something else, and therefore no Bitcoin transaction in the mainchain is to be expected to be safe ever again.

Why use this and not a full-blown trustless and open sidechain technology?

Because it is impossible.

If you ever heard someone saying "just use a sidechain", "do this in a sidechain" or anything like that, be aware that these people are either talking about "federated" sidechains (i.e., funds are kept in custody by a group of entities) or they are talking about Drivechain, or they are disillusioned and think it is possible to do sidechains in any other manner.

No, I mean a trustless 2-way peg with correctness of the withdrawals verified by the Bitcoin protocol!

That is not possible unless Bitcoin verifies all transactions that happen in all the sidechains, which would be akin to drastically increasing the blocksize and expanding the Bitcoin rules in tons of ways, i.e., a terrible idea that no one wants.

What about the Blockstream sidechains whitepaper?

Yes, that was a way to do it. The Drivechain hashrate escrow is a conceptually simpler way to achieve the same thing with improved incentives, less junk in the chain, more safety.

Isn't the hashrate escrow a very complex soft-fork?

Yes, but it is much simpler than SegWit. And, unlike SegWit, it doesn't force anything on users, i.e., it isn't a mandatory blocksize increase.

Why should we expect miners to care enough to participate in the voting mechanism?

Because it's in their own self-interest to do it, and it costs very little. Today over half of the miners mine RSK. It's not blind merged mining, it's a very convoluted process that requires them to run a RSK full node. For the Drivechain sidechains, an SPV node would be enough, or maybe just getting data from a block explorer API, so much much simpler.

What if I still don't like Drivechain even after reading this?

That is the entire point! You don't have to like it or use it as long as you're fine with other people using it. The hashrate escrow special addresses will not impact you at all, validation cost is minimal, and you get the benefit of people who want to use Drivechain migrating to their own sidechains and freeing up space for you in the mainchain. See also the point above about infighting.

See also

• Podcast episode with Ruben Somsen and Aaron van Wirdum explaining Drivechain
• Alternatives to Drivechain
• Drivechain comparison with Ethereum

@ 3bf0c63f:aefa459d

Personagens de jogos e símbolos

A sensação de "ser" um personagem em um jogo ou uma brincadeira talvez seja o mais próximo que eu tenha conseguido chegar do entendimento de um símbolo religioso.

A hóstia consagrada é, segundo a religião, o corpo de Cristo, mas nossa mente moderna só consegue concebê-la como sendo uma representação do corpo de Cristo. Da mesma forma outras culturas e outras religiões têm símbolos parecidos, inclusive nos quais o próprio participante do ritual faz o papel de um deus ou de qualquer coisa parecida.

"Faz o papel" é de novo a interpretação da mente moderna. O sujeito ali é a coisa, mas ele ao mesmo tempo que é também sabe que não é, que continua sendo ele mesmo.

Nos jogos de videogame e brincadeiras infantis em que se encarna um personagem o jogador é o personagem. não se diz, entre os jogadores, que alguém está "encenando", mas que ele é e pronto. nem há outra denominação ou outro verbo. No máximo "encarnando", mas já aí já é vocabulário jornalístico feito para facilitar a compreensão de quem está de fora do jogo.

@ 6b57533f:eaa341f5

🏝️lost in the ordinary?

Welcome to Stories

Discover a hidden paradise where the world slows down, and adventure begins..

🌊 Step into tranquility.

Wake up to the sound of gentle waves and endless blue horizons.

🛶Live the dream.

Unwind, explore, and escape—your perfect getaway is just one step away.

@ 3b7fc823:e194354f

Why You Should Only Run DeepSeek Locally: A Privacy Perspective and how to

In an era where AI tools promise immense utility, the decision to run DeepSeek locally is not merely about functionality but also about safeguarding privacy and security. Here's the rationale why:

1. Control Over Data Access: Running DeepSeek locally ensures that data processing occurs on your own machine or server, allowing you to have full control over who can access the system. This reduces the risk of unauthorized access and misuse.

2. Data Privacy: By keeping computations local, you ensure that personal data does not leave your control, minimizing the risk of exposure through cloud-based services.

3. Security Measures: Local operation provides an additional layer of security. You can implement access controls, monitor usage, and respond to incidents more effectively, which might be harder or impossible when relying on third-party platforms.

4. Practical Implementation: Tools like Ollama and OpenWebUI facilitate setting up a local environment, making it accessible even for those with limited technical expertise. This setup empowers individuals to leverage AI capabilities while maintaining privacy.

5. Right to Control Data: Privacy is a fundamental right, and running DeepSeek locally respects this by allowing users to decide what data they share and how it's accessed. This empowers individuals to make informed choices about their personal data.

For those prioritizing privacy, this approach is not just beneficial—it's essential.

Running DeepSeek Locally: A Guide for Individual Home Users

DeepSeek is a powerful AI search engine that can help with various tasks, but running it locally gives you greater control over your data and privacy. Here’s how you can set it up at home.

---

What You’ll Need

1. A Computer: A desktop or laptop with sufficient processing power (at least 4GB RAM).
2. Python and pip: To install and run DeepSeek.
3. Ollama: An open-source tool that allows you to run AI models locally.
4. OpenWebUI: A simple web interface for interacting with Ollama.

---

Step-by-Step Guide

1. Install the Prerequisites

• Python: Download and install Python from https://www.python.org.
• pip: Use pip to install Python packages. bash pip install --upgrade pip
• Ollama: bash pip install ollama
• OpenWebUI: Visit https://github.com/DeepSeek-LLM/openwebui and follow the instructions to install it.

---

2. Set Up Ollama

• Clone the official Ollama repository: bash git clone https://github.com/OllamaAI/Ollama.git cd Ollama
• Follow the installation guide on https://ollama.ai to set it up.

---

3. Run DeepSeek Locally

• Use OpenWebUI as your interface: bash # Start OpenWebUI (open a terminal and run this): python openwebui.py --model deepseek-llm-v0.2-beta
• A web browser will open, allowing you to interact with DeepSeek.

---

Tips for Optimization

1. Reduce Memory Usage: Use smaller models like deepseek-llm-v0.2-beta if your computer has limited resources.
2. Limit Model Access: Only allow authorized users to access the system by restricting IP addresses or using a VPN.
3. Regular Updates: Keep all software up to date to protect against vulnerabilities.

---

Why Run DeepSeek Locally?

• Privacy: Your data stays on your local machine, reducing the risk of unauthorized access.
• Flexability: Running locally allows you to build specific models for specific uses and provide them with RAG data.

---

Advocating for privacy does not finance itself. If you enjoyed this article, please consider zapping or sending monero

@ fbf0e434:e1be6a39

本文原载于《CERN Courier》，是由欧洲核子研究中心（CERN，全称Conseil Européen pour la Recherche Nucléaire）出版的权威科学期刊，专注于报道全球物理学、技术及创新领域的前沿动态。以下正文内容是对全球开源开发者激励平台DoraHacks的创始人张剑南的专访报道，探讨了黑客松如何成为科技创新的重要推动力以及DoraHacks在其中扮演的角色。

万维网（World Wide Web）、人工智能（Artificial Intelligence）与量子计算（Quantum Computing）——这些划时代的技术有何共同之处？DoraHacks创始人张剑南认为，它们都源于“Hacks（黑客精神）”。“当万维网在欧洲核子研究中心（CERN）诞生时，它向我们证明了一件事：要想改变并提高人类的生活方式和工作效率，关键在于以创新的思维利用现有的技术以实现突破。”张剑南解释道，“如果总是从零开始，我们永远无法取得实质性的进步。这恰恰就是开源运动和黑客马拉松的核心价值。”

十年前，张剑南参与筹办了CERN Webfest 2013，这是一场致力于探索如何以创新方式运用技术来服务科学与社会的黑客马拉松活动。通过Webfest，张剑南不仅实现了编程技能与物理学知识的跨学科融合，还与来自世界各地、背景各异的hackers建立了持久深厚的联系。随着参与黑客松次数的增多，他的“黑客精神”愈发强烈，最终驱使他创立了自己的公司。2024年，张剑南重返Webfest，但这次他不再是参与者，而是作为DoraHacks的首席执行官来见证这场盛会。

黑客马拉松是一种持续数天的社交编程活动，具有高度的包容性和开放性——参与者无需学术机构或企业背景即可加入。这种特性吸引了众多才华横溢的个体参与其中。活动中，hackers以团队形式合作，结合各自的技能，通过软件、硬件或商业计划等来解决技术难题。这不仅让物理学家、计算机科学家、工程师和企业家齐聚一堂，各展所长，也让年轻的开发者们有机会突破传统研究框架，提升技能、积累作品集，并拓展职业人脉。

“如果你对某件事充满热情，就应该能够立即投入其中并全力以赴，”张剑南强调，“追求梦想并不需要特定的学历或背景。”

对于在某个领域刚起步的研究者来说，黑客松的意义远不止于技术挑战。它为进入一个研究或行业领域提供了另一种途径，弥合了学术理论与实际应用之间的鸿沟。很多由大学举办的黑客松往往能够吸引到企业的赞助，这些赞助除了作为奖金来激励开发者持续开发，也会用来租赁大型场馆，以容纳数百甚至上千名参与者。

“正是这些大规模的黑客松吸引了众多行业猎头和导师的关注，”张剑南解释道，“他们把这类活动看作他们的人才库。通过黑客松，参与者们能够与大公司的人直接交流，加速职业发展，同时也能在实践中提升他们的编程能力。”

在2010年代，张剑南经常在周末参加黑客松，这也成为他创业的基石。“我曾经坐在计算机科学学院的公共休息室里，埋头研究我的黑客项目。我的大多数朋友也是在那里认识的，”张剑南回忆道，“但后来我意识到，如果想做出真正伟大的东西，必须有效地组织人力与资金。然后我就开始‘逃课’，不去上计算机系的课程，而是偷偷溜进商学院的教室里。”张剑南常常在商学院的教室后排听课，一边听课一边谋划自己的创业计划。他每天都与同行交流，评估各种不同的商业模式。“在创业过程中，要把工程知识与商业理论结合起来思考，”他补充道，“这是比较有趣的一点，让整个过程也轻松了一些。”

然而，从科学研究转向创业并非易事。“创业初期必须亲力亲为，要自己去学习然后完成各种任务。”张剑南坦言，“好处是能够接触到许多新技能和新朋友，但同时也得强迫自己去做那些原本不擅长的事情。”

这种经历也反映了许多创业者的共同困境：选择自己从头学习新技能，还是寻找合适的创业伙伴然后把任务分配出去？可是找到值得信赖的合作伙伴也不是一件容易的事，错误的决策甚至可能阻碍公司的发展。因此，从一开始就明确公司的愿景和使命显得尤为重要。

“解决方案其实很简单，”张剑南表示，“重点是要投入足够多的时间，亲自完成关键里程碑，以确保产品真正具备可行性。只要有了明确的商业计划和愿景，就能获得来自各方的支持。”

去中心化的社区治理

很多黑客马拉松参与者在活动结束后就会放弃自己的项目，但张剑南创立DoraHacks的初衷并非如此。他希望为全球的黑客团队提供一个平台，让他们能够将创意转化为成熟产品。“我希望黑客马拉松不仅仅是一个招聘工具，”他解释道，“它更应该推动开源开发和去中心化的社区治理。比如现在，来自坦桑尼亚的黑客可以与美国的黑客团队远程协作，然后获得持续的支持，以开发出真正有影响力的产品。这种模式让技术领域变得更多样化，同时也能够让更多人接触到不同的领域。”

DoraHacks通过帮助组织者降低后勤成本，为参与者提供更可靠的资金支持机制，使黑客松超越学术机构的限制，吸引更多对创新充满热情的个体研究者参与。然后不断发展整个社区，让年轻一代的开发者、研究者们能够在自己的职业初期，接触到比以往更多的机遇和机会。

“商业模式正在发生根本的变化，”张剑南指出，黑客马拉松正在发展成为新兴技术的基石，尤其是在量子计算、区块链和人工智能等以开源形式起步的领域。“产品创造的过程将会迎来重大变革。未来的技术发展不再依赖于孤立封闭的产品开发，而是基于黑客们可以共同贡献的平台和基础设施。”

如今，黑客马拉松的意义已不仅限于编程或建立人脉——它们更关乎突破技术边界、创造有意义的解决方案，并开辟新的职业道路。黑客马拉松是创意孵化器，并且能够对这些创意产生持久的影响力。张剑南希望帮助这些创意变为现实。“未来创新的方式一定是协作完成的，是开源的，”他再次强调，“在传统社会环境里，企业的发展依赖于在闭源技术周围筑起的护城河，这种技术更新方式的效率低下且不容易实现。而真正创新的未来，将以开放平台技术为核心，让全球开发者能够在现有项目的基础上不断迭代更新。这样的开放协作精神正是Hacker Movement（开源极客运动）如此重要的原因。”

采访者：Alex Epshtein（编辑助理）。 原文链接：https://cerncourier.com/wp-content/uploads/2025/01/CERNCourier2025JanFeb-digitaledition.pdf

@ 378562cd:a6fc6773

Chef's notes

I'm only testing this out right now. I will update the recipe as well as add my own image soon after making this dish again.

Details

• ⏲️ Prep time: 20 minutes
• 🍳 Cook time: 1 hour
• 🍽️ Servings: 4

Ingredients

• 4 to 6 potatoes (size depending)
• 1 lb ground beef
• seasonings
• 2 cans chili beans
• 1 onion
• katsup
• shredded cheese of some kind

Directions

1. saute onion and add ground beef to skillet. Season to liking.
2. peel if you like and thin slice potatoes
3. in a rectangle baking dish, layer potatoes, beans, meat and cheese (like a lasagna) until you have used all your ingredients. Try and make at least 2 or 3 layers with extra cheese on top.
4. Bake at 350 for one hour. Serve and enjoy!

@ 97c70a44:ad98e322

There was a slight dust up recently over a website someone runs removing a listing for an app someone built based on entirely arbitrary criteria. I'm not to going to attempt to speak for either wounded party, but I would like to share my own personal definition for what constitutes a "nostr app" in an effort to help clarify what might be an otherwise confusing and opaque purity test.

In this post, I will be committing the "no true Scotsman" fallacy, in which I start with the most liberal definition I can come up with, and gradually refine it until all that is left is the purest, gleamingest, most imaginary and unattainable nostr app imaginable. As I write this, I wonder if anything built yet will actually qualify. In any case, here we go.

It uses nostr

The lowest bar for what a "nostr app" might be is an app ("application" - i.e. software, not necessarily a native app of any kind) that has some nostr-specific code in it, but which doesn't take any advantage of what makes nostr distinctive as a protocol.

Examples might include a scraper of some kind which fulfills its charter by fetching data from relays (regardless of whether it validates or retains signatures). Another might be a regular web 2.0 app which provides an option to "log in with nostr" by requesting and storing the user's public key.

In either case, the fact that nostr is involved is entirely neutral. A scraper can scrape html, pdfs, jsonl, whatever data source - nostr relays are just another target. Likewise, a user's key in this scenario is treated merely as an opaque identifier, with no appreciation for the super powers it brings along.

In most cases, this kind of app only exists as a marketing ploy, or less cynically, because it wants to get in on the hype of being a "nostr app", without the developer quite understanding what that means, or having the budget to execute properly on the claim.

It leverages nostr

Some of you might be wondering, "isn't 'leverage' a synonym for 'use'?" And you would be right, but for one connotative difference. It's possible to "use" something improperly, but by definition leverage gives you a mechanical advantage that you wouldn't otherwise have. This is the second category of "nostr app".

This kind of app gets some benefit out of the nostr protocol and network, but in an entirely selfish fashion. The intention of this kind of app is not to augment the nostr network, but to augment its own UX by borrowing some nifty thing from the protocol without really contributing anything back.

Some examples might include:

• Using nostr signers to encrypt or sign data, and then store that data on a proprietary server.
• Using nostr relays as a kind of low-code backend, but using proprietary event payloads.
• Using nostr event kinds to represent data (why), but not leveraging the trustlessness that buys you.

An application in this category might even communicate to its users via nostr DMs - but this doesn't make it a "nostr app" any more than a website that emails you hot deals on herbal supplements is an "email app". These apps are purely parasitic on the nostr ecosystem.

In the long-term, that's not necessarily a bad thing. Email's ubiquity is self-reinforcing. But in the short term, this kind of "nostr app" can actually do damage to nostr's reputation by over-promising and under-delivering.

It complements nostr

Next up, we have apps that get some benefit out of nostr as above, but give back by providing a unique value proposition to nostr users as nostr users. This is a bit of a fine distinction, but for me this category is for apps which focus on solving problems that nostr isn't good at solving, leaving the nostr integration in a secondary or supporting role.

One example of this kind of app was Mutiny (RIP), which not only allowed users to sign in with nostr, but also pulled those users' social graphs so that users could send money to people they knew and trusted. Mutiny was doing a great job of leveraging nostr, as well as providing value to users with nostr identities - but it was still primarily a bitcoin wallet, not a "nostr app" in the purest sense.

Other examples are things like Nostr Nests and Zap.stream, whose core value proposition is streaming video or audio content. Both make great use of nostr identities, data formats, and relays, but they're primarily streaming apps. A good litmus test for things like this is: if you got rid of nostr, would it be the same product (even if inferior in certain ways)?

A similar category is infrastructure providers that benefit nostr by their existence (and may in fact be targeted explicitly at nostr users), but do things in a centralized, old-web way; for example: media hosts, DNS registrars, hosting providers, and CDNs.

To be clear here, I'm not casting aspersions (I don't even know what those are, or where to buy them). All the apps mentioned above use nostr to great effect, and are a real benefit to nostr users. But they are not True Scotsmen.

It embodies nostr

Ok, here we go. This is the crème de la crème, the top du top, the meilleur du meilleur, the bee's knees. The purest, holiest, most chaste category of nostr app out there. The apps which are, indeed, nostr indigitate.

This category of nostr app (see, no quotes this time) can be defined by the converse of the previous category. If nostr was removed from this type of application, would it be impossible to create the same product?

To tease this apart a bit, apps that leverage the technical aspects of nostr are dependent on nostr the protocol, while apps that benefit nostr exclusively via network effect are integrated into nostr the network. An app that does both things is working in symbiosis with nostr as a whole.

An app that embraces both nostr's protocol and its network becomes an organic extension of every other nostr app out there, multiplying both its competitive moat and its contribution to the ecosystem:

• In contrast to apps that only borrow from nostr on the technical level but continue to operate in their own silos, an application integrated into the nostr network comes pre-packaged with existing users, and is able to provide more value to those users because of other nostr products. On nostr, it's a good thing to advertise your competitors.
• In contrast to apps that only market themselves to nostr users without building out a deep integration on the protocol level, a deeply integrated app becomes an asset to every other nostr app by becoming an organic extension of them through interoperability. This results in increased traffic to the app as other developers and users refer people to it instead of solving their problem on their own. This is the "micro-apps" utopia we've all been waiting for.

Credible exit doesn't matter if there aren't alternative services. Interoperability is pointless if other applications don't offer something your app doesn't. Marketing to nostr users doesn't matter if you don't augment their agency as nostr users.

If I had to choose a single NIP that represents the mindset behind this kind of app, it would be NIP 89 A.K.A. "Recommended Application Handlers", which states:

Nostr's discoverability and transparent event interaction is one of its most interesting/novel mechanics. This NIP provides a simple way for clients to discover applications that handle events of a specific kind to ensure smooth cross-client and cross-kind interactions.

These handlers are the glue that holds nostr apps together. A single event, signed by the developer of an application (or by the application's own account) tells anyone who wants to know 1. what event kinds the app supports, 2. how to link to the app (if it's a client), and (if the pubkey also publishes a kind 10002), 3. which relays the app prefers.

As a sidenote, NIP 89 is currently focused more on clients, leaving DVMs, relays, signers, etc somewhat out in the cold. Updating 89 to include tailored listings for each kind of supporting app would be a huge improvement to the protocol. This, plus a good front end for navigating these listings (sorry nostrapp.link, close but no cigar) would obviate the evil centralized websites that curate apps based on arbitrary criteria.

Examples of this kind of app obviously include many kind 1 clients, as well as clients that attempt to bring the benefits of the nostr protocol and network to new use cases - whether long form content, video, image posts, music, emojis, recipes, project management, or any other "content type".

To drill down into one example, let's think for a moment about forms. What's so great about a forms app that is built on nostr? Well,

• There is a spec for forms and responses, which means that...
• Multiple clients can implement the same data format, allowing for credible exit and user choice, even of...
• Other products not focused on forms, which can still view, respond to, or embed forms, and which can send their users via NIP 89 to a client that does...
• Cryptographically sign forms and responses, which means they are self-authenticating and can be sent to...
• Multiple relays, which reduces the amount of trust necessary to be confident results haven't been deliberately "lost".

Show me a forms product that does all of those things, and isn't built on nostr. You can't, because it doesn't exist. Meanwhile, there are plenty of image hosts with APIs, streaming services, and bitcoin wallets which have basically the same levels of censorship resistance, interoperability, and network effect as if they weren't built on nostr.

It supports nostr

Notice I haven't said anything about whether relays, signers, blossom servers, software libraries, DVMs, and the accumulated addenda of the nostr ecosystem are nostr apps. Well, they are (usually).

This is the category of nostr app that gets none of the credit for doing all of the work. There's no question that they qualify as beautiful nostrcorns, because their value propositions are entirely meaningless outside of the context of nostr. Who needs a signer if you don't have a cryptographic identity you need to protect? DVMs are literally impossible to use without relays. How are you going to find the blossom server that will serve a given hash if you don't know which servers the publishing user has selected to store their content?

In addition to being entirely contextualized by nostr architecture, this type of nostr app is valuable because it does things "the nostr way". By that I mean that they don't simply try to replicate existing internet functionality into a nostr context; instead, they create entirely new ways of putting the basic building blocks of the internet back together.

A great example of this is how Nostr Connect, Nostr Wallet Connect, and DVMs all use relays as brokers, which allows service providers to avoid having to accept incoming network connections. This opens up really interesting possibilities all on its own.

So while I might hesitate to call many of these things "apps", they are certainly "nostr".

Appendix: it smells like a NINO

So, let's say you've created an app, but when you show it to people they politely smile, nod, and call it a NINO (Nostr In Name Only). What's a hacker to do? Well, here's your handy-dandy guide on how to wash that NINO stench off and Become a Nostr.

You app might be a NINO if:

• There's no NIP for your data format (or you're abusing NIP 78, 32, etc by inventing a sub-protocol inside an existing event kind)
• There's a NIP, but no one knows about it because it's in a text file on your hard drive (or buried in your project's repository)
• Your NIP imposes an incompatible/centralized/legacy web paradigm onto nostr
• Your NIP relies on trusted third (or first) parties
• There's only one implementation of your NIP (yours)
• Your core value proposition doesn't depend on relays, events, or nostr identities
• One or more relay urls are hard-coded into the source code
• Your app depends on a specific relay implementation to work (ahem, relay29)
• You don't validate event signatures
• You don't publish events to relays you don't control
• You don't read events from relays you don't control
• You use legacy web services to solve problems, rather than nostr-native solutions
• You use nostr-native solutions, but you've hardcoded their pubkeys or URLs into your app
• You don't use NIP 89 to discover clients and services
• You haven't published a NIP 89 listing for your app
• You don't leverage your users' web of trust for filtering out spam
• You don't respect your users' mute lists
• You try to "own" your users' data

Now let me just re-iterate - it's ok to be a NINO. We need NINOs, because nostr can't (and shouldn't) tackle every problem. You just need to decide whether your app, as a NINO, is actually contributing to the nostr ecosystem, or whether you're just using buzzwords to whitewash a legacy web software product.

If you're in the former camp, great! If you're in the latter, what are you waiting for? Only you can fix your NINO problem. And there are lots of ways to do this, depending on your own unique situation:

• Drop nostr support if it's not doing anyone any good. If you want to build a normal company and make some money, that's perfectly fine.
• Build out your nostr integration - start taking advantage of webs of trust, self-authenticating data, event handlers, etc.
• Work around the problem. Think you need a special relay feature for your app to work? Guess again. Consider encryption, AUTH, DVMs, or better data formats.
• Think your idea is a good one? Talk to other devs or open a PR to the nips repo. No one can adopt your NIP if they don't know about it.
• Keep going. It can sometimes be hard to distinguish a research project from a NINO. New ideas have to be built out before they can be fully appreciated.
• Listen to advice. Nostr developers are friendly and happy to help. If you're not sure why you're getting traction, ask!

I sincerely hope this article is useful for all of you out there in NINO land. Maybe this made you feel better about not passing the totally optional nostr app purity test. Or maybe it gave you some actionable next steps towards making a great NINON (Nostr In Not Only Name) app. In either case, GM and PV.

@ df57b498:d049124f

Chef's notes

This is cobbled together from trial and error and the web.

Serve hot pancakes with preferably butter and maple syrup. Add other toppings like bananas, nuts, or other fruits and toppings as have available and/or desired.

Details

• ⏲️ Prep time: 10 minutes
• 🍳 Cook time: 10 minutes

Ingredients

• 1 cup flour
• 2 tablespoons sugar
• 2 teaspoons baking powder
• 1 teaspoon salt
• 1 cup milk
• 2 tablespoons vegetable oil
• 1 egg, beaten

Directions

1. Combine the dry ingredients.
2. Add the wet ingredients and mix.
3. Pour or ladle the batter onto the oiled griddle or pan.
4. Cook until bubbles form, flip, and cook on the other side.

@ 3bf0c63f:aefa459d

A Causa

o Princípios de Economia Política de Menger é o único livro que enfatiza a CAUSA o tempo todo. os cientistas todos parecem não saber, ou se esquecer sempre, que as coisas têm causa, e que o conhecimento verdadeiro é o conhecimento da causa das coisas.

a causa é uma categoria metafísica muito superior a qualquer correlação ou resultado de teste de hipótese, ela não pode ser descoberta por nenhum artifício econométrico ou reduzida à simples antecedência temporal estatística. a causa dos fenômenos não pode ser provada cientificamente, mas pode ser conhecida.

o livro de Menger conta para o leitor as causas de vários fenômenos econômicos e as interliga de forma que o mundo caótico da economia parece adquirir uma ordem no momento em que você lê. é uma sensação mágica e indescritível.

quando eu te o recomendei, queria é te imbuir com o espírito da busca pela causa das coisas. depois de ler aquilo, você está apto a perceber continuidade causal nos fenômenos mais complexos da economia atual, enxergar as causas entre toda a ação governamental e as suas várias consequências na vida humana. eu faço isso todos os dias e é a melhor sensação do mundo quando o caos das notícias do caderno de Economia do jornal -- que para o próprio jornalista que as escreveu não têm nenhum sentido (tanto é que ele escreve tudo errado) -- se incluem num sistema ordenado de causas e consequências.

provavelmente eu sempre erro em alguns ou vários pontos, mas ainda assim é maravilhoso. ou então é mais maravilhoso ainda quando eu descubro o erro e reinsiro o acerto naquela racionalização bela da ordem do mundo econômico que é a ordem de Deus.

em scrap para T.P.

@ 3bf0c63f:aefa459d

Veterano não é dono de bixete

"VETERANO NÃO É DONO DE BIXETE". A frase em letras garrafais chama a atenção dos transeuntes neófitos. Paira sobre um cartaz amarelo que lista várias reclamações contra os "trotes machistas", que, na opinião do responsável pelo cartaz, "não é brincadeira, é opressão".

Eis aí um bizarro exemplo de como são as coisas: primeiro todos os universitários aprovam a idéia do trote, apoiam sua realização e até mesmo desejam sofrer o trote -- com a condição de o poderem aplicar eles mesmos depois --, louvam as maravilhas do mundo universitário, onde a suprema sabedoria se esconde atrás de rituais iniciáticos fora do alcance da imaginação do homem comum e rude, do pobre e do filhinho-de-papai das faculdades privadas; em suma: fomentam os mais baixos, os mais animalescos instintos, a crueldade primordial, destroem em si mesmos e nos colegas quaisquer valores civilizatórios que tivessem sobrado ali, ficando todos indistingüíveis de macacos agressivos e tarados.

Depois vêm aí com um cartaz protestar contra os assédios -- que sem dúvida acontecem em larguíssima escala -- sofridos pelas calouras de 17 anos e que, sendo também novatas no mundo universitário, ainda conservam um pouco de discernimento e pudor.

A incompreensão do fenômeno, porém, é tão grande, que os trotes não são identificados como um problema mental, uma doença que deve ser tratada e eliminada, mas como um sintoma da opressão machista dos homens às mulheres, um produto desta civilização paternalista que, desde que Deus é chamado "o Pai" e não "a Mãe", corrompe a benéfica, pura e angélica natureza do homem primitivo e o torna esta tão torpe criatura.

Na opinião dos autores desse cartaz é preciso, pois, continuar a destruir o que resta da cultura ocidental, e então esperar que haja trotes menos opressores.

@ 9e69e420:d12360c2

Chef's notes

arbitray

• test
• of
• chefs notes

hedding 2

Details

• ⏲️ Prep time: 20
• 🍳 Cook time: 1 hour
• 🍽️ Servings: 5

Ingredients

• Test ingredient
• 2nd test ingredient

Directions

1. Bake
2. Cool

@ ddf03aca:5cb3bbbe

We’re thrilled to announce the stable release of Cashu-TS v2.2! Although this update is a minor version bump, it brings significant improvements under the hood that enhance the overall developer experience. We’ve spent several weeks testing and refining these changes.

---

What’s New in v2.2?

While there are no breaking changes in this release, there are many internal changes. If you spot any regressions or unexpected behavior, please let us know. Here’s a rundown of the major updates:

• Enhanced Proof Creation: The way proofs are created internally has been revamped.
• User-Controlled Outputs: You now have full control over how outputs are created.
• Improved Bundling: We’ve switched our bundling tool to vite for faster and more modern builds.
• Updated Testing Tools: Our testing framework has migrated to vitest and msw, with added browser testing via Playwright.

---

New Flexibility with OutputData

In previous versions of Cashu-TS, the creation of outputs (or BlindedMessages) was hidden away. Even though there were options to tweak the process (like deterministic secrets or P2PK), you were always limited to the built-in logic.

What’s Changed?

In v2.2, we’ve introduced a public interface that not only streamlines output creation but also lets you plug in your own custom logic when needed. With the new outputData option available on all output-creating methods, you can now bypass the automatic process and provide your own outputs.

For example, you can create two proofs tied to different public keys in a single mint operation:

ts const data1 = OutputData.createP2PKData({ pubkey: "key1" }, 10, keys); const data2 = OutputData.createP2PKData({ pubkey: "key2" }, 10, keys); const { keep, send } = await wallet.send(20, proofs, { outputData: { send: [...data1, ...data2] }, });

Customization Made Easy

The outputData option now accepts anything that conforms to the OutputDataLike interface. This means you can introduce your own output creation logic—even if it’s not natively supported by Cashu-TS yet. Here’s what the interface looks like:

```ts export interface OutputDataLike { blindedMessage: SerializedBlindedMessage; blindingFactor: bigint; secret: Uint8Array;

toProof: (signature: SerializedBlindedSignature, keyset: MintKeys) => Proof; } ```

Introducing OutputData Factories

While having full control is empowering, it also means you’ll need to handle tasks like fee calculation and amount selection manually. To strike a balance between control and convenience, we now support OutputData Factories.

A factory is simply a function that takes an amount and MintKeys as input and returns an OutputDataLike object. This way, you can define a blueprint for your output data without worrying about the nitty-gritty details. For instance, you can create separate factories for amounts you keep versus those you send:

```ts function keepFactory(a: number, k: MintKeys) { return OutputData.createSingleP2PKData({ pubkey: "keepPk" }, a, k.id); }

function sendFactory(a: number, k: MintKeys) { return OutputData.createSingleP2PKData({ pubkey: "sendPk" }, a, k.id); }

const { send, keep } = await wallet.send(amount, proofs, { outputData: { send: createFactory("send"), keep: createFactory("keep") }, }); ```

Plus, you can now instantiate a CashuWallet with a default keepFactory, ensuring that all change amounts automatically lock to your key—streamlining your workflow even further.

---

Bundling Improvements with Vite

Starting with v2.2, we’ve transitioned from using tsc to vite for transpiling and bundling the library code. Although this change is mostly behind the scenes, it brings several benefits:

• Modern Build Target: We’ve updated our build target to ES6.
• Updated Exports: The package exports now reflect the latest JavaScript standards.
• Standalone Build Soon: We’re working on a standalone build that bundles Cashu-TS along with all its dependencies. This will let you import Cashu-TS directly into your HTML.

If you encounter any issues with the new bundling setup, please let us know.

A Nod to Vitest

In addition to our bundling improvements, we’ve migrated our testing framework from Jest (with nock) to vitest combined with msw. This switch gives us more flexibility in testing and mocking, plus we’ve added browser testing based on Playwright—thanks to the tip from nostr:npub16anjdksmvn5x08vtden04n64rw5k7fsjmedpw8avsx8wsh8ruhlq076pfx!

---

In Conclusion

Although Cashu-TS v2.2 is a minor version update, it comes packed with improvements that enhance both the developer experience and the flexibility of the library. We’re excited to see how you’ll use these new features in your projects! Thanks to all the amazing contributors that add to this library.

Thank you for being a part of the Cashu-TS community. As always, if you have any questions, suggestions, or issues, don’t hesitate to reach out to us.

@ 3bf0c63f:aefa459d

neuron.vim

I started using this neuron thing to create an update this same zettelkasten, but the existing vim plugin had too many problems, so I forked it and ended up changing almost everything.

Since the upstream repository was somewhat abandoned, most users and people who were trying to contribute upstream migrate to my fork too.

• https://github.com/fiatjaf/neuron.vim

@ 30b99916:3cc6e3fe

Details

• 🍳 Cook time: 10 to 8 minutes at 350
• 🍽️ Servings: About 4 dozen cookies

Ingredients

• 2 sticks of butter
• 2 eggs
• 1 cup granulated sugar
• 1 cup brown sugar
• 1 cup peanut butter
• 1 t vanilla
• 2 cups flour
• 1/2 t salt
• 1 t soda
• 6 oz Semi-Sweet Chocolate chips (optional)

Directions

1. Blend butter, eggs, vanilla and sugars together thoroughly
2. Next blend in peanut butter thoroughly
3. Next blend in flour, salt, and soda thoroughly
4. Optional blend in chocolate chips
5. Add about table spoon of cookie dough per cookie on a cookie sheet. With a fork based in sugar place a cross hatch pattern on each cookie. Bake cookies for 10 to 8 minutes and place onto cooler rack.

@ 3bf0c63f:aefa459d

On "zk-rollups" applied to Bitcoin

ZK rollups make no sense in bitcoin because there is no "cheap calldata". all data is already ~~cheap~~ expensive calldata.

There could be an onchain zk verification that allows succinct signatures maybe, but never a rollup.

What happens is: you can have one UTXO that contains multiple balances on it and in each transaction you can recreate that UTXOs but alter its state using a zk to compress all internal transactions that took place.

The blockchain must be aware of all these new things, so it is in no way "L2".

And you must have an entity responsible for that UTXO and for conjuring the state changes and zk proofs.

But on bitcoin you also must keep the data necessary to rebuild the proofs somewhere else, I'm not sure how can the third party responsible for that UTXO ensure that happens.

I think such a construct is similar to a credit card corporation: one central party upon which everybody depends, zero interoperability with external entities, every vendor must have an account on each credit card company to be able to charge customers, therefore it is not clear that such a thing is more desirable than solutions that are truly open and interoperable like Lightning, which may have its defects but at least fosters a much better environment, bringing together different conflicting parties, custodians, anyone.

@ fe41d17e:28df7452

Um es vorab klarzustellen, die einzigen Gesetze an die du dich wirklich halten musst sind die Naturgesetze, es ist deine eigene Entscheidung ob du einer einseitig vom Staat beschlossenen Auflage zustimmst oder nicht, solange du bereit bist, falls du erwischt wirst, die Konsequenzen über dich ergehen zu lassen.

Wenn du diese Unterdrückung nicht mehr haben möchtest braucht es eine Revolution um den Staat irrelevant werden zu lassen und um ihm seine Grundlage (das Geld) zu entziehen ohne dabei wie er selbst zu unmoralischen Methoden zu greifen.

Diese Revolution nennt sich Agorismus, sie wird dich unabhängig vom Staat machen und den Staat langfristig schwach/überflüssig werden lassen sobald es dir genug Leute gleichtun.

Die Revolution wird nicht leicht, sie wird dir nicht die sofortige Genugtuung verschaffen, die du möglicherweise empfindest, wenn du einen Zettel in die Wahlurne wirfst und dabei das Gefühl hast, etwas verändert zu haben. Eigentlich hast du nur denselben Leuten Macht verliehen, die seit Jahrhunderten die Politiker kontrollieren, dich ausrauben und unterdrücken. Garnichts hast du damit verändert.

Es wird schwierig werden. Es wird Eigeninitiative und Veränderungen in deinem Leben erfordern. Es wird ein zermürbender, unbefriedigender Weg sein, den viele als zu hart bezeichnen werden. Es wird Jahre über Jahre dauern, in denen die Leute dich dafür schief ansehen und du kaum Anerkennung bekommen wirst.

Hier ein paar wichtige Punkte um dich mit Agorismus vertraut zu machen:

-Wenn du bereits ein Libertärer bist, lies zuerst „Das neue Libertäre Manifest“ von Samuel Edward Konkin III. Es hat nur 30 Seiten, und wenn du damit nicht zumindest deinen Horizont erweitern kannst, dann kannst du genauso gut eine britische Flagge in Amerika schwenken, Tribut zollen und einen König fordern.

-Wenn du kein Libertärer bist, lies „Eine neue Freiheit: das libertäre Manifest“ von Murray Rothbard und anschließend „Das neue Libertäre Manifest“ von SEK3.

-Konzentriere dich in deinem Leben darauf, weniger bis keine Steuern zu zahlen.

-Finde Alternativen zum Fiatgeld und sei deine eigene Bank.

-Finde lokale Quellen für Lebensmittel und Produkte.

-Handel P2P auf freien Märkten.

-Suche nach Lösungen, die auf Dezentralisierung ausgerichtet sind.

-Baue eine gewisse Menge an Lebensmitteln an, auch wenn es nur Mikrogrün ist. Dafür sind keine großen Flächen erforderlich und du kannst diese gegen andere Lebensmittel eintauschen.

-Baue dein eigenes Unternehmen außerhalb von Konzernstrukturen auf.

-Konzentriere dich auf den Handel mit anderen Agoristen.

-Nutze jede Gelegenheit um deine Verachtung gegenüber dem Staat zu äußern.

-Verbreite Agorismus.

-Beschaffe dir Waffen.

-Vertraue nur agoristischen Medien, die unpolitisch sind. Denn jeder Journalist, der dich ermutigt, zu wählen oder innerhalb des Systems zu arbeiten, könnte gekauft oder kontrolliert sein. Agoristen, die behaupten, dass Politik nicht die Antwort ist, sind die einzigen, die die Menschen wirklich von den Kontrolleuren wegführen.

Die Herrscher dieser Welt sind sich durchaus darüber im Klaren, dass das Informationszeitalter ihren Interessen schadet. Daher arbeiten sie unermüdlich an der Schaffung psychologischer Operationen (PsyOps), kontrollierter Opposition, False-Flag-Aktionen und Ablenkungsmanövern, lass dich nicht täuschen.

Erstveröffentlichung am 12. Januar auf meinem X Profil; @realbunki

@ 3bf0c63f:aefa459d

Splitpages

The simplest possible service: it splitted PDF pages in half.

Created specially to solve the problem of those scanned books that come with two pages side-by-side as if they were a single page and are much harder to read on Kindle because of that.

It required me to learn about Heroku Buildpacks though, and fork or contribute to a Heroku Buildpack that embedded a mupdf binary.

• https://github.com/fiatjaf/splitpages
• https://splitpages.herokuapp.com/

@ c69b71dc:426ba763

Chef's notes

This raw vegan curry ramen is a vibrant, nourishing dish packed with fresh vegetables and a rich, creamy coconut curry broth. It’s quick to prepare, full of flavour, and the perfect guilt-free comfort food! 🌱 Feel free to use your favourite veggies👩🏼‍🍳

Details

• ⏲️ Prep time: 20 min.
• 🍳 Cook time: 0
• 🍽️ Servings: 2

Ingredients

• 500g or 2 packs kelp noodles
• 1/2 Lemon juice ( 1/4 for soaking and 1/4 for the soup
• Salt
• Fresh vegetables of your choice, such as: 4 medium mushrooms, 4 leaves red cabbage, 2 carrots (julienned or peeled into strips), 1 Celery stick (diced)
• 2 cups coconut milk (or coconut cream diluted with water)
• 1/2 flesh of a Coconut (optional, if using fresh coconuts) otherwise more coconut cream
• 1 thumb of fresh ginger
• 1 thumb of fresh turmeric
• 2 tbsp light miso paste
• 2 pitted dates
• 2 tbsp cashews
• 1 clove garlic
• 1 tsp curry powder or pepper (optional)

Directions

1. Prepare the Noodles: Rinse the kelp noodles thoroughly. Then soak them in warm water with a squeeze of lemon juice and a pinch of salt for 10 minutes to soften.
2. Prep the Vegetables: Thinly slice or julienne carrots, dice celery, thinly cut mushrooms, cut the red cabbage into thin strips.
3. Make the Broth: In a blender, combine the following: 2 cups coconut milk (or coconut cream diluted with water if fresh coconuts are unavailable), ginger, turmeric, 1/4 juice of 1 lemon, light miso paste, pitted dates, cashews, garlic, salt, curry powder
4. Blend on high speed for about 3 to 4 minutes until the broth is smooth and slightly warm. Do not overheat!
5. Assemble the Ramen: Drain the kelp noodles and place them in serving bowls. Arrange the prepped vegetables on top of the noodles. Pour the warm curry broth over the noodles and vegetables.
6. Serve immediately and enjoy your raw vegan ramen with chopsticks for an authentic touch!

@ 3bf0c63f:aefa459d

tempreites

My first library to get stars on GitHub, was a very stupid templating library that used just HTML and HTML attributes ("DSL-free"). I was inspired by http://microjs.com/ at the time and ended up not using the library. Probably no one ever did.

• https://github.com/fiatjaf/tempreites

@ 77be3409:5c7c2736

RMD Law - Personal Injury Lawyers is excited to announce the launch of its new scholarship program, designed to empower students and highlight the values of responsibility, resilience, and learning from life’s unexpected moments. This $2,500 scholarship aims to support students in their educational journeys while encouraging creativity and personal growth.

Scholarship Details

Award Amount: $2,500 Submission Deadline: December 30, 2025 Winner Announced: January 15, 2026

Eligibility Requirements To apply, students must meet the following criteria: - Be at least 16 years old and a permanent legal resident of the United States. - Be currently enrolled in a U.S. college, university, or trade school OR graduating from high school in 2025. - Have a cumulative GPA of 3.0 or higher. - Follow RMD Law on social media to see the winner announcement. - Submit all required materials by the December 30, 2025, deadline

Application Requirements Applicants are required to submit:

• A copy of their most recent high school or college transcript.
• A creative and thoughtful essay (up to 1,000 words) responding to the following prompt:

Essay Prompt: “Oops, That Was Close!”

Tell us about a moment when you narrowly avoided disaster—whether it was a hilarious mishap, an embarrassing accident, or a close call with serious consequences. - What did you learn (if anything) from the experience? - Who was at fault and why? - What would the appropriate restitution (if any) be in that situation?

Note: Applicants are encouraged to use creativity, levity, and personal insights to share their story. Let your unique voice shine through!

Selection Criteria The winner will be chosen based on: - Originality and creativity in their essay. - Relevance to the prompt. - Clarity and thoughtfulness of their response. The scholarship recipient will be announced on January 15, 2026.

How to Apply 1. Students can submit their application materials through the official RMD Law scholarship webpage: https://www.rmdlaw.com/scholarship/ 2. Follow RMD Law on social media to stay updated on the announcement and other initiatives.

About RMD Law

RMD Law is a leading personal injury law firm committed to providing exceptional legal services and making a positive impact in the communities it serves. Through initiatives like the scholarship program, RMD Law seeks to empower individuals and foster the next generation of leaders.

@ d1b118c6:4985b38d

Chef's notes

Let me know how it goes for you https://maria.omg.lol

Details

• ⏲️ Prep time: 5-20 minutes
• 🍳 Cook time: 20-40 minutes
• 🍽️ Servings: As many as you want omg!!!!

Ingredients

• Spaghetti/whatever pasta you want
• Garlic/smashed or diced as much as you want
• Tomatoes/ diced or more liquid state whatever you want
• Scallops/ I use the frozen bagged mini kind and just do a couple handfuls as many as you want
• Butter and/or olive oil but the butter is v good imo but also I used both
• Bacon/ make it extra crispy and then crumble up as much as you want
• Whatever seasonings

Directions

1. Set oven to 400° or so
2. Put all your bacon 🥓 strips onto tin foil lined baking sheet/s and then put the trays in the oven for 15-20 min
3. Boil up your pasta in salty water
4. Pull the bacon out when done
5. In a pan cook up the scallops real quick like 5-10 min idk
6. Sauté the tomatoes and garlic and whatever use whatever seasons and lots of butter
7. Strain the pasta when it’s ready
8. Mix pasta and sautéed sauce
9. Add more crumbled bacon on top #garnish

@ 3bf0c63f:aefa459d

litepub

A Go library that abstracts all the burdensome ActivityPub things and provides just the right amount of helpers necessary to integrate an existing website into the "fediverse" (what an odious name). Made for the gravity integration.

• https://godoc.org/github.com/fiatjaf/litepub

See also

-

@ 30b99916:3cc6e3fe

Chef's notes

Recipe modified from a recipe published from a school cookbook in 1963.

Details

• 🍳 Cook time: 8 to 10 Minutes at 400
• 🍽️ Servings: 3 dozen or so depending on cookie size

Ingredients

• 2 sticks of butter
• 1 1/2 Cup sugar
• 2 eggs
• 1 t. vanilla (optional but recommended)
• 2 3/4 cups flour
• 2 t. Cream of tartar
• 1 t. Soda
• 1/4 t. Salt

Directions

1. 1. Heat over to 400
2. 1. Mix butter, sugar, eggs, and vanilla thoroughly.
3. 1. Sift together flour, cream of tartar, soda, salt and blend into mixture.
4. 1. Form small dough balls and roll in sugar/cinnamon
5. 1. Place each cookie dough ball 2" apart on a cookie sheet

@ ccc8ee23:9f3d9783

Chef's notes

Indulge in tender, golden-fried chicken breast, crunchy with every bite. Nestled on a bed of steamed rice, this dish is elevated by a rich, velvety curry sauce, infused with the warmth of fragrant spices and the umami depth of soy.

Paired with vibrant vegetables for a harmonious balance of textures and flavors, this comforting classic promises to delight your soul.

Details

• ⏲️ Prep time: 10 min
• 🍳 Cook time: 30 min
• 🍽️ Servings: 2

Ingredients

• Chicken Fillet 250 grams
• Potato 100 grams
• Egg 1 pc
• Curry block 2 pcs or 20 grams
• breadcrumbs 100 grams / 2 cups
• flour 20 grams
• Cooking oil (for frying)
• chicken or vegetable stock 500ml
• soy sauce 1 tbsp
• Seasoning
• onion 1 pc, finely chopped
• garlic cloves 2 pcs, minced
• carrot 1 pc, chopped

Directions

1. Chicken Katsu: Pound the chicken breasts until about 1/2 inch thick. Season with salt and pepper. Coat each piece in flour, then dip in beaten egg, and finally coat with breadcrumbs. Heat oil in a pan and fry the chicken for about 3-4 minutes on each side, until golden brown and fully cooked. Place on paper towels to drain.
2. Make Curry Sauce: In a pan, sauté the onion, garlic, add potato and carrot until soft. Gradually add curry block and the stock, stir well. Simmer for 5-10 minutes until thickened. Add seasoning and soy sauce to taste.
3. Plating: Slice the cooked chicken katsu and place it over a bed of steamed rice. Pour the curry sauce on the side or over the chicken. Garnish with chopped green chilies.

@ ccc8ee23:9f3d9783

Chef's notes

Enjoy these Chocolate Sprinkle Cookies, a delightful combination of buttery richness, velvety chocolate, and a crunchy sprinkle finish

Details

• ⏲️ Prep time: 10 min
• 🍳 Cook time: 90 min
• 🍽️ Servings: 10

Ingredients

• Plain flour 250 grams
• Margarine 100 grams
• Butter 100 grams
• Vanilla essence 1 tsp
• Milk powder 1 tbsp
• Sugar 40 grams
• Chocolate bar - 80 grams, melted
• Chocolate sprinkles - for decoration

Directions

1. Make the Dough: Combine the plain flour, margarine, butter, milk powder, sugar, and vanilla essence in a mixing bowl. Knead the mixture by hand until smooth and well combined.
2. Shape and divide the dough into small balls, weighing approximately 8 grams each.
3. Preheat the oven to 175°C. Arrange the dough balls on a baking tray and bake for about 30 minutes, or until the cookies are dry and fully cooked.
4. Coat with Chocolate: Melt the chocolate bar using a double boiler or microwave. Once the cookies have cooled completely, dip each cookie into the melted chocolate, ensuring they are evenly coated.
5. Place the coated cookies onto paper cups.
6. While the chocolate coating is still wet, sprinkle chocolate sprinkles on top of each cookie.
7. Allow the chocolate to dry completely, then arrange the cookies in a decorative airtight container for storage.

@ 0463223a:3b14d673

I’m totally wasted! I don’t mean off my head on drugs, I mean absolutely physically and mentally exhausted.

Lugging heavy PA equipment up and down stairs, plus mixing shows is a lot and at my age I’m struggling with it. Yesterday was a write off due to exhaustion. My wife and I went to the cinema, and I slept through the film. A shame, it was something I wanted to see but I was toast. I went to bed at 8pm and slept for over 12 hours. I still feel wrecked today.

Live sound was always a sort of plan B. For a number of years teaching and performing with a band or a DJ was enough to get by on. I was comfortable, financially speaking. That was until about between 2012-14, that’s when we really felt the effects of the post 2008 crash. While a lot of noise was made about the initial event, reality for the likes of me was a slow and steady decline. At that time I was leading workshops with kids with difficult backgrounds, many kids in care due to abuse and neglect. That was a solid 40% of my income, another 30% came from teaching Sound Production at a local university and the final 30% from shows.

2014 cutbacks ripped services to shreds and a few friends lost jobs. Since then, doing live sound kept the rent and bills paid but fast forward to 2025 and I’m way too tired for this shit! I hate admitting it but my earnings probably peaked around 2008 with a bump in tours from 2017 till Covid. Since then earnings have been steady in £'s but getting wiped out by inflation. In fact I had decent acounts this year but every month I'm broke by the time bills and basics have been taken care of. I LOVE mixing live music and I’m pretty good at it. I’ve had musicians call me ‘musical’ which is the highest compliment but I’m totally fucked still 2 days after Friday’s show. It's unsustainable.

I’m quitting live sound unless some touring comes up again, touring is different, living on a bus for 3 weeks pays the same as 3 months of local work and I just mix, no lifting gear. The band I tour with are based in the US and only come to the UK/EU every couple of years. I get odd trips away with other artists but they’re usually fly out EU gigs. 1 or 2 shows then fly home, plus they're irregular.

Right now I’m more interested to learn ways of making income online, I started the Kali Mera Show to learn self hosting content. Committing to a project each morning has done wonders for my mental health, cutting down on morning doom scrolling. It’s been highly successful in that regard but not so much financially. However this is jst phase 1. I’m learning the tech, learning the production and making as many mistakes as possible while the stakes are low. I’m very happy 10 or so people enjoy the show on a daily basis. Tiny numbers but I don’t fuck with YouTube or the other big tech platforms. Fuck them!

Phase 2 involves getting premises and broadening the services I can produce, focussing on content for others, getting some opportunities happening for young talent, arranging meet ups and setting up a hub to bring together the crazy, talented people I know. It’s going to be tough, I’m in a run down area, there’s not much money here (relatively speaking) but it’s an area I really dig and want to make better.

Why am I telling you this? I’m writing this as a means of getting my brain straight and sharing it because I’m open to improving myself. I see people doing interesting shit here and that helps with motivation and confidence. My only social media for the last 6 years has been the Fediverse and much as I love it, there’s a gloomier outlook there. The world is a strange place with so much bad shit but out of 8 or so billion people, I can only take on so much. Building shit in my own local community and provide facilities for online wins sounds way more productive and helpful in some small way.

I accept we’re all going to hell in a handcart but may as well enjoy the ride…

There’s much to learn, I’ve only ever been ‘in business’ for a short time in my life (despite always being freelance) and I sort of gave up on my previous attempt. Had I paid more attention I could’ve built a strong YouTube presence but I’m not into being a vehicle for companies to push their products, nor do I want to teach people music online. That market is now heavily saturated and very, very boring as far as I’m concerned. My heart wasn’t in it, even back in 2015. I’m not an influencer.

With a real life space there’s premises, business rates, and investors to consider, as well as developing services that people are actually happy to part cash with. It’s going to be hard but different hard to physically lifting sub-bass speakers up and down winding staircases! I don’t want to talk too much game, it’s results that matter but wasting days to exhaustion doesn’t help. It’s time to hang up my headphones and focus (FOCUS YOU FUCKING FUCK!).

Maybe you’re reading this and thought ‘shit, this guy’s totally deluded’. That’s cool. Tell me. I value feedback. A fair few cats here give life advice so I’ll assume you might know what you’re talking about...

@ 3bf0c63f:aefa459d

questo.email

This was a thing done in a brief period I liked the idea of "indiewebcamp", a stupid movement of people saying everybody should have their site and post their lives in it.

From the GitHub postmortem:

questo.email was a service that integrated email addresses into the indieweb ecosystem by providing email-to-note and email-to-webmention triggers, which could be used for people to comment through webmention using their email addresses, and be replied, and also for people to send messages from their sites directly to the email addresses of people they knew; Questo also worked as an IndieAuth provider that used people's email addresses and Mozilla Persona.

It was live from December 2014 through December 2015.

Here's how the home page looked:

• https://github.com/fiatjaf/questo.email

See also

• jekmentions, another thing related to "indieweb"

@ ccc8ee23:9f3d9783

Chef's notes

Celebrating seasons🎉

Kastengel Chocolate-Dip, where the savoury richness of cheese meets the decadent sweetness of chocolate. A perfect flavours in every bite!

Details

• ⏲️ Prep time: 10 min
• 🍳 Cook time: 90 min
• 🍽️ Servings: 10

Ingredients

• Plain Flour 250 grams
• Margarine - 100 grams
• Butter 100 grams
• Egg yolk 1 pc
• Sugar 20 grams
• Grated cheese 100 grams (half for the dough, half for garnish, adjustable)
• Chocolate bar 80 grams, melted

Directions

1. Make the Dough: Combine the plain flour, margarine, butter, sugar, and half of the grated cheese in a bowl. Knead the mixture with your hands until smooth and well incorporated. Roll out the dough using a rolling pin and cut into desired shapes for cookies.
2. Beat the egg yolk. Brush the shaped cookies with the egg yolk mixture and sprinkle the remaining grated cheese on top.
3. Bake the cookies 175’C for about 30 minutes, or until they are dry and perfectly cooked.
4. Melt the chocolate bar in a double boiler or microwave until smooth.
5. Dip in Chocolate: Once the cookies have cooled completely, dip both the top and bottom ends of each cookie into the melted chocolate.
6. Place the dipped cookies on a wire rack or a cookie drying tray to allow the chocolate to harden and set.
7. Arrange the cookies neatly in an airtight container.

@ ac8bb9b0:70278acc

Details

• ⏲️ Prep time: 5
• 🍳 Cook time: 10
• 🍽️ Servings: 4

Ingredients

• 1 lb large shrimp, peeled and deveined
• 1 tablespoon extra virgin olive oil
• 3 cloves garlic, chopped
• 1/4 cup white wine, dry
• 14 oz can petite diced tomatoes, drained
• 1/2 cup half and half
• 1/2 teaspoon dried oregano
• kosher salt and fresh black pepper, to taste
• 1 teaspoon lemon juice
• 1/4 cup fresh parsley, chopped
• 8 ounces angel hair pasta, whole wheat, gluten-free or high fiber

Directions

1. Boil water with salt in a large pot for the pasta. Cook pasta al dente according to package directions.
2. Meanwhile, season shrimp with 1/4 teaspoon salt, black pepper and oregano.
3. Heat a large skillet over medium heat. Add the oil, when warm add the shrimp and garlic and cook about 2 minutes on each side.
4. Add tomatoes, wine, salt and pepper and cook an additional minute.
5. Remove from heat and stir in half and half. Add lemon juice and parsley and serve over pasta.
6. Divide equally in 4 plates or shallow bowls.

@ 3bf0c63f:aefa459d

idea: Rumple

a payments network based on trust channels

This is the description of a Lightning-like network that will work only with credit or trust-based channels and exist alongside the normal Lightning Network. I imagine some people will think this is undesirable and at the same time very easy to do (such that if it doesn't exist yet it must be because no one cares), but in fact it is a very desirable thing -- which I hope I can establish below -- and at the same time a very non-trivial problem to solve, as the history of Ryan Fugger's Ripple project and posterior copies of it show.

Read these first to get the full context:

1. Ryan Fugger's Ripple
2. Ripple and the problem of the decentralized commit
3. The Lightning Network solves the problem of the decentralized commit
4. Parallel Chains

Explanation about the name

Since we're copying the fundamental Ripple idea from Ryan Fugger and since the name "Ripple" is now associated with a scam coin called XRP, and since Ryan Fugger has changed the name of his old website "Ripplepay" to "Rumplepay", we will follow his lead here. If "Ripplepay" was the name of a centralized prototype to the open peer-to-peer network "Ripple", now that the centralized version is called "Rumplepay" the peer-to-peer version must be called "Rumple".

Now the idea

Basically we copy the Lightning Network, but without HTLCs or channels being opened and closed with funds committed to them on multisig Bitcoin transactions published to the blockchain. Instead we use pure trust relationships like the original Ripple concept.

And we use the blockchain commit method, but instead of spending an absurd amount of money to use the actual Bitcoin blockchain instead we use a parallel chain.

How exactly -- a protocol proposal attempt

It could work like this:

The parallel chain, or "Rumple Chain"

1. We define a parallel chain with a genesis block;
2. Following blocks must contain a. the ID of the previous block; b. a list of up to 32768 entries of arbitrary 32-byte values; c. an ID constituted by sha256(the previous block ID + the merkle root of all the entries)
3. To be mined, each parallel block must be included in the Bitcoin chain according as explained above.

Now that we have a structure for a simple "blockchain" that is completely useless, just blocks over blocks of meaningless values, we proceed to the next step of assigning meaning to these values.

The off-chain payments network, or "Rumple Network"

1. We create a network of nodes that can talk to each other via TCP messages (all details are the same as the Lightning Network, except where mentioned otherwise);
2. These nodes can create trust channels to each other. These channels are backed by nothing except the willingness of one peer to pay the other what is owed.
3. When Alice creates a trust channel with Bob (Alice trusts Bob), contrary to what happens in the Lightning Network, it's A that can immediately receive payments through that channel, and everything A receives will be an IOU from Bob to Alice. So Alice should never open a channel to Bob unless Alice trusts Bob. But also Alice can choose the amount of trust it has in Bob, she can, for example, open a very small channel with Bob, which means she will only lose a few satoshis if Bob decides to exit scam her. (in the original Ripple examples these channels were always depicted as friend relationships, and they can continue being that, but it's expected -- given the experience of the Lightning Network -- that the bulk of the channels will exist between users and wallet provider nodes that will act as hubs).
4. As Alice receive a payment through her channel with Bob, she becomes a creditor and Bob a debtor, i.e., the balance of the channel moves a little to her side. Now she can use these funds to make payments over that channel (or make a payment that combines funds from multiple channels using MPP).
5. If at any time Alice decides to close her channel with Bob, she can send all the funds she has standing there to somewhere else (for example, another channel she has with someone else, another wallet somewhere else, a shop that is selling some good or service, or a service that will aggregate all funds from all her channels and send a transaction to the Bitcoin chain on her behalf).
6. If at any time Bob leaves the network Alice is entitled by Bob's cryptographic signatures to knock on his door and demand payment, or go to a judge and ask him to force Bob to pay, or share the signatures and commitments online and hurt Bob's reputation with the rest of the network (but yes, none of these things is good enough and if Bob is a very dishonest person none of these things is likely to save Alice's funds).

The payment flow

1. Suppose there exists a route Alice->Bob->Carol and Alice wants to send a payment to Carol.
2. First Alice reads an invoice she received from Carol. The invoice (which can be pretty similar or maybe even the same as BOLT11) contains a payment hash h and information about how to reach Carol's node, optionally an amount. Let's say it's 100 satoshis.
3. Using the routing information she gathered, Alice builds an onion and sends it to Bob, at the same time she offers to Bob a "conditional IOU". That stands for a signed commitment that Alice will owe Bob an 100 satoshis if in the next 50 blocks of the Rumple Chain there appears a block containing the preimage p such that sha256(p) == h.
4. Bob peels the onion and discovers that he must forward that payment to Carol, so he forwards the peeled onion and offers a conditional IOU to Carol with the same h. Bob doesn't know Carol is the final recipient of the payment, it could potentially go on and on.
5. When Carol gets the conditional IOU from Bob, she makes a list of all the nodes who have announced themselves as miners (which is not something I have mentioned before, but nodes that are acting as miners will must announce themselves somehow) and are online and bidding for the next Rumple block. Each of these miners will have previously published a random 32-byte value v they they intend to include in their next block.
6. Carol sends payments through routes to all (or a big number) of these miners, but this time the conditional IOU contains two conditions (values that must appear in a block for the IOU to be valid): p such that sha256(p) == h (the same that featured in the invoice) and v (which must be unique and constant for each miner, something that is easily verifiable by Carol beforehand). Also, instead of these conditions being valid for the next 50 blocks they are valid only for the single next block.
7. Now Carol broadcasts p to the mempool and hopes one of the miners to which she sent conditional payments sees it and, allured by the possibility of cashing in Carol's payment, includes p in the next block. If that does not happen, Carol can try again in the next block.

Why bother with this at all?

1. The biggest advantage of Lightning is its openness

   It has been said multiple times that if trust is involved then we don't need Lightning, we can use Coinbase, or worse, Paypal. This is very wrong. Lightning is good specially because it serves as a bridge between Coinbase, Paypal, other custodial provider and someone running their own node. All these can transact freely across the network and pay each other without worrying about who is in which provider or setup.

   Rumple inherits that openness. In a Rumple Network anyone is free to open new trust channels and immediately route payments to anyone else.

   Also, since Rumple payments are also based on the reveal of a preimage it can do swaps with Lightning inside a payment route from day one (by which I mean one can pay from Rumple to Lightning and vice-versa).

2. Rumple fixes Lightning's fragility

   Lightning is too fragile.

   It's known that Lightning is vulnerable to multiple attacks -- like the flood-and-loot attack, for example, although not an attack that's easy to execute, it's still dangerous even if failed. Given the existence of these attacks, it's important to not ever open channels with random anonymous people. Some degree of trust must exist between peers.

   But one does not even have to consider attacks. The creation of HTLCs is a liability that every node has to do multiple times during its life. Every initiated, received or forwarded payment require adding one HTLC then removing it from the commitment transaction.

   Another issue that makes trust needed between peers is the fact that channels can be closed unilaterally. Although this is a feature, it is also a bug when considering high-fee environments. Imagine you pay $2 in fees to open a channel, your peer may close that unilaterally in the next second and then you have to pay another $15 to close the channel. The opener pays (this is also a feature that can double as a bug by itself). Even if it's not you opening the channel, a peer can open a channel with you, make a payment, then clone the channel, and now you're left with, say, an output of 800 satoshis, which is equal to zero if network fees are high.

   So you should only open channels with people you know and know aren't going to actively try to hack you and people who are not going to close channels and impose unnecessary costs on you. But even considering a fully trusted Lightning Network, even if -- to be extreme -- you only opened channels with yourself, these channels would still be fragile. If some HTLC gets stuck for any reason (peer offline or some weird small incompatibility between node softwares) and you're forced to close the channel because of that, there are the extra costs of sweeping these UTXO outputs plus the total costs of closing and reopening a channel that shouldn't have been closed in the first place. Even if HTLCs don't get stuck, a fee renegotiation event during a mempool spike may cause channels to force-close, become valueless or settle for very high closing fee.

   Some of these issues are mitigated by Eltoo, others by only having channels with people you trust. Others referenced above, plus the the griefing attack and in general the ability of anyone to spam the network for free with payments that can be pending forever or a lot of payments fail repeatedly makes it very fragile.

   Rumple solves most of these problems by not having to touch the blockchain at all. Fee negotiation makes no sense. Opening and closing channels is free. Flood-and-loot is a non-issue. The griefing attack can be still attempted as funds in trust channels must be reserved like on Lightning, but since there should be no theoretical limit to the number of prepared payments a channel can have, the griefing must rely on actual amounts being committed, which prevents large attacks from being performed easily.

3. Rumple fixes Lightning's unsolvable reputation issues

   In the Lightning Conference 2019, Rusty Russell promised there would be pre-payments on Lightning someday, since everybody was aware of potential spam issues and pre-payments would be the way to solve that. Fast-forward to November 2020 and these pre-payments have become an apparently unsolvable problem[^thread-402]: no one knows how to implement them reliably without destroying privacy completely or introducing worse problems.

   Replacing these payments with tables of reputation between peers is also an unsolved problem[^reputation-lightning], for the same reasons explained in the thread above.

4. Rumple solves the hot wallet problem

   Since you don't have to use Bitcoin keys or sign transactions with a Rumple node, only your channel trust is at risk at any time.

5. Rumple ends custodianship

   Since no one is storing other people's funds, a big hub or wallet provider can be used in multiple payment routes, but it cannot be immediately classified as a "custodian". At best, it will be a big debtor.

6. Rumple is fun

   Opening channels with strangers is boring. Opening channels with friends and people you trust even a little makes that relationship grow stronger and the trust be reinforced. (But of course, like it happens in the Lightning Network today, if Rumple is successful the bulk of trust will be from isolated users to big reliable hubs.)

Questions or potential issues

1. So many advantages, yes, but trusted? Custodial? That's easy and stupid!

   Well, an enormous part of the current Lightning Network (and also onchain Bitcoin wallets) already rests on trust, mainly trust between users and custodial wallet providers like ZEBEDEE, Alby, Wallet-of-Satoshi and others. Worse: on the current Lightning Network users not only trust, they also expose their entire transaction history to these providers[^hosted-channels].

   Besides that, as detailed in point 3 of the previous section, there are many unsolvable issues on the Lightning protocol that make each sovereign node dependent on some level of trust in its peers (and the network in general dependent on trusting that no one else will spam it to death).

   So, given the current state of the Lightning Network, to trust peers like Rumple requires is not a giant change -- but it is still a significant change: in Rumple you shouldn't open a large trust channel with someone just because it looks trustworthy, you must personally know that person and only put in what you're willing to lose. In known brands that have reputation to lose you can probably deposit more trust, same for long-term friends, and that's all. Still it is probably good enough, given the existence of MPP payments and the fact that the purpose of Rumple is to be a payments network for day-to-day purchases and not a way to buy real estate.

2. Why would anyone run a node in this parallel chain?

   I don't know. Ideally every server running a Rumple Network node will be running a Bitcoin node and a Rumple chain node. Besides using it to confirm and publish your own Rumple Network transactions it can be set to do BMM mining automatically and maybe earn some small fees comparable to running a Lightning routing node or a JoinMarket yield generator.

   Also it will probably be very lightweight, as pruning is completely free and no verification-since-the-genesis-block will take place.

3. What is the maturity of the debt that exists in the Rumple Network or its legal status?

   By default it is to be understood as being payable on demand for payments occurring inside the network (as credit can be used to forward or initiate payments by the creditor using that channel). But details of settlement outside the network or what happens if one of the peers disappears cannot be enforced or specified by the network.

   Perhaps some standard optional settlement methods (like a Bitcoin address) can be announced and negotiated upon channel creation inside the protocol, but nothing more than that.

[^thread-402]: Read at least the first 10 messages of the thread to see how naïve proposals like you and me could have thought about are brought up and then dismantled very carefully by the group of people most committed to getting Lightning to work properly. [^reputation-lightning]: See also the footnote at Ripple and the problem of the decentralized commit. [^hosted-channels]: Although that second part can be solved by hosted channels.

@ 3bf0c63f:aefa459d

Boardthreads

This was a very badly done service for turning a Trello list into a helpdesk UI.

Surprisingly, it had more paying users than Websites For Trello, which I was working on simultaneously and dedicating much more time to it.

The Neo4j database I used for this was a very poor choice, it was probably the cause of all the bugs.

-https://github.com/fiatjaf/boardthreads

@ ccc8ee23:9f3d9783

Chef's notes

Salmon Mentai Rice. Create your own layers of fluffy, seasoned rice are topped with tender, pan-seared chicken or salmon and a creamy, spicy mentai sauce made with spicy Japanese mayo .

Torched to golden perfection, it’s finished with nori and tobiko for a burst of texture and flavor. A simple tasty Japanese fusion delight that’s perfect🤩

Subtitude of Tobiko, white sesame seeds as economical option will add a nutty flavor and subtle crunch to the dish for texture and visual appeal.

Details

• ⏲️ Prep time: 10 min
• 🍳 Cook time: 30 min
• 🍽️ Servings: 2

Ingredients

• Steamed Rice 400 grams
• Rice vinegar 1 tbsp
• Sugar 1 tsp
• chicken breast / thighs 250 grams
• soy sauce 1 tbsp
• oyster sauce 1 tbsp
• sesame oil 1 tsp
• garlic powder 1 tsp
• cooking oil 1 tbsp
• mayonnaise (e.g., Kewpie) 4 tbsp
• sriracha or any chili sauce 1 tbsp
• tobiko if any or white sesame as optional, for texture, 2 tsp only

Directions

1. Prepared the Rice: mixed in bowl 2 cups steam rice, 1 tbsp rice vinegar, 1 tsp sugar and 1/2 tsp salt. Set a side.
2. Cook the Chicken: 1. Marinate the chicken pieces with 1 tsp soy sauce, 1 tsp oyster sauce, 1 tsp sesame oil, 1 tsp garlic powder for 15–20 minutes. 2. Heat cooking oil in a pan over medium heat and stir-fry the chicken until fully cooked and slightly caramelized. Remove from heat.
3. Make the Mentai Sauce 1. In a small bowl, combine 4 tbsp mayonnaise, 1 tbsp chili sauce, and 1 tsp sesame oil. Add tobiko if desired for texture. Mix well.
4. Assemble the Mentai Rice 1. In a heatproof bowl or tray, layer the seasoned rice as the base. 2. Add a layer of cooked chicken on top of the rice. 3. Spread the mentai sauce evenly over the chicken layer.
5. Grill or Broil: Use a kitchen torch or place the dish under a broiler for 2–3 minutes until the sauce is slightly charred and bubbly.
6. Garnish with white sesame or nori strips, or extra tobiko.

@ 3bf0c63f:aefa459d

bolt12 problems

• clients can't programatically build new offers by changing a path or query params (services like zbd.gg or lnurl-pay.me won't work)
• impossible to use in a load-balanced custodian way -- since offers would have to be pregenerated and tied to a specific lightning node.
• the existence of fiat currency fields makes it so wallets have to fetch exchange rates from somewhere on the internet (or offer a bad user experience), using HTTP which hurts user privacy.
• the vendor field is misleading, can be phished very easily, not as safe as a domain name.
• onion messages are an improvement over fake HTLC-based payments as a way of transmitting data, for sure. but we must decide if they are (i) suitable for transmitting all kinds of data over the internet, a replacement for tor; or (ii) not something that will scale well or on which we can count on for the future. if there was proper incentivization for data transmission it could end up being (i), the holy grail of p2p communication over the internet, but that is a very hard problem to solve and not guaranteed to yield the desired scalability results. since not even hints of attempting to solve that are being made, it's safer to conclude it is (ii).

bolt12 limitations

• not flexible enough. there are some interesting fields defined in the spec, but who gets to add more fields later if necessary? very unclear.
• services can't return any actionable data to the users who paid for something. it's unclear how business can be conducted without an extra communication channel.

bolt12 illusions

• recurring payments is not really solved, it is just a spec that defines intervals. the actual implementation must still be done by each wallet and service. the recurring payment cannot be enforced, the wallet must still initiate the payment. even if the wallet is evil and is willing to initiate a payment without the user knowing it still needs to have funds, channels, be online, connected etc., so it's not as if the services could rely on the payments being delivered in time.
• people seem to think it will enable pushing payments to mobile wallets, which it does not and cannot.
• there is a confusion of contexts: it looks like offers are superior to lnurl-pay, for example, because they don't require domain names. domain names, though, are common and well-established among internet services and stores, because these services have websites, so this is not really an issue. it is an issue, though, for people that want to receive payments in their homes. for these, indeed, bolt12 offers a superior solution -- but at the same time bolt12 seems to be selling itself as a tool for merchants and service providers when it includes and highlights features as recurring payments and refunds.
• the privacy gains for the receiver that are promoted as being part of bolt12 in fact come from a separate proposal, blinded paths, which should work for all normal lightning payments and indeed are a very nice solution. they are (or at least were, and should be) independent from the bolt12 proposal. a separate proposal, which can be (and already is being) used right now, also improves privacy for the receiver very much anway, it's called trampoline routing.

@ d1795b1a:15ab2129

The Ego is an Illusion – and Yet, We Can Shape It

Carl Jung spoke of the Shadow Self—the repressed parts of our psyche that unconsciously influence our lives. Buddhism, on the other hand, teaches that there is no self at all—our ego is an illusion, a fleeting construct that we cling to out of fear of emptiness.

These two perspectives seem to contradict each other. One tells us to integrate our hidden self, the other to dissolve it completely. But what if both are only half the picture?

I believe the Self is neither a fixed reality nor a mere illusion—it is a shapeable construct. If that is true, then the path is not to destroy the Ego-Self or blindly follow it, but to consciously shape it.

Between the Shadow and Emptiness

Our Ego-Self is our conscious identity—our thoughts, memories, and beliefs. Jung describes the Self as the totality of both the conscious and unconscious mind. Hidden in this unconscious space is the Shadow Self, containing everything we deny, suppress, or refuse to acknowledge. For Jung, the path to wholeness is integration—bringing light into the dark corners of the psyche.

Buddhism, however, goes further. It questions whether the Self exists at all. Our thoughts and emotions arise and disappear, our self-image is ever-changing—so why do we cling to something so impermanent?

Both views seem to offer opposite solutions: \ • Jung: Become WHOLE by integrating your Shadow. \ • Buddha: Become FREE by seeing the Self as an illusion.

But what if the synthesis of both is the key?

The Self as a Shapeable Reality

If the Self is not fixed but fluid, then the path forward is neither pure integration nor total dissolution but conscious creation. \ \ • Acknowledge the Shadow Self instead of fighting it. \ • See the Ego-Self not as absolute truth but as a flexible tool. \ • Engage the Solar Plexus—the center of the Unconscious Mind—through breathwork and self-awareness. \ • Use the Vagus Nerve as a bridge between conscious thought and unconscious emotion, actively shaping our beliefs and behaviors.

This aligns with New Thought philosophy, which suggests that our thoughts shape not only our perception but our reality itself. If we embrace this, the question is no longer “Who am I?” but rather: “Who do I want to be—and how can I create that Self?”

The Art of Shaping Yourself

Perhaps the Self is neither a rigid entity nor a complete illusion but a story we tell ourselves—a story we can rewrite. The key is not to destroy the Ego-Self but to use it consciously, rather than being used by it.

So the real question is not: “Does the Self exist?”

But rather: “How aware are we of the fact that we are shaping it every moment?”

@ 3bf0c63f:aefa459d

The Lightning Network solves the problem of the decentralized commit

Before reading this, see Ripple and the problem of the decentralized commit.

The Bitcoin Lightning Network can be thought as a system similar to Ripple: there are conditional IOUs (HTLCs) that are sent in "prepare"-like messages across a route, and a secret p that must travel from the final receiver backwards through the route until it reaches the initial sender and possession of that secret serves to prove the payment as well as to make the IOU hold true.

The difference is that if one of the parties don't send the "acknowledge" in time, the other has a trusted third-party with its own clock (that is the clock that is valid for everybody involved) to complain immediately at the timeout: the Bitcoin blockchain. If C has p and B isn't acknowleding it, C tells the Bitcoin blockchain and it will force the transfer of the amount from B to C.

Differences (or 1 upside and 3 downside)

1. The Lightning Network differs from a "pure" Ripple network in that when we send a "prepare" message on the Lightning Network, unlike on a pure Ripple network we're not just promising we will owe something -- instead we are putting the money on the table already for the other to get if we are not responsive.

2. The feature above removes the trust element from the equation. We can now have relationships with people we don't trust, as the Bitcoin blockchain will serve as an automated escrow for our conditional payments and no one will be harmed. Therefore it is much easier to build networks and route payments if you don't always require trust relationships.

3. However it introduces the cost of the capital. A ton of capital must be made available in channels and locked in HTLCs so payments can be routed. This leads to potential issues like the ones described in https://twitter.com/joostjgr/status/1308414364911841281.

4. Another issue that comes with the necessity of using the Bitcoin blockchain as an arbiter is that it may cost a lot in fees -- much more than the value of the payment that is being disputed -- to enforce it on the blockchain.[^closing-channels-for-nothing]

Solutions

Because the downsides listed above are so real and problematic -- and much more so when attacks from malicious peers are taken into account --, some have argued that the Lightning Network must rely on at least some trust between peers, which partly negate the benefit.

The introduction of purely trust-backend channels is the next step in the reasoning: if we are trusting already, why not make channels that don't touch the blockchain and don't require peers to commit large amounts of capital?

The reason is, again, the ambiguity that comes from the problem of the decentralized commit. Therefore hosted channels can be good when trust is required only from one side, like in the final hops of payments, but they cannot work in the middle of routes without eroding trust relationships between peers (however they can be useful if employed as channels between two nodes ran by the same person).

The next solution is a revamped pure Ripple network, one that solves the problem of the decentralized commit in a different way.

[^closing-channels-for-nothing]: That is even true when, for reasons of the payment being so small that it doesn't even deserve an actual HTLC that can be enforced on the chain (as per the protocol), even then the channel between the two nodes will be closed, only to make it very clear that there was a disagreement. Leaving it online would be harmful as one of the peers could repeat the attack again and again. This is a proof that ambiguity, in case of the pure Ripple network, is a very important issue.

@ fd208ee8:0fd927c1

GitCitadel Development Operations

We, at GitCitadel, have been updating, moving, and rearranging our servers, for quite some time. As a rather large, complex, sprawling project, we have the infrastructure setup to match, so we've decided to give you all a quick run-down of what we are doing behind-the-scenes.

Supplier Coordination

Our first task, this week, was figuring out who would host what where. We have four different locations, where our infra is stored and managed, including two locations from our suppliers. We got that straightened out, quickly, and it's all slowly coming together and being connected and networked. Exciting to watch our DevOps landscape evolve and all of the knowledge-transfer that the interactions provide.

OneDev Implementation

Our biggest internal infra project this week was the migration of all of our issues from Jira, build scripts from Jenkins, and repos from GitHub to a self-hosted OneDev instance. In the future, all of our internal build, test, issue, patch/PR, etc. effort will take place there. We also have a separate repo there for communicating with external developers and suppliers.

Our team's GitHub projects will be demoted to mirrors and a place for external devs to PR to. Public issues and patches will continue to be managed over our self-hosted GitWorkshop instance.

We're especially glad to finally escape the GitHub Gulag, and avoid being bled dry by Jira fees, without having to give up the important features that we've come to know and love. So, yay!

Next Infrasteps

Automated Testing

Now, that we have everything tied up in one, neat, backed-up package, we can finally move on to the nitty-gritty and the dirty work. So, we're rolling up our sleeves and writing the Selenium smoke test for our Alexandria client. We'll be running that in Docker containers containing different "typical Nostr" images, such as Chrome browser with Nostr Connect signing extension, or Firefox browser with Nos2x-fox extension. Once we get the Nsec Bunker and Amber logins going, we'll add test cases and images for them, as well. (Yes, we can do Bunker. I hope you are in awe at our powers).

We are also designing an automated infrastructure test, that will simply rattle through all the various internal and external websites and relays, to make sure that everything is still online and responsive.

After that, a Gherkin-based Behave feature test for Alexandria is planned, so that we can prevent regression of completed functionality, from one release to the next.

The Gherkin scenarios are written and attached to our stories before development begins (we use acceptance tests as requirements), a manual test-execution is then completed, in order to set the story to Done. These completed scenarios will be automated, following each release, with the resulting script linked to from the origin story.

Automated Builds

As the crowning glory of every DevOps tool chain stands the build automation. This is where everything gets tied together, straightened out, configured, tested, measured, and -- if everything passes the quality gates -- released. I don't have to tell you how much time developers spend staring at the build process display, praying that it all goes through and they can celebrate a Green Wave.

We are currently designing the various builds, but the ones we have defined for the Alexandria client will be a continuous delivery pipeline, like so:

This will make it easier for us to work and collaborate asynchronously and without unnecessary delays.

Expanding the Status Page

And, finally, we get to the point of all of this busyness: reporting.

We are going to have beautiful reports, and we are going to post them online, on our status page. We will use bots, to inform Nostriches of the current status of our systems, so go ahead and follow our GitCitadel DevOps npub, to make sure you don't miss out on the IT action.

Building on stone

All in all, we're really happy with the way things are humming along, now, and the steady increase in our productivity, as all the foundational work we've put in starts to pay off. It's getting easier and easier to add new team members, repos, or features/fixes, so we should be able to scale up and out from here. Our GitCitadel is built on a firm foundation.

Happy building!

@ 3bf0c63f:aefa459d

Webvatar

Like Gravatar, but using profile images from websites tagged with "microformats-2" tags, like people from the indiewebcamp movement liked. It falled back to favicon, gravatar and procedural avatar generators.

No one really used this, despite people saying they liked it. Since I was desperate to getting some of my programs appreciated by someone I even bought a domain. It was sad, but an enriching experience.

• https://github.com/fiatjaf/webvatar.com
• http://webvatar.com

See also

• jekmentions
• questo.email

@ 006532cb:fd8f28b4

I am new to #NOSTR and not a #Dev; however, npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn's article inspired me to research and understand further. As a result, I have condensed my learnings into 10 bullet points that seem to embody the spirit of being a nostrich and the qualities we should all strive for when engaging with one another making software choices and avoiding NINO's.

1. You shall not compromise on security: Prioritize the security and integrity of user data, using best practices and Nostr's built-in features to protect against unauthorized access and malicious activity.
2. You shall prioritize user agency: Respect users' mute lists, use their web of trust to filter out spam, and prioritize user control over their data.
3. You shall be decentralized and open: Do not hardcode relay URLs or depend on specific relay implementations, ensuring that your platform is truly decentralized and open.
4. You shall leverage Nostr's technical aspects: Take advantage of Nostr's features, such as self-authenticating data, event handlers, and relays, to build a robust and decentralized platform.
5. You shall use native Nostr solutions: Prefer Nostr-native solutions to solve problems, rather than relying on legacy web services, promoting a more decentralized and resilient ecosystem.
6. You shall prioritize interoperability: Implement NIP 89 (Recommended Application Handlers) to enable seamless interactions with other Nostr apps, promoting a unified and decentralized ecosystem.
7. You shall engage with the community: Share knowledge, contribute to the growth of the ecosystem, and collaborate with other Nostr developers to promote a unified and thriving community.
8. You shall be transparent and accountable: Be transparent in your development processes, and accountable for your actions and decisions, promoting trust and confidence in the Nostr ecosystem.
9. You shall innovate and evolve: Continuously innovate and improve your platform, staying up-to-date with the latest developments in the Nostr protocol and ecosystem, to ensure the best possible experience for users.
10. Embody Nostr: Your application should truly represent the Nostr protocol, using its features and network to provide unique value to users.

I am excited for the future. In Eric S. Raymond's book "The Cathedral and the Bazaar" he comments;

"...and the robust doesn't care too much"

Nostr embodies the spirit of the Bazaar, a vibrant and eclectic marketplace where the robust thrive, all are welcomed and empowered to become strong.

/GN!

@ da0b9bc3:4e30a4a9

Hello Stackers!

Welcome on into the ~Music Corner of the Saloon!

A place where we Talk Music. Share Tracks. Zap Sats.

So stay a while and listen.

🚨Don't forget to check out the pinned items in the territory homepage! You can always find the latest weeklies there!🚨

🚨Subscribe to the territory to ensure you never miss a post! 🚨

originally posted at https://stacker.news/items/873174

@ ccc8ee23:9f3d9783

Chef's notes

Dare to taste the bold? One bite of Jengkol Balado and you’ll be hooked

Spicy Jengkol Balado - Betawi Style A traditional dish from Betawi (Jakarta), Jengkol Balado is nutty bold and aromatic delicacy made with jengkol beans. This version uses thinly sliced jengkol for a delightful texture.

Serve it with a plate of steamed fragrant white rice and a side of crunchy cucumber for a complete meal that satisfies on every level.

Details

• 🍳 Cook time: 40 min
• 🍽️ Servings: 2

Ingredients

• Jengkol 250 grams
• Chilli 100 grams
• Shallot 5 cloves
• Garlic 2 cloves
• Tomato 1 clove (small)
• Bay leaves 2
• Galangal 2cm. Bruished
• Veggie oil 20ml or 4 tsp
• Seasoning

Directions

1. Prepare the Jengkol Wash the jengkol thoroughly and slice it thinly. Boil the slices in water with the bay leaves for 10–15 minutes to soften and reduce their strong odour. Drain and set aside.
2. Make the Balado Paste. Blend chillies, shallots, garlic, candlenut and tomatoes into a slightly coarse paste using a blender
3. Heat oil in a pan and sauté the balado paste until fragrant and the oil starts to separate. Add the galangal, bay leaves, salt, sugar, and seasoning. Stir well
4. Add jengkol to the pan. Mix until jengkol are fully coated in the balado paste.
5. If the mixture seems too dry, add a splash of water and let it simmer on low heat to allow the flavours to infuse.
6. Taste the dish and adjust the seasoning with more salt or sugar if needed.
7. Remove from heat and serve hot with steamed rice.

@ 57d1a264:69f1fee1

Hey there, as a result of the recent SN Media Kit updated, I'll try to create few simple marketing assets for ~Stackers_Stocks territory to be spread across the web.

Feel free to share in the comments below: - Few visual references you'd like the assets to be inspired on - If visuals are not your thing, a description of your idea will help too - A slogan, or some words/concepts that express the territory's values

@BlokchainB you start, let's see how we go!

originally posted at https://stacker.news/items/873112

@ 3bf0c63f:aefa459d

Eltoo

Read the paper, it's actually nice and small. You can read only everything up to section 4.2 and it will be enough. Done.

Ok, you don't want to. Or you tried but still want to read here.

Eltoo is a way of keeping payment channel state that works better than the original scheme used in Lightning. Since Lightning is a bunch of different protocols glued together, it can It replace just the part the previously dealed with keeping the payment channel.

Eltoo works like this: A and B want a payment channel, so they create a multisig transaction with deposits from both -- or from just one, doesn't matter. That transaction is only spendable if both cooperate. So if one of them is unresponsive or non-cooperative the other must have a way to get his funds back, so they also create an update transaction but don't publish it to the blockchain. That update transaction spends to a settlement transaction that then distributes the money back to A and B as their balances say.

If they are cooperative they can change the balances of the channel by just creating new update transactions and settlement transactions and number them like 1, 2, 3, 4 etc.

Solid arrows means a transaction is presigned to spend only that previous other transaction; dotted arrows mean it's a floating transaction that can spend any of the previous.

Why do they need and update and a settlement transaction?

Because if B publishes update2 (in which his balances were greater) A needs some time to publish update4 (the latest, which holds correct state of balances).

Each update transaction can be spent by any newer update transaction immediately or by its own specific settlement transaction only after some time -- or some blocks.

Hopefully you got that.

How do they close the channel?

If they're cooperative they can just agree to spend the funding transaction, that first multisig transaction I mentioned, to whatever destinations they want. If one party isn't cooperating the other can just publish the latest update transaction, wait a while, then publish its settlement transaction.

How is this better than the previous way of keeping channel states?

Eltoo is better because nodes only have to keep the last set of update and settlement transactions. Before they had to keep all intermediate state updates.

If it is so better why didn't they do it first?

Because they didn't have the idea. And also because they needed an update to the Bitcoin protocol that allowed the presigned update transactions to spend any of the previous update transactions. This protocol update is called SIGHASH_NOINPUT[^anyprevout], you've seen this name out there. By marking a transaction with SIGHASH_NOINPUT it enters a mystical state and becomes a floating transaction that can be bound to any other transaction as long as its unlocking script matches the locking script.

Why can't update2 bind itself to update4 and spend that?

Good question. It can. But then it can't anymore, because Eltoo uses OP_CHECKLOCKTIMEVERIFY to ensure that doesn't actually check not a locktime, but a sequence. It's all arcane stuff.

And then Eltoo update transactions are numbered and their lock/unlock scripts will only match if a transaction is being spent by another one that's greater than it.

Do Eltoo channels expire?

No.

What is that "on-chain protocol" they talk about in the paper?

That's just an example to guide you through how the off-chain protocol works. Read carefully or don't read it at all. The off-chain mechanics is different from the on-chain mechanics. Repeating: the on-chain protocol is useless in the real world, it's just a didactic tool.

[^anyprevout]: Later SIGHASH_NOINPUT was modified to fit better with Taproot and Schnorr signatures and renamed to SIGHASH_ANYPREVOUT.

@ 57d1a264:69f1fee1

Hey there, as a result of the recent SN Media Kit updated, I'll try to create few simple marketing assets for ~Construction_and_Engineering territory to be spread across the web.

Feel free to share in the comments below: - Few visual references you'd like the assets to be inspired on - If visuals are not your thing, a description of your idea will help too - A slogan, or some words/concepts that express the territory's values

@BlokchainB you start, let's see how we go!

originally posted at https://stacker.news/items/873104

@ 3bf0c63f:aefa459d

idea: Hosted-channels Lightning wallet that runs in the browser

Communicates over HTTP with a server that is actually connected to the Lightning Network, but generates preimages and onions locally, doing everything like the Hosted Channels protocol says. Just the communication method changes.

Could use this library: https://www.npmjs.com/package/bolt04

@ ac8bb9b0:70278acc

Details

• ⏲️ Prep time: 10
• 🍳 Cook time: 20
• 🍽️ Servings: 5

Ingredients

• 8 ounces uncooked linguine
• 1 pound chicken breast, cut into strips
• 1-2 tsp Cajun seasoning, or more to taste
• 1 tsp garlic powder
• 1 tbsp extra virgin olive oil
• 1 medium red bell pepper, thinly sliced
• 1 medium yellow bell pepper, thinly sliced
• 8 oz fresh mushrooms, sliced
• 1/2 red onion, sliced
• 3 cloves garlic, minced
• 2 tomatoes, diced
• 1 cup low sodium chicken broth
• 1/3 cup skim milk
• 1 tbsp flour
• 3 tbsp light cream cheese
• fresh cracked pepper
• 2 scallions, chopped
• kosher salt to taste
• avocado oil spray

Directions

1. Prep all your vegetables.
2. In a small blender make a slurry by combining milk, flour and cream cheese. Set aside.
3. Season chicken generously with Cajun seasoning, garlic powder and salt.
4. Prepare pasta in salted water according to package directions.
5. Heat a large heavy nonstick skillet over medium-high heat; spray with oil and add half of the chicken.
6. Sauté 5 to 6 minutes or until done, set aside on a plate and repeat with the remaining chicken. Set aside.
7. Add olive oil to the skillet and reduce to medium; add bell peppers, onions, and garlic to skillet, sauté 3-4 minutes.
8. Add mushrooms and tomatoes and sauté 3-4 more minutes or until vegetables are tender.
9. Season with 1/4 tsp salt, garlic powder and fresh cracked pepper to taste.
10. Reduce heat to medium-low; add chicken broth and pour in slurry stirring about 2 minutes.
11. Return chicken to skillet; adjust salt and Cajun seasoning to taste, cook another minute or two until hot, then add linguine; toss well to coat.
12. Top with chopped scallions and enjoy!

@ 3bf0c63f:aefa459d

The problem with ION

ION is a DID method based on a thing called "Sidetree".

I can't say for sure what is the problem with ION, because I don't understand the design, even though I have read all I could and asked everybody I knew. All available information only touches on the high-level aspects of it (and of course its amazing wonders) and no one has ever bothered to explain the details. I've also asked the main designer of the protocol, Daniel Buchner, but he may have thought I was trolling him on Twitter and refused to answer, instead pointing me to an incomplete spec on the Decentralized Identity Foundation website that I had already read before. I even tried to join the DIF as a member so I could join their closed community calls and hear what they say, maybe eventually ask a question, so I could understand it, but my entrance was ignored, then after many months and a nudge from another member I was told I had to do a KYC process to be admitted, which I refused.

One thing I know is:

• ION is supposed to provide a way to rotate keys seamlessly and automatically without losing the main identity (and the ION proponents also claim there are no "master" keys because these can also be rotated).
• ION is also not a blockchain, i.e. it doesn't have a deterministic consensus mechanism and it is decentralized, i.e. anyone can publish data to it, doesn't have to be a single central server, there may be holes in the available data and the protocol doesn't treat that as a problem.
• From all we know about years of attempts to scale Bitcoins and develop offchain protocols it is clear that you can't solve the double-spend problem without a central authority or a kind of blockchain (i.e. a decentralized system with deterministic consensus).
• Rotating keys also suffer from the double-spend problem: whenever you rotate a key it is as if it was "spent", you aren't supposed to be able to use it again.

The logic conclusion of the 4 assumptions above is that ION is flawed: it can't provide the key rotation it says it can if it is not a blockchain.

See also

• Excerpt of discussion about DIDs and ION

@ 3b7fc823:e194354f

Why Privacy Matters and How to Protect It

Privacy is about control. It’s not about hiding yourself but deciding what others can see about you. Just as you don’t share everything when buying a magazine, technology shouldn’t force you to reveal more than needed.

Why Privacy is Important

1. Personal Control: Privacy lets you choose what parts of your life are visible. You shouldn’t have to share everything just to use a service.

2. Security Against Exploitation: Without privacy, people and groups can be targeted by companies or governments. This abuse can lead to data breaches or unnecessary surveillance.

3. Building Trust: Privacy is key to trust in relationships and communities. When your info is safe, you can transact and communicate without fear of misuse.

How to Protect Your Privacy 1. Think Before You Share: Only share what’s necessary and know why you’re doing it. 2. Use Encryption: Encrypt sensitive communications like emails or messages. 3. Control Data Sharing: Avoid oversharing personal details online. 4. Enable Privacy Tools: Use VPNs or privacy settings on social media to shield your data. 5. Be Mindful of Metadata: Understand that metadata (like location data) can reveal more about you than the content itself. 6. Support Privacy-Focused Brands: Choose services that prioritize privacy, like encrypted messaging apps. 7. Read Privacy Policies: Know what data you’re sharing and with whom. 8. Tools like privacy.io can help visualize your digital footprint. 9. Block Trackers: Use tools like DoNotTrackMe or uBlock Origin to stop trackers from collecting your data.

Conclusion

Protecting privacy is a vital step in safeguarding your personal freedoms. By taking proactive measures, you can control what information is accessible and ensure that your rights are respected. Remember, you are your own best advocate for privacy—trust no one but yourself to protect your data and identity.

Join the movement to champion privacy as a fundamental human right. Advocate for stronger laws and encourage others to take action, so we can all enjoy safer, more secure digital environments.

@ ac8bb9b0:70278acc

Details

• ⏲️ Prep time: 10
• 🍳 Cook time: 20
• 🍽️ Servings: 6

Ingredients

• 2 tablespoons extra virgin olive oil
• 1 1/2 pounds ground chicken
• 1 yellow onion, chopped
• 2 tablespoons taco seasoning
• salt and black pepper
• 2 1/2 cups salsa or enchilada sauce
• 1 chipotle chili in adobo, chopped
• 2 cups fresh corn
• 4 ounces cream cheese, at room temperature
• 1/4 cup plain greek yogurt
• 1 teaspoon chili powder
• 1 1/2 cups shredded Mexican cheese blend
• 2 cups tortilla chips
• avocado, cilantro, and green onions, for serving

Directions

1. Preheat the oven to 400° F.
2. In a large oven-safe skillet, combine the olive oil, chicken, onion, salt, and pepper. Set the skillet over high heat. Cook, breaking up the meat as it cooks, until browned all over, 5 minutes. Add the taco seasoning, cook another 2 minutes. Then add 1/2 cup water. Stir in the salsa/enchilada sauce and chipotle. Simmer 5 minutes. Remove from the heat and add in the cilantro.
3. In a bowl, combine the corn, cream cheese, yogurt, chili powder, and salt. Stir in 1/2 cup cheese.
4. Dollop 1/3 of the corn mix over the skillet. Add the tortilla chips on top, pressing them gently into the skillet. Add the remaining corn mix by spoonfuls on top of the chips (like nachos). Top with the remaining cheese. Bake for 15 minutes, until the cheese is melted.
5. Serve topped as desired with avocado, cilantro, green onion, and cotija/feta cheese.

@ 07804b78:c375c543

Japanese follows. 日本語はあとで。

This article is for the 14th day of Nostr Advent Calendar 2024 (relay blogging). The article for the 13th day was "Open Sats 申請編" (Applying for Open Sats) by mono-san. The article for the 14th day will be "Nostrはじめました。" (I started Nostr) by bro-san.

Thinking of Thingstr

I've come up with an idea for Other Staff that I think is interesting (at least, for me), so I'm going to write about it. I actually wanted to show you the implementation and brag about it, but it's not solid enough to be implemented yet.

The key idea is just “add a reaction to the WikiData ID”.

WikiData

There is a service called WikiData. It is a knowledge base that provides structured data. You may be wondering what it is, but the important thing to understand here is that WikiData assigns identifiers to a fairly wide range of “objects” and “things”.

So, if you can react to this, you can think of various applications just by thinking of it for a moment, right?

For example, the anime series “There are too many losing heroines!” is assigned the ID Q123819103. The corresponding page is https://www.wikidata.org/wiki/Q123819103 .

(NOTE: The canonical URI for entities on Wikidata is http://www.wikidata.org/entity/Q1142841. This is in accordance with Semantic Web conventions, and is not https, but http. Also, this URI does not necessarily match the actual address of the correspnding web page. Just an identifier. In most cases, it will redirect).

What can wd do?

For example, what about a website that records your anime viewing history? You can record what you want to watch with 👀, what you've already watched with ✅, and your favorites with ☆. You can also express your “likes” for production companies, staff, voice actors, etc. In this way, you can see what a particular user likes.

This could be a movie, a book, a comic, an author, music, an idol group, a place, or food (Someone likes pork cutlet Q1142841). The fact that you can record everything in the same framework is what makes it interesting.

What form of event should it be recorded as?

There is probably room for discussion about how to record this information in a concrete way. The simplest way would be to use NIP-25's "Reactions to a website" kind:17 (a.k.a. Makibishi). How about something like this?

json [ ["i", "wd:Q123819103", "http://www.wikidata.org/entity/Q123819103"], ]

Since NIP-73 has External Content IDs, it would be good if we could include WikiData here so that we could write wd:Q123819103. Actually, isbn: and other identifiers have already been defined, so it is possible to use the current NIP range to describe books (however, the authors do not have IDs. If we use WikiData as an ID, we can also describe reactions related to the author). Of course, it is not a matter of choosing one or the other, and it is also fine to add the ISBN tag at the same time as the WikiData tag for books.

Search for recorded reactions

So far, this is all very simple, but it would be inconvenient if we didn't include tags to mark subsets of reactions (for example, only those related to anime) so that we can query them together. When we try to create a site that is specialized for a certain purpose, we need to be able to extract the reactions that are necessary.

On Wikidata, the predicate wdt:P31 (instance of) is used to group together concepts that represent the same thing. For example, how about including this in the l tag? "There are too many losing heroines!" is a "Japanese television anime series (Q63952888)", so:

json [ ["i", "wd:Q1142841", "http://www.wikidata.org/entity/Q1142841"], ["l", "wdt:P31 wd:Q63952888"] ]

UPDATE(2024-12-15): rnurachue-san suggested that #l or #L might be better for labeling (the first version used #a). I think that's a good idea, so I've updated the article. nostr:nevent1qgswamu0rsela0kwhj87p24ueapxdp04vzz7ar0pp6lfyq923t3l02cqyr9786635s60ra0f973nwv2sln2l74lqx4twdlgxfz2jgevpvsgtc9zwn6d

However, when you think about creating an anime website, you may want to query both TV anime and anime films. This makes things more complicated. "Japanese TV anime series (Q63952888)" is a subclass (subclass of; wdt:P279) of "Anime series (Q117467261)", which is in turn a subclass of "Anime (Q1107)". However, if you were to embed this hierarchy in each reaction, it would waste a lot of space. The following query will get all the superclasses of "Japanese TV anime series (Q63952888)", but there are 54 of them.

https://query.wikidata.org/#%23%20Subclass%20hierarchy%20traversal%20for%20Q63952888%0ASELECT%20%3Fitem%20%3FitemLabel%20%3Fsuperclass%20%3FsuperclassLabel%0AWHERE%20%7B%0A%20%20%23%20Starting%20class%0A%20%20wd%3AQ63952888%20wdt%3AP279%2a%20%3Fsuperclass%20.%0A%20%20BIND%28wd%3AQ63952888%20AS%20%3Fitem%29%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D%0AORDER%20BY%20%3Fsuperclass%0A

So, I think it should be okay for practical purposes to embed P31s of the reaction target. In other words, if you search for "anime series Q63952888" and "anime movie Q20650540", that should be enough. Fortunately, the conditions for single-character tags work with OR, so you can query multiple tags at once. we'll have to try it to see how well it works in practice, though.

Discussion: Which kind should I use?

So far we have considered using kind:17, but we have not yet decided whether it is a good idea to mix Thingstr events with reactions to web pages.

Also, there may be a debate over whether to record regular events or addressable events, depending on the purpose of use. For example, if you want to record the transition of viewing results and impressions on an anime viewing site, you should use regular events, and if you want to maintain the viewing status, you should use addressable events.

What do you think?

Other ideas

If we can react to Nodes on OpenStreetMap using the same framework, we might be able to create something like Swarm. Since the views you want to see will differ depending on the purpose, it would be good to create various sites while having a consistent way of recording. Wouldn't that be the most Nostr-like thing?

Summary

I discussed how to use WikiData and OpenStreetMap as an ID infrastructure and realize various check-in and review services with a unified data model by using them on Nostr. Please let us know if you have any feedback. Or why not try implementing it?

---

この記事は Nostr Advent Calendar 2024 の14日目の記事です。13日目の記事はmonoさんによる「Open Sats 申請編」でした。15日目の記事はbroさんによる「Nostrはじめました。」です。

Thingstrについて考えた

面白そうな（と勝手に思ってる） Other Staff のアイディアを思いついたので、書いてみます。 本当は実装を持ってきて自慢したかったのですが、まだふわっとしていて実装に落ちていません。

コアになるアイディアは「WikiData の ID に対して、Reactionをつける」これだけです。

WikiData

WikiData というサービスがあります。構造化データを提供する知識ベースです。 なにそれ？という感じですが、ここで大事なのはWikiDataはかなり広範な「もの」「こと」に識別子(Identifier)を付与している、ということです。

だから、これにリアクションできれば、ぱっと思いつくだけでもいろいろな応用ができそうじゃないですか。

例えば、アニメシリーズ「負けヒロインが多すぎる！」には Q123819103 というIDが振られています。これに対応するページとして https://www.wikidata.org/wiki/Q123819103 があります。

（ただし、WikiData のエンティティに対する canonical な URI は http://www.wikidata.org/entity/Q1142841 であることには注意が必要です。セマンティックウェブの作法で https ではなく http になっています。そして、このURIは必ずしもWebページのアドレス一致しません。大抵の場合はリダイレクトされます）。

なにができるの

たとえば、アニメの視聴記録サイトはどうでしょう。👀は見たい作品、✅は視聴済み、☆はお気に入り、みたいに記録していく。制作会社、スタッフ、声優、...に対してLikeを表明したりできそうです。そうすると、あるユーザが何にLikeしているかわかります。

これが映画でもいいし、書籍、漫画、作家でもいいし、音楽でもいいし、アイドルグループでもいいし、場所でもいいし、食べ物でもいい（とんかつ Q1142841 が好き、とか）。全部同じ枠組みで記録できるのが面白そうなところです。

どういうNostrイベントで記録する？

具体的な記録の仕方には議論の余地があるでしょう。一番単純なのは、NIP-25の "Reactions to a website" kind:17 (Makibishi) を使う方法でしょうか。こんなのはどうでしょう。

json [ ["i", "wd:Q123819103", "http://www.wikidata.org/entity/Q123819103"], ]

NIP-73にExternal Content IDsがあるので、ここにWikiDataを入れられるようにして wd:Q123819103 と書けるとよさそうです。実は isbn: などはすでに定義されているので、書籍に関しては現行のNIPの範囲でもうまいことできます（ただ、著者にはIDが振られていません。WikiDataをIDに使うと著者に関するリアクションも記述できます）。もちろん、どちらか一方を選ぶというものでもなくて、書籍にはWikiDataのタグと当時にISBNのタグを付与しておいてもいいと思います。

記録されたリアクションを検索する

ここまではシンプルでよいのですが、リアクションの部分集合（たとえばアニメに関連するものだけ、とか）をまとめてクエリできるように、目印となるタグを入れておかないと不便です。ある目的に特化したサイトを作ろうとしたとき、必要になるリアクションが抽出できるようにしておかないといけません。

WikiData では wdt:P31 (instance of) という述語で、ある概念が何を表しているかをグルーピングしてくれています。例えばこれをlタグとかに含めておくのはどうでしょうか。

負けヒロインが多すぎる！は「日本のテレビアニメシリーズ(Q63952888)」なので、

json [ ["i", "wd:Q1142841", "http://www.wikidata.org/entity/Q1142841"], ["l", "wdt:P31 wd:Q63952888"] ]

みたいな感じで付与します。

UPDATE(2024-12-15): rnurachueさんからラベル付けには #l または #L のほうがよいかもという提案をいただきました。最初のバージョンでは #a を使用していました。そのとおりだと思ったので更新しました。 nostr:nevent1qgswamu0rsela0kwhj87p24ueapxdp04vzz7ar0pp6lfyq923t3l02cqyr9786635s60ra0f973nwv2sln2l74lqx4twdlgxfz2jgevpvsgtc9zwn6d

ただ、アニメサイトを作ることを考えると、テレビアニメも劇場版アニメも両方クエリしたいこともありそうですよね。そうなると話が複雑になってきます。

「日本のテレビアニメシリーズ(Q63952888)」は「アニメシリーズ(Q117467261)」のサブクラス(subclass of; wdt:P279)で、それがさらに「アニメ(Q1107)」 のサブクラスになっています。ただ、この階層をいちいちリアクションに埋め込むのと大変なことになります。以下のようなクエリで「日本のテレビアニメシリーズ(Q63952888)」のすべての上位クラスが取れるのですが、54件もあります。

https://query.wikidata.org/#%23%20Subclass%20hierarchy%20traversal%20for%20Q63952888%0ASELECT%20%3Fitem%20%3FitemLabel%20%3Fsuperclass%20%3FsuperclassLabel%0AWHERE%20%7B%0A%20%20%23%20Starting%20class%0A%20%20wd%3AQ63952888%20wdt%3AP279%2a%20%3Fsuperclass%20.%0A%20%20BIND%28wd%3AQ63952888%20AS%20%3Fitem%29%0A%20%20SERVICE%20wikibase%3Alabel%20%7B%20bd%3AserviceParam%20wikibase%3Alanguage%20%22%5BAUTO_LANGUAGE%5D%2Cen%22.%20%7D%0A%7D%0AORDER%20BY%20%3Fsuperclass%0A

なので、リアクション対象のP31を埋め込む、くらいで実用上は問題ないような気がします。つまり、検索するときに 「アニメシリーズ Q63952888」と「アニメ映画 Q20650540」を対象にすれば、十分では、ということです。幸い、一文字タグの条件はORで効くので、複数を並べて一度にクエリできます。実際にどのくらいうまく行くかはやってみないとわからないですが。

議論: どの kind を使うべきか？

一旦 kind 17 を使うことを考えてきましたが、Thingstr のイベントが Web ページに対するリアクションと混ざるのが良いことなのか、いまいち判断がついていません。

また、用途によって regular event で記録するべきか、それとも addressable event で記録すべきか、という議論もありそうです。 アニメ視聴サイトを例にあげるなら、視聴実績とか感想の変遷を記録したいならば regular event でしょうし、視聴の状態を保持したいならば addressable とするのがよさそうです。

どう思いますか？

他のアイディア

これと同じ枠組みで OpenStreetMap の Node に対してリアクションできるようにすれば Swarm のようなものも実現できるかもしれません。

用途ごとに見たいビューは違うだろうから、一貫した記録の仕方を持ちつつ、色々なサイトを作ったらいいんじゃないでしょうか。それって最高にNostrっぽくないですか？

まとめ

WikiDataやOpenStreetMapをID基盤として活用し、Nostr上でreactすることで、様々なチェックインサービス、レビューサービスを統一的なデータモデルで実現する方法について議論しました。フィードバックがあったら教えてください。むしろ実装してみてください。

@ 57d1a264:69f1fee1

Welcome to the latest updated version of Stacker News Media Kit & Brand Guidelines v1.2, a pivotal location where all the visual elements find place and help us understand how to use them to have our communications cohesive. SN brand identity is built on simplicity, trust, innovation and a taste of Texas's Wild West. With the following guidelines, as promised, I'll try to outline the essential elements of SN visual language to be easily usable internally and externally.

As third interaction from the previous discussion, here below you will find all the media assets in PNG and SVG downloadable from this zip file. BTW: I've been using Nostr 🌸 Blossom Serverservers check them out, it's a really cool idea! In case the file will be not available we can always upload it in other servers. Just let me know if any issue downloading it, ideally I made three copies available from: - https://nosto.re/0a8b02224c970de78fba3a0195dcf1ee44d18925ba941724497173b2bcbab901.zip - https://blossom.poster.place/0a8b02224c970de78fba3a0195dcf1ee44d18925ba941724497173b2bcbab901.zip - https://nostr.download/0a8b02224c970de78fba3a0195dcf1ee44d18925ba941724497173b2bcbab901.zip

The source file of all these assets still are the same Figma file and the PenPot file. This last one, has many issues and does not allow yet the same flexibility as Figma. Both files are open for contributions and comments, just need to register a dummy/anonymous account for each of the tools.

Note: To use these assets across SN, just copy-paste the image relative code, i.e.:

Stacker News Logotype

SN logo is the most recognizable visual identifier of Stacker News. It captures the essence of its brand and is to be used across the platform and other marketing materials consistently. Find below all the possible variations and colors. Ideally you should stick with it to maintain SN identity coherent, or propose something new if you feel like. If you have any question on how to place or use the logo, DO ask below, and we'll help sort it out.

| Avatar on transparent BG | Avatar on BG | Logo Extended | Logo Vertical |#| |---|---|---|---|---| | ![](https://m.stacker.news/75562) | ![](https://m.stacker.news/75552) | ![](https://m.stacker.news/75555)| ![](https://m.stacker.news/75566) |Oil Black| | ![](https://m.stacker.news/75564) | ![](https://m.stacker.news/75554) | ![](https://m.stacker.news/75557) | ![](https://m.stacker.news/75567)| Golden Yellow | | ![](https://m.stacker.news/75563) | ![](https://m.stacker.news/75553) | ![](https://m.stacker.news/75565) | ![](https://m.stacker.news/75568)|With Shadow |

Stacker News Typography

This is the typography SN had used to create its logo. Download LightningVolt OpenType Font file.otf designed by Honey&Death, install it in your computer and play with it.

Typography is essential to identify, increase readability and create consistency of brands. SN uses the default font-family:sans-serif; of your device's OS, usually are the most common and already installed in your device: system-ui, "Segoe UI", Roboto, "Helvetica Neue", "Noto Sans", "Liberation Sans", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol", "Noto Color Emoji". Those are mostly used for:

Example Header H1

Example Header H2

Example Header H3

Example Header H4

Example Header H5

Example paragraph text The fonts selected will help to communicate the personality of the brand and provide maximum legibility for both print and screen.

Example <code> For code, the approach is the same. Let's the device OS select its default monospace one. For example, on Mac will be one of the following: SFMono-Regular, Menlo, Monaco, Consolas, "Liberation Mono", "Courier New",`

Stacker News Colors

A thoughtfully curated color palette gives SN trust, professionalism, and approachability. Colors play a key role in creating consistent visual experiences through digital and print communications. Make sure you are using the right color codes below:

| # | Name | HEX code | RGB code | HLS | |---|---|---|---|---| | | Bitcoin-only | #F6911D | rgb(246,145,29) | hsl(32,92.3%,53.9%) | | | Blackr | #000000 | rgb(0,0,0) | hsl(0,0%,0%) | | | Dark | #121214 | rgb(18,18,20) | hsl(240,5.3%,7.5%) | | | Gold | #FADA5E | rgb(250,218,94) | hsl(48,94%,67.5%) | | | Gray | #969696 | rgb(150,150,150) | hsl(0,0%,58.8%) | | | Light | #F0F0F0 | rgb(240,240,240) | hsl(0,0%,94.1%) | | | Nostrch | #8C25F4 | rgb(140,37,244) | hsl(270,90.4%,55.1%) | | | Pinkish | #E685B5 | rgb(230,133,181) | hsl(330,66%,71.2%) | | | Ruby | #C03221 | rgb(192,50,33) | hsl(6,70.7%,44.1%) | | | Sky Hover | #007CBE | rgb(0,124,190) | hsl(201,100%,37.3%) | | | Sky Links | #2E99D1 | rgb(46,153,209) | hsl(201,63.9%,50%) | | | Sky Visited | #56798E | rgb(86,121,142) | hsl(203,24.6%,44.7%) | | | So Fiat | #5C8001 | rgb(92,128,1) | hsl(77,98.4%,25.3%) |

Stacker News Icons

SN utilizes a set of bespoke icons that support its communication internally across the platform. Icons help bring instant, intuitive cues for various types of content and features. We share them here for you so you can use as you wish and satisfy your creative needs.

| ![Arrow](https://m.stacker.news/75605) | ![Bell](https://m.stacker.news/75606) | [Bounty](https://m.stacker.news/75607) | [Caret](https://m.stacker.news/75608) | [Cowboy](https://m.stacker.news/75609) | [Sun](https://m.stacker.news/75610) | |---|---|---|---|---|---| | [Edit](https://m.stacker.news/75611) | [Gun](https://m.stacker.news/75612) | [Horse](https://m.stacker.news/75613) | [Info](https://m.stacker.news/75614) | [Moon](https://m.stacker.news/75615) | [Lightning](https://m.stacker.news/75616)| | [Bald Lost Hat](https://m.stacker.news/75617)| [Markdown](https://m.stacker.news/75618)| [Nostr](https://m.stacker.news/75619)| [Referral](https://m.stacker.news/75620)| [Rewards](https://m.stacker.news/75621)| [Horse Lost Saddle](https://m.stacker.news/75622)| [Search](https://m.stacker.news/75623) | | [Shoot](https://m.stacker.news/75624) | [Texas](https://m.stacker.news/75625) | [Upload](https://m.stacker.news/75626) | [Zap Zap](https://m.stacker.news/75627) |||

Stacker News Banners

Banners are important visual elements used in our digital platforms and marketing materials. They help to highlight key stories, features or announcements while maintaining our brand aesthetic.

Here below you'll find custom banners for Sn and for individial territories. I try to build those that I follow most, for now @AGORA is the only one that designed its own banners. Comment below if you'd like some banners for your territory!

SN Dark background

|970x250| |---| | ![](https://m.stacker.news/75654 |

|250x250|300x250|300x600| |---|---|---| |![](https://m.stacker.news/75656)|![](https://m.stacker.news/75657)|![](https://m.stacker.news/75658)|

|728x90| |---| | ![](https://m.stacker.news/75655) |

SN Gold background

|970x250| |---| |![](https://m.stacker.news/75641) |

|250x250|300x250|300x600| |---|---|---| |![](https://m.stacker.news/75645) | ![](https://m.stacker.news/75646) |![](https://m.stacker.news/75647) |

|728x90| |---| |![](https://m.stacker.news/75648) |

SN by @Jon_Hodl

|970x250| |---| | ![](https://m.stacker.news/75649) |

|250x250|300x250|300x600| |---|---|---| | ![](https://m.stacker.news/75651) | ![](https://m.stacker.news/75652)| ![](https://m.stacker.news/75653) |

|728x90| |---| |![](https://m.stacker.news/75650) |

~AGORA territory

The SN P2P Marketplace |970x250| |---| | ![](https://m.stacker.news/75767) |

|250x250|300x250|300x600| |---|---|---| | ![](https://m.stacker.news/75769) | ![](https://m.stacker.news/75770)|![](https://m.stacker.news/75771)|

|728x90| |---| | ![](https://m.stacker.news/75768)|

~alter_native territory

|970x250| |---| | ![](https://m.stacker.news/75669)|

|250x250|300x250|300x600| |---|---|---| |![](https://m.stacker.news/75671)|![](https://m.stacker.news/75672)|![](https://m.stacker.news/75673)|

|728x90| |---| |![](https://m.stacker.news/75670) |

~bitcoin_beginners

|970x250| |---| | ![](https://m.stacker.news/75676) |

|250x250|300x250|300x600| |---|---|---| | ![](https://m.stacker.news/75677)|![](https://m.stacker.news/75678)|![](https://m.stacker.news/75679) |

|728x90| |---| | ![](https://m.stacker.news/75675)|

~Design territory

|970x250| |---| |![](https://m.stacker.news/75659)|

|250x250|300x250|300x600| |---|---|---| |![](https://m.stacker.news/75661)|![](https://m.stacker.news/75662)|![](https://m.stacker.news/75663)|

|728x90| |---| |![](https://m.stacker.news/75660)|

~Music territory

|970x250| |---| | ![](https://m.stacker.news/75664)|

|250x250|300x250|300x600| |---|---|---| |![](https://m.stacker.news/75666)|![](https://m.stacker.news/75667)|![](https://m.stacker.news/75668)|

|728x90| |---| | ![](https://m.stacker.news/75665)|

Anything else we could add?

If you feel something is missing, or you know a better tool to manage this media kit for SN in a collaborative and FOSS way then, DO share it in a comment below

Territory owners [^1], do you need banners for your territory? Feel free to edit the figma file liked above or comment below sharing your needs or ideas, I'll try to do something for you.

By following these guidelines, we ensure consistency and professionalism in every case where Stacker News is represented here internally to stackers or to our audience in the KYC internet, reinforcing SN credibility as a trusted source for data-driven journalism.

[^1]: FYI: @Aardvark @AGORA @anna @antic @AtlantisPleb @Bell_curve @benwehrman @bitcoinplebdev @Bitter @BlokchainB @ch0k1 @davidw @ek @elvismercury @frostdragon @grayruby @HODLR @inverselarp @Jon_Hodl @k00b @marks @MaxAWebster @mega_dreamer @niftynei @nout @OneOneSeven @OT @PlebLab @Public_N_M_E @RDClark @realBitcoinDog @roytheholographicuniverse @siggy47 @softsimon @south_korea_ln @theschoolofbitcoin @TNStacker @UCantDoThatDotNet @Undisciplined

originally posted at https://stacker.news/items/872925

@ 3bf0c63f:aefa459d

doulas.club

A full catalog of all Brazilian doulas with data carefully scrapped from many websites that contained partial catalogs and some data manually included. All this packaged as a Couchapp and served directly from Cloudant.

This was done because the idea of doulas was good, but I spotted an issue: pregnant womwn should know many doulas before choosing one that would match well, therefore a full catalog with a lot of information was necessary.

This was a huge amount of work mostly wasted.

Many doulas who knew about this didn't like it and sent angry and offensive emails telling me to remove them. This was information one should know before choosing a doula.

See also

• About CouchDB

@ ac8bb9b0:70278acc

Details

• ⏲️ Prep time: 15
• 🍳 Cook time: 1 hour 30 minutes
• 🍽️ Servings: 10

Ingredients

• 1 lb. ground beef
• 1 cup celery diced
• 1 cup carrots diced
• 1 medium onion diced
• 2 medium potatoes diced
• 5 cups beef broth
• 1 15 oz. can corn, drained
• 1 8 oz. can tomato sauce
• 1 28 oz. can diced tomatoes
• 1 teaspoon salt
• 1 teaspoon Italian seasoning
• 1 bay leaf

Directions

1. In a large dutch oven (I used a 6-quart), over medium heat brown the ground beef until done. Spoon off the excess fat.
2. Add the remaining ingredients and stir. Bring to a boil and reduce the heat. Allow to simmer for 1 to 1 ½ hours (with the lid on, but tilted so steam can release) or until the vegetables are tender.
3. Remove the bay leaf and serve.

@ e0e92e54:d630dfaa

When a Client Wants Out…& A Yellow Flag Appears

This week was an interesting one with a client that wants to exit our agreement early.

(Totally fine. It happens and usually when one or both parties want to part ways, unless it's marriage, then it's at minimum a Yellow Flag if not a Red Flag that should be observed).

I tend to work with clients that have multiple irons in the fire, hence why they need someone like me to come along side them and provide guidance and help root them in the area they must focus on.

There is a strong parallel with this irregardless of whether it's #business #life or #impact

This client had big goals, but like many business owners, they defaulted to reactionary decisions instead of a structured plan. That’s when the Yellow Flag turned into a pattern I’ve seen before—Random Acts of X.

The Cost of Random Acts of X

If your solution is:

A. Throw money at it, and/or

B. Fire, Aim, Ready...instead of Ready, Aim, Fire

This WILL result in Random Acts of X (wherein X is whatever your are focused on, ie Marketing...aka Random Acts of Marketing essentially equates to the proverbial "throw spaghetti on the wall")

Is that really a thing? Like do Italians or some other cultures actually throw spaghetti on the wall to see if it "sticks"? Inquiring minds want to know! 🤷‍♂️

As I mentioned, my clients tend to have a lot of things they are trying to accomplish at once. This leads to fragmented efforts and lack luster results.

That being said, I approach everything as a relationship. Afterall, I believe:

Leadership = Relationships!

With this particular client there was one project he abruptly ended. Again, that's fine...it's their business...

Since I'm there to help them lead well, I reminded them this is a relationship and asked "What's next that you want me to focus on?"

We got on the same page with the new project and not even 2 days later that's where the Yellow Flag appeared in the form of issue A (just throw money at it).

Shortcuts Lead to Ghost Towns (Buying Followers Won’t Work)

You see, they wanted me to lead a marketing campaign to build relationships with people their company could sponsor. BUT they just wanted to "buy followers".

When I noticed one of their social accounts has 28k followers and on average only 14 impressions per post...

I asked "How's that working out for ya?"

You see folks, real relationships take time!

One cannot simply "throw money at it" and expect sound, sustainable results.

If you’re buying an audience instead of building one, you won’t have a community—you'll have a ghost town.

What Fake Engagement Looks Like in Business & Family

Think of it this way...

Imagine all you did in your family's relationships was throw money at it. You just "bought followers" in the form of taking this trip, buying that thing for them; and you totally avoided the time investment the relationship requires?

Sure...you might have been physically there...but were you present?

I run into this often with my son. He wants me to watch him play a video game. And during that time together what is he doing? He keeps looking over his shoulder to make sure I'm paying attention to HIM and not clandestinely on my phone.

Same goes for his Basketball...he wants me there rebounding for him...not sitting in a chair idly watching.

Are You Present or Just Physically There?

Business Owners and Leaders!

Husbands, Wives, and Parents!

People whom desire to have an impact!

The Process is the Shortcut!

Play silly games. Win silly prizes.

Intentionally build relationships. Reap rewards forever.

It's...

That...

Simple...

Easy? Not really...especially for someone like me whom is just as keen to spend time in nature or chillaxing with a cup of coffee on the back porch, thinking (and wishing my garden was growing better LOL).

But simple? Yes!

Create the process, execute the process, refine the process, and repeat.

The Process is the Shortcut...

Your Next Step: Cut the Shortcuts. Build the Process.

So—where do you need to refine your process today?

💡 What’s one way you can be more present in a relationship this week?

💡 What can you eliminate to move you closer to real impact—instead of just chasing more?

🔹 Drop your answer below 👇

---

Jason Ansley* is the founder of Above The Line Leader*, where he provides tailored leadership support and operational expertise to help business owners, entrepreneurs, and leaders thrive.

Want to strengthen your leadership and enhance operational excellence? Connect with Jason at https://abovethelineleader.com/contact

📌 This article first appeared on Nostr. You can also find more Business Leadership Articles and content at: 👉 https://abovethelineleader.com/business-leadership-articles

@ f0c7506b:9ead75b8

Rainer Maria Rilke

Yalnızca güçlü olanların hakkıdır yaşamak.

Güçlü olan ileri gider ve saflar seyrekleşir. Ama üç beş büyük, güçlü ve tanrısal kişi güneşli ve aydınlık gözleriyle o yeni, o vaat edilmiş ülkeye ulaşacaktır. Belki binlerce yıl sonra ancak. Ve güçlü, adaleli, hükmetmek için yaratılmış elleriyle hastaların, zayıfların ve sakatların ölüleri üzerinde bir krallık kuracaklardır. Bir krallık!

Benim aradığım insanların kendileri değil, sesleridir.

Duyguları körelmiş, çeşitli düşüncelere saplanmış kalabalık hiçbir zaman ilerlemenin taşıyıcısı olamaz, kendi küçüklüğünün o küflü içgüdüsüyle kalabalığın kin ve nefretle baktığı bir kişi, bir büyük kişi, iradesinin gösterdiği yolda kimsenin gözünün yaşına bakmaksızın ilahi bir güç ve bir zafer gülümsemesiyle yürüyebilir ancak.

Bizim soyumuz da sonsuz oluşum piramidinin doruk noktasını oluşturmaktan uzaktır. Bizler de mükemmelliğe ulaşmış değiliz. Bizler de henüz olgunlaşmadık.

Şairler sevgiye övgüler döşenir; doğrusu sevginin güçlü bir şey olduğu kesin. Hüneşin bir ışınıdır sevgi, aydınlatıp nurlandırır insanı der bazıları; bazıları da insanı esrikliğe sürükleyen bir zehri kendisinde barındırdığını söyler. Gerçekten de yol açtığı sonuçlar, bir hekimin ağır bir ameliyattan önce korkudan titreyen hastaya teneffüs ettirdiği güldürücü gazınkine benzer, içinde tepinip duran acıyı unutturur hastaya.

Önemli olan, hayatta hiç değilse bir kez kutsal bir ilkbaharın yaşanmasıdır; öyle bir bahar ki, insanın gönlünü ilerideki bütün günleri altın yaldızla kaplamaya yetecek kadar ışık ve parıltıyla doldursun.

Şu hayat denen şey kötü bir işçiliğin ürünü, acemilere göre bir şey. Bu kepaze yaşam uğruna insan nelere katlanmıyor ki!

Kendisine sadakatten ayrılmadığı, yalnızca kendisinin olan bir tek bu var: Yalnızlığı.

Sahildeki üstü tenteli hasır koltuklar arkasındaki yüksek, sessiz kum tepeleri içinde yürürsen, tenteler altındaki insanları göremezsin; ama birinin bir diğerine seslendiğini, bir başkasının gevezelik ettiğini, bir ötekinin güldüğünü işitir ve anlarsın hemen: bu insan şöyle şöyle biridir diyebilirsin. Onun hayatı sevdiğini, bağrında büyük bir özlem ya da acı barındırdığını, bu acının da sesini ağlamaklı kıldığını her gülüşünde hissedersin.

@ dbb19ae0:c3f22d5a

List of Wordpress articles:

• https://alashazam.wordpress.com/2024/07/01/python-nostr/
• https://alashazam.wordpress.com/2024/07/02/python-nostr-2/
• https://alashazam.wordpress.com/2024/07/03/python-nostr-second-program/
• https://alashazam.wordpress.com/2024/07/04/python-nostr-sdk/
• https://alashazam.wordpress.com/2024/07/04/python-nostr-third-program/
• https://alashazam.wordpress.com/2024/07/05/python-nostr-guessing-the-npub/
• https://alashazam.wordpress.com/2024/07/06/python-nostr_sdk-fetching-metadata/
• https://alashazam.wordpress.com/tag/python/

---

```python

!/usr/bin/env python3

""" Fetches the joined date from a Nostr profile and calculates the days since account creation.

Usage: python fetch_joined_date.py [npub]

Arguments: npub : The public key of the user (in npub format).

Requirements: - nostr_sdk library - Python 3.x

Example: python fetch_joined_date.py npub1... """

import argparse import time import ssl import json import uuid import logging from datetime import datetime from nostr.event import EventKind from nostr.relay_manager import RelayManager from nostr.key import PublicKey from nostr.filter import Filter, Filters from nostr.message_type import ClientMessageType

Configure logging

logging.basicConfig(level=logging.INFO, format="%(levelname)s: %(message)s")

RELAY_URL = "wss://relay.damus.io"

def fetch_metadata(npub): """Fetches metadata from a Nostr profile given an npub key.""" pub_key = PublicKey.from_npub(npub) filters = Filters([Filter(authors=[pub_key.hex()], kinds=[EventKind.SET_METADATA])]) subscription_id = uuid.uuid1().hex request = [ClientMessageType.REQUEST, subscription_id, *filters.to_json_array()]

relay_manager = RelayManager()
relay_manager.add_relay(RELAY_URL)
relay_manager.add_subscription(subscription_id, filters)

try:
    relay_manager.open_connections({"cert_reqs": ssl.CERT_NONE})
    time.sleep(1)  # Allow time for connection
    relay_manager.publish_message(json.dumps(request))
    time.sleep(1)  # Allow time for response

    while relay_manager.message_pool.has_events():
        event_msg = relay_manager.message_pool.get_event()
        metadata = json.loads(event_msg.event.content)
        return metadata
except Exception as e:
    logging.error(f"Error fetching metadata: {e}")
finally:
    relay_manager.close_connections()

return None

def fetch_joined_date(npub): """Retrieves the joined date of a Nostr profile and calculates days since creation.""" metadata = fetch_metadata(npub) if not metadata or "created_at" not in metadata: logging.warning("Could not retrieve metadata or 'created_at' field is missing.") return

try:
    created_at = int(metadata["created_at"])
    created_date = datetime.utcfromtimestamp(created_at)
    days_since_creation = (datetime.utcnow() - created_date).days

    logging.info(f"Account created on: {created_date.strftime('%Y-%m-%d %H:%M:%S UTC')}")
    logging.info(f"Days since account creation: {days_since_creation}")
except (ValueError, TypeError):
    logging.error("Invalid 'created_at' timestamp.")

if name == "main": parser = argparse.ArgumentParser(description="Fetch the joined date from a Nostr profile.") parser.add_argument("npub", type=str, help="The public key of the user (in npub format).") args = parser.parse_args()

fetch_joined_date(args.npub)

```

@ 65912a7a:5dc638bf

Chef's notes

This is my late partner's award winning Cajun rice & beans recipe. It's an updated take on the traditional Cajun comfort food.

Chef Darin was a classically trained chef who spent 30+ years in the kitchen perfecting his recipes, and delivering authentic Cajun and Creole food to his patrons. This is a 5-star dish that will earn the respect of the most discerning Cajun afficionado. You won't be disappointed.

I suggest making this recipe exactly as directed the first time, and then make whatever adjustments you want for future batches. Also, don't cheap out on the Andouille. No Johnsonville or Hillshire Farms. Chef Aidelle's is a good choice, as is Silva's from Whole Foods. They cost a few extra bucks, but it's absolutely worth it.

Details

• ⏲️ Prep time: 30 min
• 🍳 Cook time: 3 hours
• 🍽️ Servings: 12

Ingredients

• 16oz small red beans, dry
• 2 cups long grain white rice
• 14-16oz andouille sausage, sliced
• 8oz ham, cubed
• 1 large yellow onion, chopped
• 1 green bell pepper, chopped
• 2-3 stalks celery, chopped
• 2 tbsp garlic (12 cloves), minced
• 7 cups water
• ¼ cup olive oil
• 2 large bay leaves
• 1 tbsp parsley, dried
• 1 tsp thyme, dried
• 1 tsp Cajun seasoning
• ½ tsp cayenne pepper, dried
• ¼ tsp sage, rubbed
• 1½ tsp salt (more or less to taste)

Directions

1. Soak beans in a large pot of water overnight.
2. Heat oil in a large stockpot over medium heat. Cook onion, bell pepper, celery, garlic in olive oil for 3 to 4 minutes (until onion is translucent).
3. Add beans, bay leaves, parsley, thyme, salt, MSG, Cajun seasoning, cayenne pepper, Sage, and water. Stir, bring to a boil, and then reduce heat to medium-low (btwn 2-3). Cover and simmer for 2½ hours.
4. Remove bay leaves. Mash some of the beans. Stir Andouille and ham into beans, and simmer uncovered for an additional 30 minutes.
5. Meanwhile, prepare the rice. Bring water and rice to a boil in a saucepan. Reduce heat, cover, and simmer for 20 minutes.
6. Serve beans over steamed white rice.

@ 20e17dd0:2ae504d7

1. Hardware Selection

It is important to select adequately the hardware that will be used to build your Node. The Node will be running 24h /7 days and will countain your lightning channels. It is important to use high quality hardware and spend the extra dollars for it.

At the time of building my Node, there was a shortage of Raspberry Pi and I was looking for an optimal alternative. I have decided to go ahead and purchase a used Mac Mini (late 2012).

It is recommended NOT to purchase a Mac Mini newer than 2012 (i.e 2014 and up) because Apple started to solder the RAM to the Logic Board after 2012. The Mac Mini Late 2012 is the last model that is fully customizable with SSD and RAM upgrades.

Here is the list of hardware that will be used in this build:

• 2 x 8G DDR3L Sodim 1600Mhz 1.35V
• 1 x Mac Mini (Late 2012) 2.5Ghz
• 1 x Samsung Evo 870 1Tb SSD ^

^ Note: As discussed earlier, it is important to select hardware of quality. I had initially purchased a low cost 2Tb SSD but it failed while trying to download the Bitcoin blockchain.

2. Hardware Upgrade

To facilitate the upgrade of the hardware, you will need the proper tools to remove some T6 & T8 screws.

Here are the steps to dismount the few components of the Mac Mini to upgrade the hardware:

1. Unplug the Mac Mini.
2. Turn it upside down with the black cover facing up.

3. Put your thumbs in the 2 grooves of the cover and turn the piece counterclockwise.

4. Remove the cover.

5. Remove 3 x T6 screws holding the fan.
6. Lift the fan and disconnect the connector by pulling gently straight up the wires.
7. Remove 1x T6 screw at the bottom of the shroud (black plastic piece on the left of the fan).

8. Remove the shroud by holding the top right part with your fingers and turning it clockwise.

9. Remove 4 x T8 screws of the grill WIFI cover.

10. The top of the grill is mounted under the Mac Mini case. Lift gently the bottom of the grill and pull towards yourself to remove the grill.
11. Move the grill aside, you do not have to disconnect the WIFI sensor, just be careful.

2.1 Upgrading the RAM

The RAM is visible and accessible from the moment you remove the cover. Simply release each RAM by releasing the clips on the side. Once disengaged, the RAM will spring in a 45-degree angle. Remove it and put back the upgraded RAM at a 45 degree angle and push it down for it to clip.

2.2 Upgrading the SSD

It is important to note that the Mac Mini has 2 SSD bay. They are referred to as the “upper bay” and “lower bay”. Since we have flipped the Mac Mini upside down to remove the bottom cover, the “upper bay” is located under the “lower bay”.

The “upper bay” is mounted with an expansion kit that holds the SSD in position whereas the “lower bay” SSD is simply resting on top of the “upper bay” SSD.

One important aspect is that the connecting cables for the “lower bay” and “upper bay” SSD are not the same. The “upper bay” SSD connects on the logic board on the right and the “lower bay” SSD cable connects on the left. Removing the “upper bay” SSD requires removing the logic board therefore requires more work. It is recommended to install the new SSD in the “lower” bay. Here are the 2 scenarios:

1.Your Mac Mini has already a Hard Drive installed in the “lower” bay. In that case insert a credit card under the HD and gently pry it upwards. You will be able to slide it out of the bay. The reason to pry it gently is because since there is no “upper” bay drive, The HD is being held in the air by 2 screws on the side that are aligned in 2 holes in the Mac Mini case. Once the HD is removed, transfer the connecting cable and the 2 screws to the new SSD. To put back the new SSD, it is easier to rotate the Mac Mini 90 degree and have the mounting holes at the bottom and use the gravity to get the 2 mounting screws in the holes. After, connect the connector to the logic board.

1. Your Mac Mini has already a Hard Drive installed in the “upper bay”? Leave it there, you do not need mounting screws, but you need a new connecting cable. You will have to buy a “lower bay connector”. Once installed on the SSD, slide the SSD on top of the original one. The connector will plug on the logic board on the left of the “upper bay” SSD connector.

A good preparation would be to go in “Disk Utility” menu on MacOS and search for “upper” or “lower” position before starting to disassemble.

Reassemble everything and you are done.

@ be41636e:e55c4909

Will Quantum Computers Kill Bitcoin? The Truth May Surprise You

One of the biggest fears around Bitcoin is that quantum computers (QCs) will render it obsolete. But is this really a legitimate concern, or just another doomsday myth?

The Real Threat: Not All Quantum Computers Are Equal

First, let’s get one thing straight: quantum computers already exist. The first notable ones appeared in the 1990s, built by IBM and Stanford. So why hasn’t Bitcoin already been hacked? Because it’s not about whether quantum computers exist—it’s about how powerful they need to be.

Are All Bitcoin Addresses at Risk?

No! If you’ve entered Bitcoin after 2010 or use a wallet backed up with 12 or 24 words (BIP-39, introduced in 2013), your funds are safe from quantum threats for a very long time—centuries, at least.

But why?

Understanding How Bitcoin’s Security Works

Bitcoin security is based on private keys. (These are represented by the 12-24 words you write down when setting up a wallet.) From this private key, a public key is created. In Bitcoin’s early days, people shared public keys directly to receive payments. But in 2010, Bitcoin introduced an extra layer of security: hashed addresses.

Now, instead of sharing your public key, your wallet generates a Bitcoin address, which is actually a hash of your public key. This adds an extra step for an attacker: before they can find your private key, they must first break the hash to reveal your public key.

Two Steps to Breaking Bitcoin

To steal Bitcoin using quantum computing, an attacker must:

1. Break the hash (Bitcoin address → public key) using Grover’s algorithm.
2. Break the elliptic curve cryptography (public key → private key) using Shor’s algorithm.

Where Do Quantum Computers Stand Today?

Let’s put things in perspective. Google’s Willow processor, which made headlines recently, has 105 physical qubits. But breaking Bitcoin’s elliptic curve cryptography (step 2 above) requires about 2,330 logical qubits, running for minutes to hours.

So how does 105 physical qubits compare to 2,330 logical qubits? It’s not even in the same league. To get 2,330 logical qubits, we'd likely need millions of physical qubits—a technology that is still decades away.

Now, even if we magically reached 2,330 logical qubits tomorrow, that only breaks public keys. It still wouldn't be enough to break Bitcoin addresses (step 1), which would take centuries with current quantum algorithms.

Who Should Be Worried?

• People who used Bitcoin before 2010 and still have funds sitting in old public-key-based addresses (P2PK addresses). Their funds could be stolen in minutes to hours if a powerful enough quantum computer emerged.
• People who reuse addresses—this exposes the public key, making it vulnerable to a quantum attack, even when you are using more modern addresses. (Many wallets, including Trust Wallet, SafePal, Exodus, and Atomic Wallet, still allow this bad practice!)

Who Can Sleep Soundly?

• Anyone using modern Bitcoin addresses (P2PKH, SegWit, Taproot). Their addresses are hashed, meaning an attacker would need centuries to break the first layer of protection before even getting to the public key.
• Anyone moving their coins periodically—since modern Bitcoin wallets generate new addresses for each transaction, public keys remain hidden.

The Concrete Wall Analogy

Think of your Bitcoin private key as being locked inside a massive vault. The first layer of protection is your Bitcoin address, which acts like a thick concrete wall. Cracking through this wall with current quantum algorithms would take centuries. Even if someone managed to break through, they would still face a second, much thinner barrier—your public key. This one would take only minutes to hours to breach. But by then, Bitcoin security upgrades would likely already be in place, leaving attackers empty-handed.

But What If We Make a Huge Quantum Leap?

Yes, it’s possible that new quantum algorithms emerge, or that quantum hardware advances faster than expected. But Bitcoin’s development community isn’t sitting idle, waiting to get wrecked. There are already proposals for quantum-resistant Bitcoin addresses, and they can be implemented before quantum computers reach a dangerous level.

The Bottom Line

🚀 Quantum computers won’t kill Bitcoin anytime soon.

📌 If you’re using a modern Bitcoin wallet, your funds are safe from quantum threats for the foreseeable future.

📌 If you reuse addresses, stop! It exposes your public key and makes you vulnerable much sooner.

📌 Bitcoin developers are already preparing for a quantum-resistant future.

So, no, quantum computers won’t be the end of Bitcoin. But they might be the end of bad security practices! 🔐

@ b17fccdf:b7211155

Next new resources about the MiniBolt guide have been released:

---

• 🆕 Roadmap: LINK
• 🆕 Dynamic Network map: LINK
• 🆕 Nostr community: LINK < ~ REMOVE the "[]" symbols from the URL (naddr...) to access
• 🆕 Linktr FOSS (UC) by Gzuuus: LINK
• 🆕 Donate webpage: 🚾 Clearnet LINK || 🧅 Onion LINK
• 🆕 Contact email: hello@minibolt.info

---

Enjoy it MiniBolter! 💙

@ be41636e:e55c4909

One of the biggest fears around Bitcoin is that quantum computers (QCs) will render it obsolete. But is this really a legitimate concern, or just another doomsday myth?

The Real Threat: Not All Quantum Computers Are Equal

First, let’s get one thing straight: quantum computers already exist. The first notable ones appeared in the 1990s, built by IBM and Stanford. So why hasn’t Bitcoin already been hacked? Because it’s not about whether quantum computers exist—it’s about how powerful they need to be.

Are All Bitcoin Addresses at Risk?

No! If you’ve entered Bitcoin after 2010 or use a wallet backed up with 12 or 24 words (BIP-39, introduced in 2013), your funds are safe from quantum threats for a very long time—centuries, at least.

But why?

Understanding How Bitcoin’s Security Works

Bitcoin security is based on private keys. (These are represented by the 12-24 words you write down when setting up a wallet.) From this private key, a public key is created. In Bitcoin’s early days, people shared public keys directly to receive payments. But in 2010, Bitcoin introduced an extra layer of security: hashed addresses.

Now, instead of sharing your public key, your wallet generates a Bitcoin address, which is actually a hash of your public key. This adds an extra step for an attacker: before they can find your private key, they must first break the hash to reveal your public key.

Two Steps to Breaking Bitcoin

To steal Bitcoin using quantum computing, an attacker must:

1. Break the hash (Bitcoin address → public key) using Grover’s algorithm.
2. Break the elliptic curve cryptography (public key → private key) using Shor’s algorithm.

Where Do Quantum Computers Stand Today?

Let’s put things in perspective. Google’s Willow processor, which made headlines recently, has 105 physical qubits. But breaking Bitcoin’s elliptic curve cryptography (step 2 above) requires about 2,330 logical qubits, running for minutes to hours.

So how does 105 physical qubits compare to 2,330 logical qubits? It’s not even in the same league. To get 2,330 logical qubits, we'd likely need millions of physical qubits—a technology that is still decades away.

Now, even if we magically reached 2,330 logical qubits tomorrow, that only breaks public keys. It still wouldn't be enough to break Bitcoin addresses (step 1), which would take centuries with current quantum algorithms.

Who Should Be Worried?

• People who used Bitcoin before 2010 and still have funds sitting in old public-key-based addresses (P2PK addresses). Their funds could be stolen in minutes to hours if a powerful enough quantum computer emerged.
• People who reuse addresses—this exposes the public key, making it vulnerable to a quantum attack, even when you are using more modern addresses. (Many wallets, including Trust Wallet, SafePal, Exodus, and Atomic Wallet, still allow this bad practice!)

Who Can Sleep Soundly?

• Anyone using modern Bitcoin addresses (P2PKH, SegWit, Taproot). Their addresses are hashed, meaning an attacker would need centuries to break the first layer of protection before even getting to the public key.

The Concrete Wall Analogy

Think of your Bitcoin private key as being locked inside a massive vault. The first layer of protection is your Bitcoin address, which acts like a thick concrete wall. Cracking through this wall with current quantum algorithms would take centuries. Once one breaks through this wall, they would face a second wall, which is a much thinner barrier—your public key. This one would take only minutes to hours to breach.

But What If We Make a Huge Quantum Leap?

Yes, it’s possible that new quantum algorithms emerge, or that quantum hardware advances faster than expected. But Bitcoin’s development community isn’t sitting idle, waiting to get wrecked. There are already proposals for quantum-resistant Bitcoin addresses, and they can be implemented before quantum computers reach a dangerous level.

The Bottom Line

🚀 Quantum computers won’t kill Bitcoin anytime soon.

📌 If you’re using a modern Bitcoin wallet, your funds are safe from quantum threats for the foreseeable future.

📌 If you reuse addresses, stop! It exposes your public key and makes you vulnerable much sooner.

📌 Bitcoin developers are already preparing for a quantum-resistant future.

So, no, quantum computers won’t be the end of Bitcoin. But they might be the end of bad security practices! 🔐

@ 3bf0c63f:aefa459d

início

"Vocês vêem? Vêem a história? Vêem alguma coisa? Me parece que estou tentando lhes contar um sonho -- fazendo uma tentativa inútil, porque nenhum relato de sonho pode transmitir a sensação de sonho, aquela mistura de absurdo, surpresa e espanto numa excitação de revolta tentando se impôr, aquela noção de ser tomado pelo incompreensível que é da própria essência dos sonhos..."

Ele ficou em silêncio por alguns instantes.

"... Não, é impossível; é impossível transmitir a sensação viva de qualquer época determinada de nossa existência -- aquela que constitui a sua verdade, o seu significado, a sua essência sutil e contundente. É impossível. Vivemos, como sonhamos -- sozinhos..."

• Livros mencionados por Olavo de Carvalho
• Antiga homepage Olavo de Carvalho
• Bitcoin explicado de um jeito correto e inteligível
• Reclamações

---

• Nostr
• Bitcoin
• How IPFS is broken
• Programming quibbles
• Economics
• Open-source software

---

Nostr GitHub Telegram code

@ b17fccdf:b7211155

---

Check out the MiniBolt guide -> HERE <-

---

• Core guides
• System
  • Preparations
  • Operating System
  • Remote access
  • Configuration
  • Security
  • Privacy
• Bitcoin
  • Bitcoin client (Bitcoin Core)
  • Electrum server (Fulcrum)
  • Desktop signing app (Sparrow Wallet)
  • Blockchain explorer (BTC RPC Explorer)
• Lightning
  • Lightning client (LND)
  • Channel backup
  • Web app (ThunderHub)
  • Mobile app (Zeus)
• Bonus guides
• System bonus guide
  • Dashboard & Appearance
    • Pimp the command line
    • System Overview
  • System Administration
    • Aliases
    • Statip IP & custom DNS servers
  • Install / Update / Uninstall common languages
    • Node.js + NPM
    • Rustup + Cargo
    • Go!
  • Databases
    • PostgreSQL
  • Security
    • SSH Keys
    • WireGuard VPN
    • Cloudflare Tunnel
  • Resilience
    • Tor services: bridges & relays
  • Hardware
    • Store data in a secondary disk
• Bitcoin bonus guides
  • Electrum servers
    • Electrs
  • Signing apps
    • Desktop
    • Electrum Wallet Desktop
  • Decentralized exchange
    • Bisq
  • Resilience
    • Safu Ninja
    • Ordisrespector
  • Fun
    • Download the white paper
  • Testnet
    • MiniBolt on Testnet
  • Payment processors
    • BTCPay Server
• Nostr bonus guides
  • Relays
  • Nostr relay

---

🏗️ Roadmap | 🌐 Dynamic Network map | 🔧 Issues | 📥 Pull requests | 🗣️ Discussions

---

By ⚡2FakTor⚡

---

Last updated: 22/12/2024

@ 148755e6:450c107f

突然荒野に行きたくなったので行ってきたエントリーです

まずは練習。高尾山へ

Nostrは古今東西ありとあらゆるオフ会が生えており、

まるで荒野に行きたいという私の意志を完全に汲み取ったかのように「紅葉を見にいこうようオフ」がそこに生えていたので参加した。（しおんさんご主催ありがとうございました） 前半1時間くらいの坂道がマジきつかったです。前半キツすぎて後半足痛かった。。 終始人がいっぱいいて渋谷かと思った。

確かに道がかなり整備されていて、逆にコンクリート故に足が疲れたのかもしれない。隣の人は途中の急な坂道で足を滑らせてて、横で転倒事故が起きるかと思いました。

山頂に行っても人がたくさんいて、迷子になりかけた。あそこはスクランブル交差点や。 そして山頂の先にあるもみじ台まで歩くと人がまばらで、まったりして蕎麦食べたりしながら休憩して下山。

登りは暑くて汗かきましたが、山頂でまったりしてると汗も引いてきて少し冷えました。

下山はスイスイ。16時近くで結構暗かったので、冬の間は早めの登頂・下山がおすすめですね。

登り2時間・下り1時間半で概ね見込み通りって感じでした。

高尾山は登ってると景色が変わります。ちょっと開けた場所に出て下の街が見えたり、草木があったり、階段があったり、参道があったり。。そういう意味では退屈しない2時間でした。

ビギナー山とはいえ、革靴やヒールのある靴で登ってる人がいてびっくり。ツルッと滑ることあると思いますので、スニーカーで登ることをお勧めします。

舐めプしてたとはいえめちゃくちゃキツかったおもひで。

更なる練習。小浅間山へ

さて私は荒野に行きたいワケなのですが、高尾山に荒野はありませんでした。更なる練習として小浅間山へ。

前日（か前々日）に雪が降ったようで、山に雪が残っておりました。

それでも都内の汚れてべちゃっとした感じの雪ではなく、粉砂糖がちょっと積もってるみたいな感じで綺麗だった。

登り前半の30分くらい、景色や道が変わらず、ずっと歩きっぱなしになってしまいました。時間みて休憩しながら行けばよかったなあ。

登るにつれて気温が下がっていくのか、積雪が厚くなっていく。

40分くらいは割と平坦な道が続きますが、突然山頂っぽいものが現れて、「これを登れっていうのかい...？」とビビるほどピーンと急な道が出てきました。(写真だと分かりづらいですね)

ただ、高尾山のコンクリート道に比べると足の疲れはそこまででした。雪道なので気をつけて歩くという意味では疲れましたが、春〜秋とかは快適に登れるんじゃないでしょうか。

山頂に到着するとドーンと浅間山が見えて圧巻。

風が強くて飛ばされる恐怖はありましたが、なんとか無事でいられました。あったかいお茶美味しかった〜。

なぜかギャルの看板があって、謎でした。写真はひとまずありません。

山頂が2箇所あって、それぞれで眺めを満喫していたら結構時間が経ってました。

小さい背丈くらいの木や足元にちょっとした植物があったり、自分的にはかなり理想の荒野に近かったです。（植物に対する解像度が低すぎる） 往復で2時間程度の山らしいんですが、なんやかんやと2時間半強くらいいた気がします。

荒野ビギナーは小浅間山に往け

というわけで、荒野に行きたい人はまずは小浅間山を登ると良いと思います。 また登りたい。

荒野部部長

一緒に高尾山・小浅間山に登ってくれた方、ありがとうございました！ 個人的には来年の春までに秩父多摩甲斐国立公園に行き、来年の秋までに大山隠岐国立公園に行くという目標を立ててるんですが、 少々時間が空くので次どこに行こうかしらと考えているところです。

ヒントとしては、火山で、あまり高低差のないところだとビギナーの私にちょうど良さそうです。

とある情報筋によると伊豆大島が良さそうなので、次の機会に行けたらと思っています。

みんなで荒野に行こう！

@ d57360cb:4fe7d935

What is life but a preparation for the grand finale.

Think of your life up to this point. You’ve been living in the midst of death whether you pay attention to it or not.

Your youth faded, the years go by, relationships fail, careers fail, people die, the ones close to you and those you hardly know. Civilizations wiped out, total species completely gone with no trace.

Here you are in the midst of death. A vortex of change wiping everything in its path. Creating space for the unknown and new. Nothing lasts, nothing stays the same, everything ends. Ending gives great significance to life.

How will you be in the presence of someone you love knowing they or you will vanish one day?

What wouldn’t you put off if you were aware your time was slipping and there’s nothing you can do.

What would you stop doing?

What would you let go of?

Who would you forgive?

Life comes with a bullet and it has your name on it. You don’t know when it’ll happen.

Don’t believe you ever have time it’s always a fantasy. Death will knock you on your feet when you least expect it.

Use death as a doorway to a deep meaningful life.

@ ac8bb9b0:70278acc

Chef's notes

Make Ahead: You can prepare this recipe up to one week in advance. Store it in an airtight container in the refrigerator.

To Freeze: Allow the dish to cool completely before transferring it to a freezer-safe bag. Lay the bag flat in the freezer to ensure even freezing and to save space. Thaw it in the refrigerator overnight before using it.

Details

• ⏲️ Prep time: 5
• 🍳 Cook time: 5
• 🍽️ Servings: 1

Ingredients

• ½ cup soy sauce
• 2 Tablespoons rice vinegar
• 1 Tablespoon sesame oil
• 1/4 cup + 1 Tablespoon light brown sugar
• 1 Tablespoon honey
• 3/4 teaspoon ground ginger
• 1 clove garlic , minced
• 2 teaspoons cornstarch+ 2 tsp water , mixed together to make a cornstarch slurry
• 1/4 teaspoon crushed red pepper flakes

Directions

1. Make the teriyaki sauce by adding all of the sauce ingredients to a small saucepan over medium heat.
2. Bring to a boil, stirring constantly, and boil for about 1 minute. The sauce should be thick enough to coat the back of the spoon.
3. Serve over rice or with a stir-fry. See post above for additional ideas.

@ cff1720e:15c7e2b2

Am 4. Oktober 1957 sendete Sputnik 1 erste Signale aus dem All. Die Welt war fasziniert, die Amerikaner geschockt, da die Russen sie in der Raumfahrt technologisch überholt hatten. Es folgte der Wettlauf im All mit Apollo-Programm und Mondlandung 1969. Am 27. Januar 2025 erlebte die USA einen weiteren Sputnik-Moment, diesmal durch die chinesische KI-App deepseek R1. Diese App schoss wenige Stunden nach ihrem Start auf Platz 1 der App-Stores, vorbei an dem bisherigen KI-Spitzenreiter ChatGPT. Die Aktie des KI-Chipherstellers Nvidia verlor 17% (600 Mrd. USD Börsenwert), das war der bisher höchste Tagesverlust des US-Aktienmarktes. Marc Andreessen verwendete gar die Formulierung “Sputnik-Schock", diese einseitige Sichtweise erschwert aber eine Betrachtung aus verschiedenen Perspektiven.

Was lässt sich mit ein paar Tagen Abstand daraus schlussfolgern? Die Aktionäre haben überreagiert und die Falschen bestraft. Die Nervosität der Anleger ist aber verständlich bei einem KGV von 46 bei Nvidia und 27 bei den “Magnificent Seven” (die großen US KI-Anbieter). Normale KGVs bewegen sich um 15, d.h. wir haben es mit einer ausgeprägten KI-Blase zu tun, die in Kürze platzen dürfte. Eine weitere Blase die schon vor dem Start geplatzt ist, ist das Projekt “Stargate” der Firmen OpenAI, Oracle und Softbank. In den nächsten 4 Jahren wollen sie  500 Mrd. USD für über 10 neue KI-Rechenzentren investieren, um Amerikas vermeintliche KI-Vorherrschaft gegenüber China weiter auszubauen. Die schon vorher vorhandenen Zweifel an dem Projekt (Elon Musk auf X “sie haben das Geld gar nicht”) wurden nun durch den Erfolg von deepseek verstärkt.

deepseek hat nämlich offenbart, dass die bisherige US KI-Strategie, "wir schlagen die Chinesen mit unserer DataCenter-Power", ein fataler Irrweg ist. Den Analysten von Bernstein zufolge ist das Modell von deepseek geschätzt 20 bis 40 mal billiger zu betreiben als ähnliche Modelle von OpenAI. Die Chinesen haben ihre Innovation durch Kreativität erzielt, im Gegensatz zur Gigantomanie der US-Konzerne, die sich in einem Überbietungs-Wettbewerb der Ressourcen-Verschwendung befinden. Hunderte Milliarden an Investorengeldern und ca. 9% des nationalen Stromverbrauchs führen zwar zur Bereicherung einiger Konzerne und ihrer Besitzer, nicht aber zu adäquaten Ergebnissen. Das selbe Muster konnte man bereits bei der Rüstungsbranche beobachten, die mit dem etwa 10-fachen Budget (1 Billion USD) nicht im Stande war bessere Waffensysteme zu produzieren als Russland (Oreshnik-Schock 2024).

Wenn Donald Trump wirklich Amerika stärken möchte, dann sollte er umgehend seine technokratischen Berater entlassen und Sun Tzu lesen, ein Buch, das die Grundlagen asiatischer Strategie vermittelt und den Krieg vermeiden lehrt ("Der klügste Krieger ist der, der niemals kämpfen muss"). Die chinesischen Erfolge basieren auf exzellenter Bildung, Startup-Förderung und minimaler Regulierung, Konzepte die der Westen zwar stets gepredigt aber nie geliefert hat. “Make Amerika smart again” hieße daher Abschied von Kriegsrhetorik, Embargos, Oligarchen-Projekten und der bisherigen Großmacht-Hybris. Annektionspläne für Grönland und Kanada passen nicht in das Bild, Wiederherstellung von Meinungsfreiheit und Abbau von Regulierungen schon (Streichung von Bidens KI-Regulierung Executive Order 14110). Wohin steuert Trump die USA? Wird der deepseek-Moment dabei helfen falsche Strategieansätze zu korrigieren? Das ist noch unklar, während aber schon jetzt unzweifelhaft feststeht, dass die EU und Deutschland weder bei der KI noch in der Geostrategie eine Rolle spielen, dafür aber als unangefochtene Regulierungs-Weltmeister. Herzlichen Glückwunsch!

„Man kann zwar die Realität ignorieren, aber nicht die Folgen davon ignorieren.“ Ayn Rand

Der wirkliche Gewinner dieser Woche ist aber die OpenSource-Szene mit ihren dezentralen Lösungsansätzen. Nicht nur deepseek R1 ist OpenSource sondern auch Marco o1 von Alibaba (https://github.com/huggingface). Die Nutzung ist kostenlos (ChatGPT kostet 200 USD pro Monat), daher können sowohl die Modellbildung, die Trainingsdaten als auch die Rechenleistung von unzähligen Aktivisten weltweit verteilt erbracht werden. Dafür braucht es weder Milliarden-Budgets, Regierungsprogramme oder neue DataCenter. Das Potential der Crowd übertrifft jeden zentralistischen Ansatz. Die Ergebnisse sind besser und die Kontrolle liegt nicht in den Händen einzelner. Smarte Lösung sind verteilt, das beweisen Projekte wie Bitcoin (seit 16 Jahren), Lightning und neuerdings auch Nostr. Deshalb haben wir Pareto (https://pareto.space) auf diesen Fundamenten entwickelt (Nostr, Lightning) und in 6 Monaten mit Freiwilligen mehr erreicht als viele große IT-Unternehmen in Jahren. Die Dinosaurier sterben aus, dem Schwarm gehört die Zukunft.

@ e262ed3a:e147fbcb

Feel free to develop

I got an idea while watching a video from @BTCSessions, which I personally cannot implement technically. Therefore, I would like to present it here for discussion and free implementation. It makes sense to me, but what do I know? Let the swarm intelligence decide.

The goal of the business idea is:

How can I bring as many solo miners as possible into a pool without them having to pay for the electricity for mining and their mining hardware can be amortized quickly, so they can purchase more mining hardware? How can we financially support Bitcoin and Nostr developers in the long term? How can we intensify developers for the implementation of this idea? How can we encourage non-Bitcoiners to invest in the support of the Bitcoin network? How can we get non-Bitcoin retailers to invest in the Bitcoin network?

**The answer is: PROSPECT OF WINNING

The solution lies in a kind of RAFFLE. (Not a betting website) !**

The legal difference between a BET and a RAFFLE varies from country to country. It lies in the fact that a raffle must be very transparent regarding the chances of winning and the proceeds must go to a good cause. Those involved in the implementation can, of course, be compensated (also with a profit for the individual participants). The extent to which this is allowed would have to be checked by those who want to implement this idea.

In the following, I will describe the implementation roughly. Since this is not a sales presentation, please excuse me if the following proposal is not fully structured.

**Participants in the idea are:

Consumers (ticket buyers) Bitcoin miners Retailers Non-profit company that implement the project**

What's it about? @BTCSessions has a YouTube video about the miner FutureBit. In the dashboard of the solo miner, you could see how high the hash rate was. But above all, you could see how high the chance of winning was for the solo miner in the overall network. In the case of BTCSessions FutureBit, the hash rate was around 5 TerraHash and the chance of winning was around 1:1,000,000. (Which, according to my calculations, was not correct). The power consumption was around 32 watts. When I saw that, it suddenly dawned on me.

Could it be possible to create a website/app that determines the total hash rate of a mining pool and then offers an electronic, numbered ticket for each 1 TerraHash (TH/s) of the pool for, for example, 0.1 USD? The minimum purchase amount would be 10 tickets. The customer sees the chance of winning and could even see the possible payout. The ticket is only valid for the next block (similar to roulette).

Another variant could be that the buyer can select one or more of the next 10 blocks and purchase tickets for the selected block. Since you don't know in advance how high the pool hash rate will be 5 or 10 blocks ahead, the amount of tickets to be issued for the 2nd block, for example, could only be 90% of the current pool hash rate, the 3rd block only 80%, and so on. If block 3, for example, advances to position 2, the previously unavailable 10% will be released for further tickets. (Determined by the pool hash rate at that time)

The purchase of 10 or more tickets could be automated in the customer's account on the website/app (intervals: hourly, daily, weekly, every 10 blocks, etc.). Customers could also top up their account with satoshis, enabling automatic deductions for ticket purchases. This could be facilitated by automatically issuing a Nostr npub to each customer, which would also create a wallet at Primal.net (Strike). For non-Bitcoiners, Zaprite could be used to recharge their account. Alternatively, customers could enter a NostrWalletConnection NWC to enable automatic deductions from their Lightning wallet. The project operators might also consider running their own ecash mint, which would allow them to assign an integrated ecash address to customers without a Lightning address. Tickets with ascending numbers would be allocated strictly in the order of payment receipts.

Calculations for the miners: The FutureBit miner consumed approximately 30 watts per terahash/hour. Let's assume that 10 terahash consume 300 watts per hour, then the miner consumes 50 watts per 10 minutes (per block). Let's further assume that a kilowatt-hour of electricity costs between 10 and 30 cents, then it costs the miner 3-9 cents per hour for electricity at 10 terahash mining capacity. So, 0.5-1.5 cents per block. In the case that each ticket is sold for 1 terahash for the next block, one could automatically transfer, for example, 5% of the satoshis received from ticket sales to each participating miner in the pool (proportional to the average hash rate delivered by the miner in the last block in the pools). This happens even if the block is not found. If fewer tickets are sold than the maximum possible amount, then the 5% of the sold tickets will be distributed proportionally. (See also my Excel file?

At the center of the project is a website/app that manages the raffle. Here, anyone can register and create an account. Either as a miner, retailer, or customer with or without KYC, for example, with their own nostr nsec, wallet signature, email and password or phone number and password.

Once logged into the account, Bitcoiners can enter their Lightning address and a Bitcoin on-chain address. Non-Bitcoiners enter their financial data in case they win.

Miners must enter a Bitcoin and Lightning (or ecash) address. The pooling process is also managed in the miner's account.

Tickets can be purchased (like in a regular online shop) and paid for in any way. Zaprite could be a solution here. But also Strike, Cashapp, etc. As described above, such purchases could also be automated.

Retailers can also register as such. They will then have the opportunity to sell "tickets" to their customers and collect the money in cash. To sell tickets, they must enter the customer's name and a valid email address. After payment, they must send the purchase price via Lightning to the non-profit company, which will then confirm the purchase to the ticket buyer and the retailer with all the data. This is the receipt for the buyer. In the event of a win (the mined block must have 3-6 block confirmations), the ticket buyer will receive an email explaining all the further details of how to claim the prize. This could be a link that takes them directly to the website and logs them in directly. The winner can then enter their data on how and where the money should be paid out (Bitcoin address or bank details). Alternatively, they can go to their retailer, who can assist them by entering the data in their sub-account (customer account). To prevent the retailer from falsifying the data entry, the winner will first receive an email with the entered data, which they can confirm (if correct). Since the retailer is also involved in the win, they will also be notified.

How many tickets can be offered per round (Bitcoin block)? The number of tickets depends on the hash rate in the pool. One ticket can be issued per 1 TerraHash (TH/s). How the ticket is generated per round and customer, I don't know, as I lack the technical knowledge. Maybe as a kind of NFT that contains the corresponding data (customer number (npub) of the buyer and possibly retailer, block number, ticket number). Or as a Taproot asset on Lightning? Or as a minted ecash coin? Or simply as an entry in a database that the customer can see in their account.

The maximum payout of the winnings in the event of a found block to the ticket holders could be 70%. The remaining 30% would be distributed to the miners and retailers. For example: Miners 25%, retailers 5%. The non-profit organization receives nothing from the block rewards. Instead, it receives 65% of the revenue from all ticket sales. With a mining pool hash rate of 10,000 TH/s, where all tickets are sold continuously, a daily donation of around 93,000 USD would be generated. (see Excel.file)

The revenue, after deducting the possible costs of the organization, goes directly to @opensats and/or other organizations that support the Bitcoin network after each block. Either via Lightning or Bitcoin on-chain payment.

In the attached Excel file, you can find my calculations. Here, anyone can play through different scenarios.

What I noticed was that with maximum ticket sales per block, only around 200 USD per 10 tickets would be paid out, since each participating ticket wins in the event of a found block. Since I believe that this is not a very great incentive for buying tickets, I suggest the following variants.

Winning variants: Each purchased ticket has a running number. Ticket 1 has the number 000.000, ticket 2 has the number 000.001, ticket 10.120 has the number 010.119, and so on.

If the next block is found, then this found block in the Bitcoin blockchain has a hash. For example, block 881367 has the hash 000000000000000000014b0fab24355c71c6940584d9cd5990c0b081a31d54a4

Let's now remove the letters and read only the numbers from back to front, so the last 3 numbers are 544

Instead of every participating ticket winning, in this variant, only the tickets with the ending digits 544 win.

With, for example, 11,000 tickets sold, the ticket numbers 000.544 / 001.544 / 002.544 ... 010.544 would win. So, 11 ticket participants would win. Each winner with this number would receive around 0.284 Bitcoin (3.125 BTC / 11).

One could also let the ticket numbers with the ending digits 44 win, and thus every hundredth ticket. Or even combine it.

What I also noticed was that with retailers, a special case arises. Retailers receive 5% of the block rewards in the event of a found block. But only proportionally to the tickets sold by the retailer. This means that in order for the entire 5% to be distributed to the retailers, all 10,000 tickets of 10.000 possible tickets would have to be sold by retailers. Since not all tickets will be sold by retailers, a remaining amount will be left over. This could be distributed additionally to the miners. Or any other variant.

I hope the idea finds resonance and invites discussion. Maybe I've made some mistakes in thinking, and the idea is not feasible. But if you like the idea, please forward it to developers, investors, and others you know.

Stay humble hash sats

@nostr:npub1uf3w6w3z4kxy0zc80m6a03tt9s7855c9r8kkjmkju47xtc28l09sc30gqq

Excel sheet for download

@ 26bb2ebe:70530958

nostterに画像最適化機能つけたよ（サーバー編）

この記事はNostr Advent Calendar 2024 の3日目の記事です。

あまり技術的な話はないので暇つぶし程度に読んでみてください。

どうしてこうなった？

そもそも認証の改善以前にNostrあんまり人が増えてないのが一番課題だよねと思ったのが始まりでした。 Nostrに人が増えないのはオーガニック検索流入が少ないからに違いないと特に根拠もなく思ったのでNostrのまとめサイト(Toggeter)のようなものを作ろうと考えました。

ところでNostrのまとめを行うアプリ自体は鎌倉さんという方がノスリというのを作成されていました。ブログ形式のイベントにTwitterライクな短文投稿をまとめるというものでまさしくToggeterですが、そこまで活用されていません。 そこでその仕組みをありがたくそのまま転用してまとめ記事を何らかの方法で量産しつつ、一つのドメインのサイトにまとめてSEOもなんかうまいことやれば検索流入増えるんじゃねという目論みです。

ところでそのまとめサイトは静的サイトジェネレータで（SSG：Static Site Generator）でつくりたいなと思いました。いや普通に考えてSSRにしてサーバ側でNostrからデータとってきたらSEO的にもよくねって感じなんですが、SSRでサーバーでウェブソケット呼ぶのだる…レイテンシを考慮すると結構不利じゃないかなと思ったわけです。うそです。そこまで考えてなくてほとんど個人的な好みです。（多分ちゃんとキャッシュきかせればそんなにレイテンシ問題にならなさそうな気がする）。ただキャッシュとかも考慮すると結構複雑な気はする。

ということで今年の6月頃にNostrのブログ記事をSSGするサイトをためしに作りました。 去年のアドベントカレンダー記事とか乗っけてます。

全然画像最適化の話になりませんね。もうちょっとです。

SSGのブログといえばGatsby（今は下火かも）とかで作成した経験があります。Gatsbyでは画像用のプラグインが公式に用意されていて生成されたブログに表示される画像はもとの画像データから変換され、表示時のサイズに最適化されたサイズにリサイズすることができます。

それだけではなくサイトの初期表示時には画像の画質を落としてぼやけた画像を表示してその後元画像が読み込まれたらきれいな画像を表示する、みたいなことができます。インラインでデータを持っているのでHTMLの表示と同時に画像の初期表示ができたりします。（その頃はよくわかってなかったがNostrのNIP-92で定義されているblurhashとかを使っていたんでしょう多分）

とにかくSSGは初期表示の速さが良い。というのが自分の頭の中にあるわけです。SSGのブログをNostrで作るとなると当然同じことがやりたい。

しかし、Nostrの画像はただのURLです。(オプショナルで画像のメタデータを定義できるimetaタグはあるが…)

基本的にSSGの画像最適化というのはローカルに存在する画像データをビルド時に変換するという流れで行われます。もしくはリモートURLに画像が置かれる場合は画像ストレージサービスやCDN上で配信されるときに最適化されることになります。

参考: Svelteの画像ベストプラクティス

Nostrの画像はただの外部のURLですから(2回目)、ローカルの画像を変換する方法は採用できないわけです。無理やり実行するならビルド時にURLからすべての画像を一旦ダウンロードして変換するとかも考えましたが、ただの外部URLというのはつまりは一体どういうファイルなのかダウンロードしてみるまでわからない、要するに全然信頼できないということですから、よくわからないURLをかたっぱしからダウンロードするようなことは避けたいわけですね。（極端な話100GBの画像URLとかつくって攻撃されたら破綻しますよね）

ここが結構他の中央集権的なSNSと違って辛いところなのかなと思います。X（Twitter）とかであれば画像ストレージサーバは一つなので表示される画像の形式も一つに限定されるのですが、画像のアップロードが外部頼みでただのURLなので（３回目）何が来るかわからないということですね。

サーバ側で画像形式などを制限できない(imetaも信頼できるかわからない)となるとクライアント側でなんとか対応する必要があり、Nostrはクライアント側が大変なプロトコルだなあとということに思いを馳せていましたが、いろいろ考えたり調べた結果として作るべきものは画像最適化のためのプロキシサーバであるということがわかりました。

プロキシサーバというのはここでどういう働きをするのかというと、もとの画像がおいてあるサーバとクライアントのあいだに入って、もとの画像を一旦ダウンロードして圧縮したり縮小したりしてそのあとクライアントに送ってあげるという働きをします。

プロキシがないとき

[画像置き場] -> [クライアント]

プロキシがあるとき

[画像置き場] -> [プロキシ] -> [クライアント]

利点としてはクライアントが実際にダウンロードするのはサイズの小さな画像になるので通信量や画像の表示スピードは改善します。が、一方でサーバを経由する分通信にかかる時間（レイテンシ）が長くなります。というわけなので、当初の目的である表示速度の改善を実現するには、画像をエッジキャッシュするなどの対応が必須となります。平たく言うと一度送った画像はプロキシで保存しておいて次に要求されたらそれをすぐ返すということです。

画像をどれくらいのサイズにするか、画質はどうするかなどはプロキシに指示してあげれば良いのでクライアント側は想定通りの画像を受け取れてハッピーということになります。嘘です。ある程度はハッピーですが、プロキシ自体がエラーを返す可能性もあるし、処理できなくてもとの画像をそのまま返す場合もあります。そんなあれこれの結果、クライアントはフォールバック処理を実装する必要がありました。（それはまた別の記事で）

一方で自分はNostrのモバイルクライアントのヘビーユーザですので、Nostrの通信量の多さも解決したい課題でした。Nostrやってるとすぐギガがなくなります。 通信量の多さのボトルネックはウェブソケットで送られるNostrのイベントの通信量というよりは投稿に添付される画像のダウンロードの方ではないかという話もTLで耳にしたため（特に裏もとらず）、いっちょ画像最適化のプロキシサーバを作ってクライアントに実装してプルリクエスト投げるかと考えました。

そこで私はまずクライアントをAmethystからnostterに乗り換えることから始めました。なぜならばAmethystよりもTypeScriptとSvelteで書かれているnostterのほうがコントリビュートしやすかったという私的な事情です。

解決したい課題

遠回りしてきましたが課題はこれ。

• Nostrの画像の表示改善
• Nostrの通信量の改善

インターフェイス(設計)

画像最適化のプロキシは実装よりもインターフェースを考えるのが大変です。ここはとても苦労しそうな気がしたので、何も考えず cloudflare Imagesのインターフェースをそのまま借用することにしました。

https://developers.cloudflare.com/images/transform-images/transform-via-url/

また何かあってもcloudflare Imageに課金して乗り換えることが可能という利点もあります。

実装

とにかく時間がないので手グセでかけるTypeScriptかJS。かつ課金しないで可用性を維持できる無料枠のサーバレス環境が使いたかったので cloudflare workers に目星をつけて調査したところ、非常に素晴らしい記事を見つけましたのでこのwasmのライブラリをTSから呼び出して使わせていただくことにしました。

自分の実装したところはURLのパースと、キャッシュAPIの呼び出しを行って、最後にこのライブラリを叩くだけです。 ほかはクライアントキャッシュ用のヘッダーを書き換えたりとか細かいことはやっていますが全く大したことはやっておらず、サーバは非常にリーズナブルにやりたいことを実装した形になりました。 大変助かりました。

実装したものがこちらです。

https://github.com/ocknamo/nostr-image-optimizer

実装後の課題

このプロキシただのパブリックAPIなのでDoS攻撃に弱いです。何回もAPIをたたかれたら無料枠をすぐに超えてしまうことが容易に想像できました。 無料枠超えても使えなくなるだけで破産はしないので安心ですが、しかし対策は考える必要があります。

WAF

WAFです。APIに対するリクエスト回数などに対する制限をIPごとにかけています。また攻撃された場合検知できれば特定のIPや地域をブラックリストに入れることも可能です。

細かいことを説明してギリギリを攻めて攻撃されても困るので細かく説明しませんが、当初は全力でDoS攻撃されても無料枠超えないくらいの感じで制限をかけていました。 しかしNostrのTLをちょっと早めに表示するとすぐにWAFに引っかかってエラーになるという状態になることもあり、結局アイコンの表示は画像最適化の対象にしない方針にするなどの影響がありました。

いろいろあって、前提が変わり、もう少し制限をゆるくしたのでアイコンの対応は今後は検討できるかもしれません。

まとめ

割と手抜きで作ったことがわかるかと思います。実装しててNostrへの貢献ではあるはずですが、Nostrのプロトコル(NIPsとか)全然関係ないことやってるなと思いました。

フロントについては来週書きます。

次回のアドベントカレンダーの記事は eyemono.moe さんによる”クライアント自作を通して得られた知見まとめ”ですね！楽しみです！

@ c230edd3:8ad4a712

Chef's notes

This recipe is not my own, but it was great and easy, so I'm moving it here. Cooking as instructed serves 2, but this could easily be adjusted to include stir fry vegetables and rice, to make this a meal for 4.

Details

• ⏲️ Prep time: 15 minutes, 1-24 hours marinating
• 🍳 Cook time: 10-15 minutes
• 🍽️ Servings: 2-4

Ingredients

• 1 Venison Heart (elk would work well, too. recipe would need to be doubled)
• 1/2 Asian Pear, grated
• 2 Cloves Garlic, grated
• 1 Tbsp Ginger, grated
• 3 Tbsp Soy Sauce
• 1 Tbsp Honey
• 1 Tbsp Onion, grated
• 1 Tbsp Toasted Sesame Oil
• 1 tsp Red Pepper Flakes
• 2 Shallots, chopped
• Sesame Seeds
• Cooking Oil

Directions

1. Mix all ingredients besides heart, shallots, sesame seeds and cooking oil in a medium bowl.
2. Remove arteries and excess fat from heart, cut in half and rinse
3. Cut into thin slices or bite size pieces
4. Add to marinade, mix and cover. Allow to soak for 1-24 hours.
5. Heat oil in large frying pan over med-high to high heat
6. Drain excess marinade.
7. Place heart in pan and sear on both sides to desired doneness. Medium rare is ideal for heart.
8. Remove from pan and garnish with chopped shallots and sesame seeds. Serve with stir fry veggies and rice, if desired.

@ a012dc82:6458a70d

The cryptocurrency landscape is witnessing a remarkable resurgence, with Bitcoin once again leading the charge. After a period of volatility and uncertainty, Bitcoin has reclaimed its throne as the king of cryptocurrencies, drawing renewed interest from investors and financial experts alike. This article delves into the factors behind Bitcoin's comeback, its implications for the market, and what the future might hold.

Table Of Content

• The Remarkable Recovery of Bitcoin

• The Ripple Effect on the Crypto Market

• Investor Sentiment: Cautious Optimism

• The Future Outlook: Opportunities and Challenges

• A New Era for Bitcoin

• Conclusion

• FAQs

The Remarkable Recovery of Bitcoin

A Surge in Value

After a tumultuous phase marked by sharp declines and skepticism, Bitcoin has made a striking comeback. The digital currency's value has seen a significant upswing, reminding investors of its potential as a high-reward, albeit high-risk, asset. This recovery is not just a numerical increase but a symbol of resilience in the face of market adversities.

Driving Factors

Several factors have contributed to Bitcoin's resurgence. These include an increase in institutional adoption, technological advancements within the blockchain ecosystem, and a growing recognition of Bitcoin as a 'digital gold' amidst economic uncertainties. Moreover, regulatory clarity in some regions has provided a more stable environment for cryptocurrency investments.

The Ripple Effect on the Crypto Market

Boosting Market Confidence

Bitcoin's rebound has had a ripple effect across the entire cryptocurrency market. Altcoins and emerging digital assets have also seen a boost in both value and investor interest. This resurgence has rekindled the enthusiasm for decentralized finance (DeFi) and non-fungible tokens (NFTs), which had waned during the market downturn.

Impact on Blockchain Innovation

The renewed interest in Bitcoin has spurred further innovation in blockchain technology. Developers and entrepreneurs are increasingly exploring new use cases for blockchain, expanding beyond traditional financial applications to areas like supply chain management, digital identity, and more.

Investor Sentiment: Cautious Optimism

Institutional Investors' Role

Institutional investors, once wary of Bitcoin's volatility, are now more open to including it in their portfolios. This shift is partly due to the improved infrastructure and regulatory frameworks that make investing in Bitcoin less risky than in its early years.

Retail Investors' Perspective

Retail investors, who were significantly affected by the previous market downturn, are approaching Bitcoin with cautious optimism. Many are drawn by the potential for high returns but remain mindful of the risks involved.

The Future Outlook: Opportunities and Challenges

Potential for Growth

With its current momentum, Bitcoin has the potential for further growth. Its evolving role in the financial ecosystem, particularly in areas like digital payments and remittances, suggests a bright future.

Navigating Challenges

However, challenges remain. Regulatory uncertainties, potential market manipulations, and the environmental impact of Bitcoin mining are issues that need addressing. How these challenges are managed will significantly influence Bitcoin's trajectory.

A New Era for Bitcoin

A Testament to Resilience

Bitcoin's comeback is a testament to its resilience and the enduring faith of its supporters. It has not only reclaimed its position as the leading cryptocurrency but has also reinforced the belief in the potential of digital currencies.

A Dynamic Future Ahead

As investors, both institutional and retail, continue to take notice, Bitcoin's journey is far from over. Its ability to adapt, innovate, and overcome challenges will shape not just its future but also that of the broader cryptocurrency market. The current phase is just the beginning of what promises to be a dynamic and transformative era for Bitcoin and digital currencies as a whole.

Conclusion

Bitcoin's resurgence marks a significant milestone in the cryptocurrency world. Its ability to bounce back from adversity and regain its status as the leading digital currency has not only bolstered investor confidence but also highlighted the growing maturity of the crypto market. As Bitcoin continues to evolve, navigating through regulatory landscapes and technological advancements, it stands as a symbol of innovation and resilience in the ever-changing world of finance.

FAQs

Why has Bitcoin's value surged recently? Bitcoin's value has surged due to factors like increased institutional adoption, advancements in blockchain technology, and its growing recognition as a digital store of value amidst economic uncertainties.

How has Bitcoin's recovery affected the overall crypto market? Bitcoin's recovery has positively impacted the entire crypto market, boosting the value of altcoins and reigniting interest in decentralized finance (DeFi) and non-fungible tokens (NFTs).

Are institutional investors now more interested in Bitcoin? Yes, institutional investors are showing increased interest in Bitcoin, thanks to improved investment infrastructure and clearer regulatory frameworks.

What are the main challenges facing Bitcoin in the future? The main challenges include regulatory uncertainties, potential market manipulations, and the environmental impact of Bitcoin mining.

Is it safe for retail investors to invest in Bitcoin now? While Bitcoin offers potential high returns, it remains a high-risk investment. Retail investors should approach with caution and consider diversifying their investment portfolio.

That's all for today

If you want more, be sure to follow us on:

NOSTR: croxroad@getalby.com

X: @croxroadnews.co

Instagram: @croxroadnews.co

Youtube: @croxroadnews

Store: https://croxroad.store

Subscribe to CROX ROAD Bitcoin Only Daily Newsletter

https://www.croxroad.co/subscribe

DISCLAIMER: None of this is financial advice. This newsletter is strictly educational and is not investment advice or a solicitation to buy or sell any assets or to make any financial decisions. Please be careful and do your own research.

@ 3369d0a7:eb020757

Chef's notes

This recipe was a staple at every thanksgiving with family and now I share it with you nostr family. Absolutely one of my favorite side dish during the holiday. The corn pudding in the photo is NOT baked, I will update it. I hate stock photos.

Details

• ⏲️ Prep time: 15-20 min
• 🍳 Cook time: 30-40 min
• 🍽️ Servings: 6-8

Ingredients

• 2 cans of creamed corn
• 2c Milk
• 1 Box of Jiffy Cornbread Mix
• 3 eggs
• 1/4-1/3c sugar
• 1/2- green bell pepper or pepper onion blend
• 1/4TBsp vanilla
• 1/2tsp Salt
• 2TBsp Butter

Directions

1. Grab medium saucepan and desired baking dish at least 9x9
2. Place saucepan on medium-high heat
3. Add butter and sauté pepper onion blend until tender
4. Combine milk, eggs, sugar and vanilla, mix well
5. Lather warmed (NOT HOT) baking dish with butter
6. Sprinkle half a box of Jiffy corn bread mix in the baking dish
7. Add both cans of creamed corn to peppers and onions
8. Pour wet ingredients into slightly cooled creamed corn mixture
9. Sprinkle the other half box of jiffy mix into the baking dish
10. Incorporate the wet and dry ingredients in dish so there are no dry lumps
11. Let set for 10 min before placing in a 325 degree oven for 30-40 minutes, until the center is solid and the edges are golden brown.

@ df478568:2a951e67

Garlic Cashew Recipe

I wrote about selling roasted cashews as an experiment in capitalism here. I make them myself and in the spirit of free and open source software, I figured I would open-source the recipe with a catch. You can get the recipe in one of two ways.

1. Become a paid subscriber to my Substack and you will get a key to unlock the cipher text
2. Read it in the clear(un-encrypted) on nostr. The easiest way to do this is to navigate to primal.net in your browser and search for “marc26z.” Click on my profile and *you can find all of my writing in the clear in the reads section.

I tried using PGP in another article, but it’s a little cumbersome and pretentious. Andreas Grifin said, Nostr is what PGP should have been. A web of trust with easy-to-use encryption and verification. I tend to agree. So I’m using something else.

https://8gwifi.org/CipherFunctions.jsp

Decrypt using the passphrase below the paywall.

"To encrypt is to indicate the desire for privacy, and to encrypt with weak cryptography is to indicate not too much desire for privacy.”

I do not indicate a desire for too much privacy here, but I like playing with these things. I hope you enjoy playing with them too.

How To Decrypt

1. Go to https://encrypt-online.com/decrypt/ on your favorite web browser.
2. Choose aes-256-cbc(this is the default setting)
3. Copy and paste the cipher text into the decryption field
4. enter the passphrase into the passphrase field
5. press the Decrypt button
6. Optional: Copy and paste the decrypted recipe into a markdown editor like https://dillinger.io/

U2FsdGVkX1+4jxMfWCc6kNsbDa0i/J3eiV81r7/z5c0Eqe73vw01M22uRFm9PjRRaj/CJN+BidtuNXQW6G3hk3S/4AoGN2gKfKkKSbzEHsONZ2LeXuoPflikratDU+lADVeR5IlsVaATyImBO0k/cXq54TOlEXBoVRCIqaA9tO8UA126GfTdmegXX14jUcdV9EISSGw8Bn5fksptm6qKyz2GsmyiKcmNczh8Nz7biyhCrnrt2hyLDbirIAjZcCTJjkAlJjrrvuLHJZx6pmq6MsMv2eHT35d/WL/+ZpBgLVh2Xq2u+J9izNKYMgvMSsJKylC7MJvj4xAOosJuq9IyGN6b/7z2UTSsR13Utc8aFeW3zxtkvAqYthh7XV1H2e1nEKOij8gOfFHvlfj10IiG0g3QbEch1nTTGq3Lncql9Q1a9QZb5pcsellPWeR4vhko3ssdxzIkLnvGz5Cjy1brMjZ97j7sSmHE9FT10L4L6ijXWuW25ikDRK0xnks0VfAvDVz75NCE+Qaz9MLPt8h0ESto3bTyuXrHFNNPOxnaEDw4TvSTN5G0tmUrqotRMmu5DadAm6aLMmJHL1OHVNGK4fH7Hb9S+7dBLEbQG3vRivz2SzpqgKFnFYwMJTQykUC3

Passphrase: implored-junker-requires

Here is the decrypted recipe if you do not wish to learn about encryption, but want to try my delicious non-vegan cashew recipe anyway.

1 LB organic raw cashews 2 TBS beef tallow 2 TBS salt 1 TBS garlic powder

Melt tallow in the microwave Brush the tallow on the nuts. Spread onto a cookie sheet.

Preheat oven 350 degrees

Bake for 10 minutes.

Let cool.

Violá!

Enjoy your garlic-roasted cashews. Or...you can pick some up at nostr:npub1marc26z8nh3xkj5rcx7ufkatvx6ueqhp5vfw9v5teq26z254renshtf3g0

A Crumby Commercial

npub1marc26z8nh3xkj5rcx7ufkatvx6ueqhp5vfw9v5teq26z254renshtf3g0

881,805https://mempool.marc26z.com/block/00000000000000000000f5d9aa481b8f2555deaa8638a3c1f2eb4ffa8f474f9d

Merch

@ cbaa0c82:e9313245

TheWholeGrain - #January2025

This January we really got to start the story telling of our first adventure series painted by Dakota Jernigan a.k.a. The Bitcoin Painter! The typical Singles of the month were released on Sunday along with a special Single released on the first to celebrate the New Year! Here we go, 2025! And, even with all that the monthly Concept Art, Bitcoin Art, and the newest Cover Art from Toast's Comic Collection were all still released! Not only was the first month of 2025 quite packed full of fun content, but the Bread and Toast website got a makeover! Did you notice all the explanation points!? We're all so excited we just can't help ourselves from using them!

January Sunday Singles 2025-01-01 | Sunday Single 73 Title: Happy New Year 2025 Happy New Year! What a year 2024 has been! We can’t wait to see what 2025 has in store for us! https://i.nostr.build/QFTmeR5p2FthPMXp.png

2025-01-05 | Sunday Single 074 Title: Snowflake It’s the most beautiful snowflake Toast has ever seen… until this one melts then it’s on to the next one! https://i.nostr.build/YHGeOcYv8WEP1fAf.png

2025-01-12 | Sunday Single 075 Title: Weight Lifting End-Piece has been working out since last year’s resolution. Now, time for heavy lifting! https://i.nostr.build/8lxeovAr5aK598Ze.png

2025-01-19 | Sunday Single 076 Title: Good Morning GM, Everybody! https://i.nostr.build/9jn2D2if4sFfNXzU.png

2025-01-26 | Sunday Single 077 Title: Chess When it comes to the chessboard, Bread is King. https://i.nostr.build/LZq57iL7tOWbHAKc.png

Adventure Series: Questline Bread, Toast, and End-Piece have started their journey in Grain Valley, and they have already found themselves in what used to be a village that is now been burnt to a crisp!

Writer: Daniel David (dan 🍞) Artist: Dakota Jernigan (The Bitcoin Painter)

2025-01-14 | Questline 001 - The Adventure Begins Our heroes take their first steps upon one of the oldest paths in all of Grain Valley. They can see the mountains in the background of the landscape before them. As they walk, they see in the distance ahead of them large amounts of black smoke rising until it disappears into the sky. https://i.nostr.build/ygjmYlWAZ4uPfPCn.png

2025-01-28 | Questline 002 - A Village Burned The source of smoke surrounds our heroes as their path brings them to the center of what used to be a village. It seems to be completely abandoned with no signs of life. Yet, all the remains of the village appear to have only recently burned to a crisp. What could have possibly happened here? https://i.nostr.build/BJ4L1shKh5YERzWc.png

Other Content Released in January 2025 2025-01-01 | Toast's Comic Collection Title: Iron Bread #9 "I am Iron Bread." - Tony Starch https://i.nostr.build/QJKkDCbfgc6Vqzcq.png

2025-01-08 | Concept Art Title: Second Bread Sketch A second sketch of the character Bread. Remade and cleaned up. https://i.nostr.build/4TXIRSUGA6viEaJx.png

2025-01-15 | Bitcoin Art Title: Stack Sats Toast is constantly stacking sats! https://i.nostr.build/txxkux0oJqyjNcSL.png

Thanks for checking out the fifth issue of The Whole Grain. The Whole Grain is released on the first of every month and covers all of the content released by Bread and Toast in the previous month. For all Bread and Toast content visit BreadandToast.com!

Thanks for helping us kick off 2025! Bread, Toast, and End-Piece

BreadandToast #SundaySingle #Questline #ToastsComicCollection #ConceptArt #BitcoinArt #Bread #Toast #EndPiece #Artstr #Comic #Cartoon #NostrOnly #🖼️

List of nPubs Mentioned: The Bitcoin Painter: npub1tx5ccpregnm9afq0xaj42hh93xl4qd3lfa7u74v5cdvyhwcnlanqplhd8g

dan 🍞: npub16e3vzr7dk2uepjcnl85nfare3kdapxge08gr42s99n9kg7xs8xhs90y9v6

@ 2fb77d26:c47a6ee1

In H. G. Wells’ Roman Die Zeitmaschine und den diversen Verfilmungen werden sie als »ausschweifend, langsam und naiv« dargestellt. Von »untermenschlicher Intelligenz« gezeichnet. Für Dan Simmons sind sie »faul, ungebildet und unkultiviert«. Die Eloi. Die als Nahrungsquelle der Morlocks gehaltenen Nachfahren des Homo sapiens. »Sie entwickeln sich rückläufig und verlernen Jahrtausende von Kultur, Denken und Vernunft, bis sie sich mit dem Vergnügen des bloßen Daseins zufrieden geben«. Ertönt das Schlüsselsignal, auf das sie von ihren Züchtern konditioniert wurden – eine umgebaute Zivilschutzsirene – trotten sie freiwillig und in hypnotischer Apathie zur Schlachtbank.

Ein ähnlichen Eindruck hatten viele Maßnahmenkritiker von den Unterstützern der mittlerweile in allen Punkten widerlegten Covid-Propaganda. Zurecht. Das Gefolge von Drosten, Lauterbach und Co. war blind für Fakten und ist ins offene Messer gelaufen. Bedauerlicherweise verhalten sich viele Maßnahmenkritiker aber nun in weiten Teilen genauso. Sie haben Idole gefunden. Wollen glauben. Sie ignorieren Informationen, Fakten und Daten und werden Opfer einer neu justierten, gut geölten Propagandamaschine. Nur, um die in ihre neuen Helden gesetzten Hoffnungen nicht aufgeben und der wenig erbaulichen Realität nicht ins Auge blicken zu müssen.

Sie glauben an Donald Trump, Javier Milei, Alice Weidel, Peter Thiel und vor allem Elon Musk. Daran, dass der supranationale Nachhaltigkeitskorporatismus am Ende sei, das Finanzsystem gerettet und Gerechtigkeit hergestellt wird. Die Widerständler von gestern sind die »Schlafschafe« von heute. Sie scheinen vergessen zu haben, wie Propaganda funktioniert. Aus diesem Grund – und weil es ein so schön griffiges Wort ist, bei dem man nur einen Buchstaben verändern muss, um daraus den Vornamen eines vermeintlichen Heilsbringers zu basteln – erlaube ich mir, die Anhänger des MAGA-Kults im Zuge der folgenden Seiten mokant als Eloi zu bezeichnen. Ein bisschen Spaß muss sein.

Kurskorrektur mit Ansage

Lynn Forester de Rothschild, in der finanzoligarchischen Hackordnung mindestens eine Ebene über BlackRock und Co. anzusiedeln, kündigte den aktuellen Narrativwechsel bereits am 30. August 2023 an, als sie bei Bloomberg sagte, der Begriff »ESG gehöre in die Tonne«. Er sei verbrannt. Auch BlackRock-CEO Larry Fink, der Marktteilnehmer zur Unterstützung von ESG »zwingen« wollte, teilte seinen Investoren bereits am 26. März 2023 mit, das in Verruf gekommene Label ESG durch den Begriff »Energiepragmatismus« zu ersetzen.

Sowohl Rothschild als auch Fink räumten aber gleichzeitig ein, dass sich die übergeordnete Agenda nicht ändern und man die »Green Economy« weiter vorantreiben werde, man diese aber besser vermarkten müsse, um konservative Kreise nicht weiter gegen sich aufzubringen. Ein simpler Marketing-Trick. Wenig überraschend also, dass sowohl BlackRock als auch sechs amerikanische Großbanken Anfang 2025 die Net Zero Initiative verließen. Zum »perfekten Zeitpunkt«, wie die New York Post bemerkt, um nicht von der negativen, anti-woken Berichterstattung rund um die verheerenden Feuersbrünste in Los Angeles tangiert zu werden.

Es scheint, als hätten die Eloi bereits wieder verdrängt, dass die WEF-Meetings 2021 und 2024 unter Arbeitstiteln wie »The Great Narrative« und »Rebuilding Trust« liefen. Artikuliertes Ziel der Davoser PR-Abteilung für Globalisierungsfragen war nämlich, sich den zunehmend echauffierten, misstrauischen Pöbel vom Hals zu halten. Durch neue Narrative und vertrauensbildende Maßnahmen. Und das hat, zumindest vorerst, ausgezeichnet funktioniert.

In den USA stieg das Vertrauen in ordnungsgemäß durchgeführte Präsidentschaftswahlen 2024 zum ersten Mal seit Jahren wieder etwas an. In Europa macht sich ebenfalls Zuversicht breit. Schließlich haben die sogenannten »Rechtspopulisten« nicht mehr nur in Italien und Ungarn, sondern auch in Finnland, der Slowakei und den Niederlanden Oberwasser. Von den Erfolgen der AFD ganz zu schweigen. Diese führen, wie zuletzt in Thüringen, trotz klarem Wählervotum zwar nicht zur Regierungsbeteiligung, weil »demokratische Prozesse« und »Brandmauern« das zu verhindern wissen – aber dabei sein ist ja bekanntlich alles. Dass Friedenstreiberin Alice Weidel den bundesdeutschen Rüstungsetat auf knapp 200 Milliarden verdoppeln will, scheint die euphorisierten Kritiker dunkelgrüner Militarisierung auch nicht auszubremsen. Hauptsache nicht grün. Oder woke.

Überstaatliche Sphären

Dabei scheint Euphorie in Anbetracht der Tatsachen alles andere als angebracht. So hat Milei nach Angaben von Global Finance zwar das argentinische »Staatsdefizit nach 123 Jahren beendet«, dafür leben heute 53 Prozent der 45 Millionen Argentinier in Armut. Der höchste Wert seit 20 Jahren. Ende 2023 waren es noch 41,7 Prozent. Daran ändert auch semantische Schützenhilfe von libertären Denkfabriken wie der Hoover Institution nichts. Die radikalen Privatisierungsfeldzüge von »El Loco« haben einen hohen Preis. Ob Aerolineas Argentinas, die staatliche Fluglinie, der Stahlproduzent IMPSA oder das Transportunternehmen Trenes Argentinos Cargas, das 7.800 Kilometer Bahnstrecke betreibt – das Volksvermögen wird an die Meistbietenden verscherbelt. Wer das ist, kann sich wohl jeder ausmalen. Denn sein Schlachtruf »Afuera!« (Raus hier!) gilt augenscheinlich nicht für BlackRock und Co. – schließlich sei Argentinien »ziemlich billig« zu haben, wie es Rick Rieder, Top-Bond-Manager des Unternehmens schon 2019 formulierte.

Man muss allerdings nicht in die Ferne schweifen, um sich der realen Gefahren für die Freiheit bewusst zu werden. Jener Gefahren, die von Personalien gänzlich unberührt bleiben. So arbeitet die Europäische Union weiter an der eID, der Grundlage des technokratisch-totalitären Kontroll-Grids. Ihre Einführung ist beschlossene Sache. Offen ist lediglich, ab wann sie zum Obligatorium wird. Auch das persönliche CO2-Budget ist auf Kurs. Mit ETS2 (EU Emissions Trading System) nimmt die EPA (Environmental Protection Agency) seit dem 1. Januar 2025 nach der Konzernwirtschaft nun kleine und mittlere Unternehmen in den Fokus und verpflichtet diese, CO2-Kompensationsabgaben auf ihren Gas-, Benzin- und Mineralölverbrauch zu entrichten. Das dürfte Heiz-, Fracht- und folglich die Lebenshaltungskosten des Bürgers in neue Höhen treiben. Bis der Sonntagsausflug mit dem Familienauto nicht mehr nur Zeit, Benzin und Nerven, sondern auch CO2-Gebühren kostet, dauert es also wohl nicht mehr allzu lange.

Dieser überparteilichen, supranational koordinierten Überwachungs- und Enteignungsagenda ist weder durch die Wahl des geringeren Übels noch durch Auswandern zu entkommen. Denn wie sich der Internetpräsenz des »Global Governance Forum« (GGF) entnehmen lässt, wird bereits eifrig an »Global Government« gearbeitet. Die UN-nahe Nichtregierungsorganisation hat sich nämlich zum Ziel gesetzt, die Charta der Vereinten Nationen bis 2028 zu aktualisieren und den allseits bekannten »Herausforderungen unserer Zeit« anzupassen. Pünktlich ab 2030 soll das neue Vertragswerk ratifiziert werden und neben neuen Befugnissen für den Internationalen Gerichtshof sowie einer UN-Streitmacht auch eine Regierungsstruktur analog der Europäischen Union ermöglichen. Sprich, eine Weltregierung. Ganz demokratisch selbstverständlich.  

Neben eID und CO2-Budget sind natürlich auch die Ausweispflicht fürs Internet und die automatisierte Zensur unliebsamer Inhalte weiter auf Kurs. Nachdem die Vereinten Nationen im September 2024 bereits dem totalitären »Pakt für die Zukunft« zustimmten, wurde am Heiligabend 2024 noch rasch die neue »Konvention gegen Onlineverbrechen« durchgewunken. Und seit Januar 2025 treibt die UN die Umsetzung eines noch weitreichenderen Abkommens namens »Global Digital Compact« voran. Ein Papier, vor dem ich bereits im Juli 2023 gewarnt habe. Was all das für den Bürger bedeutet, zeigt sich in Griechenland, wo die Regierung seit Anfang des Jahres Social-Media-Konten mit Steuer-Identifikationsnummern verknüpft, um eine Alterskontrolle fürs Internet einzuführen. Damit folgt die von der EU in Kreditsklaverei gehaltene Regierung in Athen dem Vorbild Australiens, wo der Zugang so Social-Media-Plattformen künftig erst ab einem Alter von 16 Jahren erlaubt werden soll – wofür man schlussendlich jeden Nutzer kontrollieren muss, der online geht.

Auch das von vielen noch immer als Mythos abgetane Geoengineering wird derweil munter weitergeführt. Obwohl Berichte des US-Kongress und mittlerweile sogar wissenschaftliche Berater der EU-Kommission vor großflächigem Solar Radiation Management warnen. Im Rahmen eines offiziellen, 54 Seiten umfassenden Reports an die EU-Kommission sowie eines Artikels des britischen Guardian vom 9. Dezember 2024 verwies das siebenköpfige Forscherteam auf die unabschätzbaren Konsequenzen solcher Eingriffe und forderte ein EU-weites Moratorium.

Wie genau Trump, Musk, Milei, Meloni, Weidel und Co. die Welt vor diesem Sammelsurium an totalitären Übergriffigkeiten retten wollen, konnte mir bislang keiner der Eloi sagen.

DJ Trump

Warum die in Donald Trump, den »Vater der Impfung«, und sein zionistisches Kriegstreiberkabinett gesetzten Hoffnungen bald bitterer Enttäuschung weichen dürften, habe ich bereits am 14. November 2024 ausführlich beschrieben. Dass auch die beiden Hauptargumente seiner Befürworter – dass er die mRNA-Kampagne mittlerweile bereue und in seiner ersten Amtsperiode Friedenspolitik betrieben habe – schlichtweg falsch sind, ebenfalls. Denn anhand der nackten Zahlen lässt sich eindeutig belegen, dass Trump »der kriegslüsternste Präsident der jüngeren Geschichte« war. Und wie stolz er auf »Operation Warp Speed« ist, die unzählige Amerikaner Gesundheit oder Leben kostete, ließ er die Welt zuletzt am 17. November 2024 auf seinem Social-Media-Netzwerk Truth Social wissen.

Trumps Interesse gilt nicht Frieden und Freiheit, sondern Donald Trump. So war es sein ganzes Leben lang. Wenn sich »The Donald« jemandem verpflichtet fühlt, ist es vielleicht Wilbur Ross, der ehemalige Chef von Rothschild Inc. Bankruptcy Advising. Denn wie das Forbes Magazine am 8. Dezember 2016 korrekt erläuterte, rette das Bankhaus vor gut 30 Jahren nicht nur Trumps bankrotte Casinos, sondern damit auch seine ganze Karriere. Nicht weil man in Trumps Geschäften und Immobilien einen besonderen Wert sah, sondern weil man die Person Donald Trump als »Anlage« betrachtete. Trotzdem ist es sicher nur Zufall, dass Ross von 2017 bis 2021 Handelsminister der Vereinigten Staaten war.

Elon Musk

Auch über den PayPal-Mafioso, CIA-Handlanger und Bilderberg-Executive Peter Thiel, dessen Protegé JD Vance nun US-Vizepräsident ist, habe ich bereits im September 2024 einen ausführlichen Artikel geschrieben. Gleiches gilt für Elon Musk, dessen trügerisches Image als Genius, Erfinder und Entrepreneur ich sogar schon im Oktober 2022 durchleuchtet habe. Zitat:

»Dass Elon Musk nicht rein zufällig zur liberal-coolen Ikone avancierte, legt ein Blick in seine Anfangsjahre als Unternehmer nahe. Denn während im sagenumwobenen Silicon Valley Ende der 1990er-Jahre eine Vielzahl an erfolgreicheren Tech-Entrepreneuren existierte, war es ausgerechnet Elon Musk, der für einen absolut inhaltsleeren Gastauftritt bei CNN gefilmt wurde, sodass zum ersten Mal eine breitere Öffentlichkeit von ihm Notiz nehmen musste. Dabei war sein erstes Unternehmen – Zip2 –, das er im Jahre 1995 mit seinem Bruder sowie einem weiteren Partner gegründet und im Februar 1999 für circa 300 Millionen US-Dollar an Compaq veräußert hatte, nicht das revolutionärste Unterfangen im kalifornischen IT-Mekka dieser Tage. Es handelte sich um ein simples Telefonbuch fürs Internet. Wenig mehr als eine Datenbank, in die sich Unternehmen eintragen konnten, um ihre Adresse im Netz zu hinterlegen.«

Meine fast zweieinhalb Jahre alte Analyse bedarf allerdings dringend einer Aktualisierung. Denn was Musk in der Zwischenzeit trieb – und für die Zukunft plant – hat so gar nichts mit dem zu tun, was seine geradezu fanatisierten Anhänger in ihm sehen wollen.

Fangen wir der Vollständigkeit halber aber noch mal vorne an: Elon Musk hat weder PayPal gegründet noch den Tesla erfunden. Auch wenn er das gerne so darstellt. Dafür fertigte Tesla unter seiner Ägide dann aber »RNA Mikrofabriken« für das deutsche Unternehmen CureVac, das zusammen mit Bayer mRNA-Injektionen gegen Corona auf den Markt brachte. Und während Musk gegenüber der New York Post am 30. September 2020 sagte, sich nicht gegen Covid impfen lassen zu wollen, erklärte er dem TIME Magazine am 13. Dezember 2021, bereits geimpft zu sein. Zeitgeistig flexibel ist er also. Wer behauptet, Musk hätte seine Meinung zur mRNA-Technologie seit dem Covid-Fiasko signifikant geändert und sehe das Produkt nun kritisch, ist schlecht informiert. Noch am 12. April 2023 erklärte er bei Twitter, dass er mRNA für eine »medizinische Revolution« hält. Vergleichbar mit dem Schritt »von analog zu digital«.

Was Musk mit digitaler Revolution meint, zeigte sich 2017 mit Hurricane Irma. Damals gab das Unternehmen für Besitzer von Fahrzeugen mit 75 kWh ein Softwareupdate heraus, das die Reichweite von 338 auf 400 Kilometer steigerte – was im Umkehrschluss bedeutet, dass Tesla-Besitzer um eine eigentlich abrufbare Leistung ihres eigenen Fahrzeugs betrogen werden, wenn gerade keine Naturkatastrophe wütet. Dass Tesla-Kunden darüber hinaus permanent überwacht werden, zeigte sich unlängst im Rahmen der Explosion eines Cybertrucks in Las Vegas. Augenbewegungen, Mimik, Geschlecht, Hautfarbe, Körpertemperatur, Gepäckanordnung, Route, Ladestopps, Bezahlvorgänge, Telefonbuch, Musik-Playlist, Online-Abos, et cetera. Was von Sensoren und Verbindungen zu erfassen ist, wird erfasst, wie eine Untersuchung von Mozilla im Herbst 2023 feststellte. Das gilt im Übrigen nicht nur für Tesla, sondern für praktisch alle modernen Autos. Ein Tesla hat es dabei nur am leichtesten. Die gesammelten Daten werden entweder zum Schleuderpreis verkauft und/oder gegen uns verwendet.

Doch zurück zu Musk, der Twitter nicht übernahm, um Meinungsfreiheit herzustellen, sondern um die Plattform zur »Alles-App« zu machen. Sein erklärtes Vorbild: die chinesische Spionage-App WeChat. Deswegen will er alle Nutzer »als echte Menschen identifizieren«. Biometrisch versteht sich. Dafür arbeitet man bei Twitter bevorzugt mit israelischen Unternehmen zusammen, die von ehemaligen Mossad-Agenten gegründet wurden. Vielleicht stellte ja Doppelagent Jeffrey Epstein den Kontakt zum Mossad her, nachdem er Musk als regelmäßigen Teilnehmer seiner Edge-Foundation Seminare zum Thema Nudging schätzen gelernt hatte. Epstein war nämlich der einzige nennenswerte Sponsor von Edge.

Twitter kaufte Musk übrigens nicht von seinem eigenen Geld, sondern mit Hilfe von 94 Investoren, deren Namen ein US-Bundesrichter erst im August 2024 veröffentlichte, weil Jacob Silverman (Reporters Committee for Freedom of the Press) sie einklagte. Die Liste umfasst so illustre Namen wie Fidelity Investments, Sequoia Capital, Andreessen Horowitz, Bandera Fund, Binance Capital Management, Sean Combs (alias Diddy) Capital, Jack Dorsey (Twitter Gründer), Baron Opportunity Fund oder Prinz Alwaleed bin Talal al Saud von der saudischen Königsfamilie. Da wird also offenbar »der Sumpf« mit mehr Sumpf »trockengelegt«. Von der Nominierung des WEF Executive Chair Linda Yaccarino als neuer Twitter-CEO und »Freedom of Speech« versus »Freedom of Reach« mal ganz abgesehen.

Auch die von den Eloi als sensationelle Enthüllung gefeierten Twitter Files sind leider nicht ernst zu nehmen. Denn sie offenbarten nichts, was man nicht schon wusste. Zudem ist bis heute unklar, woher die veröffentlichten Informationen kamen, wer den Zugriff darauf gesteuert hat, was dort noch gespeichert war, warum praktisch nur ein von Elon ausgewählter Journalist Zugriff darauf hatte und dieser nur Screenshots, anstelle ganzer Dokumente veröffentlichen durfte. Ein echter Leak besteht aus einem Archiv, das man selbst durchsuchen kann – nicht aus ein paar handverlesenen Screenshots.

Fehlt noch Space X. Ein Unternehmen, das Musk zwar selbst gegründet hat, dessen Erfolge aber in weiten Teilen anderen Umständen zu verdanken sind. So schreibt beispielsweise inside Tesla am 22. März 2022: 

»Schon Anfang der 2000er-Jahre hatte die NASA erkannt, dass ihr bald die Möglichkeit fehlen würde, selbst Astronauten und Material ins All und zur ISS zu bringen. Man machte sich also auf die Suche nach Partnern aus der Privatwirtschaft und wurde unter anderem bei Elon Musks Space X fündig. Bereits 2006, also noch in der Entwicklungsphase der Falcon 1, erhielt Musks Unternehmen fast 400 Millionen US-Dollar Startfinanzierung unter dem COTS-Programm.«

Space X war von Beginn an als verlängerte Werkbank der NASA gedacht, weil der US-Weltraumbehörde immer mehr Mittel gestrichen wurden. Die Öffentlichkeit hatte nämlich das Interesse an ziviler Raumfahrt verloren. Daher setzte man in Washington immer öfter den Rotstift an. Doch seit Musk die Menschen öffentlichkeitswirksam zum Mars befördern will – »let’s build Marsian Technocracy« – steigt das Interesse wieder. Leider muss ich die Vorfreude auf eine planetare Kolonie aber etwas dämpfen. Denn Space X wird nicht betrieben, um Menschen auf den Mars zu bringen, sondern um das »weltgrösste Netzwerk an Spionagesatelliten aufzubauen«.

Musks Weltraumagentur ist Handlanger des militärisch-industriellen Komplexes und einer der wichtigsten Vertragspartner des Pentagon. Das konnte man 2017 schon im Observer nachlesen. Oder am 9. Januar 2018 bei CNBC, die vom (missglückten) Transport eines streng geheimen US-Spionagesatelliten berichtete. Am 15. April 2022 kommentierte Tech Unwrapped zwei weitere Spionagesatelliten des US-Militärs, die Space X in die Umlaufbahn beförderte. Seit Jahren erhält das Unternehmen Milliarden von US-Regierung und Geheimdiensten. Siehe Los Angeles Times vom 30. Mai 2015: 4,9 Milliarden. Oder ein Artikel des Wall Street Journal vom 23. Februar 2024: 1,8 Milliarden. Oder eine lange Liste von staatlichen Zuwendungen, die Business Insider am 15. Dezember 2021 veröffentlichte. Damit basiert der Erfolg von Space X nicht primär auf Musks genialem Unternehmergeist, sondern auf Subventionen. Auf Steuergeldern.

Nicht zu vergessen: Starlink. Das von Space X betriebene, weltumspannende Satellitennetzwerk. Es mag den Vorteil haben, dass damit auch Menschen in entlegenen Regionen des Planeten oder Katastrophengebieten Zugriff auf das Internet haben. Dabei sollte allerdings nicht unterschlagen werden, dass Starlink in seiner finalen Ausbaustufe circa 42.000 Satelliten umfassen und damit ein permanentes Strahlungsfeld erzeugen wird. Gesundheitliche Risiken für den Homo sapiens: unklar. Darüber hinaus haben die Orbiter Zugriff auf das NORAD-Datenbanksystem, um Weltraumschrott ausweichen zu können. Sprich, sie sind permanent mit Systemen des US-Militär verbunden. Aus diesem Grund ermöglicht Starlink auch die Steuerung von Kampfdrohnen – siehe Ukraine-Konflikt – sowie 30 mal schnelleres Senden von Daten an und von US-Kampfflugzeugen. Während die Öffentlichkeit Musks Satellitennetzwerk vor allem als ziviles Produkt betrachtet, ist Starlink primär von militärischem Interesse. Nicht umsonst wird parallel Starshield aufgebaut, das dem geheimdienstlich-militärischen Komplex unter anderem die diskrete Echtzeitüberwachung der ganzen Welt erlaubt. Auch von DEW-Fähigkeiten (Directed Energy Weapon) ist die Rede. Ende 2024 befanden sich bereits 98 solcher Satelliten in erdnaher Umlaufbahn.

In Anbetracht dieser Informationen ist es also kaum verwunderlich, dass Musk seit Jahren offen für Technokratie wirbt. Für ein zentralistisches, faschistoides Herrschaftsmodell, das schon sein Großvater Joshua Haldemann als führender Kopf in den USA und Kanada vertrat. Der Familientradition folgend empfiehlt Musk eine CO2-Steuer zum Kampf gegen den Klimawandel, ein universelles Grundeinkommen, um die von der KI ausgelösten Disruptionen abzufangen und sein Neuralink Gehirnimplantat, um dem drohenden Transhumanismus etwas Transhumanismus entgegenzusetzen.

Futurum Technologicus

Für Kunden, denen Chips im Kopf irgendwie zu altbacken sind, entwickelt Musks Unternehmen in Zusammenarbeit mit iota Biosciences natürlich ein zeitgemäßeres Premiumprodukt: Neural Dust. Intelligente Nanopartikel in Staubkorngröße, die sich im Gehirn anreichern. Die lassen sich dann wahrscheinlich – wie die in Indien bereits zugelassene Nasal-Impfung gegen Covid – durch die Nase ziehen. Oder durch Luftschächte öffentlicher Gebäude pumpen. Man kann die neue Freiheit also förmlich riechen.

Ganz wie es der 44 Seiten starke »National Nanotechnology Initiative Strategic Plan« (NNI Plan) des Weißen Hauses im Oktober 2021 vorsah: »Die Öffentlichkeit einbeziehen und Mitarbeiterzahlen im Bereich Nanotechnologie erhöhen«. Nicht umsonst hat Donald Trump der entsprechenden Behörde in seiner ersten Amtszeit zusätzliche Mittel genehmigt. Genau wie Joe Biden nach ihm.

Das von der Technokratie-Bewegung vor fast einem Jahrhundert definierte nordamerikanische Technate – sprich, der amerikanische Verantwortungsbereich einer weltweiten Technokratie – sieht der von Trump und Musk reanimierten Vision einer »nordamerikanischen Union« übrigens verblüffend ähnlich. Wen interessiert bei all der Make-Great-Euphorie schon noch, dass Imperialismus scheisse, Dänemark ein souveräner Staat und der Panamakanal ein strategisches Nadelöhr der internationalen Handelsschifffahrt ist. Oder, dass die »nordamerikanische Union« nicht nur bei Trump-Cheerleadern wie Alex Jones vor ein paar Jahren noch als »böser Globalisten-Plan« galt.

Schauen wir nach vorne. In Richtung »goldenes Zeitalter«, wie Trump es nennt. Dieses dürfte für den Normalbürger nämlich sehr ungemütlich werden. Denn es wird dominiert von Algorithmen. Von Künstlicher Intelligenz. Für die Eloi also primär von Grok, dem auf Twitter (und Teslas) integrierten Chatbot. Dieser basiert auf Technologie des Unternehmens xAI – laut Wikipedia gegründet von Elon Musk im März 2023. Das mag zwar so im Handelsregister stehen, ist wohl aber nur die halbe Wahrheit. Denn xAI dürfte die Fortführung eines DARPA-Projekts darstellen, das bereits 2015 unter dem Titel »Explainable Artificial Intelligence« (XAI) gestartet wurde und 2021 auslief. Als die Finanzierung seitens DARPA eingestellt wurde, machte XAI die Forschungsergebnisse auf einem Server zugänglich. Circa 18 Monate Jahre später engagierte Elon Musk Igor Babuschkin als Chefingenieur für xAI. Babuschkin hatte zuvor acht Jahre lang für Googles DeepMind-Projekt gearbeitet und nutzte aller Wahrscheinlichkeit nach die DARPA-Ergebnisse um xAI, beziehungsweise Grok zu entwickeln.

Im Juli 2023 verkündete Musk, xAI sei im Gegensatz zu den Konkurrenzprodukten von Google, Microsoft und OpenAI eine »gute« KI. Erstaunlich, wenn die gleichen Ingenieure am Werk sind und die KI auf Basis eines Militärprojekts entsteht. Zudem sprechen auch die Top-Sponsoren von xAI nicht unbedingt für das »Gute«. Denn unter den größten Geldgebern der letzten Finanzierungsrunde vom 23. Dezember 2024 befinden sich so illustre Namen wie BlackRock, AMD, Nvidia und Fidelity, die zusammen weitere sechs Milliarden Dollar für Musks KI-Unternehmen zur Verfügung stellten.

Genug Liquidität, um xAI für die »Alles-App« weiterzuentwickeln, wo Grok seit einer Weile automatisch Kurzbeschreibungen für Profile erstellt, die man weder abschalten noch ändern kann. Twitter-Nutzer müssen nun also nicht mehr selbst das Profil eines Accounts durchstöbern, um sich einen ersten Eindruck von der Person zu machen, sondern bekommen diesen von Elon Musks KI geliefert. Vorurteil auf Knopfdruck sozusagen. Vergleichbar mit einem Sozialkreditsystem. Denn die täglich neu generierte Zusammenfassung basiert auf dem Nutzerverhalten.

»Die neuen, KI-generierten Grok-Kurzprofile unter jedem X-Nutzerprofil SIND de facto ein Social Credit System nach chinesischem Vorbild für den Westen. Das Profil jedes Nutzers wird tagesaktuell neu berechnet. Äußert man sich zu verschiedenen Themen, nennt die KI das schnell mal »verheddern«. Grok gibt zu, das Profil wird erstellt aus dem eigenen Nutzerverhalten des Tages, seinen eigenen Berechnungen und nicht näher definierten Anweisungen«,  kommentierte Journalistin Aya Velázquez die Neuerung am 14. Januar 2025.

Andere Nutzer werden als »leicht erregbar« beschrieben, »verzetteln« sich oder »glauben an Wettermanipulation zur Klimakontrolle«. Offener wird ein Debattenraum dank solcher Adjektive und Zusammenfassungen sicher nicht. Wer möchte schon das Profil von leicht erregbaren Chemtrail-Gläubigen anschauen oder gar mit diesen assoziiert werden. Gegen solch eine automatisierte, herablassend daherkommende Einordnung durch intransparent operierende KI war die Faktencheck-Industrie geradezu harmlos. Wer also annimmt, die Abschaffung der Faktenchecker bei Facebook und Co. bedeute ein Ende der Zensur, irrt. Sie wird im Gegenteil deutlich raffinierter und weitreichender werden.

Details zum persönlichen Punktestand im Grok-Sozialkreditsystem oder Information über das Zustandekommen der Bewertung erhält man auf Anfrage natürlich nicht. Twitter wird die daraus entstehende Hierarchie aber mit Sicherheit für Reichweitensteuerung, Nudging-Kampagnen und weitere sozialarchitektonische Funktionen nutzen. Vor allem, wenn 2025 das Bezahlsystem »X Money« eingeführt wird. Dann werden die Eloi bald nicht mehr nur um Reichweite, Follower und Re-Tweets buhlen, sondern auch um Geld – das als Folge unliebsamer Postings zu Genozid X, Krieg Y oder Person Z künftig schneller eingefroren werden dürfte als jedes Bankkonto. De-Banking der nächsten Generation. Und irgendwann trifft das jeden. Außer, man schwimmt immer mit dem Strom.

Doch damit nicht genug. Am 13. Dezember 2024 gab das wohl den wenigsten bekannte Unternehmen WISeSat bekannt, künftig mit Space X zusammenzuarbeiten, um »verschiedene Produkte und Systeme zu kombinieren«. Die WISeSat AG ist eine Tochterfirma der in Genf (Schweiz) ansässigen WISeKey International Holding AG, die im Bereich Cybersicherheit, KI und IoT (Internet of Things) tätig ist. Die Ankündigung dieser Kollaboration ließ die WISeKey-Aktie kurzfristig um 107,73 Prozent steigen. Ein erster gemeinsamer Start zum Transport sogenannter Picosatelliten fand am 14. Januar 2025 von der Vandenberg Space Force Base in Kalifornien statt.

Aber was genau macht WISeSat? Einer Presseerklärung des Unternehmens vom 15. September 2023 lässt sich entnehmen:

»WISeSAT AG zeichnet sich dank ihrer Konstellation von ultra-sicheren Picosatelliten und Infrastruktur durch sichere und effektive Kommunikationsstrategien für vernetzte Geräte aus. Die Expertise des Unternehmens in kryptografischer Technologie und sicherem Datenmanagement hat die sichere IoT-Implementierung in zahlreichen Bereichen neu definiert, von städtischen Innovationen in Smart Cities bis hin zu modernster industrieller Automatisierung. (…) WISeSAT steht an vorderster Front bei der Entwicklung von ultra-sicheren Picosatelliten-Lösungen in Zusammenarbeit mit ihrem Verbündeten FOSSA Systems. Es setzt sich für sichere IoT-Kommunikation über raumbasierte Netzwerke ein und nutzt die neuesten kryptografischen Innovationen, um sichere und sofortige Datenaustausche in verschiedenen Bereichen zu gewährleisten (…).«

Im Klartext: WISeSat bringt Satelliten von der Größe einer Tupperdose ins All. Diese Mini-Orbiter umkreisen den Planeten in niedrigen Umlaufbahnen und etablieren dort ein Netzwerk für kryptografierte Echtzeitdatenübertragung. Fliegende 5G-Masten sozusagen. Oder WLAN-Router. Nur viel schneller. Für das Internet der Dinge – und Smart Cities.

»In dieser Woche startet WISeSat einen Satelliten der neuen Generation und markiert damit einen wichtigen Meilenstein in der Entwicklung einer globalen Satellitenkonstellation, die eine umfassende Erdabdeckung mit ultraniedriger Latenzzeit ermöglicht. Entwickelt, um Billionen von IoT-Geräten in Echtzeit zu verfolgen und aufzuspüren.« (Carlos Creus Moreira, WISeKEy CEO, 12. Januar 2025)

Welche Datenträger dieses Picosatelliten-Netzwerk künftig verfolgen und aufspüren soll, zeigt sich bei einem Blick auf das Produktportfolio der Holding-Gesellschaft WISeKey – einem »weltweit führenden Anbieter von Cybersicherheit, digitaler Identität und Internet der Dinge (IoT) Lösungen«. Denn die Holding existiert seit 24 Jahren, besteht aus fünf Unternehmen, hat mehr als eineinhalb Milliarden Chips und über fünf Milliarden »Roots of Trust« installiert, residiert an sechs internationalen Standorten und hat gut 3.000 Kunden in Staat und Wirtschaft beglückt. Einen Wikipedia-Eintrag gibt es für das bei NASDAQ und SIX gelistete Unternehmen erstaunlicherweise trotzdem nicht.

Dafür aber für den seit Mai 2021 amtierenden »Chief Digital Transformation Officer« Pierre Maudet. Der war ab Juni 2012 Mitglied des Genfer Staatsrats, 2013 bei den Young Global Leaders des Weltwirtschaftsforums und 2015 bei der Bilderberger Konferenz in Telfs-Buchen (Österreich). Nachdem er im Februar 2021 vom Genfer Polizeigericht wegen Vorteilsnahme verurteilt wurde, trat er als Staatsrat zurück – und drei Monate später bei WISeKey an. Am 30. April 2023 wurde er, ungeachtet seiner kriminellen Vergangenheit, zusätzlich wieder in den Genfer Staatsrat gewählt. Wie praktisch. Solch eine schamlose Unverfrorenheit scheint Maudet perfekt für das zu qualifizieren, was bei WISeKey unter dem Deckmantel der »Quantensicherheit« entwickelt wird – ein raumbasiertes eID-Ökosystem.

»Quantensicherheit nutzt Prinzipien der Quantenmechanik, um den Datenschutz und die sichere Informationsübertragung zu revolutionieren. Kernstück ist die Quantenschlüsselverteilung (Quantum Key Distribution, QKD), eine Spitzentechnologie, die mithilfe der Quantenmechanik vernetzte Teilchen für den sicheren Austausch von Verschlüsselungskennwerten erzeugt.«

Ob digitale Identität, Unterschrift, Cloud oder Software – von der Know-Your-Customer-Biometrie bis hin zur Unternehmenslösung für die Mitarbeiteridentifikation. WISeKey hilft. Anmelden kann sich jeder. Während die Produktpalette für den privaten Sektor noch nach Lieferketten-Management, Sendungsverfolgung, Login-Lösung für eBanking oder Face ID auf dem Smartphone klingt – aber deutlich weitreichender ist, schauen sie sich die Homepage an – sprechen die WISeKey-Angebote im Bereich Regierungen eine ganz andere Sprache. Denn unter diesem Menüpunkt bewirbt der diskret operierende Konzern seine »CertifyID Trust Center Platform«:

»Die CertifyID Trust Center Platform ist eine industrialisierte eID-Verwaltungslösung für Bürger, die Benutzer und ihre Anmeldeinformationen verwaltet, insbesondere digitale IDs und digitale Zertifikate für groß angelegte Anwendungen wie landesweite E-Government-Dienste. Es handelt sich um eine vollständige industrielle Public Key Infrastruktur- und ID-Verwaltungslösung, die Regierungsdienste rund um die Uhr unterstützt.

Die CertifyID Trust Center Plattform wird in einer Reihe von Anwendungen der Regierung und des öffentlichen Sektors verwendet, zum Beispiel: Personalausweis, ePassport (ICAO-konform), Führerschein, Gesundheit, Wahlen/Abstimmen.

Die CertifyID Plattform wurde unter Verwendung der Sicherheits- und Public Key Infrastruktur-Expertise von WISeKey entwickelt und kann vollständig in E-Government-Frameworks, kommerzielle Frameworks (…) und in das Bereitstellungsframework für E-Government-Dienste eines Landes integriert werden.«

Da passt es doch wunderbar ins Bild, dass WISeKey am 13. Oktober 2022 eine »Partnerschaftsvereinbarung zur Zusammenarbeit bei der Entwicklung weltraumbezogener Aktivitäten« mit der Schweizer Armee bekannt gab – schließlich residieren in der Alpenrepublik nicht nur UN, GAVI, WEF, Club of Rome und jede Menge NGOs, sondern auch die Bank für Internationalen Zahlungsausgleich (BIZ), die ganz sicher Verwendung für ein quantengesichertes Echtzeit-Picosatellitennetzwerk findet, wenn ihr »Unified Ledger« (Zentrales Hauptbuch) für das Blockchain-Weltfinanzsystem von morgen zum Einsatz kommt. In Anbetracht der »allumfassenden Marktblase« (D. Webb, 2024) ist damit wohl in absehbarer Zeit zu rechnen.

Das also sind die Projekte, Pläne und neuen Partner von Elon. Auf mich machen ja speziell die korrupten Genfer Quantenspezialisten mit ihren Picosatelliten und schlüsselfertigen eID-Lösungen nicht unbedingt den Eindruck von Freiheitskämpfern. Und auch die am 22. Januar 2024 bei einer Pressekonferenz im Weißen Haus angekündigten »personalisierten mRNA-Injektionen gegen Krebs« lassen mich eher skeptisch zurück.

Genau wie der Umstand, dass diese binnen 48 Stunden »personalisierte mRNA« durch die Rechenleistung von OpenAI ermöglicht werden soll. Denn das von Elon Musk mitgegründete Unternehmen des WEF- und Bilderberg-affinen Sam Altman steht im berechtigten Verdacht, für den Tod eines Whistleblowers im Dezember 2024 verantwortlich zu sein. Während Polizei und Medien den Tod des OpenAI-Forschers Suchir Balaji als Selbstmord deklarieren, sprechen sowohl die Umstände am Fundort seiner Leiche als auch Balajis Eltern von »eiskaltem Mord«. Nicht zu vergessen, dass Altman von seiner eigenen Schwester des jahrelangen Missbrauchs beschuldigt wird und sich dafür demnächst vor Gericht verantworten muss. Selbst The Economist räumte am 10. Dezember 2024 ein, dass »die PayPal Mafia die amerikanische Regierung übernimmt«. Und das mit der »Mafia« scheint man in Washington mittlerweile wörtlich zu nehmen.

Aber die von einigen aus der Hüfte geschossenen Präsidialdekreten euphorisierten Eloi werden sicher Gründe finden, das alles zu ihren Gunsten auszulegen. Immerhin hat Trump ein paar Leute begnadigt und will aus der WHO austreten. Wie seine Fanbase es bewerkstelligt, auszublenden, dass »The Donald« schon in seiner ersten Amtszeit aus der WHO austreten wollte und es unterließ, erschließt sich mir aber leider nicht. Genau wie die Begeisterung für ein Gespräch zwischen Musk und Weidel. Man stelle sich nur mal vor, George Soros, Bill Gates oder Eric Schmitt konferierten mit deutschen Politikern. Oder bekämen Sendezeit im ÖRR. Nicht auszudenken.

Wie heißt es so schön: »Eine schmerzliche Wahrheit ist besser als eine Lüge« (Thomas Mann). Stimmt. Nur fällt es relativ schwer, eine Lüge einzugestehen, wenn der, dem man sie beichten muss, der Lügner ist.

So bleibt nur zu hoffen, dass möglichst viele Eloi diesen Schritt trotzdem möglichst bald hinter sich bringen. Im eigenen Interesse. Denn wie schon Ernst Freiherr von Feuchtersleben feststellte, ist »Reue der Verstand, der zu spät kommt«. Und das kann in diesen Tagen verheerende Folgen haben.

@ c1e6505c:02b3157e

Chef's notes

Leftover ground beef? Not sure what to do with it?

Here’s what I do with mine. I call it…

The Beef Panzone

It’s like an omelette, a calzone, and a quesadilla had a baby. I called it that for now, but hey, if you’ve got a better name, lemme hear it!

The beef’s already cooked and seasoned with sea salt, but feel free to spice it up however you like.

Watch the video here: https://video.nostr.build/ad4856d2704ab0626a1907f5da8fedcb776495080bbaa92f4472db402c9f689d.mp4

Details

• ⏲️ Prep time: 5
• 🍳 Cook time: 10
• 🍽️ Servings: 1-2

Ingredients

• ground beef
• 2-3 eggs
• water
• sea salt
• honey
• coconut oil

Directions

1. Leftover ground beef – Chop it into small pieces. Trust me, the smaller, the better—it’ll cover more surface area in the pan.
2. Two eggs, whipped with a dash of water.
3. Heat up a small pan.
4. Add coconut oil (around a tablespoon).
5. Once the oil’s warmed up, throw in the beef.
6. Stir it around.
7. I like to add local honey here—sweeten it up to your taste.
8. Mix it all around.
9. Pour in the egg mixture, making sure it spreads out evenly. I use chopsticks here because they make it easier to maneuver.
10. Use those chopsticks to poke through the egg and let the uncooked top flow to the pan. This speeds up cooking time.
11. Cover it for 1–3 minutes.
12. Optional step: Cut it down the middle.
13. Fold it over like a calzone.
14. Plate it up, either by flipping the pan over onto the plate or scooping it out.
15. PANZONE!

@ 4fe4a528:3ff6bf06

In my last article I wrote about NOSTR. I found another local bitcoiner via NOSTR last week so here is why it is important to join / use NOSTR — start telling people “Look me up on NOSTR”

Self-sovereign identity (SSI) is a revolutionary approach to digital identity that puts individuals in control of their own identity and personal data. Unlike traditional digital identity models, which rely on third-party organizations to manage and authenticate identities, SSI empowers individuals to own and manage their digital identity.

This approach is made possible by emerging technologies such as secure public / private key pairs. Decentralized identifiers, conceived and developed by nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is an attempt to create a global technical standard around cryptographically secured identifiers - a secure, universal, and sovereign form of digital ID. This technology uses peer-to-peer technology to remove the need for intermediaries to own and authenticate ID information.

Notably, NOSTR, a decentralized protocol, has already begun to utilize decentralized IDs, demonstrating the potential of this technology in real-world applications. Via NOSTR, users can be sure that the person or computer publishing to a particular npub knows their nsec (password for your npub), highlighting the secure and decentralized nature of this approach.

With SSI, individuals can decide how their personal data is used, shared, and protected, giving them greater control and agency over their digital lives.

The benefits of SSI are numerous, including:

Enhanced security and protection of personal data. Reduced risk of identity theft and fraud Increased autonomy and agency over one's digital identity. Improved scalability and flexibility in digital identity management

challenges:

Ensuring the security and integrity of decentralized identity systems. Developing standards and protocols for interoperability and compatibility. Addressing concerns around ownership and control of personal data. Balancing individual autonomy with the need for verification and authentication in various contexts.

Overall, self-sovereign identity has the potential to transform the way we think about digital identity and provide individuals with greater control and agency over their personal data. Without people in control of their bitcoin seed words no freedom loving people would be able to exchange their money with others. Yes, keep enjoying using the only free market on the planet BITCOIN. Long live FREEDOM!

@ 617f0a85:b403d1ed

Chef's notes

I got this recipe from a friend in college. I'm not sure where she came across it, but I don't think she'd mind me posting it here.

Details

• ⏲️ Prep time: 15 min

Ingredients

• 2.5 cups unbleached all-purpose flour
• 1 tsp salt
• 2 tbsp sugar
• 12 tbsp cold unsalted butter
• 0.5 cup lard
• 0.25 cup vodka
• 0.25 cup cold water

Directions

1. Process 1.5 cups flour, salt, and sugar in food processor until combined, about 2 one-second pulses. Add butter and shortening and process until homogeneous dough just starts to collect in uneven clumps, about 15 seconds (dough will resemble cottage cheese curds and there should be no uncoated flour). Scrape bowl with rubber spatula and redistribute dough evenly around processor blade. Add remaining cup flour and pulse until mixture is evenly distributed around bowl and mass of dough has been broken up, 4 to 6 quick pulses. Empty mixture into medium bowl
2. Sprinkle vodka and water over mixture. With rubber spatula, use folding motion to mix, pressing down on dough until dough is slightly tacky and sticks together. Divide dough into two even balls and flatten each into 4-inch disk. Wrap each in plastic wrap and refrigerate at least 45 minutes or up to 2 days.

@ 9f51b59f:75e7c3a2

Chef's notes

Use bone in or boneless short rib. This recipe also works with ox tail and pork shoulder or any kind of meat that’s ideal for braising low and slow.

Details

• ⏲️ Prep time: 30 mins
• 🍳 Cook time: 2.5-3.5 hours
• 🍽️ Servings: 6-8

Ingredients

• 3 Tablespoons natural cooking oil (I use tallow or ghee)
• 2 lbs boneless short ribs (bone-in also works)
• Salt & Pepper
• 1 small red onion, diced
• 5 garlic cloves rough chopped
• 1 bell or poblano pepper, seeded & diced
• 2 teaspoon chili powder
• 1 teaspoon ancho chili powder
• 1 tablespoon smoked paprika
• 1 tablespoon dark coco powder
• 2 teaspoon cumin
• 1 tablespoon graham masla
• 1 teaspoon dried oregano
• 3 tablespoons apple cider vinegar
• 1/2 cup tomato puree
• 3 tablespoons chipotle adobo sauce
• 3 bay leaves
• 1.5 cups stock or water
• 2 fresh limes, juiced
• Banana leaves, optional
• Avocado, sour cream, lime juice
• Shaved red cabbage with lime juice

Directions

1. Preheat oven to 315 degrees F. Using a Dutch oven or braising pan, begin heating oil over high heat on the stove top.
2. Season beef with salt and pepper and begin searing in the pot. Once browned on all sides set the beef aside and add the onions, garlic, and peppers to the same pan and reduce the heat.
3. Season and cook the veggies 5 to 8 minutes until they start to caramelize. Add the chili pepper, paprika, coco, cumin, marsala, and dried oregano.
4. Briefly toast the spices and deglaze with the vinegar and immediately add the tomato puree.
5. Add the adobo sauce, broth, and using a stick blender or blender buzz the cooking liquid. (if using banana leaves remove the cooking liquid from the pan or use a new pot with lid. Line the pot with the leaves shingled over one another, return the cooking liquid over the leaves.)
6. Return the beef to the pot and cover with lid or foil (fold leaves over the meat then cover).
7. Place the pot in the oven and cook for 2 hours before checking, the meat should be fork tender when done.
8. Mash the avocado into the sour cream and season with lime juice or hot sauce. Serve on tortillas with the crema and cabbage.

@ eff2631b:4732bd7e

This is a test. Trying to use Obsidian for everything. Nostr works out of the box? First try failed, this is my second try.

@ 4dc2e570:7b8126f9

Chef's notes

Pickled pearl onions can usually be found at a middle eastern grocery store.

Details

• ⏲️ Prep time: 30 - 45 minutes
• 🍳 Cook time: 2 hours and 30 minutes
• 🍽️ Servings: 6

Ingredients

• 2.5 lbs stew meat
• 4 cloves Garlic
• 2 onions
• 6oz Bacon, chopped
• 4 Carrots (cut in 1/2 in pieces)
• 3 celery sticks (cut in 1 in pieces)
• 5 or so small gold potatoes, quartered
• 3ish tbps Flour
• 4 tbsp tomato paste
• 14 oz Guinness Beer
• 3 cups chicken stock
• 1 tsp Thyme
• 2 bay leaves
• Ghee
• Salt and pepper

Directions

1. Pat dry then salt and pepper the beef. Melt 1/2 tbsp ghee over high med-high heat. Brown the beef on each side well, makes the stew tasty. This takes patience. Do some breath work while you're at it. :) Add ghee as necessary so browny bits on bottom dont burn. Put meat aside.
2. In same pan, sauté onion and garlic for a few min. Throw in bacon till browned. Put in carrot and celery.
3. Add 3tbsp flour (or a bit more, basically till oil is soaked up) and stir for a minute. Add tomato paste. Stir a couple more minutes.
4. Add thin layer of beer and scrape yummy bits from bottom of pan. Mix everything well. Add rest of beer, broth, and herbs.
5. Carmelize the pickled pearl onion on low med heat with a lil olive oil and stirring occasionally.
6. Simmer covered for 2 hours. Add potatoes. Simmer for a further 30 minutes uncovered to let the sauce reduce a bit. Salt and pepper as you like. Add in some pearl onions. Enjoy.

@ eff2631b:4732bd7e

This is a test. Trying to use Obsidian for everything. Nostr works out of the box?

@ 4dc2e570:7b8126f9

Chef's notes

Pickled pearl onions can usually be found at a middle eastern grocery store.

Details

• ⏲️ Prep time: 30 - 45 minutes
• 🍳 Cook time: 2 hours and 30 minutes
• 🍽️ Servings: 6

Ingredients

• 2.5 lbs stew meat
• 4 cloves Garlic
• 2 onions
• 6oz Bacon, chopped
• 4 Carrots (cut in 1/2 in pieces)
• 3 celery sticks (cut in 1 in pieces)
• 5 or so small gold potatoes, quartered
• 3ish tbps Flour
• 4 tbsp tomato paste
• 14 oz Guinness Beer
• 3 cups chicken stock
• 1 tsp Thyme
• 2 bay leaves
• Ghee
• Salt and pepper

Directions

1. Pat dry then salt and pepper the beef. Melt 1/2 tbsp ghee over high med-high heat. Brown the beef on each side well, makes the stew tasty. This takes patience. Do some breath work while you're at it. :) Add ghee as necessary so browny bits on bottom dont burn. Put meat aside.
2. In same pan, sauté onion and garlic for a few min. Throw in bacon till browned. Put in carrot and celery.
3. Add 3tbsp flour (or a bit more, basically till oil is soaked up) and stir for a minute. Add tomato paste. Stir a couple more minutes.
4. Add thin layer of beer and scrape yummy bits from bottom of pan. Mix everything well. Add rest of beer, broth, and herbs.
5. Carmelize the pickled pearl onion on low med heat with a lil olive oil and stirring occasionally.
6. Simmer covered for 2 hours. Add potatoes. Simmer for a further 30 minutes uncovered to let the sauce reduce a bit. Salt and pepper as you like. Add in some pearl onions. Enjoy.

@ df478568:2a951e67

Details

• ⏲️ Prep time: 10 minutes
• 🍳 Cook time: 30 minutes
• 🍽️ Servings: 4

Ingredients

• rice
• 2 lb. ground beef
• 8 oz. sliced mushrooms
• 1 stalk of geeen onions, chopped
• 1/4 tsp. garlic salt
• 1 10.5 oz. can of cream of mushroom soup
• 1 cup sour cream
• peas

Directions

1. Cook the rice
2. Brown ground beef. Remove and set aside.
3. Saute mushrooms and green onions
4. Cook peas(I usually use the microwave)
5. Return beef to Dutch oven. Add cream of mushroom and sour cream
6. Cooknon low heat for 12 minutes.

@ 9e69e420:d12360c2

Federal employees must remove pronouns from email signatures by the end of the day. This directive comes from internal memos tied to two executive orders signed by Donald Trump. The orders target diversity and equity programs within the government.

CDC, Department of Transportation, and Department of Energy employees were affected. Staff were instructed to make changes in line with revised policy prohibiting certain language.

One CDC employee shared frustration, stating, “In my decade-plus years at CDC, I've never been told what I can and can't put in my email signature.” The directive is part of a broader effort to eliminate DEI initiatives from federal discourse.

@ df478568:2a951e67

Chef's notes

Easy Beef Stroganoff(Fast AF Beef Stroganaff)

This is an easy weaknight meal.

Details

• ⏲️ Prep time: 10 minutes
• 🍳 Cook time: 30 minutes
• 🍽️ Servings: 4

Ingredients

• rice
• 2 lb. ground beef
• 8 oz. sliced mushrooms
• 1 stalk of geeen onions, chopped
• 1/4 tsp. garlic salt
• 1 10.5 oz. can of cream of mushroom soup
• 1 cup sour cream
• peas

Directions

1. Cook the rice
2. Brown ground beef. Remove and set aside.
3. Saute mushrooms and green onions
4. Cook peas(I usually use the microwave)
5. Return beef to Dutch oven. Add cream of mushroom and sour cream
6. Cooknon low heat for 12 minutes.

@ edeb837b:ac664163

In today’s fast-paced financial markets, having quick access to real-time data, trade insights, and the ability to share trades with a like-minded community is invaluable. That’s where NVSTly’s Discord bot comes in. It’s more than just a bot — it’s a powerful tool for social trading, designed to help traders and investors track their trades, share insights, and collaborate with others in real-time, all within Discord.

What the NVSTly Discord Bot Does

NVSTly’s Discord bot is built with the goal of making financial data and trading insights easily accessible to the entire trading community on Discord. Whether you’re a seasoned trader or just starting, the bot helps you stay on top of your trades and market trends. Some of the key features of the bot include:

• Real-Time Trade Tracking & Sharing: The bot tracks your trades and allows you to share them with others. Whether you’re trading stocks, options, forex, or cryptocurrencies, your trades are instantly shared with your followers and can be posted to social media or sent through Discord DMs or webhooks, fostering a transparent and collaborative environment.
• Trader Stats & Performance Recaps: The bot generates visual reports of your trading performance, including win rates, total gains, and individual trade stats. You can view a trader’s daily, weekly, or monthly recaps, complete with details on stock tickers, options info, and profit/loss calculations.
• Market Data & Charts: Get instant access to live market data, stock charts, and detailed information on tickers. The bot provides a variety of commands for stock price movements, charts, and other data, with plans to expand this to cover more markets in the future.
• Comprehensive Coverage: The bot currently supports stocks, options, forex, and crypto for trade tracking and sharing. Futures markets are also planned for the future. While the bot supports these markets for trade tracking, data-related features like market sentiment analysis or earnings reports will be available in the future.

How the Bot Integrates with NVSTly’s Social Trading App

The NVSTly Discord bot is fully integrated with the NVSTly social trading app, creating a seamless experience for users across platforms. Traders can track their trades on the app, and the bot will automatically share those trades directly with their followers, via DMs, social media, or webhooks. This integration means that everything you do on the NVSTly app can be easily shared with your community in real-time via Discord, making it simple to stay connected with your trading network.

The bot doesn’t just show trades — it also gives users insights into their trading performance and connects them with other traders for discussions, tips, and strategies. With NVSTly’s unique social features, traders can collaborate, share strategies, and learn from each other in a dynamic and interactive environment.

What’s Next for the NVSTly Discord Bot?

The future of the NVSTly Discord bot is incredibly exciting, with plans to add even more features designed to elevate the trading experience. Some of the upcoming features include:

• Expanded Market Coverage for Data Commands: In addition to stocks, the bot will soon offer data-related commands for crypto, forex, and futures markets. This will allow users to access even more comprehensive market data, including earnings reports, options flow, and more.
• AI & Machine Learning Integration: NVSTly plans to integrate AI and machine learning to generate trade signals, analyze market trends, and even offer personalized trading tips. This will help traders refine their strategies and make more informed decisions.
• Real-Time Alerts & Notifications: Users can already receive trade alerts sent directly to their DMs from traders they follow. In the future, users will also be able to set more customized alerts based on price targets or specific market activity.

Why the NVSTly Discord Bot is Perfect for Trading Communities

Discord has become a hub for traders and investors, and the NVSTly Discord bot takes full advantage of this by providing a platform where traders can interact, share trades, and learn from one another. The bot’s ability to instantly share trade recaps and stats creates an environment of transparency and collaboration. Traders can discuss strategies, ask questions, and even challenge each other to improve their performance.

By integrating market data, charts, and trade performance tracking, the bot offers a complete package for traders on Discord. It’s not just a tool for sharing trades — it’s a vital part of a thriving trading community.

Why NVSTly’s Discord Bot is the Fastest Growing Finance Bot on Discord

With its comprehensive features and seamless integration with the NVSTly app, the NVSTly Discord bot has quickly become the go-to tool for traders on Discord. What sets it apart from other finance bots is its focus on user engagement. The bot is not just about providing data — it’s about building a community of traders who can share their experiences, insights, and successes.

Traders have flocked to the NVSTly Discord bot because it provides real-time data, easy trade tracking, and powerful analytics — all in a user-friendly format. It’s no wonder it’s quickly becoming the fastest-growing finance bot on Discord.

On Track to be the Greatest Finance Bot on Discord

NVSTly is on track to become the greatest finance bot on Discord, if it’s not already. With plans for expanding market coverage, adding advanced AI-driven features, and constantly improving its user experience, the bot is poised to revolutionize the way traders use Discord.

By offering a comprehensive set of tools that integrate seamlessly with the NVSTly app, the bot is becoming an essential resource for traders who want to stay informed, track their performance, and engage with the trading community.

---

NVSTly is available for free on web, mobile devices (iOS & Google Play), and is fully integrated with Discord via a unique bot- the only of it’s kind and available to any server or trading community on Discord. Or feel free to join a community of over 45,000 investors & traders on our Discod server.

@ de75eb1d:710c3014

Chef's notes

Traditional Victorian recipe made better with the addition of chocolate, fills x6 one lb jars and each jar makes approximately 15 pies or one large tart.

Store in a cool dry place for 12 months for an even deeper flavour.

Unlike supermarket mincemeat, this recipe is naturally palm oil free when made using traditional ingredients (NOT Atora!), you could swap the animal fat for ghee or solid cocoa butter.

Go wild on the dried fruit, anything and everything works. This is a great area to play around and make extra special versions - like Cherry Brandied Chocolate! You can also swap or omit the nuts

Details

• ⏲️ Prep time: 30 mins
• 🍳 Cook time: 3 hours

Ingredients

• 1 lb cooking apples, cored and diced
• 1.5lb mixed dried fruit
• 1lb unrefined sugar (or honey)
• 1/2lb beef suet
• 1/2lb candied citrus peel
• 2oz chopped or flaked almonds
• 4tsp mixed spice
• 1tsp ground cinnamon
• 1/2tsp ground nutmeg
• 1/2lb dark chocolate roughly chopped
• 6tbspn brandy or rum
• zest and juice of 2 oranges & lemons

Directions

1. Combine all of the ingredients except the chocolate and alcohol in a large oven proof bowl, cover and leave overnight to infuse
2. Next day cover the bowl with foil and bake slowly for 3 hours in a preheated oven at 120c
3. As the mincemeat cools periodically stir in the fat and when completely cold add the alcohol and chocolate chips
4. Pack into sterilised jars and cover with a wax disk or 1tsp melted suet, screw the lids on tight and it will keep for 3-5 years

@ edeb837b:ac664163

Join Benzinga as they sit down with NVSTly, the cutting-edge platform revolutionizing social trading and investing. In this exclusive interview, NVSTly shares insights on empowering retail traders, fostering transparency, and building a thriving community for investors of all levels. Discover how NVSTly is shaping the future of trading with innovative features, real-time trade tracking, and global collaboration.

NVSTly Web: https://nvstly.com
iOS: https://nvstly.com/go/ios
Google Play: https://nvstly.com/go/android

@ 21b41910:91f41a5e

Chef's notes

Based on assorted recipes and refined over time, this round of beef tastes great as a result of the sweet and savory marinade.

Details

• ⏲️ Prep time: 5 minutes (+ 1 day)
• 🍳 Cook time: 20 minutes

Ingredients

• 2 pounds lean beef (may be labeled as London Broil)
• 1/3 cup olive oil
• 1/4 cup soy sauce
• 1/4 cup malt vinegar
• 1/4 cup lemon juice
• 1 tbsp sweetener of choice (honey, molasses, syrup, 4 packets of duck sauce, etc)
• 2 tsp old bay seasoning
• 1 tsp garlic powder
• 1 tsp sea salt
• 1/2 tsp black pepper

Directions

1. Day Before: Mix all ingredients except the beef in a bowl to form a marinade. Place the cut of beef in a gallon sized Ziploc bag. Pour marinade over beef, ensure fully covered. Remove any excess air from the bag and seal. Place back in refrigerator for up to 24 hours before cooking.
2. Cooking: Bring beef out of refrigerator (still in bag), and allow to rise to room temperature (about 30-40 minutes). Preheat broiler for about 15 minutes (your oven will vary). Broil for about 7-8 minutes on one side, then flip over. Continue broiling for another 7-10 minutes until temperature reads 140°F. Remove from broiler and let rest for 10 minutes before slicing thinly.

@ 8cd9d25d:69e9894d

Chef's notes

Note that youtube recipe is asking for 1tablespoon of salt, which is waaaaaay too much. Recipe works fine with a teaspoon,, but your mileage may vary. Play around with it.

You don't need to prove modern packet yeasts in my experience... just yolo it.

If you want an extra crispy crust, add a second baking pan to the base of the oven as you pre-heat. Then once you've placed the dough in, to the oven, take some boiling water and pour into the second baking tray. This gives you a steam oven on a budget :)

Details

• ⏲️ Prep time: 15min (not including time for dough rises)
• 🍳 Cook time: 30mins
• 🍽️ Servings: 4-5

Ingredients

• 500 grams wholemeal spelt flour
• 1 packet baker's yeast (10grams)
• 350 ml lukewarm water
• 350 ml lukewarm water
• 1 teaspoon salt 🧂

Directions

1. Preheat your oven to Preheat oven to 430°F and put a baking tray in at the same time to heat up.
2. Add all ingredients to a bowl (best to use a stand mixer to save time, but you can do by hand too. Mix and knead until the dough comes together. After about 5 mins you should have a moist dough that doesn't stick to your hands... if it is a bit sticky, just add a bit more flour (different flours like differenent amounts of water)... If too dry, add a bit more water... etc.
3. Remove dough from bowl & form into a ball (smooth on top, never mind if not perfectly smooth on its base). Put back in a bowl and cover with a damp cloth. Allow to rest for 30mins/1hr until dough has roughly doubled in size. Time will depend on the ambient temp where you are. In the tropics, 30mins is just fine.
4. Take risen dough out of bowl and put on a floured surface and press the gas out of it... flatten the dough with your hands, and then fold each edge in until you have a rectangle (video makes this bit clear). Then roll the rectangle up into a cylinder. This gives you a nice tight dough for baking. Pinch the ends of the cylinder to seal the dough.
5. Place dough onto a baking sheet/ piece of parchment paper etc... cover with damp towlel and let rise for 15/30mins
6. Score the risen dough (a razer blade, clean box cutter, or serrated knife works well) , this lets steam escape from the loaf as it bakes without slpititng it in ways you wouldn't like.
7. Take your hot baking tray out of the over and transfer your dough onto it. Put into oven.
8. Bake at 430°F (220°C) for 15mins, then reduce oven temp to 350°F (180°C) for the final 15mins. Total bake time 30mins.
9. Remove from oven and allow to cool for 20-30mins.