@ 3bf0c63f:aefa459d

O Planetinha

Fumaça verde me entrando pelas narinas e um coro desafinado fazia uma base melódica.

nos confins da galáxia havia um planetinha isolado. Era um planeta feliz.

O homem vestido de mago começava a aparecer por detrás da fumaça verde.

O planetinha recebeu três presentes, mas o seu habitante, o homem, estava num estado de confusão tão grande que ameaçava estragá-los. Os homens já havia escravizado o primeiro presente, a vida; lutavam contra o segundo presente, a morte; e havia alguns que achavam que deviam destruir totalmente o terceiro, o amor, e com isto levar a desordem total ao pobre planetinha perdido, que se chamava Terra.

O coro desafinado entrou antes do "Terra" cantando várias vezes, como se imitasse um eco, "terra-terra-terraaa". Depois de uma pausa dramática, o homem vestido de mago voltou a falar.

Terra, nossa nave mãe.

Neste momento eu me afastei. À frente do palco onde o mago e seu coral faziam apelos à multidão havia vários estandes cobertos com a tradicional armação de quatro pernas e lona branca. Em todos os cantos da praça havia gente, gente dos mais variados tipos. Visitantes curiosos que se aproximavam atraídos pela fumaça verde e as barraquinhas, gente que aproveitava o movimento para vender doces sem pagar imposto, casais que se abraçavam de pé para espantar o frio, os tradicionais corredores que faziam seu cooper, gente cheia de barba e vestida para imitar os hippies dos anos 60 e vender colares estendidos no chão, transeuntes novos e velhos, vestidos como baladeiros ou como ativistas do ônibus grátis, grupos de ciclistas entusiastas.

O mago fazia agora apelos para que nós, os homens, habitantes do isolado planetinha, passássemos a ver o planetinha, nossa nave mãe, como um todo, e adquiríssemos a consciência de que ele estava entrando em maus lençóis. A idéia, reforçada pela logomarca do evento, era que parássemos de olhar só para a nossa vida e pensássemos no planeta.

A logomarca do evento, um desenho estilizado do planeta Terra, nada tinha a ver com seu nome: "Festival Andando de Bem com a Vida", mas havia sido ali colocada estrategicamente pelos organizadores, de quem parecia justamente sair a mensagem dita pelo mago.

Aquela multidão de pessoas que, assim como eu, tinham suas próprias preocupações, não podiam ver o quadro caótico que formavam, cada uma com seus atos isolados, ali naquela praça isolada, naquele planeta isolado. Quando o hippie barbudo, quase um Osho, assustava um casal para tentar vender-lhes um colar, a quantidade de caos que isto acrescentava à cena era gigantesca. Por um segundo, pude ver, como se estivesse de longe e acima, com toda a pretensão que este estado imaginativo carrega, a cena completa do caos.

---

Uma nave-mãe, dessas de ficção científica, habitada por milhões de pessoas, seguia no espaço sem rumo, e sem saber que logo à frente um longo precipício espacial a esperava, para a desgraça completa sua e de seus habitantes.

Acostumados àquela nave tanto quanto outrora estiveram acostumados à sua terra natal, os homens viviam as próprias vidas sem nem se lembrar que estavam vagando pelo espaço. Ninguém sabia quem estava conduzindo a nave, e ninguém se importava.

No final do filme descobre-se que era a soma completa do caos que cada habitante produzia, com seus gestos egoístas e incapazes de levar em conta a totalidade, é que determinava a direção da nave-mãe. O efeito, no entanto, não era imediato, como nunca é. Havia gente de verdade encarregada de conduzir a nave, mas era uma gente bêbada, mau-caráter, que vivia brigando pelo controle da nave e o poder que isto lhes dava. Poder, status, dinheiro!

Essa gente bêbada era atraída até ali pela corrupção das instituições e da moral comum que, no fundo no fundo, era causada pelo egoísmo da população, através de um complexo -- mas que no filme aparece simplificado pela ação individual de um magnata do divertimento público -- processo social.

O homem vestido de mago era mais um agente causador de caos, com sua cena cheia de fumaça e sua roupa estroboscópica, ele achava que estava fazendo o bem ao alertar sua platéia, todos as sextas-feiras, de que havia algo que precisava ser feito, que cada um que estava ali ouvindo era responsável pelo planeta. A sua incapacidade, porém, de explicar o que precisava ser feito só aumentava a angústia geral; a culpa que ele jogava sobre seu público, e que era prontamente aceita e passada em frente, aos familiares e amigos de cada um, atormentava-os diariamente e os impedia de ter uma vida decente no trabalho e em casa. As famílias, estressadas, estavam constantemente brigando e os motivos mais insignificantes eram responsáveis pelas mais horrendas conseqüências.

O mago, que após o show tirava o chapéu entortado e ia tomar cerveja num boteco, era responsável por uma parcela considerável do caos que levava a nave na direção do seu desgraçado fim. No filme, porém, um dos transeuntes que de passagem ouviu um pedaço do discurso do mago despertou em si mesmo uma consiência transformadora e, com poderes sobre-humanos que lhe foram então concedidos por uma ordem iniciática do bem ou não, usando só os seus poderes humanos mesmo, o transeunte -- na primeira versão do filme um homem, na segunda uma mulher -- consegue consertar as instituições e retirar os bêbados da condução da máquina. A questão da moral pública é ignorada para abreviar a trama, já com duas horas e quarenta de duração, mas subentende-se que ela também fora resolvida.

---

No planeta Terra real, que não está indo em direção alguma, preso pela gravidade ao Sol, e onde as pessoas vivem a própria vida porque lhes é impossível viver a dos outros, não têm uma consciência global de nada porque só é possível mesmo ter a consciência delas mesmas, e onde a maioria, de uma maneira ou de outra, está tentando como pode, fazer as coisas direito, o filme é exibido.

Para a maioria dos espectadores, é um filme que evoca reflexões, um filme forte. Por um segundo elas têm o mesmo vislumbre do caos generalizado que eu tive ali naquela praça. Para uma pequena parcela dos espectadores -- entre eles alguns dos que estavam na platéia do mago, o próprio mago, o seguidor do Osho, o casal de duas mulheres e o vendedor de brigadeiros, mas aos quais se somam também críticos de televisão e jornal e gente que fala pelos cotovelos na internet -- o filme é um horror, o filme é uma vulgarização de um problema real e sério, o filme apela para a figura do herói salvador e passa uma mensagem totalmente errada, de que a maioria da população pode continuar vivendo as suas própria vidinhas miseráveis enquanto espera por um herói que vem do Olimpo e os salva da mixórdia que eles mesmos causaram, é um filme que presta um enorme desserviço à causa.

No dia seguinte ao lançamento, num bar meio caro ali perto da praça, numa mesa com oito pessoas, entre elas seis do primeiro grupo e oito do segundo, discute-se se o filme levará ou não o Oscar. Eu estou em casa dormindo e não escuto nada.

@ f977c464:32fcbe00

Kendisini aynada ilk defa gördüğü o gün, diğerleri gibi olduğunu anlamıştı. Oysaki her insan biricik olmalıydı. Sözgelimi sinirlendiğinde bir kaşı diğerinden birkaç milimetre daha az çatılabilirdi veya sevindiğinde dudağı ona has bir açıyla dalgalanabilirdi. Hatta bunların hiçbiri mümkün değilse, en azından, gözlerinin içinde sadece onun sahip olabileceği bir ışık parlayabilirdi. Çok sıradan, öyle sıradan ki kimsenin fark etmediği o milyonlarca minik şeyden herhangi biri. Ne olursa.

Ama yansımasına bakarken bunların hiçbirini bulamadı ve diğer günlerden hiç de farklı başlamamış o gün, işe gitmek için vagonunun gelmesini beklediği alelade bir metro istasyonunda, içinde kaybolduğu illüzyon dağılmaya başladı.

İlk önce derisi döküldü. Tam olarak dökülmedi aslında, daha çok kıvılcımlara dönüşüp bedeninden fırlamış ve bir an sonra sönerek külleşmiş, havada dağılmıştı. Ardında da, kaybolmadan hemen önce, kısa süre için hayal meyal görülebilen, bir ruhun yok oluşuna ağıt yakan rengârenk peri cesetleri bırakmıştı. Beklenenin aksine, havaya toz kokusu yayıldı.

Dehşete düştü elbette. Dehşete düştüler. Panikle üstlerini yırtan 50 işçi. Her şeyin sebebiyse o vagon.

Saçları da döküldü. Her tel, yere varmadan önce, her santimde ikiye ayrıla ayrıla yok oldu.

Bütün yüzeylerin mat olduğu, hiçbir şeyin yansımadığı, suyun siyah aktığı ve kendine ancak kameralarla bakabildiğin bir dünyada, vagonun içine yerleştirilmiş bir aynadan ilk defa kendini görmek.

Gözlerinin akları buharlaşıp havada dağıldı, mercekleri boşalan yeri doldurmak için eriyip yayıldı. Gerçeği görmemek için yaratılmış, bu yüzden görmeye hazır olmayan ve hiç olmayacak gözler.

Her şeyin o anda sona erdiğini sanabilirdi insan. Derin bir karanlık ve ölüm. Görmenin görmek olduğu o anın bitişi.

---

Ben geldiğimde ölmüşlerdi.

Yani bozulmuşlardı demek istiyorum.

Belleklerini yeni taşıyıcılara takmam mümkün olmadı. Fiziksel olarak kusursuz durumdaydılar, olmayanları da tamir edebilirdim ama tüm o hengamede kendilerini baştan programlamış ve girdilerini modifiye etmişlerdi.

Belleklerden birini masanın üzerinden ileriye savurdu. Hınca hınç dolu bir barda oturuyorlardı. O ve arkadaşı.

Sırf şu kendisini insan sanan androidler travma geçirip delirmesin diye neler yapıyoruz, insanın aklı almıyor.

Eliyle arkasını işaret etti.

Polislerin söylediğine göre biri vagonun içerisine ayna yerleştirmiş. Bu zavallılar da kapı açılıp bir anda yansımalarını görünce kafayı kırmışlar.

Arkadaşı bunların ona ne hissettirdiğini sordu. Yani o kadar bozuk, insan olduğunu sanan androidi kendilerini parçalamış olarak yerde görmek onu sarsmamış mıydı?

Hayır, sonuçta belirli bir amaç için yaratılmış şeyler onlar. Kaliteli bir bilgisayarım bozulduğunda üzülürüm çünkü parasını ben vermişimdir. Bunlarsa devletin. Bana ne ki?

Arkadaşı anlayışla kafasını sallayıp suyundan bir yudum aldı. Kravatını biraz gevşetti.

Bira istemediğinden emin misin?

İstemediğini söyledi. Sahi, neden deliriyordu bu androidler?

Basit. Onların yapay zekâlarını kodlarken bir şeyler yazıyorlar. Yazılımcılar. Biliyorsun, ben donanımdayım. Bunlar da kendilerini insan sanıyorlar. Tiplerine bak.

Sesini alçalttı.

Arabalarda kaza testi yapılan mankenlere benziyor hepsi. Ağızları burunları bile yok ama şu geldiğimizden beri sakalını düzeltip duruyor mesela. Hayır, hepsi de diğerleri onun sakalı varmış sanıyor, o manyak bir şey.

Arkadaşı bunun delirmeleriyle bağlantısını çözemediğini söyledi. O da normal sesiyle konuşmaya devam etti.

Anlasana, aynayı falan ayırt edemiyor mercekleri. Lönk diye kendilerini görüyorlar. Böyle, olduğu gibi...

Nedenmiş peki? Ne gerek varmış?

Ne bileyim be abicim! Ahiret soruları gibi.

Birasına bakarak dalıp gitti. Sonra masaya abanarak arkadaşına iyice yaklaştı. Bulanık, bir tünelin ucundaki biri gibi, şekli şemalı belirsiz bir adam.

Ben seni nereden tanıyorum ki ulan? Kimsin sen?

Belleği makineden çıkardılar. İki kişiydiler. Soruşturmadan sorumlu memurlar.

─ Baştan mı başlıyoruz, diye sordu belleği elinde tutan ilk memur.

─ Bir kere daha deneyelim ama bu sefer direkt aynayı sorarak başla, diye cevapladı ikinci memur.

─ Bence de. Yeterince düzgün çalışıyor.

Simülasyon yüklenirken, ayakta, biraz arkada duran ve alnını kaşıyan ikinci memur sormaktan kendisini alamadı:

─ Bu androidleri niye böyle bir olay yerine göndermişler ki? Belli tost olacakları. İsraf. Gidip biz baksak aynayı kırıp delilleri mahvetmek zorunda da kalmazlar.

Diğer memur sandalyesinde hafifçe dönecek oldu, o sırada soruyu bilgisayarın hoparlöründen teknisyen cevapladı.

Hangi işimizde bir yamukluk yok ki be abi.

---

Ama bir son değildi. Üstlerindeki tüm illüzyon dağıldığında ve çıplak, cinsiyetsiz, birbirinin aynı bedenleriyle kaldıklarında sıra dünyaya gelmişti.

Yere düştüler. Elleri -bütün bedeni gibi siyah turmalinden, boğumları çelikten- yere değdiği anda, metronun zemini dağıldı.

Yerdeki karolar öncesinde beyazdı ve çok parlaktı. Tepelerindeki floresan, ışığını olduğu gibi yansıtıyor, tek bir lekenin olmadığı ve tek bir tozun uçmadığı istasyonu aydınlatıyorlardı.

Duvarlara duyurular asılmıştı. Örneğin, yarın akşam kültür merkezinde 20.00’da başlayacak bir tekno blues festivalinin cıvıl cıvıl afişi vardı. Onun yanında daha geniş, sarı puntolu harflerle yazılmış, yatay siyah kesiklerle çerçevesi çizilmiş, bir platformdan düşen çöp adamın bulunduğu “Dikkat! Sarı bandı geçmeyin!” uyarısı. Biraz ilerisinde günlük resmi gazete, onun ilerisinde bir aksiyon filminin ve başka bir romantik komedi filminin afişleri, yapılacakların ve yapılmayacakların söylendiği küçük puntolu çeşitli duyurular... Duvar uzayıp giden bir panoydu. On, on beş metrede bir tekrarlanıyordu.

Tüm istasyonun eni yüz metre kadar. Genişliği on metre civarı.

Önlerinde, açık kapısından o mendebur aynanın gözüktüğü vagon duruyordu. Metro, istasyona sığmayacak kadar uzundu. Bir kılıcın keskinliğiyle uzanıyor ama yer yer vagonların ek yerleriyle bölünüyordu.

Hiçbir vagonda pencere olmadığı için metronun içi, içlerindekiler meçhuldü.

Sonrasında karolar zerrelerine ayrılarak yükseldi. Floresanın ışığında her yeri toza boğdular ve ortalığı gri bir sisin altına gömdüler. Çok kısa bir an. Afişleri dalgalandırmadılar. Dalgalandırmaya vakitleri olmadı. Yerlerinden söküp aldılar en fazla. Işık birkaç kere sönüp yanarak direndi. Son kez söndüğünde bir daha geri gelmedi.

Yine de etraf aydınlıktı. Kırmızı, her yere eşit dağılan soluk bir ışıkla.

Yer tamamen tele dönüşmüştü. Altında çapraz hatlarla desteklenmiş demir bir iskelet. Işık birkaç metreden daha fazla aşağıya uzanamıyordu. Sonsuzluğa giden bir uçurum.

Duvarın yerini aynı teller ve demir iskelet almıştı. Arkasında, birbirine vidalarla tutturulmuş demir plakalardan oluşan, üstünden geçen boruların ek yerlerinden bazen ince buharların çıktığı ve bir süre asılı kaldıktan sonra ağır, yağlı bir havayla sürüklendiği bir koridor.

Diğer tarafta paslanmış, pencerelerindeki camlar kırıldığı için demir plakalarla kapatılmış külüstür bir metro. Kapının karşısındaki aynadan her şey olduğu gibi yansıyordu.

---

Bir konteynırın içini andıran bir evde, gerçi gayet de birbirine eklenmiş konteynırlardan oluşan bir şehirde “andıran” demek doğru olmayacağı için düpedüz bir konteynırın içinde, masaya mum görüntüsü vermek için koyulmuş, yarı katı yağ atıklarından şekillendirilmiş kütleleri yakmayı deniyordu. Kafasında hayvan kıllarından yapılmış grili siyahlı bir peruk. Aynı kıllardan kendisine gür bir bıyık da yapmıştı.

Üstünde mavi çöp poşetlerinden yapılmış, kravatlı, şık bir takım.

Masanın ayakları yerine oradan buradan çıkmış parçalar konulmuştu: bir arabanın şaft mili, üst üste konulmuş ve üstünde yazı okunamayan tenekeler, boş kitaplar, boş gazete balyaları... Hiçbir şeye yazı yazılmıyordu, gerek yoktu da zaten çünkü merkez veri bankası onları fark ettirmeden, merceklerden giren veriyi sentezleyerek insanlar için dolduruyordu. Yani, androidler için. Farklı şekilde isimlendirmek bir fark yaratacaksa.

Onların mercekleri için değil. Bağlantıları çok önceden kopmuştu.

─ Hayatım, sofra hazır, diye bağırdı yatak odasındaki karısına.

Sofrada tabak yerine düz, bardak yerine bükülmüş, çatal ve bıçak yerine sivriltilmiş plakalar.

Karısı salonun kapısında durakladı ve ancak kulaklarına kadar uzanan, kocasınınkine benzeyen, cansız, ölü hayvanların kıllarından ibaret peruğunu eliyle düzeltti. Dudağını, daha doğrusu dudağının olması gereken yeri koyu kırmızı bir yağ tabakasıyla renklendirmeyi denemişti. Biraz da yanaklarına sürmüştü.

─ Nasıl olmuş, diye sordu.

Sesi tek düzeydi ama hafif bir neşe olduğunu hissettiğinize yemin edebilirdiniz.

Üzerinde, çöp poşetlerinin içini yazısız gazete kağıtlarıyla doldurarak yaptığı iki parça giysi.

─ Çok güzelsin, diyerek kravatını düzeltti kocası.

─ Sen de öylesin, sevgilim.

Yaklaşıp kocasını öptü. Kocası da onu. Sonra nazikçe elinden tutarak, sandalyesini geriye çekerek oturmasına yardım etti.

Sofrada yemek niyetine hiçbir şey yoktu. Gerek de yoktu zaten.

Konteynırın kapısı gürültüyle tekmelenip içeri iki memur girene kadar birbirlerine öyküler anlattılar. O gün neler yaptıklarını. İşten erken çıkıp yemyeşil çimenlerde gezdiklerini, uçurtma uçurduklarını, kadının nasıl o elbiseyi bulmak için saatlerce gezip yorulduğunu, kocasının kısa süreliğine işe dönüp nasıl başarılı bir hamleyle yaşanan krizi çözdüğünü ve kadının yanına döndükten sonra, alışveriş merkezinde oturdukları yeni dondurmacının dondurmalarının ne kadar lezzetli olduğunu, boğazlarının ağrımasından korktuklarını...

Akşam film izleyebilirlerdi, televizyonda -boş ve mat bir plaka- güzel bir film oynayacaktı.

İki memur. Çıplak bedenleriyle birbirinin aynı. Ellerindeki silahları onlara doğrultmuşlardı. Mum ışığında, tertemiz bir örtünün serili olduğu masada, bardaklarında şaraplarla oturan ve henüz sofranın ortasındaki hindiye dokunmamış çifti gördüklerinde bocaladılar.

Hiç de androidlere bilinçli olarak zarar verebilecek gibi gözükmüyorlardı.

─ Sessiz kalma hakkına sahipsiniz, diye bağırdı içeri giren ikinci memur. Söylediğiniz her şey...

Cümlesini bitiremedi. Yatak odasındaki, masanın üzerinden gördüğü o şey, onunla aynı hareketleri yapan android, yoksa, bir aynadaki yansıması mıydı?

Bütün illüzyon o anda dağılmaya başladı.

Not: Bu öykü ilk olarak 2020 yılında Esrarengiz Hikâyeler'de yayımlanmıştır.

@ 32e18276:5c68e245

I’m going to be on an ordinals panels as one of the people who is counter arguing the claim that they are good for bitcoin. I decided to brush up on the technicals on how inscriptions work. I am starting to see luke’s perspective on how it is exploiting a loophole in bitcoin’s anti-data-spam mechanisms.

Storing data in Bitcoin, the “standard” way

The standard way you add “data” to bitcoin is by calling the OP_RETURN opcode. Bitcoin devs noticed that people were storing data (like the bitcoin whitepaper) in the utxo set via large multisig transactions. The problem with this is that this set is unprunable and could grow over time. OP_RETURN outputs on the other-hand are provably prunable and don’t add to utxo bloat.

Here’s an excerpt from the march 2014 0.9.0 release notes that talks about this:

On OP_RETURN: There was been some confusion and misunderstanding in the community, regarding the OP_RETURN feature in 0.9 and data in the blockchain. This change is not an endorsement of storing data in the blockchain. The OP_RETURN change creates a provably-prunable output, to avoid data storage schemes – some of which were already deployed – that were storing arbitrary data such as images as forever-unspendable TX outputs, bloating bitcoin’s UTXO database. Storing arbitrary data in the blockchain is still a bad idea; it is less costly and far more efficient to store non-currency data elsewhere.

Much of the work on bitcoin core has been focused on making sure the system continues to function in a decentralized way for its intended purpose in the presence of people trying to abuse it for things like storing data. Bitcoin core has always discouraged this, as it is not designed for storage of images and data, it is meant for moving digital coins around in cyberspace.

To help incentive-align people to not do stupid things, OP_RETURN transactions were not made non-standard, so that they are relayable by peers and miners, but with the caveat:

1. They can only push 40 bytes (later increased to 80,83, I’m guessing to support larger root merkle hashes since that is the only sane usecase for op_return)

Bitcoin also added an option called -datacarriersize which limits the total number of bytes from these outputs that you will relay or mine.

Why inscriptions are technically an exploit

Inscriptions get around the datacarriersize limit by disguising data as bitcoin script program data via OP_PUSH inside OP_IF blocks. Ordinals do not use OP_RETURN and are not subjected to datacarriersize limits, so noderunners and miners currently have limited control over the total size of this data that they wish to relay and include in blocks. Luke’s fork of bitcoin-core has some options to fight this spam, so hopefully we will see this in core sometime soon as well.

Inscriptions are also taking advantage of features in segwit v1 (witness discount) and v2/taproot (no arbitrary script size limit). Each of these features have interesting and well-justified reasons why they were introduced.

The purpose of the witness discount was to make it cheaper to spend many outputs which helps the reduction of the utxo set size. Inscriptions took advantage of this discount to store monke jpegs disguised as bitcoin scripts. Remember, bitcoin is not for storing data, so anytime bitcoin-devs accidentally make it cheap and easy to relay data then this should be viewed as an exploit. Expect it to be fixed, or at least provide tools to noderunners for fighting this spam.

Where do we go from here

The interesting part of this story is that people seem to attach value to images stored on the bitcoin blockchain, and they are willing to pay the fee to get it in the block, so non-ideologic miners and people who don’t care about the health and decentralization of bitcoin are happy to pay or collect the fee and move on.

Data should not get a discount, people should pay full price if they want to store data. They should just use op_return and hashes like opentimestamps or any other reasonable protocol storing data in bitcoin.

After going through this analysis I’ve come to the opinion that this is a pretty bad data-spam exploit and bitcoin devs should be working on solutions. Ideological devs like luke who actually care about the health and decentralization of the network are and I’m glad to see it.

@ 8fb140b4:f948000c

Embarking on the journey of operating your own Lightning node on the Bitcoin Layer 2 network is more than just a tech-savvy endeavor; it's a step into a realm of financial autonomy and cutting-edge innovation. By running a node, you become a vital part of a revolutionary movement that's reshaping how we think about money and digital transactions. This role not only offers a unique perspective on blockchain technology but also places you at the heart of a community dedicated to decentralization and network resilience. Beyond the technicalities, it's about embracing a new era of digital finance, where you contribute directly to the network's security, efficiency, and growth, all while gaining personal satisfaction and potentially lucrative rewards.

In essence, running your own Lightning node is a powerful way to engage with the forefront of blockchain technology, assert financial independence, and contribute to a more decentralized and efficient Bitcoin network. It's an adventure that offers both personal and communal benefits, from gaining in-depth tech knowledge to earning a place in the evolving landscape of cryptocurrency.

Running your own Lightning node for the Bitcoin Layer 2 network can be an empowering and beneficial endeavor. Here are 10 reasons why you might consider taking on this task:

1. Direct Contribution to Decentralization: Operating a node is a direct action towards decentralizing the Bitcoin network, crucial for its security and resistance to control or censorship by any single entity.

2. Financial Autonomy: Owning a node gives you complete control over your financial transactions on the network, free from reliance on third-party services, which can be subject to fees, restrictions, or outages.

3. Advanced Network Participation: As a node operator, you're not just a passive participant but an active player in shaping the network, influencing its efficiency and scalability through direct involvement.

4. Potential for Higher Revenue: With strategic management and optimal channel funding, your node can become a preferred route for transactions, potentially increasing the routing fees you can earn.

5. Cutting-Edge Technological Engagement: Running a node puts you at the forefront of blockchain and bitcoin technology, offering insights into future developments and innovations.

6. Strengthened Network Security: Each new node adds to the robustness of the Bitcoin network, making it more resilient against attacks and failures, thus contributing to the overall security of the ecosystem.

7. Personalized Fee Structures: You have the flexibility to set your own fee policies, which can balance earning potential with the service you provide to the network.

8. Empowerment Through Knowledge: The process of setting up and managing a node provides deep learning opportunities, empowering you with knowledge that can be applied in various areas of blockchain and fintech.

9. Boosting Transaction Capacity: By running a node, you help to increase the overall capacity of the Lightning Network, enabling more transactions to be processed quickly and at lower costs.

10. Community Leadership and Reputation: As an active node operator, you gain recognition within the Bitcoin community, which can lead to collaborative opportunities and a position of thought leadership in the space.

These reasons demonstrate the impactful and transformative nature of running a Lightning node, appealing to those who are deeply invested in the principles of bitcoin and wish to actively shape its future. Jump aboard, and embrace the journey toward full independence. 🐶🐾🫡🚀🚀🚀

@ de496884:72617b81

Hola nostriches. Hoy quiero hacer una publicación a modo de acercamiento al surgimiento de las categorías de género y feminismo. Así que si te interesa el tema haz un esfuerzo, quédate y lee hasta el final.

El «nuevo» feminismo surge en los años 60 en aquellos países desarrollados que acordaron el reconocimiento a los derechos humanos contenidos en la declaración respectiva de la ONU. Entonces, como extensión a dicho reconocimiento es que se gesta el movimiento feminista. A partir de entonces, se vuelve a plantear la relación entre naturaleza y cultura y se llega a la conclusión de que las diferencias sociales van más allá de las diferencias biológicas, lo cual tiene que ver con que hasta la satisfacción de las necesidades elementales como son la alimentación, la vivienda o el vestuario, están condicionadas por construcciones sociales.

Pues resulta que una de las primeras propuestas identificó la subordinación femenina producto de una organización patriarcal, tomando la categoría patriarcado de Max Weber. Es así como la visión de patriarcado se extendió al discurso político y académico. Sin embargo, no existía información acerca del desarrollo histórico de dicha categoría, sistematización, variaciones, etc., debido a que era algo que recién se percibía en sociedad.

Sin embargo, la misma categoría de patriarcado junto a la de relaciones de poder para explicar fenómenos sociales contemporáneos, constituye uno de los principales aportes del feminismo. Es así como han logrado primero visibilizar y luego deconstruir y desmontar una serie de patrones existentes en la cultura que hacían a la mujer subordinarse al hombre, y que estaban presentes en el sistema sexo/género.

Imagen relativa a la lucha contra el patriarcado

Hasta ese momento, en las investigaciones de corte sociológico se podía observar un androcentrismo excesivo al dar cuenta de que el discurso científico giraba en torno al hombre como sujeto y objeto de la investigación. Incluso para muchos positivistas como el mismo Weber, los problemas relativos a las mujeres quedaban en un segundo plano y eran achacados a una supuesta pasividad en el ámbito doméstico-familiar. Dicha pasividad partía de la supuesta inferioridad biológica del género femenino.

El patriarcado entonces era una categoría vacía en sí misma, sin valor explicativo. Desde el punto de vista político pudo ser útil para la movilización pero no resistió la polémica de los críticos del feminismo ni problematizó los conflictos a ser resueltos. Pero por otro lado, un grupo de mujeres -académicas principalmente- se puso manos a la obra en una tarea más pequeña pero con mayores resultados a la larga. Se propusieron generar conocimientos sobre las condiciones de vida de la mujer, buscar en el pasado y el presente los aportes de las mujeres a la sociedad, hacerlas visibles en la historia. Es así como surgen centros académicos, ONG, proyectos, centros de estudios sobre la mujer, etc.

Convendría distinguir entonces dos posturas que acompañaron a la investigación sobre las mujeres: uno que toma como objeto de estudio a la mujer; condiciones de vida, trabajo, cultura, y otra que privilegia a la sociedad como generadora de la subordinación de las mujeres. Mientras la primera perspectiva generaba conocimiento sobre las mujeres en el estudio de las relaciones mujer-hombre y mujer-mujer, la segunda tenía una visión más holística ya que planteaba que hay que estudiar la sociedad ya que la subordinación de las mujeres es producto de la organización de esta, y que no se avanzará solamente estudiando a las mujeres, pues el estudio debe ser más amplio y en diferentes niveles, ámbitos y tiempos.

Es en esta búsqueda donde nace y se desarrolla el concepto de género como categoría social. Es así que los sistemas de género/sexo fueron entendidos como conjuntos de prácticas, símbolos, representaciones, normas y valores sociales que las sociedades construyen a partir de la diferencia anatomofisiológica y que dotan de sentido a los impulsos sexuales, la reproducción y en general a las relaciones de las personas. Por tanto, este sistema pasó a ser el objeto de estudio para comprender la subordinación de la mujer al hombre. Al ser el reconocimiento de una dimensión de la desigualdad social hasta entonces desconocida, se considera la ruptura epistemológica más importante de la segunda mitad del siglo pasado.

Imagen representativa del binarismo de género

Hay que decir que los fenómenos sociales se definen por la relación que guardan entre sí. Es así que la contextualización adquiere gran importancia. Varones y hembras tenemos la capacidad de producir con el cuerpo, pero solo los cuerpos de las hembras pueden gestar y por tanto asegurar la especie humana. Todo grupo humano que pretenda sobrevivir debe asegurarse cierto número de hembras que lo hagan posible. De ahí un poder particular del cuerpo de las hembras que además es económicamente útil. Dicho poder no es en tanto entidad biológica, sino que es la sociedad la que le otorga este poder. En este punto es importante preguntarnos históricamente ¿quiénes han controlado la capacidad reproductiva de las mujeres?, ¿quiénes han tenido la preferencia en el acceso sexual? Para asegurar un control efectivo sobre la reproducción es necesario asegurar el acceso a la sexualidad.

Imagen alegórica al embarazo

Ello también lleva a dirigir el trabajo que hacen porque de lo contrario, las mujeres pudieran tener espacio para representar una amenaza al dominio de los hombres. Es importante atender a las etapas del desarrollo de las mujeres, que permitirá ver cómo se moldean para aceptar la desigualdad y las jerarquías según el género en las distintas sociedades y culturas.

Otro contexto a delimitar es el ámbito doméstico donde históricamente ha estado ubicada la subordinación femenina. Se ha puesto al descubierto que en mujeres que comparten la misma posición de clase y raza, la condición femenina se redefine a lo largo de la vida y que algunas mujeres gozan de poder sobre otras aún en contextos de alta dominación masculina, donde se les inviste de autoridad, creando el sistema zonas de incertidumbre que las divide como género e impide alianzas y se legitima la dominación. Foucault decía que «el poder se ejerce, no se posee», siempre está en peligro de perderse y no basta con normas, leyes, amenazas o castigos. De ahí que los espacios de subordinación sean también espacios de poder de las mujeres. Es en estos espacios donde aparece la inseguridad, la tensión, la confrontación y por ejemplo, las mujeres pueden reclamar la anticoncepción.

Para terminar, es importante tener en cuenta que el género es una forma de desigualdad social que siempre está articulado con otras formas de desigualdad ya sea clase, raza, grupo etario, etc. Hay que pensar la dominación masculina con un comienzo vago en el tiempo, pero que permite desligar la subordinación de las mujeres de la evolución «natural» de la humanidad y entenderla como un proceso histórico. En ese sentido es necesario destacar que, respecto a la raza, en sociedades plurales hay que atender al contexto étnico-cultural ya que en dependencia de las relaciones entre personas de razas distintas, estarán condicionadas las relaciones entre los géneros.

Imagen de mujeres de distintas razas

Por otro lado, si bien es sabido que históricamente el sistema de género social imperante ha contribuido a invisibilizar a la mujer, asociar necesariamente dicha categoría únicamente a ella, lo que hace es nuevamente recrear el absolutismo histórico que tanto daño ha hecho, ahora como lo antagónico al hombre. En la construcción social participan todos los individuos presentes en el sistema género.

Hasta aquí la publicación de hoy, de la cual aun se puede ahondar mucho más, sobre todo en lo referido al origen de la dominación o de la jerarquización del binomio «hombre/mujer» desde un punto de vista antropológico, pero eso quedará pendiente para otro momento. ¡Así que hasta la próxima!, ¡nos vemos en Nostr!

........................................

English version

Hello nostriches. Today I want to make a post by way of an approach to the emergence of the categories of gender and feminism. So if you are interested in the topic make an effort, stay and read to the end.

The "new" feminism emerged in the 60's in those developed countries that agreed to recognize the human rights contained in the respective UN declaration. Then, as an extension of that recognition, the feminist movement was born. From then on, the relationship between nature and culture was raised again and the conclusion was reached that social differences go beyond biological differences, which has to do with the fact that even the satisfaction of elementary needs such as food, housing or clothing are conditioned by social constructions.

It turns out that one of the first proposals identified female subordination as a product of a patriarchal organization, taking Max Weber's category of patriarchy. This is how the vision of patriarchy was extended to political and academic discourse. However, there was no information about the historical development of this category, systematization, variations, etc., because it was something that was only recently perceived in society.

However, the same category of patriarchy, together with that of power relations to explain contemporary social phenomena, constitutes one of the main contributions of feminism. This is how they have first made visible and then deconstructed and dismantled a series of existing patterns in the culture that made women subordinate to men, and that were present in the sex/gender system.

Image relating to the fight against patriarchy

Up to that time, in sociological research, an excessive androcentrism could be observed as scientific discourse revolved around men as the subject and object of research. Even for many positivists such as Weber himself, the problems related to women remained in the background and were blamed on a supposed passivity in the domestic-family sphere. This passivity was based on the supposed biological inferiority of the female gender.

Patriarchy was then an empty category in itself, with no explanatory value. From the political point of view, it could be useful for mobilization, but it did not resist the polemic of feminism's critics, nor did it problematize the conflicts to be resolved. But on the other hand, a group of women - mainly academics - set to work on a smaller task but with greater results in the long run. They set out to generate knowledge about women's living conditions, to search in the past and present for women's contributions to society, to make them visible in history. This is how academic centers, NGOs, projects, women's studies centers, etc., came into being.

It would be convenient to distinguish then two postures that accompanied the research on women: one that takes women as the object of study; living conditions, work, culture, and the other that privileges society as the generator of women's subordination. While the first perspective generated knowledge about women in the study of woman-man and woman-woman relations, the second had a more holistic vision, since it proposed that society must be studied, since the subordination of women is a product of its organization, and that progress will not be made only by studying women, since the study must be broader and at different levels, spheres and times.

It is in this search that the concept of gender as a social category was born and developed. Thus, gender/sex systems were understood as a set of practices, symbols, representations, norms and social values that societies construct on the basis of anatomophysiological differences and that give meaning to sexual impulses, reproduction and, in general, to people's relationships. Therefore, this system became the object of study to understand the subordination of women to men. As the recognition of a hitherto unknown dimension of social inequality, it is considered the most important epistemological breakthrough of the second half of the last century.

Representative image of gender binarism

It must be said that social phenomena are defined by their relationship with each other. Thus, contextualization acquires great importance. Males and females have the capacity to produce with their bodies, but only the bodies of females can gestate and therefore ensure the human species. Any human group that intends to survive must ensure a certain number of females to make it possible. Hence a particular power of the female body, which is also economically useful. This power is not as a biological entity, but it is society that gives it this power. At this point it is important to ask ourselves historically, who has controlled the reproductive capacity of women, who has had the preference in sexual access? To ensure effective control over reproduction, it is necessary to ensure access to sexuality.

Allegorical image of pregnancy

This also leads to directing the work they do because otherwise, women may have room to pose a threat to men's dominance. It is important to pay attention to the stages of women's development, which will allow us to see how they are shaped to accept inequality and gender hierarchies in different societies and cultures.

Another context to delimit is the domestic sphere where female subordination has historically been located. It has been discovered that in women who share the same class and race position, the feminine condition is redefined throughout life and that some women enjoy power over others even in contexts of high male domination, where they are invested with authority, creating the system of uncertainty zones that divide them as a gender and prevent alliances and legitimize domination. Foucault said that "power is exercised, not possessed", it is always in danger of being lost and norms, laws, threats or punishments are not enough. Hence, the spaces of subordination are also spaces of women's power. It is in these spaces where insecurity, tension, confrontation appear and where, for example, women can demand contraception.

To conclude, it is important to keep in mind that gender is a form of social inequality that is always articulated with other forms of inequality, be it class, race, age group, etc. It is necessary to think of male domination with a vague beginning in time, but which allows us to separate the subordination of women from the "natural" evolution of humanity and to understand it as a historical process. In this sense, it is necessary to emphasize that, with respect to race, in plural societies it is necessary to pay attention to the ethno-cultural context since, depending on the relations between people of different races, the relations between genders will be conditioned.

Image of women of different races

On the other hand, although it is known that historically the prevailing social gender system has contributed to make women invisible, to necessarily associate this category only to women is to recreate the historical absolutism that has done so much damage, this time as antagonistic to men. All individuals present in the gender system participate in the social construction.

So much for today's publication, of which we can still go much deeper, especially with regard to the origin of domination or the hierarchization of the binomial "man/woman" from an anthropological point of view, but that will be left for another time. So until next time, see you in Nostr!

Créditos | Credits

Bibliografía consultada | Consulted bibliography:

1. Barbieri, T. (1993). Sobre la categoría género. Una introducción teórico-metodológica. Debates en Sociología. (18). 1-19. https://doi.org/10.18800/debatesensociologia.199301.006

2. Echevarría, D. (2020). Desigualdades de género e interseccionalidad. Análisis del contexto cubano 2008-2018. Facultad Latinoamericana de Ciencias Sociales (Programa-Cuba). https://www.clacso.org.ar/libreria-latinoamericana-cm/libro_detalle_resultado.php?id_libro=2346&campo=cm&texto=248

Traducción | Translation:

DeepL

@ 8fb140b4:f948000c

Chef's notes

Serving these two dishes together will create a delightful centerpiece for your Thanksgiving meal, offering a perfect blend of traditional flavors with a homemade touch.

Details

• ⏲️ Prep time: 30 min
• 🍳 Cook time: 1 - 2 hours
• 🍽️ Servings: 4-6

Ingredients

• 1 whole turkey (about 12-14 lbs), thawed and ready to cook
• 1 cup unsalted butter, softened
• 2 tablespoons fresh thyme, chopped
• 2 tablespoons fresh rosemary, chopped
• 2 tablespoons fresh sage, chopped
• Salt and freshly ground black pepper
• 1 onion, quartered
• 1 lemon, halved
• 2-3 cloves of garlic
• Apple and Sage Stuffing
• 1 loaf of crusty bread, cut into cubes
• 2 apples, cored and chopped
• 1 onion, diced
• 2 stalks celery, diced
• 3 cloves garlic, minced
• 1/4 cup fresh sage, chopped
• 1/2 cup unsalted butter
• 2 cups chicken broth
• Salt and pepper, to taste

Directions

1. Preheat the Oven: Set your oven to 325°F (165°C).
2. Prepare the Herb Butter: Mix the softened butter with the chopped thyme, rosemary, and sage. Season with salt and pepper.
3. Prepare the Turkey: Remove any giblets from the turkey and pat it dry. Loosen the skin and spread a generous amount of herb butter under and over the skin.
4. Add Aromatics: Inside the turkey cavity, place the quartered onion, lemon halves, and garlic cloves.
5. Roast: Place the turkey in a roasting pan. Tent with aluminum foil and roast. A general guideline is about 15 minutes per pound, or until the internal temperature reaches 165°F (74°C) at the thickest part of the thigh.
6. Rest and Serve: Let the turkey rest for at least 20 minutes before carving.
7. Next: Apple and Sage Stuffing
8. Dry the Bread: Spread the bread cubes on a baking sheet and let them dry overnight, or toast them in the oven.
9. Cook the Vegetables: In a large skillet, melt the butter and cook the onion, celery, and garlic until soft.
10. Combine Ingredients: Add the apples, sage, and bread cubes to the skillet. Stir in the chicken broth until the mixture is moist. Season with salt and pepper.
11. Bake: Transfer the stuffing to a baking dish and bake at 350°F (175°C) for about 30-40 minutes, until golden brown on top.

@ 8fb140b4:f948000c

Testing a brand new YakiHonne native client for iOS. Smooth as butter (not penis butter 🤣🍆🧈) with great visual experience and intuitive navigation. Amazing work by the team behind it! * lists * work

Bold text work!

Images could have used nostr.build instead of raw S3 from us-east-1 region.

Very impressive! You can even save the draft and continue later, before posting the long-form note!

🐶🐾🤯🤯🤯🫂💜

@ 32e18276:5c68e245

Hey guys, I'm spending some time today preparing v1.6 for the app store, it's been a long time coming with many new features. Here's a breakdown of everything new in this version!

Notable new features in 1.6

• Custom built, embedded C WASM interpreter (nostrscript), which will be used for custom algos, filters and lists
• Longform note support
• Hashtag following
• Configurable reactions
• New Live user status NIP (music, general)
• Adjustable font sizes
• A very long list of bug fixes and performance improvements
• Fast and persistent profile searching using nostrdb

Top priorities for 1.7

• Lists
• Custom algos and filters using nostrscript
• Stories
• Multi account
• Tor integration
• Better NWC integration (wallet balances, transaction history)
• Advanced note search via nostrdb
• Fully switch to nostrdb for all notes
• Discord-like relays (click a relay to view all the notes on it)

So much more but maybe I will not try to be too ambitious ...

Contributors

name added removed commits William Casarin +57964 -8274 288 petrikaj +1524 -0 1 Terry Yiu +1266 -964 9 ericholguin +1234 -252 11 Daniel D’Aquino +1223 -399 19 Suhail Saqan +905 -70 16 Grimless +838 -736 6 Bryan Montz +793 -744 30 Jon Marrs +658 -60 3 Joel Klabo +653 -105 6 transifex-integration[bot] +176 -0 9 Fishcake +129 -21 5 Daniel D‘Aquino +123 -9 5 Jericho Hasselbush +78 -2 2 cr0bar +66 -19 11 Daniel D'Aquino +55 -32 2 Mazin +53 -0 1 gladiusKatana +37 -8 1 doffing.brett +10 -6 1 tappu75e@duck.com +5 -1 2 Ben Harvie +5 -0 1

Changelog

• 76 Fixes
• 18 Changes
• 26 Additions

Added

• Add "Do not show #nsfw tagged posts" setting (Daniel D’Aquino)
• Add ability to change order of custom reactions (Suhail Saqan)
• Add close button to custom reactions (Suhail Saqan)
• Add followed hashtags to your following list (Daniel D’Aquino)
• Add initial longform note support (William Casarin)
• Add r tag when mentioning a url (William Casarin)
• Add relay log in developer mode (Montz)
• Add settings for disabling user statuses (William Casarin)
• Add space when tagging users in posts if needed (William Casarin)
• Add support for multilingual hashtags (cr0bar)
• Add support for multiple reactions (Suhail Saqan)
• Add support for status URLs (William Casarin)
• Add the ability to follow hashtags (William Casarin)
• Added feedback when user adds a relay that is already on the list (Daniel D'Aquino)
• Added generic user statuses (William Casarin)
• Added live music statuses (William Casarin)
• Added merch store button to sidebar menu (Daniel D’Aquino)
• Added padding under word count on longform account (William Casarin)
• Adjustable font size (William Casarin)
• Click music statuses to display in spotify (William Casarin)
• Enable banner image editing (Joel Klabo)
• Finnish translations (petrikaj)
• Hold tap to preview status URL (Jericho Hasselbush)
• Re-add nip05 badges to profiles (William Casarin)
• Show nostr address username and support abbreviated _ usernames (William Casarin)
• Suggested Users to Follow (Joel Klabo)

Changed

• Allow reposting and quote reposting multiple times (William Casarin)
• Damus icon now opens sidebar (Daniel D’Aquino)
• Hide nsec when logging in (cr0bar)
• Improve UX around clearing cache (Daniel D’Aquino)
• Improved memory usage and performance when processing events (William Casarin)
• Increase size of the hitbox on note ellipsis button (Daniel D’Aquino)
• Make carousel tab dots tappable (Bryan Montz)
• Move the "Follow you" badge into the profile header (Grimless)
• Remove nip05 on events (William Casarin)
• Remove note size restriction for longform events (William Casarin)
• Rename NIP05 to "nostr address" (William Casarin)
• Show muted thread replies at the bottom of the thread view (#1522) (Daniel D’Aquino)
• Show renotes in Notes timeline (William Casarin)
• Start at top when reading longform events (William Casarin)
• Switch to nostrdb for @'s and user search (William Casarin)
• Updated relay view (ericholguin)
• Use nostrdb for profiles (William Casarin)
• clear statuses if they only contain whitespace (William Casarin)

Fixed

• Allow relay logs to be opened in dev mode even if relay (Daniel D'Aquino)
• Allow user to login to deleted profile (William Casarin)
• Apply filters to hashtag search timeline view (Daniel D’Aquino)
• Avoid notification for zaps from muted profiles (tappu75e@duck.com)
• Crash when muting threads (Bryan Montz)
• Dismiss qr screen on scan (Suhail Saqan)
• Don't always show text events in reposts (William Casarin)
• Don't spam lnurls when validating zaps (William Casarin)
• Eliminate nostr address validation bandwidth on startup (William Casarin)
• Ensure the person you're replying to is the first entry in the reply description (William Casarin)
• Fix Invalid Zap bug in reposts (William Casarin)
• Fix PostView initial string to skip mentioning self when on own profile (Terry Yiu)
• Fix UI freeze after swiping back from profile (#1449) (Daniel D’Aquino)
• Fix UTF support for hashtags (Daniel D‘Aquino)
• Fix action bar appearing on quoted longform previews (William Casarin)
• Fix broken markdown renderer (William Casarin)
• Fix bug where it would sometimes show -1 in replies (tappu75e@duck.com)
• Fix compilation error on test target in UserSearchCacheTests (Daniel D‘Aquino)
• Fix crash when long pressing custom reactions (William Casarin)
• Fix crash when long-pressing reactions (William Casarin)
• Fix freezing bug when tapping Developer settings menu (Terry Yiu)
• Fix icons on settings view (cr0bar)
• Fix images and links occasionally appearing with escaped slashes (Daniel D‘Aquino)
• Fix issue where malicious zappers can send fake zaps to another user's posts (William Casarin)
• Fix issue where relays with trailing slashes cannot be removed (#1531) (Daniel D’Aquino)
• Fix issue where typing cc@bob would produce brokenb ccnostr:bob mention (William Casarin)
• Fix issue with emojis next to hashtags and urls (William Casarin)
• Fix issue with slashes on relay urls causing relay connection problems (William Casarin)
• Fix lag when creating large posts (William Casarin)
• Fix localization issues and export strings for translation (Terry Yiu)
• Fix localization issues and export strings for translation (Terry Yiu)
• Fix long status lines (William Casarin)
• Fix nav crashing and buggyness (William Casarin)
• Fix nostr:nostr:... bugs (William Casarin)
• Fix npub mentions failing to parse in some cases (William Casarin)
• Fix padding of username next to pfp on some views (William Casarin)
• Fix padding on longform events (William Casarin)
• Fix paragraphs not appearing on iOS17 (cr0bar)
• Fix parsing issue with NIP-47 compliant NWC urls without double-slashes (Daniel D’Aquino)
• Fix potential fake profile zap attacks (William Casarin)
• Fix profile not updating (William Casarin)
• Fix profile post button mentions (cr0bar)
• Fix profiles not updating (William Casarin)
• Fix rare crash triggered by local notifications (William Casarin)
• Fix reaction button breaking scrolling (Suhail Saqan)
• Fix situations where the note composer cursor gets stuck in one place after tagging a user (Daniel D’Aquino)
• Fix small graphical toolbar bug when scrolling profiles (Daniel D’Aquino)
• Fix some note composer issues, such as when copying/pasting larger text, and make the post composer more robust. (Daniel D’Aquino)
• Fix status events not expiring locally (William Casarin)
• Fix text composer wrapping issue when mentioning npub (Daniel D’Aquino)
• Fix text editing issues on characters added right after mention link (Daniel D’Aquino)
• Fix wiggle when long press reactions (Suhail Saqan)
• Fix wikipedia url detection with parenthesis (William Casarin)
• Fix zaps sometimes not appearing (William Casarin)
• Fixed a bug where following a user might not work due to poor connectivity (William Casarin)
• Fixed audio in video playing twice (Bryan Montz)
• Fixed disappearing text on iOS17 (cr0bar)
• Fixed issue where hashtags were leaking in DMs (William Casarin)
• Fixed issue where reposts would sometimes repost the wrong thing (William Casarin)
• Fixed issues where sometimes there would be empty entries on your profile (William Casarin)
• Fixed nav bar color on login, eula, and account creation (ericholguin)
• Fixed nostr reporting decoding (William Casarin)
• Fixed nostrscript not working on smaller phones (William Casarin)
• Fixed old notifications always appearing on first start (William Casarin)
• Fixes issue where username with multiple emojis would place cursor in strange position. (Jericho Hasselbush)
• Hide quoted or reposted notes from people whom the user has muted. (#1216) (Daniel D’Aquino)
• Hide users and hashtags from home timeline when you unfollow (William Casarin)
• Make blurred videos viewable by allowing blur to disappear once tapped (Daniel D’Aquino)
• Mute hellthreads everywhere (William Casarin)
• Show QRCameraView regardless of same user (Suhail Saqan)
• Show longform previews in notifications instead of the entire post (William Casarin)
• Stop tab buttons from causing the root view to scroll to the top unless user is coming from another tab or already at the root view (Daniel D’Aquino)
• don't cutoff text in notifications (William Casarin)
• endless connection attempt loop after user removes relay (Bryan Montz)
• icon color for developer mode setting is incorrect in low-light mode (Bryan Montz)
• relay detail view is not immediately available after adding new relay (Bryan Montz)

Removed

• Remove following Damus Will by default (William Casarin)
• Remove old @ and & hex key mentions (William Casarin)

@ 3bf0c63f:aefa459d

Nostr: a quick introduction, attempt #1

Nostr doesn't have a material existence, it is not a website or an app. Nostr is just a description what kind of messages each computer can send to the others and vice-versa. It's a very simple thing, but the fact that such description exists allows different apps to connect to different servers automatically, without people having to talk behind the scenes or sign contracts or anything like that.

When you use a Nostr client that is what happens, your client will connect to a bunch of servers, called relays, and all these relays will speak the same "language" so your client will be able to publish notes to them all and also download notes from other people.

That's basically what Nostr is: this communication layer between the client you run on your phone or desktop computer and the relay that someone else is running on some server somewhere. There is no central authority dictating who can connect to whom or even anyone who knows for sure where each note is stored.

If you think about it, Nostr is very much like the internet itself: there are millions of websites out there, and basically anyone can run a new one, and there are websites that allow you to store and publish your stuff on them.

The added benefit of Nostr is that this unified "language" that all Nostr clients speak allow them to switch very easily and cleanly between relays. So if one relay decides to ban someone that person can switch to publishing to others relays and their audience will quickly follow them there. Likewise, it becomes much easier for relays to impose any restrictions they want on their users: no relay has to uphold a moral ground of "absolute free speech": each relay can decide to delete notes or ban users for no reason, or even only store notes from a preselected set of people and no one will be entitled to complain about that.

There are some bad things about this design: on Nostr there are no guarantees that relays will have the notes you want to read or that they will store the notes you're sending to them. We can't just assume all relays will have everything — much to the contrary, as Nostr grows more relays will exist and people will tend to publishing to a small set of all the relays, so depending on the decisions each client takes when publishing and when fetching notes, users may see a different set of replies to a note, for example, and be confused.

Another problem with the idea of publishing to multiple servers is that they may be run by all sorts of malicious people that may edit your notes. Since no one wants to see garbage published under their name, Nostr fixes that by requiring notes to have a cryptographic signature. This signature is attached to the note and verified by everybody at all times, which ensures the notes weren't tampered (if any part of the note is changed even by a single character that would cause the signature to become invalid and then the note would be dropped). The fix is perfect, except for the fact that it introduces the requirement that each user must now hold this 63-character code that starts with "nsec1", which they must not reveal to anyone. Although annoying, this requirement brings another benefit: that users can automatically have the same identity in many different contexts and even use their Nostr identity to login to non-Nostr websites easily without having to rely on any third-party.

To conclude: Nostr is like the internet (or the internet of some decades ago): a little chaotic, but very open. It is better than the internet because it is structured and actions can be automated, but, like in the internet itself, nothing is guaranteed to work at all times and users many have to do some manual work from time to time to fix things. Plus, there is the cryptographic key stuff, which is painful, but cool.

@ fa0165a0:03397073

I just tested building a browser plugin, it was easier than I thought. Here I'll walk you through the steps of creating a minimal working example of a browser plugin, a.k.a. the "Hello World" of browser plugins.

First of all there are two main browser platforms out there, Chromium and Mozilla. They do some things a little differently, but similar enough that we can build a plugin that works on both. This plugin will work in both, I'll describe the firefox version, but the chromium version is very similar.

What is a browser plugin?

Simply put, a browser plugin is a program that runs in the browser. It can do things like modify the content of a webpage, or add new functionality to the browser. It's a way to extend the browser with custom functionality. Common examples are ad blockers, password managers, and video downloaders.

In technical terms, they are plugins that can insert html-css-js into your browser experience.

How to build a browser plugin

Step 0: Basics

You'll need a computer, a text editor and a browser. For testing and development I personally think that the firefox developer edition is the easiest to work with. But any Chrome based browser will also do.

Create a working directory on your computer, name it anything you like. I'll call mine hello-world-browser-plugin. Open the directory and create a file called manifest.json. This is the most important file of your plugin, and it must be named exactly right.

Step 1: manifest.json

After creation open your file manifest.json in your text editor and paste the following code:

json { "manifest_version": 3, "name": "Hello World", "version": "1.0", "description": "A simple 'Hello World' browser extension", "content_scripts": [ { "matches": ["<all_urls>"], "js": ["hello.js"] //The name of your script file. // "css": ["hello.css"] //The name of your css file. } ] }

If you wonder what the json file format is, it's a normal text file with a special syntax such that a computer can easily read it. It's the json syntax you see in the code above. Let's go through what's being said here. (If you are not interested, just skip to the next step after pasting this we are done here.)

• manifest_version: This is the version of the manifest file format. It's currently at version 3, and it's the latest version. It's important that you set this to 3, otherwise your plugin won't work.
• name: This is the name of your plugin. It can be anything you like.
• version: This is the version of your plugin. It can be anything you like.
• description: This is the description of your plugin. It can be anything you like.
• content_scripts: This is where you define what your plugin does. It's a list of scripts that will be executed when the browser loads a webpage. In this case we have one script, called hello.js. It's the script that we'll create in the next step.
• matches: This is a list of urls that the script will be executed on. In this case we have <all_urls>, which means that the script will be executed on all urls. You can also specify a specific url, like https://brave.com/*, which means that the script will only be executed on urls that start with https://brave.com/.
• js: This is a list of javascript files that will be executed. In this case we have one file, called hello.js. It's the script that we'll create in the next step.
• css: This is where you can add a list of css files that will be executed. In this case we have none, but you can add css files here if you want to.
• //: Text following these two characters are comments. They are ignored by the computer, You can add comments anywhere you like, and they are a good way to document your code.

Step 2: hello.js

Now it's time to create another file in your project folder. This time we'll call it hello.js. When created, open it in your text editor and paste the following code:

js console.log("Hello World!"); That's javascript code, and it's what will be executed when you run your plugin. It's a simple console.log statement, which will print the text "Hello World!" to the console. The console is a place where the browser prints out messages, and it's a good place to start when debugging your plugin.

Step 3: Load and launch your plugin

Firefox

Now it's time to load your plugin into your browser. Open your browser and go to the url about:debugging#/runtime/this-firefox. You should see a page that looks something like this:

Click the button that says "Load Temporary Add-on...". A file dialog will open, navigate to your project folder and select the file manifest.json. Your plugin should now be loaded and running.

Go to a website, any website, and open the inspector then navigate to the console. You'll find the inspector by right-clicking anywhere within the webpage, and click "Inspector" in the drop-down menu. When opening the console you might see some log messages from the site you visited and... you should see the text "Hello World!" printed there, from our little plugin! Congratulations!

Chrome

Open your browser and go to the url chrome://extensions/. Click the button that says "Load unpacked". A file dialog will open, navigate to your project folder and select the folder hello-world-browser-plugin. Your plugin should now be loaded and running.

Note the difference, of selecting the file manifest.json in firefox, and selecting the folder hello-world-browser-plugin in chrome. Otherwise, the process is the same. So I'll repeat the same text as above: (for those who skipped ahead..)

Go to a website, any website, and open the inspector then navigate to the console. You'll find the inspector by right-clicking anywhere within the webpage, and click "Inspector" in the drop-down menu. When opening the console you might see some log messages from the site you visited and... you should see the text "Hello World!" printed there, from our little plugin! Congratulations!

---

As you can see this isn't as complicated as one might think. Having preformed a "Hello-World!"-project is a very useful and valuable first step. These setup steps are the basics for any browser plugin, and you can build on this to create more advanced plugins.

@ cd408a69:797e8162

Nostrasia Hackathon

Welcome FOSS hackers and creatives who care deeply about freedom technology!

自由のテクノロジーに深い関わりたい FOSS ハッカーとクリエイター、あつまれ！

We're joining forces with Bolt.Fun for a month-long hackathon bridging Bitcoin and NOSTR (Notes and Other Stuff Transmitted by Relays), culminating with a special three day sprint and live event in Tokyo at the Nostrasia Conference.

私たちは、Bolt.Fun と協力して、ビットコインと Nostrを橋渡しする ハッカソンを、1 か月間かけて開催します。 クライマックスは東京で開催されるNostrasia Tokyo が舞台。3日間の特別なスプリントとライブ イベントで最高潮に達します。

Be a Part of the Early Days of Nostr

Nostr の創成期を共に作り上げましょう

Help build the future of Nostr! Like the early days of Bitcoin or of the Internet, Nostr is nascent open technology shaping new types of social experiences to connect people across the globe. It carries a foundation of principles similar to Bitcoin, like decentralization, simplicity, and censorship-resistance.

Nostr の未来を築くのに協力してください！ビットコインやインターネットの初期と同じように、Nostr は世界中の人々をつなぐ新しいソーシャル体験を形成するオープン テクノロジーの初期段階にあります。 Nostr には「分散化」「シンプルさ」「検閲耐性」など、ビットコインと同様の原則が組み込まれています。

Orange-Pill people through the Purple-Nostr-Pill

オレンジピル（ビットコイン）から紫の Nostr のピルへ

Bitcoin and Nostr communities are in synergy. What started as a social protocol is quickly transforming into a space for exploration on ways to support content creators through bitcoin lightning micro payments, often referred to as zaps. Bitcoin integration to the nostr protocol strengthens Bitcoin's use case as a currency of exchange. It carves new paths to a culture of value4value.

ビットコインと Nostr のコミュニティは相乗効果を発揮します。 Nostr はソーシャルプロトコルとしてはじまりましたが、今では Zap （ビットコイン の ライトニング マイクロペイメント）を通じてコンテンツ クリエイターをサポートする方法を模索する空間へと急速に進化しています。 Nostr プロトコルにビットコインが組み合わさることで、交換通貨としてのビットコインの働きが強化されます。 それは、"value4value" の文化への新しい道を切り開くでしょう。

Help People HODL their Keys (Social+Monetary)

人々が自分のキーを HODL （長期保有）できるように支援します （ソーシャル + 金銭的に）

Nostr exists outside of the rule of platforms and those who seek to control them. HODLing your nostr keys is hodling your identity and social graph, outside of KYC. By helping develop and educate on NOSTR, you are helping people escape walled gardens & gain control and choice over their identities & their money. The Internet, over time, has become centralized, help Nostr stay decentralized by supporting the growth of an ecosystem of apps, websites, microapps, relay services...

Nostr はプラットフォームやそれを制御しようとする人々の支配の外にあります。 Nostr keys を持つことは、KYC （本人確認）以外であなたのアイデンティティとソーシャル グラフを保持することになります。 Nostr の開発や教育に貢献することは、人々が束縛から解放され、アイデンティティやお金に対する主導権を得られるよう支援することにもなるのです。 時間の経過とともに集中化されてきたインターネットですが、Nostr のアプリ／Web サイト／マイクロアプリ／リレー サービスのエコシステムの成長をサポートすることで、Nostr の分散化を維持できるようになります。

Permissionless Building

許可を必要としない構築

Opportunities abound in an environment ripe for innovation:

• Develop & design new nostr white label clients, middleware, microapps...
• Help improve existing Nostr FOSS projects
• Contribute directly to protocol development through NIPs (Nostr Implementation Possibilities)
• Encourage nostr and bitcoin adoption through art, education, and any way you like

イノベーションの機が熟した環境には、チャンスが溢れています。

• Nostr の真新しい クライアント、ミドルウェア、マイクロアプリを開発したりデザインする
• 既存の Nostr FOSS プロジェクトの改善に寄与する
• NIP (Nostr Implementation Possibilities) を通じたプロトコル開発に直接貢献する
• 芸術、教育、その他好きな方法を通じて Nostr とビットコインの普及を推進する

Hack in a Supportive Environment

サポートされた環境でハックしよう

We have a growing list of knowledgeable people with skin-in-the-game to mentor and support your journey. Once your project matures, you may also have 1-on-1 guidance to help you reach your vision and discover ways of growing and funding it.

私たちは、あなたの道のりを指導しサポートしてくれる知識豊富なメンターを増やしています。 プロジェクトが成熟した暁には、1対1のガイダンスを受けられる可能性もあります。それは、あなたのビジョンを達成し、成長させて資金を得る方法を発見するのに役立つでしょう。

Nostr has a blossoming community open to innovation. It is also a great testing ground, as people in the community are open to giving and receiving feedback. It is an environment encouraging conversation on feature ideas as well as possible solutions to social media issues and product bugs.

Nostr には、イノベーションに対してオープンで、発展しているコミュニティがあります。 コミュニティの人々はフィードバックの授受にオープンであるため、優れた実験の場にもなります。 機能のアイデアや、ソーシャル メディアの課題や製品のバグの解決策についての会話を促進する環境です。

NostrHack Tracks

You have 3 options

NostrHack Tracks には3つのオプションがあります

Track 1: Builder's Track - Reimagine Nostr

トラック1 : ビルダーのトラック - Nostr を再考しよう

If you can think of it, it can be engineered! Nostr encourages permissionless building while staying mindful of interoperability and network support. Help BUIDL, design, and improve an area you are passionate about. Reimagine and BUIDL features, tools, clients... Help solve issues and create new experiences in social media.

思いつくことができれば、エンジニアリングできる！ Nostr は、相互運用性とネットワーク サポートに留意しながら、パーミッションレスな構築 (BUIDL) を奨励しています。 あなたが情熱を注いでいる分野での構築、設計、改善に貢献してください。 機能やツール、クライアントを再考して構築 (BUIDL) し、ソーシャル メディアでの課題を解決して新しい体験を生み出すのに協力してください。

Possibilities...

これを踏まえて…

BUILD on the NOSTR Protocol

The Nostr Implementation Possibilities (NIPs) are optional protocol features anyone can add to their clients. Improve and strengthen existing NIPs or build on new ones. NOSTR is a balance of simplicity, interoperability, backward-compatibility and innovation.

NIPs は、誰でもクライアントに追加できるオプションのプロトコル機能です。 既存の NIP を改善および強化するか、新しい NIP を構築してください。 Nostr は、シンプルさ、相互運用性、下位互換性、革新性のバランスを保っています。

Focus on UX

Nostr is made up of a wide range of clients and tools. To make NOSTR scalable, you can help improve its user experience and education.

Nostr は幅広いクライアントとツールで形成されています。 Nostr をスケーラブルにするために、UX と教育の改善に協力してください。

Help shape a Web of Trust

Nostr cares about removing the KYC tied to our identities. To use Nostr you do not need to give up your phone number, email, financial information, or any metadata tied to your real world identity to be later harvested and sold. You are not the product. What are ways that trust can be earned to prevent impersonation, spam...?

Nostr は、私たちの身元に関連付けられた KYC （個人情報）を取り除けるようにしています。 Nostr を使用しても、電話番号、電子メール、財務情報、または現実世界のアイデンティティに関連付けられたメタデータを、収集されたり販売されたりして手放すことになる心配がありません。 あなたは商品ではないのです。 その中で、なりすましやスパムを防ぐために、信頼を獲得するにはどうすればよいでしょうか...?

NIP05/Nostr address

One of the solutions to build a web of trust used today, is to tie your nostr hex public key to a domain. Although this makes it harder for bots to have nostr addresses, it is not a perfect solution. Domains are centralized through DNS. To help people who do not have their own domains or cannot easily add a NIP05 on their sites, your nostr address can be hosted as a service along with other people's. At this moment, you can highlight just one nostr address per profile. In the future, could it include your website, where you work, and other identifiers... What are other possible solutions?

現在使用されている信頼獲得のための解決策の 1 つは、Nostr の HEX 公開鍵をドメインに結び付けることです。 これにより、完璧な解決策ではないものの、bot などが Nostr アドレスを持つことが難しくなります。 ドメインは DNS を通じて一元化されています。 独自のドメインを持っていない人や、自分では NIP-05 を簡単に追加できない人のために、あなたの Nostr アドレスをサービスとして他の人のものと一緒にホストすることも可能です。 現時点では、プロフィールごとに1つの Nostr アドレスのみを強調表示できますが、将来的には、Web サイト、勤務先、その他の識別情報も含められるようになる可能性があります...この他にも考えられる解決策は何かありますか？

On Decentralization & Discoverability

分散化と発見可能性について

Your identity in NOSTR is tied to your keys, but your information needs to be shared and found across a network of relays. To promote decentralization and censorship resistance, relays need to be easy to setup, lightweight, and sustainable. Relays get to choose what information passes through them, so they are also a form of spam prevention that could potentially also become censoring, so both the relay-runners and the individuals connecting to relays need to have choice and policies cannot be homogenous one-size-fits-all. What are possible solutions to make setting up relays easier, to make running a relay sustainable, to have new ways of discovering information...

Nostr での ID はキーに関連付けられていますが、その情報はリレーのネットワーク全体で共有され、検索できる必要があります。 分散化と検閲耐性を促進するために、リレーはセットアップが簡単で、軽量で、持続可能である必要があります。 リレーは通過する情報を選択できるため、スパム防止の一形態である一方で検閲にもなり得ます。そのため、リレー管理者とリレーに接続する個人の両方に選択権が必要で、ポリシーが全てに対し画一的になってはいけません。 リレーのセットアップを容易にし、リレーの実行を持続可能にし、情報を発見する新しい方法を実現するには、どのような解決策が考えられるでしょうか...？

Buidl tools to connect to Git, as a decentralized alternative to GitHub

GitHub の分散型代替手段として、Git に接続するための BUIDL ツール

Media Uploads

To keep relays lightweight, images are hosted by uploading them to the web, and keeping only the links to them in the data within individual nostr notes. This has led to developing image uploading services specific to nostr, but they carry the risk of centralization or censorship. Some product makers and relay runners are looking into direct uploads to Cloud services. What are possible solutions to the handling of media (images, videos, music...)?

リレーを軽量に保つために、画像は Web にアップロードしてホストされ、各投稿のデータには画像へのリンクのみが保持されます。そんな中で、Nostr に特化した画像アップロード サービスが開発されましたが、集中化や検閲のリスクが伴います。 一部のプロダクト開発者やリレー管理者は、クラウド サービスへの直接アップロードを検討しています。 メディア（画像、ビデオ、音楽など）の処理について、考えられるよい解決策はありますか？

Social Signals

People have the choice to block and mute others, this gives signals to relays, which can reenact policies based on those and other signals. Relays need to be able to differentiate real signals from those wanting to game the system for censorship. Relay runners need to have the capacity to make decisions on what to allow or reject.

ユーザーは他のユーザーをブロックしたりミュートできます。ユーザーの設定内容はリレーに送信され、リレーはその設定に基づいてそれぞれのポリシーを再現できます。 リレーは、実際の設定と、検閲のためにシステムを操作しようとする設定を区別する必要があります。 リレーの管理者には、何を許可し、何を拒否するかを決定する能力が必要です。

Track 2 : Marketplaces & Value4Value

Make freedom of exchange fun again! Nostr extends beyond social. It is integrating ways for content creators to be supported through lightning micropayments, called zaps, for their creations. The possibilities of building niche value4value economies through the exchange of products, services, and ideas, is growing through various avenues: Marketplaces, fundraising, blogs, music, streaming... devise new robust ways of integrating NOSTR and Bitcoin of monetary and skill exchange. Seek to explore distributed, digital reciprocity and free trade. Encourage a culture of value4value.

自由な交流を再び楽しく！ Nostr はソーシャルを超えて広がります。 Zap と呼ばれるマイクロペイメントを通じて、コンテンツクリエイターの作品をサポートできる方法を兼ね備えています。 製品、サービス、アイデアの交換を通じてニッチな価値と価値（value4value）の経済を構築する可能性は、さまざまな手段を通じて拡大しています : マーケットプレイス、資金調達、ブログ、音楽、ストリーミングなど... Nostr とビットコインを組み合わせて、金銭とスキルの交換を行う新しい堅牢な方法を考案します。分散型、デジタル相互主義、自由貿易を探究してください。 価値対価値（value4value）の文化を促進してください。

A value4value culture is not only about the individuals using NOSTR products and services, but also about the developers and creatives building sustainable projects. What are ways of sustaining NOSTR through Bitcoin that do NOT make the individual user the product and that are privacy mindful?

value4value の文化は、Nostr の製品やサービスを使用する個人だけでなく、持続可能なプロジェクトを構築する開発者やクリエイターにも関係します。 個人ユーザーを製品にすることなくプライバシーに配慮しながら、ビットコインを通じて Nostr を持続させる方法は何ですか？

Possibilities...

On Social and Economic Signals

Zaps

Many nostr clients have implemented lightning zap payments. Imagine instead of liking a nostr note, you can zap someone's note and they can receive bits/sats in appreciation for their content. It is a strong signal to creators of the kind of content their audiences are looking for. The Apple App Store has recently banned the zapping of specific notes, per Apple's policy that makes the sale of digital content prohibited except when paid through their services. Fortunately, Nostr exists in many decentralized forms outside of app stores and the community is creating new and innovative ways to send bitcoin and free speech from relay to relay, circumventing barriers as they appear. What are solutions that can make NOSTR and zaps ubiquitous?

多くの Nostr クライアントが Zap を導入しています。Nostr での投稿を「いいね」する代わりに Zap すると、その内容に対する感謝としてビットコイン（サトシ）を受け取ることができるイメージです。 これは、フォロワーがどのような種類のコンテンツを求めているかをクリエイターに伝える強力なシグナルになります。 Apple App Storeは最近、サービスを通じて支払われる場合を除きデジタルコンテンツの販売を禁止するというAppleのポリシーに従い、特定の投稿への Zap を禁止しました。 幸い、Nostr は多くが App Store の外で分散型で存在しているため、コミュニティは障壁を回避しながら、ビットコインと言論の自由をリレーからリレーに送信するための革新的な方法を生み出しています。 Nostr と Zaps をユビキタスにするソリューションとは何ですか？

Track 3 : Empower Communities

Give choice and control back to the individual! Create paths forward to help onboard millions of new users and restore free and uncensored speech to the world

選択とコントロールを個人に返そう。 何百万人もの新規ユーザーの参加を支援し、自由で検閲されていない言論を世界に取り戻すための道筋を作り出してください。

Possibilities...

On Security, Privacy & Self-Custody

Private Communication

Direct Messages on NOSTR are encrypted, but metadata is leaked. If someone's key is compromised, whoever has access to that account can read those messages. Integrating secure and reliable encrypted communication protocols, like the SimpleX messaging protocol, is especially desired by the community, as many in Nostr are aware of the risks of surveillance, authoritarianism, government and Big Tech overreach... Private communication is important for individual rights, in particular for activists and journalists across the globe.

Nostr のダイレクト メッセージは暗号化されていますが、メタデータは漏洩します。 誰かのキーが侵害された場合、そのアカウントにアクセスできる人は誰でもそれらのメッセージを読むことができてしまうのです。Nostr の多くの人が監視、権威主義、政府とビッグテックの行き過ぎのリスクを認識しているため、 SimpleX メッセージング プロトコルのような安全で信頼性の高い暗号化通信プロトコルの統合が、コミュニティによって特に望まれています...プライベート通信は個人の権利にとって重要です 、特に世界中の活動家やジャーナリストにとって。

Zaps & Privacy

Current lightning zap payments tend to be custodial and not mindful of privacy, though they are helping onboard people unto lightning. What are ways that people can grow into non-custodial solutions? A wider adoption of Bolt-12 would improve zap payment privacy, what are ways to encourage that development? What are other possible solutions?

現在のザップの支払いは、ライトニングペイメントに出会うのに役立っているものの、カストディアル（管理的）でプライバシーに配慮していない傾向にあります。 ノンカストディアル（非監護的）なものになるよう解決する方法はありませんか？ Bolt-12 が広く採用されれば、Zap 支払いのプライバシーが向上しますが、その開発を促進するにはどのような方法がありますか？また、他に考えられる解決策はありませんか？

Closing Live 3-Day Sprint at the Nostrasia Conference

Nostrasia Tokyo 3日間のライブスプリントによる締めくくり

Tokyo | Nov 1-3 (you can also join virtually)

If you heard of the Nostrica unconference, which happened in Costa Rica in March of this year, Nostrasia is the second Nostr World conference, bringing NOSTR and Bitcoin awareness to the heart of Asia, where freedom communication and freedom money are direly needed.

今年の3月にコスタリカで開催された Nostrica のことをご存知の方もいると思いますが、ノストラジアは2回目の Nostr 世界カンファレンスです。自由なコミュニケーションと自由なお金が切実に必要とされているアジアの中心にNostr とビットコインの認識をもたらします。

Tokyo and Hong Kong are beautiful cultural hubs with budding Nostr and thriving Bitcoin communities of their own. We are eager to spread NOSTR education and development in those regions and beyond. We will close this Nostrasia month-long hackathon with a 3-day sprint at the Nostrasia Conference in Tokyo.

東京と香港は、新進気鋭のNostrと繁栄する独自のビットコインコミュニティを持つ美しい文化の中心地です。 私たちは、Nostr の教育と開発をこれらの地域やその他の地域に広めることに熱心に取り組んでいます。 この Nostrasia の 1 か月にわたるハッカソンは、Nostrasia Tokyo での 3 日間のスプリントをもって終了します。

We will have a dedicated workshop area and food for you to hack away on the final details of your projects. On the last day of the conference, the most robust projects will get time on stage to present. We will close the Nostrasia Hackathon with a special presentation.

プロジェクトの最終的な詳細を検討するための専用のワークショップ エリアと食事をご用意します。 カンファレンスの最終日には、最も強力なプロジェクトがステージ上でプレゼンテーションを行う時間が与えられます。 Nostrasia Hackathon は特別なプレゼンテーションで締めくくられます。

We cannot wait to see what new and exciting projects are proposed for the Nostrasia Hackathon. We’re eager to welcome devs and non-devs alike to contribute to this space and help #grownostr in any small way to help onboard Asia, and the rest of the world to this robust open communication protocol and decentralized freedom of speech tool.

Nostrasia Hackathon ではどんな斬新でエキサイティングなプロジェクトが提案されるのか楽しみです。 私たちは、開発者も非開発者も同様にこの分野に貢献し、アジアやその他の世界をこの堅牢なオープン通信プロトコルと分散型言論の自由ツールに参加させるために、どんな小さな方法でも #grownostr を支援してくれることを心から歓迎しています。

@ 8fb140b4:f948000c

As the title states, scratch behind my ear and you get it. 🐶🐾🫡

@ f866d5b1:c526b32f

ทุกสิ่งในโลกล้วนมีทั้งด้านความต้องการบริโภค (อุปสงค์) และด้านความต้องการผลิต (อุปทาน) อยู่เสมอ การแก้ปัญหาที่ต้องการให้เลิกบริโภคอย่างยั่งยืนต้องไปแก้ที่ต้นเหตุ นั่นคือ ต้องลดความต้องการบริโภคสินค้าลงให้ได้ ไม่ใช่การขยันออกกฎหมายมาห้ามนู้นนี่นั่นไปเรื่อยเปื่อย

หากเราขยันออกกฎหมายมาห้าม ก็ต้องมีการบังคับใช้กฎหมายอย่างเข้มงวดทุกกรณี เช่น การห้ามเด็กอายุต่ำกว่า 20 ปี ซื้อเครื่องดื่มที่มีแอลกอฮอล์ ก็ต้องทำให้เข้มงวด รัดกุม ไม่ใช่ปล่อยให้มีร้านขายของชำบางร้าน แอบขายให้เด็กที่อายุต่ำกว่า 20 ปี เป็นต้น 
 การแก้ปัญหาความต้องการบริโภคสินค้าเสพติดแบบยั่งยืนต้องแก้ที่ด้านอุปสงค์ ซึ่งเครื่องมือของรัฐที่มีไว้ใช้ในการลดจำนวนนักดื่มคือ การให้ความรู้ หรือ การเก็บภาษี ซึ่งมาตรการให้ความรู้ที่ถูกต้องมันยุ่งยากและใช้เวลาในการดำเนินนโยบายมากกว่ามาตรการเก็บภาษี



หากจะใช้มาตรการเก็บภาษีเพื่อแก้ปัญหาที่มาจากด้านอุปสงค์ ก็ต้องเก็บภาษีแบบเซอร์ไพร์ส คือประกาศขึ้นอัตราภาษีเหล้าเบียร์แบบสูงลิบลิ่วและไม่ทันได้ตั้งตัว ซึ่งอย่างเหล้าเบียร์เนี่ย มันเป็นสินค้าทดแทนได้ยาก เพราะมันเป็นเครื่องดื่มที่เสพแล้วติด จึงต้องเก็บภาษีให้สูงมาก ๆ เพื่อลดจำนวนนักดื่มลงมา


หรือไม่รัฐบาลก็ต้องให้ความรู้ความเข้าใจที่ถูกต้องถึงผลเสียที่ตามมาจากการดื่มเหล้าเบียร์ที่มากเกินไป หรือหาสินค้าทดแทนอื่น ๆ ที่สร้างความมึนเมา และสนุกสนานในวงสนทนา ที่ส่งผลเสียต่อสุขภาพน้อยกว่า มาให้ประชาชนได้บริโภคแทนเหล้าเบียร์ นั่นเอง

มิเช่นนั้น มาตรการภาษีที่ใช้ไป ก็เป็นแค่เพียงเครื่องมือในการสร้างรายได้ให้ภาครัฐเอาไปถลุงในเรื่องต่าง ๆ ที่อาจไม่เกิดประโยชน์แท้จริงต่อส่วนรวม ไม่ได้ทำให้ปัญหาที่เกิดจากการดื่มเครื่องดื่มแอลกอฮอล์มากเกินไป หายไปจากสังคมนั้นอย่างถาวร

@ 32e18276:5c68e245

Hey guys!

Another day, another TestFlight build. This fixes many mention bugs and includes bandwidth improvements.

During nostrica, jack told everyone to open their phones and say GM to fiatjaf. This actually brought down nostrica's wifi! Damus is really dumb when it first opens and makes many requests. Sometimes hundreds (nip05 validation, etc). This build fixes all those issues. Damus will no longer:

1. Make hundreds of nostr address validation requests.
2. Make tons of duplicate lnurl requests when validating zaps

nostr address validation only happens when you open someones profile now.

This build also fixes some annoying mention issues. If you forget a space when mentioning someone, it will automatically add it.

I've also removed the restriction where you were not allowed to login to "deleted" accounts. This was way too confusing for people, and logging into a deleted account will allow you to reset the profile information and get it going again. You're welcome NVK.

Another thing that was added in this build is support for _ usernames in nostr addresses. This will hide your full nostr address username when used. Damus will also hide your username if it matches your profile username. Damus always did this before but it was incorrect. Now it will show your full nostr address (nip05) with its proper username. You can stop bugging me about this now Semisol.

Last but not least there are some small tweaks to longform note padding. Nothing too crazy but it does make notes like this look less cramped.

Until next time!

Added

• Show nostr address username and support abbreviated _ usernames (William Casarin)
• Re-add nip05 badges to profiles (William Casarin)
• Add space when tagging users in posts if needed (William Casarin)
• Added padding under word count on longform account (William Casarin)

Fixed

• Don't spam lnurls when validating zaps (William Casarin)
• Eliminate nostr address validation bandwidth on startup (William Casarin)
• Allow user to login to deleted profile (William Casarin)
• Fix issue where typing cc@bob would produce brokenb ccnostr:bob mention (William Casarin)

@ a10260a2:caa23e3e

It seems like blogstack is meant to replace Substack if not already apparent by the name. If that's the case, it's already better in a few ways.

1. Hit the ground running

I'm already getting started out of the gate with more readers than I would have if I just started a Substack. This, of course, is due to the fact that I'm creating on top of a protocol where I'm able to have the same audience across all clients of that protocol. This is in stark contrast to the legacy apps from centralized entities where you have to corral your audience from one platform to the next.

2. Readers need not subscribe

Technically, if you're following me, you're subscribed. But you don't have to subscribe for a set price and amount of time (e.g. $5/month or $50/year). I believe this is a win for both of us as I can write my best notes and you can choose to reward me as you see fit. Value 4 value.

3. More conducive to conversation

Writing on Substack felt like writing into a void, with little to no feedback. A post shows up in my readers' inbox and I'll see some stats on whether it was opened or not. That's it. Based on what I've seen so far, blog posts created on Nostr appear in the client apps (e.g Damus, Primal, and Plebstr) as just another note, but with nice formatting and such. From there, I can receive zaps, shakas, comments, and even be reposted.

This is just the beginning. Right now, I'm using blogstack. But what's to stop me from using another tool down the line? I'll have the ability to do so by simply connecting my private key. Can't wait to see what new tools are created down the line.

So ₿ULLISH on #Nostr

@ 2448a66f:838296c9

Chef's notes

สูตรขนมกุยช่ายสำหรับทานแบบนึ่ง สูตรนี้ปั้นลูกขนาดพอดีคำได้ 25 ลูก

Details

• ⏲️ Prep time: 30 นาที
• 🍳 Cook time: 30 นาที
• 🍽️ Servings: 4

Ingredients

• แป้งมัน 50 กรัม
• แป้งข้าวเจ้า 25 กรัม
• แป้งท้าวยายม่อม 10 กรัม
• กุยช่าย 200 กรัม
• น้ำเปล่า 200 กรัม
• น้ำมันพืช 50 กรัม
• เกลือ 1 หยิบมือ
• เบกกิ้งโซดา 1 หยิบมือ

Directions

1. เทน้ำเปล่าลงไปผสมกับแป้งมัน แป้งข้าวเจ้า แป้งท้าวยายม่อม เกลือ คนจนส่วนผสมเข้ากัน ระวังอย่าให้แป้งเป็นก้อน
2. ใส่กุยช่าย น้ำมันพืชและ เบกกิ้งโซดา ลงไปผสมกับแป้ง และขย้ำจนกว่าน้ำแป้งจะเปลี่ยนเป็นสีเขียวเล็กน้อย เพื่อให้กลิ่นของกุยช่ายระเหยออกมา และทำให้กุยช่ายนิ่มลง
3. ตั้งกระทะบนเตา ใช้ไฟอ่อน เทส่วนผสมที่เราผสมไว้ลงไป กวนจนแป้งใส จับตัวเป็นก้อน ไม่ติดกระทะ
4. ปั้นแป้งขนาดพอดีคำ หรือจะกดให้เป็นแผ่นก็ได้ ตามใจชอบ
5. ระหว่างปั้นแป้งเป็นก้อน ให้ต้มน้ำเตรียมนึ่ง ใส่ใบเตยลงไปในน้ำ เพื่อเพิ่มความหอม
6. เมื่อน้ำเดือดได้ที่ นำแป้งที่ปั้นไว้ลงไปนึ่งประมาณ 10 นาที จนแป้งใส จากนั้นตั้งขึ้นพักให้อุ่น พร้อมเสิร์ฟ

@ 3cd2ea88:bafdaceb

📊 Negli ultimi giorni, il Grayscale Bitcoin Trust (GBTC) ha sperimentato un notevole deflusso di fondi, causato dalla sua recente conversione da fondo a ETF. In questo articolo, esamineremo le dinamiche di GBTC, analizzeremo le ragioni dietro il suo massiccio sell-off e valuteremo l'impatto potenziale su Bitcoin e sul mercato delle criptovalute nel complesso. 📊 Il Contesto di GBTC 📊 Il Grayscale Bitcoin Trust è un veicolo d'investimento regolamentato che consente agli investitori di ottenere esposizione ai movimenti di prezzo di Bitcoin senza possederne direttamente la criptovaluta. La sua recente conversione da fondo a ETF ha scatenato un significativo sell-off, con oltre $1,5 miliardi usciti dal fondo. 📊 Cause della Vendita di Massa 📊 Gli analisti di JPMorgan individuano diversi fattori alla base di questo sell-off. Una strategia chiave sembra essere il take profit adottato da alcuni investitori di GBTC, che chiudono posizioni per massimizzare i profitti. La struttura delle commissioni di GBTC, la più elevata tra i suoi omologhi, ha spinto alcuni investitori verso alternative con commissioni più basse, come l'iShares Bitcoin Trust (IBIT) di BlackRock. 📊 Impatto su Bitcoin e il Mercato delle Criptovalute 📊 Il sell-off di GBTC ha avuto un impatto significativo su Bitcoin, con una diminuzione dell'11% dal lancio dell'ETF su BTC negli Stati Uniti. Gli analisti avvertono che un ulteriore deflusso da GBTC potrebbe ammontare a $5-10 miliardi, mettendo in discussione la sua liquidità. Il fondatore di Galaxy Digital, Mike Novogratz, rimane ottimista, suggerendo che gli investitori potrebbero spostarsi su altri ETF con commissioni più competitive. 📊 Riflessioni e Conclusioni 📊 Il recente sell-off di GBTC sottolinea la necessità di maggiore flessibilità e commissioni competitive nel mercato delle criptovalute. Sebbene la vendita di massa fosse in parte prevedibile, l'entità del deflusso di fondi e la forte pressione sui prezzi di Bitcoin evidenziano l'interconnessione tra veicoli d'investimento e il mercato generale. 📊 L'impatto inatteso del sell-off di GBTC ha stimolato il dibattito sulla necessità di adeguare le commissioni per allinearle agli standard del settore. Gli investitori stanno ora rivalutando le loro strategie, considerando alternative con commissioni più competitive. Il sell-off di GBTC rappresenta un'opportunità per gli investitori tradizionali di accedere più facilmente al mercato delle criptovalute. 📊 Leggi l'articolo completo su Bitget Academy - https://www.bitget.com/it/academy/causes-and-impacts-of-gbtc-sell-off per una visione approfondita delle dinamiche di mercato e ulteriori dettagli sull'analisi del sell-off di GBTC. 📊 Bitget 10% di sconto a vita 6w5d o link: https://bonus.bitget.com/U1JNEK

@ 81870f53:29bef6a6

1月27日のメディア報道によると、本選挙が近づく中、バイデン政権は3月末までに530億ドル相当の第3弾「チップ法」補助金の交付を発表する予定で、インテルやTSMCなどが参入すると予想されている。大手半導体企業は全米での新工場建設を加速するため数十億ドルを受け取ることになる。

報道によると、今回の3回目の補助金は前2回とは異なり、先端半導体技術を対象とした補助金であり、資本額も大幅に増額されており、補助金を受けている企業のほとんどはスマートフォンや人工知能向けの先端チップを生産する製造会社であるという。 、など。

2022年8月、バイデン氏は米国の半導体の研究開発、製造、労働力育成に527億ドルを提供するチップ法に署名したが、法案の提出から1年以上が経過しても、米国政府は未だに補助金や譲歩を一切提供していない。以前はTSMCやIntelなどの大手チップメーカーと約束していた。

同メディアは、この問題に詳しい関係者の話として、バイデン氏が先端製造用チップの生産をさらに刺激するため、3月7日の一般教書演説の前にこのニュースを発表すると予想されており、インテルとTSMCが補助金を受け取る可能性が最も高いと伝えた。 :

インテルは、米国のオレゴン州、アリゾナ州、ニューメキシコ州、オハイオ州に435億ドル以上をかけて工場を改修または新設する計画だ。

TSMCは総投資額400億ドルをかけてアリゾナ州フェニックス近郊に2つのチップ工場を建設する計画だ。

世界有数の OEM である TSMC の米国でのプロジェクトは頻繁に阻止されており、今年 1 月の TSMC 法会議で TSMC 幹部は、米国政府の奨励金と税制補助金政策の不確実性を理由に、同社がプロジェクトを再び延期することを明らかにした。アリゾナ州の第2工場は2027年か2028年に稼働する予定で、これはTSMCが以前予想していた2026年より少なくとも1年遅れる。

さらにTSMC幹部らは、同工場で生産されるチップの具体的な種類はまだ決まっておらず、同工場で3ナノメートルの先端プロセスチップを生産するかどうかは不明であると指摘した。

TSMCは昨年7月、米国での最初の工場建設を延期し、生産時期を当初発表していた2024年から2025年に延期すると発表したが、当時TSMCは工場建設には熟練労働者不足の問題があったと主張していた。そしてコストの上昇。

TSMCの最高財務責任者、黄仁照氏によると、TSMCは第1工場のつまずきにより第2工場の建設が遅れたという。

この記事がお役に立てば幸いです。 もしそうなら、チップをおくるどうぞ https://getalby.com/p/bitcap

@ 3bf0c63f:aefa459d

Pequenos problemas que o Estado cria para a sociedade e que não são sempre lembrados

- **vale-transporte**: transferir o custo com o transporte do funcionário para um terceiro o estimula a morar longe de onde trabalha, já que morar perto é normalmente mais caro e a economia com transporte é inexistente.
- **atestado médico**: o direito a faltar o trabalho com atestado médico cria a exigência desse atestado para todas as situações, substituindo o livre acordo entre patrão e empregado e sobrecarregando os médicos e postos de saúde com visitas desnecessárias de assalariados resfriados.
- **prisões**: com dinheiro mal-administrado, burocracia e péssima alocação de recursos -- problemas que empresas privadas em competição (ou mesmo sem qualquer competição) saberiam resolver muito melhor -- o Estado fica sem presídios, com os poucos existentes entupidos, muito acima de sua alocação máxima, e com isto, segundo a bizarra corrente de responsabilidades que culpa o juiz que condenou o criminoso por sua morte na cadeia, juízes deixam de condenar à prisão os bandidos, soltando-os na rua.
- **justiça**: entrar com processos é grátis e isto faz proliferar a atividade dos advogados que se dedicam a criar problemas judiciais onde não seria necessário e a entupir os tribunais, impedindo-os de fazer o que mais deveriam fazer.
- **justiça**: como a justiça só obedece às leis e ignora acordos pessoais, escritos ou não, as pessoas não fazem acordos, recorrem sempre à justiça estatal, e entopem-na de assuntos que seriam muito melhor resolvidos entre vizinhos.
- **leis civis**: as leis criadas pelos parlamentares ignoram os costumes da sociedade e são um incentivo a que as pessoas não respeitem nem criem normas sociais -- que seriam maneiras mais rápidas, baratas e satisfatórias de resolver problemas.
- **leis de trãnsito**: quanto mais leis de trânsito, mais serviço de fiscalização são delegados aos policiais, que deixam de combater crimes por isto (afinal de contas, eles não querem de fato arriscar suas vidas combatendo o crime, a fiscalização é uma excelente desculpa para se esquivarem a esta responsabilidade).
- **financiamento educacional**: é uma espécie de subsídio às faculdades privadas que faz com que se criem cursos e mais cursos que são cada vez menos recheados de algum conhecimento ou técnica útil e cada vez mais inúteis.
- **leis de tombamento**: são um incentivo a que o dono de qualquer área ou construção "histórica" destrua todo e qualquer vestígio de história que houver nele antes que as autoridades descubram, o que poderia não acontecer se ele pudesse, por exemplo, usar, mostrar e se beneficiar da história daquele local sem correr o risco de perder, de fato, a sua propriedade.
- **zoneamento urbano**: torna as cidades mais espalhadas, criando uma necessidade gigantesca de carros, ônibus e outros meios de transporte para as pessoas se locomoverem das zonas de moradia para as zonas de trabalho.
- **zoneamento urbano**: faz com que as pessoas percam horas no trânsito todos os dias, o que é, além de um desperdício, um atentado contra a sua saúde, que estaria muito melhor servida numa caminhada diária entre a casa e o trabalho.
- **zoneamento urbano**: torna ruas e as casas menos seguras criando zonas enormes, tanto de residências quanto de indústrias, onde não há movimento de gente alguma.
- **escola obrigatória + currículo escolar nacional**: emburrece todas as crianças.
- **leis contra trabalho infantil**: tira das crianças a oportunidade de aprender ofícios úteis e levar um dinheiro para ajudar a família.
- **licitações**: como não existem os critérios do mercado para decidir qual é o melhor prestador de serviço, criam-se comissões de pessoas que vão decidir coisas. isto incentiva os prestadores de serviço que estão concorrendo na licitação a tentar comprar os membros dessas comissões. isto, fora a corrupção, gera problemas reais: __(i)__ a escolha dos serviços acaba sendo a pior possível, já que a empresa prestadora que vence está claramente mais dedicada a comprar comissões do que a fazer um bom trabalho (este problema afeta tantas áreas, desde a construção de estradas até a qualidade da merenda escolar, que é impossível listar aqui); __(ii)__ o processo corruptor acaba, no longo prazo, eliminando as empresas que prestavam e deixando para competir apenas as corruptas, e a qualidade tende a piorar progressivamente.
- **cartéis**: o Estado em geral cria e depois fica refém de vários grupos de interesse. o caso dos taxistas contra o Uber é o que está na moda hoje (e o que mostra como os Estados se comportam da mesma forma no mundo todo).
- **multas**: quando algum indivíduo ou empresa comete uma fraude financeira, ou causa algum dano material involuntário, as vítimas do caso são as pessoas que sofreram o dano ou perderam dinheiro, mas o Estado tem sempre leis que prevêem multas para os responsáveis. A justiça estatal é sempre muito rígida e rápida na aplicação dessas multas, mas relapsa e vaga no que diz respeito à indenização das vítimas. O que em geral acontece é que o Estado aplica uma enorme multa ao responsável pelo mal, retirando deste os recursos que dispunha para indenizar as vítimas, e se retira do caso, deixando estas desamparadas.
- **desapropriação**: o Estado pode pegar qualquer propriedade de qualquer pessoa mediante uma indenização que é necessariamente inferior ao valor da propriedade para o seu presente dono (caso contrário ele a teria vendido voluntariamente).
- **seguro-desemprego**: se há, por exemplo, um prazo mínimo de 1 ano para o sujeito ter direito a receber seguro-desemprego, isto o incentiva a planejar ficar apenas 1 ano em cada emprego (ano este que será sucedido por um período de desemprego remunerado), matando todas as possibilidades de aprendizado ou aquisição de experiência naquela empresa específica ou ascensão hierárquica.
- **previdência**: a previdência social tem todos os defeitos de cálculo do mundo, e não importa muito ela ser uma forma horrível de poupar dinheiro, porque ela tem garantias bizarras de longevidade fornecidas pelo Estado, além de ser compulsória. Isso serve para criar no imaginário geral a idéia da __aposentadoria__, uma época mágica em que todos os dias serão finais de semana. A idéia da aposentadoria influencia o sujeito a não se preocupar em ter um emprego que faça sentido, mas sim em ter um trabalho qualquer, que o permita se aposentar.
- **regulamentação impossível**: milhares de coisas são proibidas, há regulamentações sobre os aspectos mais mínimos de cada empreendimento ou construção ou espaço. se todas essas regulamentações fossem exigidas não haveria condições de produção e todos morreriam. portanto, elas não são exigidas. porém, o Estado, ou um agente individual imbuído do poder estatal pode, se desejar, exigi-las todas de um cidadão inimigo seu. qualquer pessoa pode viver a vida inteira sem cumprir nem 10% das regulamentações estatais, mas viverá também todo esse tempo com medo de se tornar um alvo de sua exigência, num estado de terror psicológico.
- **perversão de critérios**: para muitas coisas sobre as quais a sociedade normalmente chegaria a um valor ou comportamento "razoável" espontaneamente, o Estado dita regras. estas regras muitas vezes não são obrigatórias, são mais "sugestões" ou limites, como o salário mínimo, ou as 44 horas semanais de trabalho. a sociedade, porém, passa a usar esses valores como se fossem o normal. são raras, por exemplo, as ofertas de emprego que fogem à regra das 44h semanais.
- **inflação**: subir os preços é difícil e constrangedor para as empresas, pedir aumento de salário é difícil e constrangedor para o funcionário. a inflação força as pessoas a fazer isso, mas o aumento não é automático, como alguns economistas podem pensar (enquanto alguns outros ficam muito satisfeitos de que esse processo seja demorado e difícil).
- **inflação**: a inflação destrói a capacidade das pessoas de julgar preços entre concorrentes usando a própria memória.
- **inflação**: a inflação destrói os cálculos de lucro/prejuízo das empresas e prejudica enormemente as decisões empresariais que seriam baseadas neles.
- **inflação**: a inflação redistribui a riqueza dos mais pobres e mais afastados do sistema financeiro para os mais ricos, os bancos e as megaempresas.
- **inflação**: a inflação estimula o endividamento e o consumismo.
- **lixo:** ao prover coleta e armazenamento de lixo "grátis para todos" o Estado incentiva a criação de lixo. se tivessem que pagar para que recolhessem o seu lixo, as pessoas (e conseqüentemente as empresas) se empenhariam mais em produzir coisas usando menos plástico, menos embalagens, menos sacolas.
- **leis contra crimes financeiros:** ao criar legislação para dificultar acesso ao sistema financeiro por parte de criminosos a dificuldade e os custos para acesso a esse mesmo sistema pelas pessoas de bem cresce absurdamente, levando a um percentual enorme de gente incapaz de usá-lo, para detrimento de todos -- e no final das contas os grandes criminosos ainda conseguem burlar tudo.

@ 9810d9af:b3f2bf82

Chef's notes

Details

• ⏲️ Prep time: 60
• 🍳 Cook time: 30
• 🍽️ Servings: 4

Ingredients

• 1 pound lean ground pork
• 1¹/² cups finely chopped onions
• 1½ cups finely chopped chayote squash or sweet potato
• 1½ cups finely chopped jicama (or other root veg)
• 2 tablespoons minced garlic
• 1 tablespoon soy sauce
• 1 tablespoon ground black pepper
• 50 lumpia or spring roll wrap (about 7"x7")
• Hot chilli in oil is optional
• Plum sauce is favourite dip
• 1 large egg
• Generous pinch of sea salt
• 2 tablespoons oyster sauce
• ¹/² cup bread crumbs

Directions

1. In a large bowl or pot, blend all ingredients together mixing in with the ground meat throughly. Add bread crumbs as needed to thicken into a good paste.
2. Have a small dish on the side for dipping finger tips in water. Set up a work station with large cutting board or smooth surface. Set up the wraps by having them thawed from frozen and transferring them from packaging to a plate with a damp paper towel over pile of sheets. This will keep them fresh and prevent hardening too early.
3. Pour some warm water onto a plate and add a dash of flour or cornstarch to mix in, creating a kind of glue for your lumpia wraps!
4. Now the fun part! - Splash some water ("glue" mix) onto your clean, flat surface.
5. Carefully separate 2 sheets of wraps and place flat on the watered surface (in a diamond shape ideally)
6. Using a fork or spoon, scoop up about 1.5 table spoons of your meat/veg/spice mix into the center of the wrap. Try to create a 3" x 1" shape that is long left to right and form it solid and uniform as possible
7. Lift the bottom corner (nearest to you) of the wraps and fold over the meat, tucking under meat as tightly as possible.
8. Roll wrap and meat together about half way, fold in the sides. (you might need to splash more water on the corners or in folds if you find it is not sticking, be careful though bc it can over saturate and then your are F'd.
9. Complete the rolling and follow through while trying to keep sides near and secure. Some times I toss some flour in and around the final corner to add more stickiness.
10. Lay the completed rolled piece in a tupperware container and continue until you have amount desired.
11. *IT GETS EASIER AS YOU DEVELOP YOUR OWN TECHNIQUES, be patient and take your time.
12. Preheat your over/oil/airfryer Whip up an egg in a bowl and add a dash of milk or cream. Add pinch of salt and stir.
13. Spread some parchment paper on a strong baking sheet, spray with cooking spray.
14. brush all sides and around both end folds of each roll with generous coating of egg wash
15. Place on greased pan if oven baking (this is easiest and yields about 18-20 pieces quickly)
16. Bake uncovered, in oven, and on middle rack @400°F for about 15 min. Then turn all pieces over and bake for about another 15min.
17. Once all pieces are golden brown and crispy, remove from oven and transfer to a wire cooling rack.
18. Dipping sauce is whatever you like, but plum sauce is most appealing along with a hot chilli paste. Also can simply serve chopped on sticky rice.
19. If freezing pieces raw then do so quickly after rolling them. For best freezer storing results, lay them out separately when you put in freezer to grab a few at a time in order to keep them from blocking together.

@ 3bf0c63f:aefa459d

nostr - Notes and Other Stuff Transmitted by Relays

The simplest open protocol that is able to create a censorship-resistant global "social" network once and for all.

It doesn't rely on any trusted central server, hence it is resilient; it is based on cryptographic keys and signatures, so it is tamperproof; it does not rely on P2P techniques, therefore it works.

Very short summary of how it works, if you don't plan to read anything else:

Everybody runs a client. It can be a native client, a web client, etc. To publish something, you write a post, sign it with your key and send it to multiple relays (servers hosted by someone else, or yourself). To get updates from other people, you ask multiple relays if they know anything about these other people. Anyone can run a relay. A relay is very simple and dumb. It does nothing besides accepting posts from some people and forwarding to others. Relays don't have to be trusted. Signatures are verified on the client side.

This is needed because other solutions are broken:

The problem with Twitter

• Twitter has ads;
• Twitter uses bizarre techniques to keep you addicted;
• Twitter doesn't show an actual historical feed from people you follow;
• Twitter bans people;
• Twitter shadowbans people.
• Twitter has a lot of spam.

The problem with Mastodon and similar programs

• User identities are attached to domain names controlled by third-parties;
• Server owners can ban you, just like Twitter; Server owners can also block other servers;
• Migration between servers is an afterthought and can only be accomplished if servers cooperate. It doesn't work in an adversarial environment (all followers are lost);
• There are no clear incentives to run servers, therefore they tend to be run by enthusiasts and people who want to have their name attached to a cool domain. Then, users are subject to the despotism of a single person, which is often worse than that of a big company like Twitter, and they can't migrate out;
• Since servers tend to be run amateurishly, they are often abandoned after a while — which is effectively the same as banning everybody;
• It doesn't make sense to have a ton of servers if updates from every server will have to be painfully pushed (and saved!) to a ton of other servers. This point is exacerbated by the fact that servers tend to exist in huge numbers, therefore more data has to be passed to more places more often;
• For the specific example of video sharing, ActivityPub enthusiasts realized it would be completely impossible to transmit video from server to server the way text notes are, so they decided to keep the video hosted only from the single instance where it was posted to, which is similar to the Nostr approach.

The problem with SSB (Secure Scuttlebutt)

• It doesn't have many problems. I think it's great. In fact, I was going to use it as a basis for this, but
• its protocol is too complicated because it wasn't thought about being an open protocol at all. It was just written in JavaScript in probably a quick way to solve a specific problem and grew from that, therefore it has weird and unnecessary quirks like signing a JSON string which must strictly follow the rules of ECMA-262 6th Edition;
• It insists on having a chain of updates from a single user, which feels unnecessary to me and something that adds bloat and rigidity to the thing — each server/user needs to store all the chain of posts to be sure the new one is valid. Why? (Maybe they have a good reason);
• It is not as simple as Nostr, as it was primarily made for P2P syncing, with "pubs" being an afterthought;
• Still, it may be worth considering using SSB instead of this custom protocol and just adapting it to the client-relay server model, because reusing a standard is always better than trying to get people in a new one.

The problem with other solutions that require everybody to run their own server

• They require everybody to run their own server;
• Sometimes people can still be censored in these because domain names can be censored.

How does Nostr work?

• There are two components: clients and relays. Each user runs a client. Anyone can run a relay.
• Every user is identified by a public key. Every post is signed. Every client validates these signatures.
• Clients fetch data from relays of their choice and publish data to other relays of their choice. A relay doesn't talk to another relay, only directly to users.
• For example, to "follow" someone a user just instructs their client to query the relays it knows for posts from that public key.
• On startup, a client queries data from all relays it knows for all users it follows (for example, all updates from the last day), then displays that data to the user chronologically.
• A "post" can contain any kind of structured data, but the most used ones are going to find their way into the standard so all clients and relays can handle them seamlessly.

How does it solve the problems the networks above can't?

• Users getting banned and servers being closed
• A relay can block a user from publishing anything there, but that has no effect on them as they can still publish to other relays. Since users are identified by a public key, they don't lose their identities and their follower base when they get banned.
• Instead of requiring users to manually type new relay addresses (although this should also be supported), whenever someone you're following posts a server recommendation, the client should automatically add that to the list of relays it will query.
• If someone is using a relay to publish their data but wants to migrate to another one, they can publish a server recommendation to that previous relay and go;
• If someone gets banned from many relays such that they can't get their server recommendations broadcasted, they may still let some close friends know through other means with which relay they are publishing now. Then, these close friends can publish server recommendations to that new server, and slowly, the old follower base of the banned user will begin finding their posts again from the new relay.

• All of the above is valid too for when a relay ceases its operations.

• Censorship-resistance

• Each user can publish their updates to any number of relays.

• A relay can charge a fee (the negotiation of that fee is outside of the protocol for now) from users to publish there, which ensures censorship-resistance (there will always be some Russian server willing to take your money in exchange for serving your posts).

• Spam

• If spam is a concern for a relay, it can require payment for publication or some other form of authentication, such as an email address or phone, and associate these internally with a pubkey that then gets to publish to that relay — or other anti-spam techniques, like hashcash or captchas. If a relay is being used as a spam vector, it can easily be unlisted by clients, which can continue to fetch updates from other relays.

• Data storage

• For the network to stay healthy, there is no need for hundreds of active relays. In fact, it can work just fine with just a handful, given the fact that new relays can be created and spread through the network easily in case the existing relays start misbehaving. Therefore, the amount of data storage required, in general, is relatively less than Mastodon or similar software.

• Or considering a different outcome: one in which there exist hundreds of niche relays run by amateurs, each relaying updates from a small group of users. The architecture scales just as well: data is sent from users to a single server, and from that server directly to the users who will consume that. It doesn't have to be stored by anyone else. In this situation, it is not a big burden for any single server to process updates from others, and having amateur servers is not a problem.

• Video and other heavy content

• It's easy for a relay to reject large content, or to charge for accepting and hosting large content. When information and incentives are clear, it's easy for the market forces to solve the problem.

• Techniques to trick the user

• Each client can decide how to best show posts to users, so there is always the option of just consuming what you want in the manner you want — from using an AI to decide the order of the updates you'll see to just reading them in chronological order.

FAQ

• This is very simple. Why hasn't anyone done it before?

I don't know, but I imagine it has to do with the fact that people making social networks are either companies wanting to make money or P2P activists who want to make a thing completely without servers. They both fail to see the specific mix of both worlds that Nostr uses.

• How do I find people to follow?

First, you must know them and get their public key somehow, either by asking or by seeing it referenced somewhere. Once you're inside a Nostr social network you'll be able to see them interacting with other people and then you can also start following and interacting with these others.

• How do I find relays? What happens if I'm not connected to the same relays someone else is?

You won't be able to communicate with that person. But there are hints on events that can be used so that your client software (or you, manually) knows how to connect to the other person's relay and interact with them. There are other ideas on how to solve this too in the future but we can't ever promise perfect reachability, no protocol can.

• Can I know how many people are following me?

No, but you can get some estimates if relays cooperate in an extra-protocol way.

• What incentive is there for people to run relays?

The question is misleading. It assumes that relays are free dumb pipes that exist such that people can move data around through them. In this case yes, the incentives would not exist. This in fact could be said of DHT nodes in all other p2p network stacks: what incentive is there for people to run DHT nodes?

• Nostr enables you to move between server relays or use multiple relays but if these relays are just on AWS or Azure what’s the difference?

There are literally thousands of VPS providers scattered all around the globe today, there is not only AWS or Azure. AWS or Azure are exactly the providers used by single centralized service providers that need a lot of scale, and even then not just these two. For smaller relay servers any VPS will do the job very well.

@ 8fb140b4:f948000c

Test Bounty Note

@ e6ce6154:275e3444

Este artigo foi censurado pelo estado e fomos obrigados a deletá-lo após ameaça de homens armados virem nos visitar e agredir nossa vida e propriedade.

Isto é mais uma prova que os autoproclamados antirracistas são piores que os racistas.

https://rothbardbrasil.com/pelo-direito-de-ser-racista-fascista-machista-e-homofobico

Segue artigo na íntegra. 👇

Sem dúvida, a escalada autoritária do totalitarismo cultural progressista nos últimos anos tem sido sumariamente deletéria e prejudicial para a liberdade de expressão. Como seria de se esperar, a cada dia que passa o autoritarismo progressista continua a se expandir de maneira irrefreável, prejudicando a liberdade dos indivíduos de formas cada vez mais deploráveis e contundentes.

Com a ascensão da tirania politicamente correta e sua invasão a todos os terrenos culturais, o autoritarismo progressista foi se alastrando e consolidando sua hegemonia em determinados segmentos. Com a eventual eclosão e a expansão da opressiva e despótica cultura do cancelamento — uma progênie inevitável do totalitarismo progressista —, todas as pessoas que manifestam opiniões, crenças ou posicionamentos que não estão alinhados com as pautas universitárias da moda tornam-se um alvo.

Há algumas semanas, vimos a enorme repercussão causada pelo caso envolvendo o jogador profissional de vôlei Maurício Sousa, que foi cancelado pelo simples fato de ter emitido sua opinião pessoal sobre um personagem de história em quadrinhos, Jon Kent, o novo Superman, que é bissexual. Maurício Sousa reprovou a conduta sexual do personagem, o que é um direito pessoal inalienável que ele tem. Ele não é obrigado a gostar ou aprovar a bissexualidade. Como qualquer pessoa, ele tem o direito pleno de criticar tudo aquilo que ele não gosta. No entanto, pelo simples fato de emitir a sua opinião pessoal, Maurício Sousa foi acusado de homofobia e teve seu contrato rescindido, sendo desligado do Minas Tênis Clube.

Lamentavelmente, Maurício Sousa não foi o primeiro e nem será o último indivíduo a sofrer com a opressiva e autoritária cultura do cancelamento. Como uma tirania cultural que está em plena ascensão e usufrui de um amplo apoio do establishment, essa nova forma de totalitarismo cultural colorido e festivo está se impondo de formas e maneiras bastante contundentes em praticamente todas as esferas da sociedade contemporânea. Sua intenção é relegar ao ostracismo todos aqueles que não se curvam ao totalitarismo progressista, criminalizando opiniões e crenças que divergem do culto à libertinagem hedonista pós-moderna. Oculto por trás de todo esse ativismo autoritário, o que temos de fato é uma profunda hostilidade por padrões morais tradicionalistas, cristãos e conservadores.

No entanto, é fundamental entendermos uma questão imperativa, que explica em partes o conflito aqui criado — todos os progressistas contemporâneos são crias oriundas do direito positivo. Por essa razão, eles jamais entenderão de forma pragmática e objetiva conceitos como criminalidade, direitos de propriedade, agressão e liberdade de expressão pela perspectiva do jusnaturalismo, que é manifestamente o direito em seu estado mais puro, correto, ético e equilibrado.

Pela ótica jusnaturalista, uma opinião é uma opinião. Ponto final. E absolutamente ninguém deve ser preso, cancelado, sabotado ou boicotado por expressar uma opinião particular sobre qualquer assunto. Palavras não agridem ninguém, portanto jamais poderiam ser consideradas um crime em si. Apenas deveriam ser tipificados como crimes agressões de caráter objetivo, como roubo, sequestro, fraude, extorsão, estupro e infrações similares, que representam uma ameaça direta à integridade física da vítima, ou que busquem subtrair alguma posse empregando a violência.

Infelizmente, a geração floquinho de neve — terrivelmente histérica, egocêntrica e sensível — fica profundamente ofendida e consternada sempre que alguém defende posicionamentos contrários à religião progressista. Por essa razão, os guerreiros da justiça social sinceramente acreditam que o papai-estado deve censurar todas as opiniões que eles não gostam de ouvir, assim como deve também criar leis para encarcerar todos aqueles que falam ou escrevem coisas que desagradam a militância.

Como a geração floquinho de neve foi criada para acreditar que todas as suas vontades pessoais e disposições ideológicas devem ser sumariamente atendidas pelo papai-estado, eles embarcaram em uma cruzada moral que pretende erradicar todas as coisas que são ofensivas à ideologia progressista; só assim eles poderão deflagrar na Terra o seu tão sonhado paraíso hedonista e igualitário, de inimaginável esplendor e felicidade.

Em virtude do seu comportamento intrinsecamente despótico, autoritário e egocêntrico, acaba sendo inevitável que militantes progressistas problematizem tudo aquilo que os desagrada.

Como são criaturas inúteis destituídas de ocupação real e verdadeiro sentido na vida, sendo oprimidas unicamente na sua própria imaginação, militantes progressistas precisam constantemente inventar novos vilões para serem combatidos.

Partindo dessa perspectiva, é natural para a militância que absolutamente tudo que exista no mundo e que não se enquadra com as regras autoritárias e restritivas da religião progressista seja encarado como um problema. Para a geração floquinho de neve, o capitalismo é um problema. O fascismo é um problema. A iniciativa privada é um problema. O homem branco, tradicionalista, conservador e heterossexual é um problema. A desigualdade é um problema. A liberdade é um problema. Monteiro Lobato é um problema (sim, até mesmo o renomado ícone da literatura brasileira, autor — entre outros títulos — de Urupês, foi vítima da cultura do cancelamento, acusado de ser racista e eugenista).

Para a esquerda, praticamente tudo é um problema. Na mentalidade da militância progressista, tudo é motivo para reclamação. Foi em função desse comportamento histérico, histriônico e infantil que o famoso pensador conservador-libertário americano P. J. O’Rourke afirmou que “o esquerdismo é uma filosofia de pirralhos chorões”. O que é uma verdade absoluta e irrefutável em todos os sentidos.

De fato, todas as filosofias de esquerda de forma geral são idealizações utópicas e infantis de um mundo perfeito. Enquanto o mundo não se transformar naquela colorida e vibrante utopia que é apresentada pela cartilha socialista padrão, militantes continuarão a reclamar contra tudo o que existe no mundo de forma agressiva, visceral e beligerante. Evidentemente, eles não vão fazer absolutamente nada de positivo ou construtivo para que o mundo se transforme no gracioso paraíso que eles tanto desejam ver consolidado, mas eles continuarão a berrar e vociferar muito em sua busca incessante pela utopia, marcando presença em passeatas inúteis ou combatendo o fascismo imaginário nas redes sociais.

Sem dúvida, estamos muito perto de ver leis absurdas e estúpidas sendo implementadas, para agradar a militância da terra colorida do assistencialismo eterno onde nada é escasso e tudo cai do céu. Em breve, você não poderá usar calças pretas, pois elas serão consideradas peças de vestuário excessivamente heterossexuais. Apenas calças amarelas ou coloridas serão permitidas. Você também terá que tingir de cor-de-rosa uma mecha do seu cabelo; pois preservar o seu cabelo na sua cor natural é heteronormativo demais da sua parte, sendo portanto um componente demasiadamente opressor da sociedade.

Você também não poderá ver filmes de guerra ou de ação, apenas comédias românticas, pois certos gêneros de filmes exaltam a violência do patriarcado e isso impede o mundo de se tornar uma graciosa festa colorida de fraternidades universitárias ungidas por pôneis resplandecentes, hedonismo infinito, vadiagem universitária e autogratificação psicodélica, que certamente são elementos indispensáveis para se produzir o paraíso na Terra.

Sabemos perfeitamente, no entanto, que dentre as atitudes “opressivas” que a militância progressista mais se empenha em combater, estão o racismo, o fascismo, o machismo e a homofobia. No entanto, é fundamental entender que ser racista, fascista, machista ou homofóbico não são crimes em si. Na prática, todos esses elementos são apenas traços de personalidade; e eles não podem ser pura e simplesmente criminalizados porque ideólogos e militantes progressistas iluminados não gostam deles.

Tanto pela ética quanto pela ótica jusnaturalista, é facilmente compreensível entender que esses traços de personalidade não podem ser criminalizados ou proibidos simplesmente porque integrantes de uma ideologia não tem nenhuma apreciação ou simpatia por eles. Da mesma forma, nenhum desses traços de personalidade representa em si um perigo para a sociedade, pelo simples fato de existir. Por incrível que pareça, até mesmo o machismo, o racismo, o fascismo e a homofobia merecem a devida apologia.

Mas vamos analisar cada um desses tópicos separadamente para entender isso melhor.

Racismo

Quando falamos no Japão, normalmente não fazemos nenhuma associação da sociedade japonesa com o racismo. No entanto, é incontestável o fato de que a sociedade japonesa pode ser considerada uma das sociedades mais racistas do mundo. E a verdade é que não há absolutamente nada de errado com isso.

Aproximadamente 97% da população do Japão é nativa; apenas 3% do componente populacional é constituído por estrangeiros (a população do Japão é estimada em aproximadamente 126 milhões de habitantes). Isso faz a sociedade japonesa ser uma das mais homogêneas do mundo. As autoridades japonesas reconhecidamente dificultam processos de seleção e aplicação a estrangeiros que desejam se tornar residentes. E a maioria dos japoneses aprova essa decisão.

Diversos estabelecimentos comerciais como hotéis, bares e restaurantes por todo o país tem placas na entrada que dizem “somente para japoneses” e a maioria destes estabelecimentos se recusa ostensivamente a atender ou aceitar clientes estrangeiros, não importa quão ricos ou abastados sejam.

Na Terra do Sol Nascente, a hostilidade e a desconfiança natural para com estrangeiros é tão grande que até mesmo indivíduos que nascem em algum outro país, mas são filhos de pais japoneses, não são considerados cidadãos plenamente japoneses.

Se estes indivíduos decidem sair do seu país de origem para se estabelecer no Japão — mesmo tendo descendência nipônica legítima e inquestionável —, eles enfrentarão uma discriminação social considerável, especialmente se não dominarem o idioma japonês de forma impecável. Esse fato mostra que a discriminação é uma parte tão indissociável quanto elementar da sociedade japonesa, e ela está tão profundamente arraigada à cultura nipônica que é praticamente impossível alterá-la ou atenuá-la por qualquer motivo.

A verdade é que — quando falamos de um país como o Japão — nem todos os discursos politicamente corretos do mundo, nem a histeria progressista ocidental mais inflamada poderão algum dia modificar, extirpar ou sequer atenuar o componente racista da cultura nipônica. E isso é consequência de uma questão tão simples quanto primordial: discriminar faz parte da natureza humana, sendo tanto um direito individual quanto um elemento cultural inerente à muitas nações do mundo. Os japoneses não tem problema algum em admitir ou institucionalizar o seu preconceito, justamente pelo fato de que a ideologia politicamente correta não tem no oriente a força e a presença que tem no ocidente.

E é fundamental enfatizar que, sendo de natureza pacífica — ou seja, não violando nem agredindo terceiros —, a discriminação é um recurso natural dos seres humanos, que está diretamente associada a questões como familiaridade e segurança.

Absolutamente ninguém deve ser forçado a apreciar ou integrar-se a raças, etnias, pessoas ou tribos que não lhe transmitem sentimentos de segurança ou familiaridade. Integração forçada é o verdadeiro crime, e isso diversos países europeus — principalmente os escandinavos (países que lideram o ranking de submissão à ideologia politicamente correta) — aprenderam da pior forma possível.

A integração forçada com imigrantes islâmicos resultou em ondas de assassinato, estupro e violência inimagináveis para diversos países europeus, até então civilizados, que a imprensa ocidental politicamente correta e a militância progressista estão permanentemente tentando esconder, porque não desejam que o ocidente descubra como a agenda “humanitária” de integração forçada dos povos muçulmanos em países do Velho Mundo resultou em algumas das piores chacinas e tragédias na história recente da Europa.

Ou seja, ao discriminarem estrangeiros, os japoneses estão apenas se protegendo e lutando para preservar sua nação como um ambiente cultural, étnico e social que lhe é seguro e familiar, assim se opondo a mudanças bruscas, indesejadas e antinaturais, que poderiam comprometer a estabilidade social do país.

A discriminação — sendo de natureza pacífica —, é benévola, salutar e indubitavelmente ajuda a manter a estabilidade social da comunidade. Toda e qualquer forma de integração forçada deve ser repudiada com veemência, pois, mais cedo ou mais tarde, ela irá subverter a ordem social vigente, e sempre será acompanhada de deploráveis e dramáticos resultados.

Para citar novamente os países escandinavos, a Suécia é um excelente exemplo do que não fazer. Tendo seguido o caminho contrário ao da discriminação racional praticada pela sociedade japonesa, atualmente a sociedade sueca — além de afundar de forma consistente na lama da libertinagem, da decadência e da deterioração progressista — sofre em demasia com os imigrantes muçulmanos, que foram deixados praticamente livres para matar, saquear, esquartejar e estuprar quem eles quiserem. Hoje, eles são praticamente intocáveis, visto que denunciá-los, desmoralizá-los ou acusá-los de qualquer crime é uma atitude politicamente incorreta e altamente reprovada pelo establishment progressista. A elite socialista sueca jamais se atreve a acusá-los de qualquer crime, pois temem ser classificados como xenófobos e intolerantes. Ou seja, a desgraça da Europa, sobretudo dos países escandinavos, foi não ter oferecido nenhuma resistência à ideologia progressista politicamente correta. Hoje, eles são totalmente submissos a ela.

O exemplo do Japão mostra, portanto — para além de qualquer dúvida —, a importância ética e prática da discriminação, que é perfeitamente aceitável e natural, sendo uma tendência inerente aos seres humanos, e portanto intrínseca a determinados comportamentos, sociedades e culturas.

Indo ainda mais longe nessa questão, devemos entender que na verdade todos nós discriminamos, e não existe absolutamente nada de errado nisso. Discriminar pessoas faz parte da natureza humana e quem se recusa a admitir esse fato é um hipócrita. Mulheres discriminam homens na hora de selecionar um parceiro; elas avaliam diversos quesitos, como altura, aparência, status social, condição financeira e carisma. E dentre suas opções, elas sempre escolherão o homem mais atraente, másculo e viril, em detrimento de todos os baixinhos, calvos, carentes, frágeis e inibidos que possam estar disponíveis. Da mesma forma, homens sempre terão preferência por mulheres jovens, atraentes e delicadas, em detrimento de todas as feministas de meia-idade, acima do peso, de cabelo pintado, que são mães solteiras e militantes socialistas. A própria militância progressista discrimina pessoas de forma virulenta e intransigente, como fica evidente no tratamento que dispensam a mulheres bolsonaristas e a negros de direita.

A verdade é que — não importa o nível de histeria da militância progressista — a discriminação é inerente à condição humana e um direito natural inalienável de todos. É parte indissociável da natureza humana e qualquer pessoa pode e deve exercer esse direito sempre que desejar. Não existe absolutamente nada de errado em discriminar pessoas. O problema real é a ideologia progressista e o autoritarismo politicamente correto, movimentos tirânicos que não respeitam o direito das pessoas de discriminar.

Fascismo

Quando falamos de fascismo, precisamos entender que, para a esquerda política, o fascismo é compreendido como um conceito completamente divorciado do seu significado original. Para um militante de esquerda, fascista é todo aquele que defende posicionamentos contrários ao progressismo, não se referindo necessariamente a um fascista clássico.

Mas, seja como for, é necessário entender que — como qualquer ideologia política — até mesmo o fascismo clássico tem o direito de existir e ocupar o seu devido lugar; portanto, fascistas não devem ser arbitrariamente censurados, apesar de defenderem conceitos que representam uma completa antítese de tudo aquilo que é valioso para os entusiastas da liberdade.

Em um país como o Brasil, onde socialistas e comunistas tem total liberdade para se expressar, defender suas ideologias e até mesmo formar partidos políticos, não faz absolutamente o menor sentido que fascistas — e até mesmo nazistas assumidos — sofram qualquer tipo de discriminação. Embora socialistas e comunistas se sintam moralmente superiores aos fascistas (ou a qualquer outra filosofia política ou escola de pensamento), sabemos perfeitamente que o seu senso de superioridade é fruto de uma pueril romantização universitária da sua própria ideologia. A história mostra efetivamente que o socialismo clássico e o comunismo causaram muito mais destruição do que o fascismo.

Portanto, se socialistas e comunistas tem total liberdade para se expressar, não existe a menor razão para que fascistas não usufruam dessa mesma liberdade.

É claro, nesse ponto, seremos invariavelmente confrontados por um oportuno dilema — o famoso paradoxo da intolerância, de Karl Popper. Até que ponto uma sociedade livre e tolerante deve tolerar a intolerância (inerente a ideologias totalitárias)?

As leis de propriedade privada resolveriam isso em uma sociedade livre. O mais importante a levarmos em consideração no atual contexto, no entanto — ao defender ou criticar uma determinada ideologia, filosofia ou escola de pensamento —, é entender que, seja ela qual for, ela tem o direito de existir. E todas as pessoas que a defendem tem o direito de defendê-la, da mesma maneira que todos os seus detratores tem o direito de criticá-la.

Essa é uma forte razão para jamais apoiarmos a censura. Muito pelo contrário, devemos repudiar com veemência e intransigência toda e qualquer forma de censura, especialmente a estatal.

Existem duas fortes razões para isso:

A primeira delas é a volatilidade da censura (especialmente a estatal). A censura oficial do governo, depois que é implementada, torna-se absolutamente incontrolável. Hoje, ela pode estar apontada para um grupo de pessoas cujas ideias divergem das suas. Mas amanhã, ela pode estar apontada justamente para as ideias que você defende. É fundamental, portanto, compreendermos que a censura estatal é incontrolável. Sob qualquer ponto de vista, é muito mais vantajoso que exista uma vasta pluralidade de ideias conflitantes na sociedade competindo entre si, do que o estado decidir que ideias podem ser difundidas ou não.

Além do mais, libertários e anarcocapitalistas não podem nunca esperar qualquer tipo de simpatia por parte das autoridades governamentais. Para o estado, seria infinitamente mais prático e vantajoso criminalizar o libertarianismo e o anarcocapitalismo — sob a alegação de que são filosofias perigosas difundidas por extremistas radicais que ameaçam o estado democrático de direito — do que o fascismo ou qualquer outra ideologia centralizada em governos burocráticos e onipotentes. Portanto, defender a censura, especialmente a estatal, representa sempre um perigo para o próprio indivíduo, que mais cedo ou mais tarde poderá ver a censura oficial do sistema se voltar contra ele.

Outra razão pela qual libertários jamais devem defender a censura, é porque — ao contrário dos estatistas — não é coerente que defensores da liberdade se comportem como se o estado fosse o seu papai e o governo fosse a sua mamãe. Não devemos terceirizar nossas próprias responsabilidades, tampouco devemos nos comportar como adultos infantilizados. Assumimos a responsabilidade de combater todas as ideologias e filosofias que agridem a liberdade e os seres humanos. Não procuramos políticos ou burocratas para executar essa tarefa por nós.

Portanto, se você ver um fascista sendo censurado nas redes sociais ou em qualquer outro lugar, assuma suas dores. Sinta-se compelido a defendê-lo, mostre aos seus detratores que ele tem todo direito de se expressar, como qualquer pessoa. Você não tem obrigação de concordar com ele ou apreciar as ideias que ele defende. Mas silenciar arbitrariamente qualquer pessoa não é uma pauta que honra a liberdade.

Se você não gosta de estado, planejamento central, burocracia, impostos, tarifas, políticas coletivistas, nacionalistas e desenvolvimentistas, mostre com argumentos coesos e convincentes porque a liberdade e o livre mercado são superiores a todos esses conceitos. Mas repudie a censura com intransigência e mordacidade.

Em primeiro lugar, porque você aprecia e defende a liberdade de expressão para todas as pessoas. E em segundo lugar, por entender perfeitamente que — se a censura eventualmente se tornar uma política de estado vigente entre a sociedade — é mais provável que ela atinja primeiro os defensores da liberdade do que os defensores do estado.

Machismo

Muitos elementos do comportamento masculino que hoje são atacados com virulência e considerados machistas pelo movimento progressista são na verdade manifestações naturais intrínsecas ao homem, que nossos avôs cultivaram ao longo de suas vidas sem serem recriminados por isso. Com a ascensão do feminismo, do progressismo e a eventual problematização do sexo masculino, o antagonismo militante dos principais líderes da revolução sexual da contracultura passou a naturalmente condenar todos os atributos genuinamente masculinos, por considerá-los símbolos de opressão e dominação social.

Apesar do Brasil ser uma sociedade liberal ultra-progressista, onde o estado protege mais as mulheres do que as crianças — afinal, a cada semana novas leis são implementadas concedendo inúmeros privilégios e benefícios às mulheres, aos quais elas jamais teriam direito em uma sociedade genuinamente machista e patriarcal —, a esquerda política persiste em tentar difundir a fantasia da opressão masculina e o mito de que vivemos em uma sociedade machista e patriarcal.

Como sempre, a realidade mostra um cenário muito diferente daquilo que é pregado pela militância da terra da fantasia. O Brasil atual não tem absolutamente nada de machista ou patriarcal. No Brasil, mulheres podem votar, podem ocupar posições de poder e autoridade tanto na esfera pública quanto em companhias privadas, podem se candidatar a cargos políticos, podem ser vereadoras, deputadas, governadoras, podem ser proprietárias do próprio negócio, podem se divorciar, podem dirigir, podem comprar armas, podem andar de biquíni nas praias, podem usar saias extremamente curtas, podem ver programas de televisão sobre sexo voltados única e exclusivamente para o público feminino, podem se casar com outras mulheres, podem ser promíscuas, podem consumir bebidas alcoólicas ao ponto da embriaguez, e podem fazer praticamente tudo aquilo que elas desejarem. No Brasil do século XXI, as mulheres são genuinamente livres para fazer as próprias escolhas em praticamente todos os aspectos de suas vidas. O que mostra efetivamente que a tal opressão do patriarcado não existe.

O liberalismo social extremo do qual as mulheres usufruem no Brasil atual — e que poderíamos estender a toda a sociedade contemporânea ocidental — é suficiente para desmantelar completamente a fábula feminista da sociedade patriarcal machista e opressora, que existe única e exclusivamente no mundinho de fantasias ideológicas da esquerda progressista.

Tão importante quanto, é fundamental compreender que nenhum homem é obrigado a levar o feminismo a sério ou considerá-lo um movimento social e político legítimo. Para um homem, ser considerado machista ou até mesmo assumir-se como um não deveria ser um problema. O progressismo e o feminismo — com o seu nefasto hábito de demonizar os homens, bem como todos os elementos inerentes ao comportamento e a cultura masculina — é que são o verdadeiro problema, conforme tentam modificar o homem para transformá-lo em algo que ele não é nem deveria ser: uma criatura dócil, passiva e submissa, que é comandada por ideologias hostis e antinaturais, que não respeitam a hierarquia de uma ordem social milenar e condições inerentes à própria natureza humana. Com o seu hábito de tentar modificar tudo através de leis e decretos, o feminismo e o progressismo mostram efetivamente que o seu real objetivo é criminalizar a masculinidade.

A verdade é que — usufruindo de um nível elevado de liberdades — não existe praticamente nada que a mulher brasileira do século XXI não possa fazer. Adicionalmente, o governo dá as mulheres uma quantidade tão avassaladora de vantagens, privilégios e benefícios, que está ficando cada vez mais difícil para elas encontrarem razões válidas para reclamarem da vida. Se o projeto de lei que pretende fornecer um auxílio mensal de mil e duzentos reais para mães solteiras for aprovado pelo senado, muitas mulheres que tem filhos não precisarão nem mesmo trabalhar para ter sustento. E tantas outras procurarão engravidar, para ter direito a receber uma mesada mensal do governo até o seu filho completar a maioridade.

O que a militância colorida da terra da fantasia convenientemente ignora — pois a realidade nunca corresponde ao seu conto de fadas ideológico — é que o mundo de uma forma geral continua sendo muito mais implacável com os homens do que é com as mulheres. No Brasil, a esmagadora maioria dos suicídios é praticada por homens, a maioria das vítimas de homicídio são homens e de cada quatro moradores de rua, três são homens. Mas é evidente que uma sociedade liberal ultra-progressista não se importa com os homens, pois ela não é influenciada por fatos concretos ou pela realidade. Seu objetivo é simplesmente atender as disposições de uma agenda ideológica, não importa quão divorciadas da realidade elas são.

O nível exacerbado de liberdades sociais e privilégios governamentais dos quais as mulheres brasileiras usufruem é suficiente para destruir a fantasiosa fábula da sociedade machista, opressora e patriarcal. Se as mulheres brasileiras não estão felizes, a culpa definitivamente não é dos homens. Se a vasta profusão de liberdades, privilégios e benefícios da sociedade ocidental não as deixa plenamente saciadas e satisfeitas, elas podem sempre mudar de ares e tentar uma vida mais abnegada e espartana em países como Irã, Paquistão ou Afeganistão. Quem sabe assim elas não se sentirão melhores e mais realizadas?

Homofobia

Quando falamos em homofobia, entramos em uma categoria muito parecida com a do racismo: o direito de discriminação é totalmente válido. Absolutamente ninguém deve ser obrigado a aceitar homossexuais ou considerar o homossexualismo como algo normal. Sendo cristão, não existe nem sequer a mais vaga possibilidade de que algum dia eu venha a aceitar o homossexualismo como algo natural. O homossexualismo se qualifica como um grave desvio de conduta e um pecado contra o Criador.

A Bíblia proíbe terminantemente conduta sexual imoral, o que — além do homossexualismo — inclui adultério, fornicação, incesto e bestialidade, entre outras formas igualmente pérfidas de degradação.

Segue abaixo três passagens bíblicas que proíbem terminantemente a conduta homossexual:

“Não te deitarás com um homem como se deita com uma mulher. Isso é abominável!” (Levítico 18:22 — King James Atualizada)

“Se um homem se deitar com outro homem, como se deita com mulher, ambos terão praticado abominação; certamente serão mortos; o seu sangue estará sobre eles.” (Levítico 20:13 — João Ferreira de Almeida Atualizada)

“O quê! Não sabeis que os injustos não herdarão o reino de Deus? Não sejais desencaminhados. Nem fornicadores, nem idólatras, nem adúlteros, nem homens mantidos para propósitos desnaturais, nem homens que se deitam com homens, nem ladrões, nem gananciosos, nem beberrões, nem injuriadores, nem extorsores herdarão o reino de Deus.” (1 Coríntios 6:9,10 —Tradução do Novo Mundo das Escrituras Sagradas com Referências)

Se você não é religioso, pode simplesmente levar em consideração o argumento do respeito pela ordem natural. A ordem natural é incondicional e incisiva com relação a uma questão: o complemento de tudo o que existe é o seu oposto, não o seu igual. O complemento do dia é a noite, o complemento da luz é a escuridão, o complemento da água, que é líquida, é a terra, que é sólida. E como sabemos o complemento do macho — de sua respectiva espécie — é a fêmea.

Portanto, o complemento do homem, o macho da espécie humana, é naturalmente a mulher, a fêmea da espécie humana. Um homem e uma mulher podem naturalmente se reproduzir, porque são um complemento biológico natural. Por outro lado, um homem e outro homem são incapazes de se reproduzir, assim como uma mulher e outra mulher.

Infelizmente, o mundo atual está longe de aceitar como plenamente estabelecida a ordem natural pelo simples fato dela existir, visto que tentam subvertê-la a qualquer custo, não importa o malabarismo intelectual que tenham que fazer para justificar os seus pontos de vista distorcidos e antinaturais. A libertinagem irrefreável e a imoralidade bestial do mundo contemporâneo pós-moderno não reconhecem nenhum tipo de limite. Quem tenta restabelecer princípios morais salutares é imediatamente considerado um vilão retrógrado e repressivo, sendo ativamente demonizado pela militância do hedonismo, da luxúria e da licenciosidade desenfreada e sem limites.

Definitivamente, fazer a apologia da moralidade, do autocontrole e do autodomínio não faz nenhum sucesso na Sodoma e Gomorra global dos dias atuais. O que faz sucesso é lacração, devassidão, promiscuidade e prazeres carnais vazios. O famoso escritor e filósofo francês Albert Camus expressou uma verdade contundente quando disse: “Uma só frase lhe bastará para definir o homem moderno — fornicava e lia jornais”.

Qualquer indivíduo tem o direito inalienável de discriminar ativamente homossexuais, pelo direito que ele julgar mais pertinente no seu caso. A objeção de consciência para qualquer situação é um direito natural dos indivíduos. Há alguns anos, um caso que aconteceu nos Estados Unidos ganhou enorme repercussão internacional, quando o confeiteiro Jack Phillips se recusou a fazer um bolo de casamento para o “casal” homossexual Dave Mullins e Charlie Craig.

Uma representação dos direitos civis do estado do Colorado abriu um inquérito contra o confeiteiro, alegando que ele deveria ser obrigado a atender todos os clientes, independente da orientação sexual, raça ou crença. Preste atenção nas palavras usadas — ele deveria ser obrigado a atender.

Como se recusou bravamente a ceder, o caso foi parar invariavelmente na Suprema Corte, que decidiu por sete a dois em favor de Jack Phillips, sob a alegação de que obrigar o confeiteiro a atender o “casal” homossexual era uma violação nefasta dos seus princípios religiosos. Felizmente, esse foi um caso em que a liberdade prevaleceu sobre a tirania progressista.

Evidentemente, homossexuais não devem ser agredidos, ofendidos, internados em clínicas contra a sua vontade, nem devem ser constrangidos em suas liberdades pelo fato de serem homossexuais. O que eles precisam entender é que a liberdade é uma via de mão dupla. Eles podem ter liberdade para adotar a conduta que desejarem e fazer o que quiserem (contanto que não agridam ninguém), mas da mesma forma, é fundamental respeitar e preservar a liberdade de terceiros que desejam rejeitá-los pacificamente, pelo motivo que for.

Afinal, ninguém tem a menor obrigação de aceitá-los, atendê-los ou sequer pensar que uma união estável entre duas pessoas do mesmo sexo — incapaz de gerar descendentes, e, portanto, antinatural — deva ser considerado um matrimônio de verdade. Absolutamente nenhuma pessoa, ideia, movimento, crença ou ideologia usufrui de plena unanimidade no mundo. Por que o homossexualismo deveria ter tal privilégio?

Homossexuais não são portadores de uma verdade definitiva, absoluta e indiscutível, que está acima da humanidade. São seres humanos comuns que — na melhor das hipóteses —, levam um estilo de vida que pode ser considerado “alternativo”, e absolutamente ninguém tem a obrigação de considerar esse estilo de vida normal ou aceitável. A única obrigação das pessoas é não interferir, e isso não implica uma obrigação em aceitar.

Discriminar homossexuais (assim como pessoas de qualquer outro grupo, raça, religião, nacionalidade ou etnia) é um direito natural por parte de todos aqueles que desejam exercer esse direito. E isso nem o direito positivo nem a militância progressista poderão algum dia alterar ou subverter. O direito natural e a inclinação inerente dos seres humanos em atender às suas próprias disposições é simplesmente imutável e faz parte do seu conjunto de necessidades.

Conclusão

A militância progressista é absurdamente autoritária, e todas as suas estratégias e disposições ideológicas mostram que ela está em uma guerra permanente contra a ordem natural, contra a liberdade e principalmente contra o homem branco, cristão, conservador e tradicionalista — possivelmente, aquilo que ela mais odeia e despreza.

Nós não podemos, no entanto, ceder ou dar espaço para a agenda progressista, tampouco pensar em considerar como sendo normais todas as pautas abusivas e tirânicas que a militância pretende estabelecer como sendo perfeitamente razoáveis e aceitáveis, quer a sociedade aceite isso ou não. Afinal, conforme formos cedendo, o progressismo tirânico e totalitário tende a ganhar cada vez mais espaço.

Quanto mais espaço o progressismo conquistar, mais corroída será a liberdade e mais impulso ganhará o totalitarismo. Com isso, a cultura do cancelamento vai acabar com carreiras, profissões e com o sustento de muitas pessoas, pelo simples fato de que elas discordam das pautas universitárias da moda.

A história mostra perfeitamente que quanto mais liberdade uma sociedade tem, mais progresso ela atinge. Por outro lado, quanto mais autoritária ela for, mais retrocessos ela sofrerá. O autoritarismo se combate com liberdade, desafiando as pautas de todos aqueles que persistem em implementar a tirania na sociedade. O politicamente correto é o nazismo dos costumes, que pretende subverter a moral através de uma cultura de vigilância policial despótica e autoritária, para que toda a sociedade seja subjugada pela agenda totalitária progressista.

Pois quanto a nós, precisamos continuar travando o bom combate em nome da liberdade. E isso inclui reconhecer que ideologias, hábitos e costumes de que não gostamos tem o direito de existir e até mesmo de serem defendidos.

@ ee0be83f:c260a740

Ingredients

• test

Directions

1. test

@ 3bf0c63f:aefa459d

Bluesky is a scam

Bluesky advertises itself as an open network, they say people won't lose followers or their identity, they advertise themselves as a protocol ("atproto") and because of that they are tricking a lot of people into using them. These three claims are false.

protocolness

Bluesky is a company. "atproto" is the protocol. Supposedly they are two different things, right? Bluesky just releases software that implements the protocol, but others can also do that, it's open!

And yet, the protocol has an official webpage with a waitlist and a private beta? Why is the protocol advertised as a company product? Because it is. The "protocol" is just a description of whatever the Bluesky app and servers do, it can and does change anytime the Bluesky developers decide they want to change it, and it will keep changing for as long as Bluesky apps and servers control the biggest part of the network.

Oh, so there is the possibility of other players stepping in and then it becomes an actual interoperable open protocol? Yes, but what is the likelihood of that happening? It is very low. No serious competitor is likely to step in and build serious apps using a protocol that is directly controlled by Bluesky. All we will ever see are small "community" apps made by users and small satellite small businesses -- not unlike the people and companies that write plugins, addons and alternative clients for popular third-party centralized platforms.

And last, even if it happens that someone makes an app so good that it displaces the canonical official Bluesky app, then that company may overtake the protocol itself -- not because they're evil, but because there is no way it cannot be like this.

identity

According to their own documentation, the Bluesky people were looking for an identity system that provided global ids, key rotation and human-readable names.

They must have realized that such properties are not possible in an open and decentralized system, but instead of accepting a tradeoff they decided they wanted all their desired features and threw away the "decentralized" part, quite literally and explicitly (although they make sure to hide that piece in the middle of a bunch of code and text that very few will read).

The "DID Placeholder" method they decided to use for their global identities is nothing more than a normal old boring trusted server controlled by Bluesky that keeps track of who is who and can, at all times, decide to ban a person and deprive them from their identity (they dismissively call a "denial of service attack").

They decided to adopt this method as a placeholder until someone else doesn't invent the impossible alternative that would provide all their desired properties in a decentralized manner -- which is nothing more than a very good excuse: "yes, it's not great now, but it will improve!".

openness

Months after launching their product with an aura of decentralization and openness and getting a bunch of people inside that believed, falsely, they were joining an actually open network, Bluesky has decided to publish a part of their idea of how other people will be able to join their open network.

When I first saw their app and how they were very prominently things like follower counts, like counts and other things that are typical of centralized networks and can't be reliable or exact on truly open networks (like Nostr), I asked myself how were they going to do that once they became and open "federated" network as they were expected to be.

Turns out their decentralization plan is to just allow you, as a writer, to host your own posts on "personal data stores", but not really have any control over the distribution of the posts. All posts go through the Bluesky central server, called BGS, and they decide what to do with it. And you, as a reader, doesn't have any control of what you're reading from either, all you can do is connect to the BGS and ask for posts. If the BGS decides to ban, shadow ban, reorder, miscount, hide, deprioritize, trick or maybe even to serve ads, then you are out of luck.

Oh, but anyone can run their own BGS!, they will say. Even in their own blog post announcing the architecture they assert that "it’s a fairly resource-demanding service" and "there may be a few large full-network providers". But I fail to see why even more than one network provider will exist, if Bluesky is already doing that job, and considering the fact there are very little incentives for anyone to switch providers -- because the app does not seem to be at all made to talk to multiple providers, one would have to stop using the reliable, fast and beefy official BGS and start using some half-baked alternative and risk losing access to things.

When asked about the possibility of switching, one of Bluesky overlords said: "it would look something like this: bluesky has gone evil. there's a new alternative called freesky that people are rushing to. I'm switching to freesky".

The quote is very naïve and sounds like something that could be said about Twitter itself: "if Twitter is evil you can just run your own social network". Both are fallacies because they ignore the network-effect and the fact that people will never fully agree that something is "evil". In fact these two are the fundamental reasons why -- for social networks specifically (and not for other things like commerce) -- we need truly open protocols with no owners and no committees.

@ 8fb140b4:f948000c

Intro

This short tutorial will help you set up your own Nostr Wallet Connect (NWC) on your own LND Node that is not using Umbrel. If you are a user of Umbrel, you should use their version of NWC.

Requirements

You need to have a working installation of LND with established channels and connectivity to the internet. NWC in itself is fairly light and will not consume a lot of resources. You will also want to ensure that you have a working installation of Docker, since we will use a docker image to run NWC.

• Working installation of LND (and all of its required components)
• Docker (with Docker compose)

Installation

For the purpose of this tutorial, we will assume that you have your lnd/bitcoind running under user bitcoin with home directory /home/bitcoin. We will also assume that you already have a running installation of Docker (or docker.io).

Prepare and verify

git version - we will need git to get the latest version of NWC. docker version - should execute successfully and show the currently installed version of Docker. docker compose version - same as before, but the version will be different. ss -tupln | grep 10009- should produce the following output: tcp LISTEN 0 4096 0.0.0.0:10009 0.0.0.0: tcp LISTEN 0 4096 [::]:10009 [::]:**

For things to work correctly, your Docker should be version 20.10.0 or later. If you have an older version, consider installing a new one using instructions here: https://docs.docker.com/engine/install/

Create folders & download NWC

In the home directory of your LND/bitcoind user, create a new folder, e.g., "nwc" mkdir /home/bitcoin/nwc. Change to that directory cd /home/bitcoin/nwc and clone the NWC repository: git clone https://github.com/getAlby/nostr-wallet-connect.git

Creating the Docker image

In this step, we will create a Docker image that you will use to run NWC.

• Change directory to nostr-wallet-connect: cd nostr-wallet-connect
• Run command to build Docker image: docker build -t nwc:$(date +'%Y%m%d%H%M') -t nwc:latest . (there is a dot at the end)
• The last line of the output (after a few minutes) should look like => => naming to docker.io/library/nwc:latest
• nwc:latest is the name of the Docker image with a tag which you should note for use later.

Creating docker-compose.yml and necessary data directories

• Let's create a directory that will hold your non-volatile data (DB): mkdir data
• Indocker-compose.ymlfile, there are fields that you want to replace (<> comments) and port “4321” that you want to make sure is open (check with ss -tupln | grep 4321which should return nothing).
• Create docker-compose.ymlfile with the following content, and make sure to update fields that have <> comment:

version: "3.8" services: nwc: image: nwc:latest volumes: - ./data:/data - ~/.lnd:/lnd:ro ports: - "4321:8080" extra_hosts: - "localhost:host-gateway" environment: NOSTR_PRIVKEY: <use "openssl rand -hex 32" to generate a fresh key and place it inside ""> LN_BACKEND_TYPE: "LND" LND_ADDRESS: localhost:10009 LND_CERT_FILE: "/lnd/tls.cert" LND_MACAROON_FILE: "/lnd/data/chain/bitcoin/mainnet/admin.macaroon" DATABASE_URI: "/data/nostr-wallet-connect.db" COOKIE_SECRET: <use "openssl rand -hex 32" to generate fresh secret and place it inside ""> PORT: 8080 restart: always stop_grace_period: 1m

Starting and testing

Now that you have everything ready, it is time to start the container and test.

• While you are in the nwcdirectory (important), execute the following command and check the log output, docker compose up
• You should see container logs while it is starting, and it should not exit if everything went well.
• At this point, you should be able to go to http://<ip of the host where nwc is running>:4321 and get to the interface of NWC
• To stop the test run of NWC, simply press Ctrl-C , and it will shut the container down.
• To start NWC permanently, you should execute docker compose up -d , “-d” tells Docker to detach from the session.
• To check currently running NWC logs, execute docker compose logs to run it in tail mode add -f to the end.
• To stop the container, execute docker compose down

That's all, just follow the instructions in the web interface to get started.

Updating

As with any software, you should expect fixes and updates that you would need to perform periodically. You could automate this, but it falls outside of the scope of this tutorial. Since we already have all of the necessary configuration in place, the update execution is fairly simple.

• Change directory to the clone of the git repository, cd /home/bitcoin/nwc/nostr-wallet-connect
• Run command to build Docker image: docker build -t nwc:$(date +'%Y%m%d%H%M') -t nwc:latest . (there is a dot at the end)
• Change directory back one level cd ..
• Restart (stop and start) the docker compose config docker compose down && docker compose up -d
• Done! Optionally you may want to check the logs: docker compose logs

@ b12b632c:d9e1ff79

I love testing every new self hosted app and I can say that Nostr "world" is really good regarding self hosting stuff.

Today I tested a Nostr relay named Strfry.

Strfry is really simple to setup and support a lot's of Nostr NIPs.

Here is the list of what it is able to do :

• Supports most applicable NIPs: 1, 2, 4, 9, 11, 12, 15, 16, 20, 22, 28, 33, 40
• No external database required: All data is stored locally on the filesystem in LMDB
• Hot reloading of config file: No server restart needed for many config param changes
• Zero downtime restarts, for upgrading binary without impacting users
• Websocket compression: permessage-deflate with optional sliding window, when supported by clients
• Built-in support for real-time streaming (up/down/both) events from remote relays, and bulk import/export of events from/to jsonl files
• negentropy-based set reconcilliation for efficient syncing with remote relays

Installation with docker compose (v2)

Spoiler : you need to have a computer with more than 1 (v)Core / 2GB of RAM to build the docker image locally. If not, this below might crash your computer during docker image build. You may need to use a prebuilt strfry docker image.

I assume you've read my first article on Managing domain with Nginx Proxy Manager because I will use the NPM docker compose stack to publish strfry Nostr relay. Without the initial NPM configuration done, it may not work as expected. I'll use the same docker-compose.yml file and folder.

Get back in the "npm-stack" folder :

cd npm-stack

Cloning the strfry github repo locally :

git clone https://github.com/hoytech/strfry.git

Modify the docker-compose file to locate the strfry configuration data outside of the folder repo directory to avoid mistake during futures upgrades (CTRL + X, S & ENTER to quit and save modifications) :

nano docker-compose.yml

You don't have to insert the Nginx Proxy Manager part, you should already have it into the file. If not, check here. You should only have to add the strfry part.

``` version: '3.8' services: # should already be present into the docker-compose.yml app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: # These ports are in format : - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port # Add any other Stream port you want to expose # - '21:21' # FTP

# Uncomment the next line if you uncomment anything in the section
# environment:
  # Uncomment this if you want to change the location of
  # the SQLite DB file within the container
  # DB_SQLITE_FILE: "/data/database.sqlite"

  # Uncomment this if IPv6 is not enabled on your host
  # DISABLE_IPV6: 'true'

volumes:
  - ./nginxproxymanager/data:/data
  - ./nginxproxymanager/letsencrypt:/etc/letsencrypt

strfry-nostr-relay: container_name: strfry build: ./strfry volumes: - ./strfry-data/strfry.conf:/etc/strfry.conf - ./strfry-data/strfry-db:/app/strfry-db

ports is commented by NPM will access through docker internal network

no need to expose strfry port directly to the internet

ports:

- "7777:7777"

```

Before starting the container, we need to customize the strfry configuration file "strfry.conf". We'll copy the strfry configuration file and place it into the "strfry-data" folder to modify it with our own settings :

mkdir strfry-data && cp strfry/strfry.conf strfry-data/

And modify the strfry.conf file with your own settings :

nano strfry-data/strfry.conf

You can modify all the settings you need but the basics settings are :

• bind = "127.0.0.1" --> bind = "0.0.0.0" --> otherwise NPM won't be able to contact the strfry service

• name = "strfry default" --> name of your nostr relay

• description = "This is a strfry instance." --> your nostr relay description

• pubkey = "" --> your pubkey in hex format. You can use the Damu's tool to generate your hex key from your npub key : https://damus.io/key/

• contact = "" --> your email

``` relay { # Interface to listen on. Use 0.0.0.0 to listen on all interfaces (restart required) bind = "127.0.0.1"

# Port to open for the nostr websocket protocol (restart required)
port = 7777

# Set OS-limit on maximum number of open files/sockets (if 0, don't attempt to set) (restart required)
nofiles = 1000000

# HTTP header that contains the client's real IP, before reverse proxying (ie x-real-ip) (MUST be all lower-case)
realIpHeader = ""

info {
    # NIP-11: Name of this server. Short/descriptive (< 30 characters)
    name = "strfry default"

    # NIP-11: Detailed information about relay, free-form
    description = "This is a strfry instance."

    # NIP-11: Administrative nostr pubkey, for contact purposes
    pubkey = ""

    # NIP-11: Alternative administrative contact (email, website, etc)
    contact = ""
}

```

You can now start the docker strfry docker container :

docker compose up -d

This command will take a bit of time because it will build the strfry docker image locally before starting the container. If your VPS doesn't have lot's of (v)CPU/RAM, it could fail (nothing happening during the docker image build). My VPS has 1 vCore / 2GB of RAM and died few seconds after the build beginning.

If it's the case, you can use prebuilt strfry docker image available on the Docker hub : https://hub.docker.com/search?q=strfry&sort=updated_at&order=desc

That said, otherwise, you should see this :

``` user@vps:~/npm-stack$ docker compose up -d [+] Building 202.4s (15/15) FINISHED
=> [internal] load build definition from Dockerfile 0.2s => => transferring dockerfile: 724B 0.0s => [internal] load .dockerignore 0.3s => => transferring context: 2B 0.0s => [internal] load metadata for docker.io/library/ubuntu:jammy 0.0s => [build 1/7] FROM docker.io/library/ubuntu:jammy 0.4s => [internal] load build context 0.9s => => transferring context: 825.64kB 0.2s => [runner 2/4] WORKDIR /app 1.3s => [build 2/7] WORKDIR /build 1.5s => [runner 3/4] RUN apt update && apt install -y --no-install-recommends liblmdb0 libflatbuffers1 libsecp256k1-0 libb2-1 libzstd1 && rm -rf /var/lib/apt/lists/* 12.4s => [build 3/7] RUN apt update && apt install -y --no-install-recommends git g++ make pkg-config libtool ca-certificates libyaml-perl libtemplate-perl libregexp-grammars-perl libssl-dev zlib1g-dev l 55.5s => [build 4/7] COPY . . 0.9s => [build 5/7] RUN git submodule update --init 2.6s => [build 6/7] RUN make setup-golpe 10.8s => [build 7/7] RUN make -j4 126.8s => [runner 4/4] COPY --from=build /build/strfry strfry 1.3s => exporting to image 0.8s => => exporting layers 0.8s => => writing image sha256:1d346bf343e3bb63da2e4c70521a8350b35a02742dd52b12b131557e96ca7d05 0.0s => => naming to docker.io/library/docker-compose_strfry-nostr-relay 0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
[+] Running 02/02
⠿ Container strfry Started 11.0s ⠿ Container npm-stack-app-1 Running ```

You can check if everything is OK with strfry container by checking the container logs :

user@vps:~/npm-stack$ docker logs strfry date time ( uptime ) [ thread name/id ] v| 2023-07-21 19:26:58.514 ( 0.039s) [main thread ]INFO| arguments: /app/strfry relay 2023-07-21 19:26:58.514 ( 0.039s) [main thread ]INFO| Current dir: /app 2023-07-21 19:26:58.514 ( 0.039s) [main thread ]INFO| stderr verbosity: 0 2023-07-21 19:26:58.514 ( 0.039s) [main thread ]INFO| ----------------------------------- 2023-07-21 19:26:58.514 ( 0.039s) [main thread ]INFO| CONFIG: Loading config from file: /etc/strfry.conf 2023-07-21 19:26:58.529 ( 0.054s) [main thread ]INFO| CONFIG: successfully installed 2023-07-21 19:26:58.533 ( 0.058s) [Websocket ]INFO| Started websocket server on 0.0.0.0:7777

Now, we have to create the subdomain where strfry Nostr relay will be accessible. You need to connect to your Nginx Proxy Manager admin UI and create a new proxy host with these settings :

"Details" tab (Websockets support is mandatory!, you can replace "strfry" by whatever you like, for instance : mybeautifulrelay.yourdomain.tld)

"Details" tab:

"SSL" tab:

And click on "Save"

If everything is OK, when you go to https://strfry.yourdomain.tld you should see :

To verify if strfry is working properly, you can test it with the (really useful!) website https://nostr.watch. You have to insert your relay URL into the nostr.watch URL like this : https://nostr.watch/relay/strfry.yourdomain.tld

You should see this :

If you are seeing your server as online, readable and writable, you made it ! You can add your Nostr strfry server to your Nostr prefered relay and begin to publish notes ! 🎇

Future work:

Once done, strfry will work like a charm but you may need to have more work to update strfry in the near future. I'm currently working on a bash script that will :

• Updatethe "strfry" folder,
• Backup the "strfry.conf" file,
• Download the latest "strfry.conf" from strfry github repo,
• Inject old configuration settings into the new "strfry.conf" file,
• Compose again the stack (rebuilding the image to get the latest code updates),
• etc.

Tell me if you need the script!

Voilààààà

See you soon in another Fractalized story!

@ 3bf0c63f:aefa459d

Parallel Chains

We want merged-mined blockchains. We want them because it is possible to do things in them that aren't doable in the normal Bitcoin blockchain because it is rightfully too expensive, but there are other things beside the world money that could benefit from a "distributed ledger" -- just like people believed in 2013 --, like issued assets and domain names (just the most obvious examples).

On the other hand we can't have -- like people believed in 2013 -- a copy of Bitcoin for every little idea with its own native token that is mined by proof-of-work and must get off the ground from being completely valueless into having some value by way of a miracle that operated only once with Bitcoin.

It's also not a good idea to have blockchains with custom merged-mining protocol (like Namecoin and Rootstock) that require Bitcoin miners to run their software and be an active participant and miner for that other network besides Bitcoin, because it's too cumbersome for everybody.

Luckily Ruben Somsen invented this protocol for blind merged-mining that solves the issue above. Although it doesn't solve the fact that each parallel chain still needs some form of "native" token to pay miners -- or it must use another method that doesn't use a native token, such as trusted payments outside the chain.

How does it work

With the SIGHASH_NOINPUT/SIGHASH_ANYPREVOUT soft-fork[^eltoo] it becomes possible to create presigned transactions that aren't related to any previous UTXO.

Then you create a long sequence of transactions (sufficient to last for many many years), each with an nLockTime of 1 and each spending the next (you create them from the last to the first). Since their scriptSig (the unlocking script) will use SIGHASH_ANYPREVOUT you can obtain a transaction id/hash that doesn't include the previous TXO, you can, for example, in a sequence of transactions A0-->B (B spends output 0 from A), include the signature for "spending A0 on B" inside the scriptPubKey (the locking script) of "A0".

With the contraption described above it is possible to make that long string of transactions everybody will know (and know how to generate) but each transaction can only be spent by the next previously decided transaction, no matter what anyone does, and there always must be at least one block of difference between them.

Then you combine it with RBF, SIGHASH_SINGLE and SIGHASH_ANYONECANPAY so parallel chain miners can add inputs and outputs to be able to compete on fees by including their own outputs and getting change back while at the same time writing a hash of the parallel block in the change output and you get everything working perfectly: everybody trying to spend the same output from the long string, each with a different parallel block hash, only the highest bidder will get the transaction included on the Bitcoin chain and thus only one parallel block will be mined.

See also

• Drivechain

[^eltoo]: The same thing used in Eltoo.

@ 18e3af1e:1d42e5df

You don't own Bitcoin because you don't want to.

> In a world of an ever growing number go up; people that lives in countries like Venezuela, Argentina, Turkey; or any other country where dilution of money is the rule; It is hard to stack sats (buy Bitcoin) with ease... But sometimes you just gotta open up a little bit and let information flow in. That’s why you’re here. You are going to stack sats without buying it!

Caveats:

1. It’s not going to be FREE (nothing is) it will take you a couple minutes of your time and some will make you walk for it.

2. It won’t make you rich, but will add up and eventually who knows, you may have enough to be…

3. By the time of writing all this sites are up, if they don’t operate anymore or links are broken when you’re reading this… Don’t shoot me.

---

Walky Walk with sMiles sats for walk:

Pretty straight forward. Earn Sats for walking. You can also spin the wheel and use Fort Nakamoto for extra sats.

---

Bitcoin Lottery with LNscratch:

Also very self explanatory. Scratch a digital paper to get a chance to win sats when you get 4 check-marks in a straight line. I usually get 21 sats every time. You only need a Lightning wallet like GetAlby, Wallet of Satoshi (this are the most popular you can take a deeper look at it) and you are set.

---

Get paid for easy tasks sats4likes :

The tasks are usually: Follow, repost, coment, like and/or subscribe. That’s it. You get paid certain ammount of sats set by the owner of the task. The only downside is that you need a twitter account (bad bad, you should be using Nostr) to log in. But if you don’t care about that here it is.

---

Nostr:

The best way to stack so far, join the force and get zapped (sats) for any note (post) people find to have value. At the moment there is a whole ecosystem being built upon the protocol layer. All this clients (websites or apps built over Nostr) are going to be interoperable, meaning that with one keypair (account) will be possible to access them all.

The point is that Nostr uses Lightning Network (Bitcoin) as a form of transacting value, giving the value for value model a tremendous boost.

Imagine getting sats for posting a funny meme, or getting sats for writing an article (like this one), or for making songs and using stemstr, zapstr.live… The clients are as many as we want them to be, and can make anything we want them to make. Possibilities are endless.

Here is a intuitive and short introduction Hey Nostr

If you have any other forms of earning sats please let me know! I’ll add them to this article. Thanks for reading!

---

Get paid by sharing content Stacker.news:

It’s a great way to not only stack more sats but stack some knowledge and keep up with recent news about Bitcoin, Nostr, Finance, Tech, etc… Simply create an account with any of their methods, Although Lightning is recommended. Then deposit some sats if you have them already (10 sats are necessary to post or comment), then just watch your bag grow. The more interesting and well executed your link/discussion is the more sats you get.

---

Stack when you use your FIAT to buy things: The Bitcoin Company, Fold app , Lolli

I put all of the together because they’re essentially pretty similar. When you purchase a giftcard you get Satsback (instead of cashback), they work and don’t in different locations; so do your own research in that matter.

Fold is a more popular option (currently only working within the US) because they have a card you can use and get satsback even easier.

---

Get sats by listening or making Podcasts: Fountain.fm

If you’re a podcast lover you definitely need to check this one out! Just by listening you can earn sats. You can find podcasts that has this feature enabled, whatever topic it is (doesn’t need to be strictly about Bitcoin or Nostr or even Tech Related).

If you have or want to have a podcast, I recommend taking this option. You don’t need sponsors to make your podcast profitable. Boosts (like a sat donation) or Sat Streams (giving to you a certain amount of satoshis for each minute people hear your podcast) are a way to monetize. The better your content is, the more people will throw money at you (quite literal).

---

Use Lightning Faucets Like this one:

Simply follow the steps and redeem your sats.

If you live in a country where inflation is not stupid high (Like the US) consider a donating to the cause.

---

Read for sats Bitcoin Magazine App:

I wasn't sure to add this one but it does work if the only thing you want to do is stack and don't mind articles too much.

Just read articles all the way down (your fingers can do it faster than your eyes wink wink) and get sats for it! You can also reedem flashcodes from BM Twitter (yuck); they're very active with those codes!

Follow me Nostr: Lou@zap.stream 🤙🏼🤙🏼

Hosting "Permissionless Purple Podcast" (spanish) https://fountain.fm/show/XsscCx4P85iMpafjBZAB 🎧

@ b12b632c:d9e1ff79

Self hosting web applications comes quickly with the need to deal with HTTPS protocol and SSL certificates. The time where web applications was published over the 80/TCP port without any encryption is totally over. Now we have Let's Encrypt and other free certification authority that lets us play web applications with, at least, the basic minimum security required.

Second part of web self hosting stuff that is really useful is the web proxifycation.

It's possible to have multiple web applications accessible through HTTPS but as we can't use the some port (spoiler: we can) we are forced to have ugly URL as https://mybeautifudomain.tld:8443.

This is where Nginx Proxy Manager (NPM) comes to help us.

NPM, as gateway, will listen on the 443 https port and based on the subdomain you want to reach, it will redirect the network flow to the NPM differents declared backend ports. NPM will also request HTTPS cert for you and let you know when the certificate expires, really useful.

We'll now install NPM with docker compose (v2) and you'll see, it's very easy.

You can find the official NPM setup instructions here.

But before we absolutely need to do something. You need to connect to the registrar where you bought your domain name and go into the zone DNS section.You have to create a A record poing to your VPS IP. That will allow NPM to request SSL certificates for your domain and subdomains.

Create a new folder for the NPM docker stack :

mkdir npm-stack && cd npm-stack

Create a new docker-compose.yml :

nano docker-compose.yml

Paste this content into it (CTRL + X ; Y & ENTER to save/quit) :

``` version: '3.8' services: app: image: 'jc21/nginx-proxy-manager:latest' restart: unless-stopped ports: # These ports are in format : - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port # Add any other Stream port you want to expose # - '21:21' # FTP

# Uncomment the next line if you uncomment anything in the section
# environment:
  # Uncomment this if you want to change the location of
  # the SQLite DB file within the container
  # DB_SQLITE_FILE: "/data/database.sqlite"

  # Uncomment this if IPv6 is not enabled on your host
  # DISABLE_IPV6: 'true'

volumes:
  - ./nginxproxymanager/data:/data
  - ./nginxproxymanager/letsencrypt:/etc/letsencrypt

```

You'll not believe but it's done. NPM docker compose configuration is done.

To start Nginx Proxy Manager with docker compose, you just have to :

docker compose up -d

You'll see :

user@vps:~/tutorials/npm-stack$ docker compose up -d [+] Running 2/2 ✔ Network npm-stack_default Created ✔ Container npm-stack-app-1 Started

You can check if NPM container is started by doing this command :

docker ps

You'll see :

user@vps:~/tutorials/npm-stack$ docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 7bc5ea8ac9c8 jc21/nginx-proxy-manager:latest "/init" About a minute ago Up About a minute 0.0.0.0:80-81->80-81/tcp, :::80-81->80-81/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp npm-stack-app-1

If the command show "Up X minutes" for the npm-stack-app-1, you're good to go! You can access to the NPM admin UI by going to http://YourIPAddress:81.You shoud see :

The default NPM login/password are : admin@example.com/changeme .If the login succeed, you should see a popup asking to edit your user by changing your email password : And your password : Click on "Save" to finish the login. To verify if NPM is able to request SSL certificates for you, create first a subdomain for the NPM admin UI : Click on "Hosts" and "Proxy Hosts" : Followed by "Add Proxy Host" If you want to access the NPM admin UI with https://admin.yourdomain.tld, please set all the parameters like this (I won't explain each parameters) :

Details tab : SSL tab : And click on "Save".

NPM will request the SSL certificate "admin.yourdomain.tld" for you.

If you have an erreor message "Internal Error" it's probably because your domaine DNS zone is not configured with an A DNS record pointing to your VPS IP.

Otherwise you should see (my domain is hidden) :

Clicking on the "Source" URL link "admin.yourdomain.tld" will open a pop-up and, surprise, you should see the NPM admin UI with the URL "https://admin.yourdomain.tld" !

If yes, bravo, everything is OK ! 🎇

You know now how to have a subdomain of your domain redirecting to a container web app. In the next blog post, you'll see how to setup a Nostr relay with NPM ;)

Voilààààà

See you soon in another Fractalized story!

@ 3bf0c63f:aefa459d

Rede Relâmpago

Ao se referir à Lightning Network do O que é Bitcoin?, nós, brasileiros e portugueses, devemos usar o termo "Relâmpago" ou "Rede Relâmpago". "Relâmpago" é uma palavra bonita e apropriada, e fácil de pronunciar por todos os nossos compatriotas. Chega de anglicismos desnecessários.

Exemplo de uma conversa hipotética no Brasil usando esta nomenclatura:

– Posso pagar com Relâmpago?

– Opa, claro! Vou gerar um boleto aqui pra você.

Repare que é bem mais natural e fácil do que a outra alternativa:

– Posso pagar com láitenim?

– Leite ninho?

@ 69a0a091:c968228d

There's no "right" way to run a relay, any relay operator is free to make their own decisions. I like nostr's simplicity and tendency to favor user independence and choice. I want to see nostr grow and remain reslient, so that's why I have been sharing tools to keep small relays running in tip-top shape.

The is the first part in a series. The follow up should explain the workings of our friend-of-friend trust model.

strfry is fast

bitcoiner.social is one of the oldest nostr relays. In the early days, it ran a reference relay implementation called Relayer. It crashed a lot, but a simple systemd restart policy kept it alive and mostly functional for the first year. Somewhere around November I switched it over to the rust-rs-relay, which was stable and used a simple sqlite backend. That lasted a matter of weeks before the usage rose enough to warrant changing back to a postgre backend with nostream. Nostr was growing fast!

By the outset of 2023, the relay was still being completely overwhelmed. Each request coming in would cause postgresql to gobble up compute cycles. Any amount of tuning on parameters was a futile effort. The demand was unsustainable and the best way to remedy the situation wasn't immediately clear.

Then, I think in early February, I saw a post from jb55 that he was trying a new relay written in C++ called strfry. A glance at github revealed that strfry was using a new kind of backend storage method called LMDB. The difference in compute effeciency was night and day: where SQL queries were maxing all server cores, our CPU charts showed that strfry sipped compute cycles. Even a small virtual machine could handle thousands of requests. It reminds me of switching from an old IIS or Apache webserver over to nginx. We continue to run strfry to this day. And most of my relay tooling tends to be focused around it.

ansible is simple

Last year I started an Ansible Role for installing strfry. It enabled me to commit the entire process of setting up the relay into a repository, ala Infrastructure as Code. This ensured that I'd be able to quickly restore the relay in the event of a catastrohpic loss. And I wouldn't forget how to set the thing up. Besides building strfry from source, it automates the basic setup steps needed to use an excellent plugin by Alex Gleason called strfry-policies. I also started an Ansible role for snort, a nostr web client.

Smart people will tell you that Ansible is far from being the best way to manage relay infrastructure, but it is plenty good enough to get the job done. I'd like to do a nix implementation at some point, when time permits. But it's a low priority so I'm hoping someone else will beat me to it.

One of my first projects when I was learning Ansible was setting up an observability stack. It's entirely necessary to monitor the availability of a nostr relay, and running my own monitoring stack has been one of my most useful preperations for being a relay admin. I haven't taken the time to put together a proper example, but all of my infra code is FOSS so you can see it in my stack playbook and host vars. I even proposed to do a whole talk on this at Tabconf 2023 (although I'm glad they turned me down).

If you're wanting to set up your own first observability stack, it might be easiest to start with a few containers (e.g. awesome-compose/prometheus-grafana).

rules are necessary

Spam and abuse is prevelant on nostr, so event ingestion and retention are two primary concerns for a relay operator.

ingest and digest

To address the firehose of notes coming in from the internet (ingestion) we use the strfry-policies plugin. The plugin allows the admin to define policy rules to prevent unwanted events from being ingested on the relay. So far I've added two policy types, one filters by event kind and another filters for the size of the event.

I'll document it more in a follow-up article, but I implemented policy exclusions for friends, and friends-of-friends (foaf). I recently published a simple cli tool for reading relay reports. Reviewing reports is necessary to deal with whatever comes through the cracks of our policies. The admin can use the reports to ban abusive accounts, and delete their content from the relay.

to retain, or not retain

To address data retention, I wrote a simple Deno Typescript tool to prune events. strfry itself has a brute delete function, but every relay will want to keep certain kinds of events longer than others (such as profiles or contact lists). I haven't published it anywhere yet, but it basically looks like this:

```typescript import { readLines } from 'https://deno.land/std@0.201.0/io/mod.ts';

const kindAgeLimitDefault = 90; const kindAgeLimits: Record = { 0: 365, // Profiles 3: 365, // Contacts 9735: 180, // Zap Receipts 24133: 365, // NWC 10002: 730, // NIP-65 };

const exportEventsStdin = async (): Promise => { if (Deno.isatty(Deno.stdin.rid)) { Deno.exit(1); } for await (const line of readLines(Deno.stdin)) { if (line.length === 0) { return; } exportLine(line); } };

const exportLine = (line: string): void => { const eventJson = JSON.parse(line); const created_at = new Date(eventJson.created_at * 1000); // convert seconds to ms const kindAgeLimit = (kindAgeLimits[eventJson.kind] || kindAgeLimitDefault) * 24 * 60 * 60 * 1000; // convert days to ms const ageLimitDate = new Date(Date.now() - kindAgeLimit); if (created_at > ageLimitDate) { console.log(line); } };

await exportEventsStdin(); ```

The bitcoiner.social relay uses a modified version that takes into account a friend-of-a-friend model. We retain events from friends of our friends much longer than we keep the notes of total strangers. One side-effect of pruning events is that it reduces the compute load on the server. Having a policy like that can generally keep the relay at a sustainable level for long periods of time. I have a systemd timer (cronjob) that runs the policy on a regular schedule.

We run strfry compact every week to keep the database index orderly and effecient. These are the kind of optimizations that keep a small relay in a healthy state for the long-term.

@ 3bf0c63f:aefa459d

Anglicismos estúpidos no português contemporâneo

Palavras e expressões que ninguém deveria usar porque não têm o sentido que as pessoas acham que têm, são apenas aportuguesamentos de palavras inglesas que por nuances da história têm um sentido ligeiramente diferente em inglês.

Cada erro é acompanhado também de uma sugestão de como corrigi-lo.

Palavras que existem em português com sentido diferente

• submissão (de trabalhos): envio, apresentação
• disrupção: perturbação
• assumir: considerar, pressupor, presumir
• realizar: perceber
• endereçar: tratar de
• suporte (ao cliente): atendimento
• suportar (uma idéia, um projeto): apoiar, financiar
• suportar (uma função, recurso, característica): oferecer, ser compatível com
• literacia: instrução, alfabetização
• convoluto: complicado.
• acurácia: precisão.
• resiliência: resistência.

Aportuguesamentos desnecessários

• estartar: iniciar, começar
• treidar: negociar, especular

Expressões

• "não é sobre...": "não se trata de..."

Ver também

• Algumas expressões e ditados excelentes da língua portuguesa, e outras não tão excelentes assim

@ fa0165a0:03397073

Probability theory is the study of random phenomena. This post is a pilot post for potentially further posting in this series. Feedback appreciated. Introduction

Probability theory is the study of random phenomena. It is used in many fields, such as statistics, machine learning, and finance. It is also used in everyday life, for example when playing games of chance, or when estimating the risk of an event. The most classic example is the coin toss, closely followed by the dice roll.

When we toss a coin, the result is either heads or tails. In the case of an ideal coin, the “random trail” of tossing the coin has an equal probability for both outcomes. Similarly, for a die roll of a fair dice, we know that the probability for each outcome is 1/6. In the study of probability we dive deep into the mathematics of these random phenomena, how to model them, and how to calculate the probability of different events. To do this in precise terms, we define words and concepts as tools for discussing and communicating about the subject.

This is the first of what I expect to be a 15 part series of my lecture & study notes from my university course in probability theory MT3001 at Stockholm University. References to definitions and theorems will use their numeration in the course literature, even if I may rephrase them myself. The book I’ve had as a companion through this course is a Swedish book called Stokastik by Sven Erick Alm and Tom Britton; ISBN:978–91–47–05351–3. This first module concerns basic concepts and definitions, needed for the rest of the course. The language of Probability theory

An experiment is a process that produces a randomized result. If our experiment is throwing a die, we then have the following: The result of throwing the die is called an outcome, the set of all possible outcomes is called the sample space and a subset of the sample space is called an event. We will use the following notation:

outcome is the result of an experiment, denoted with a small letter, ex. 𝑢₁, 𝑢₂, 𝑢₃, …
event is the subset of the sample space, denoted with a capital letter, ex. 𝐴, 𝐵, 𝐶, …
sample space is the set of all possible outcomes of an experiment, denoted Ω.

Adding numbers to our dice example, we have the sample space Ω = {𝟏,𝟐,𝟑,𝟒,𝟓,𝟔} containing all the possible events 𝑢₁=𝟏, 𝑢₂=𝟐, 𝑢₃=𝟑, 𝑢₄=𝟒, 𝑢₅=𝟓 and 𝑢₆=𝟔. And we could study some specific sub events like the chance of getting an even number, 𝐴={𝟐,𝟒,𝟔}, or the chance of getting a prime number, 𝐵={𝟐,𝟑,𝟓}. As it happens, the probability of both 𝐴 and 𝐵 is 50%. Sample space

The sample space is the set of all possible outcomes of an experiment. It is denoted Ω. And there are two types of sample spaces, discrete and continuous. A discrete sample space is a finite or countably infinite set, and all other kind of sample spaces are called continuous.

The coin toss and the dice roll are both examples of discrete sample spaces. Studying a problem, like the temperature outside, would in reality require a continuous sample space. But in practice, we can often approximate a continuous sample space with a discrete one. For example, we could divide the temperature into 10 degree intervals, and then we would have a discrete sample space.

Remember that continuous sample spaces exist, and expect more information about them in later modules. For starters, we focus on discrete sample spaces. Set Theory notation and operations

When talking about probabilities we will arm ourselves with the language of “set theory”, it is a crucial tool for the study of probability. Feeling comfortable with the subject of set theory since before is useful, but not necessary. I will try to explain the concepts as we go along.

Even tough the events from the dice rolls are represented by numbers, it is important to note that they aren’t numbers, but rather elements. This might become more clear if we alter our example to be a deck of cards. This deck of cards have four suits Ω = {♥, ♠, ♦, ♣ } and in our experiments we draw a card from the deck and look at the suit. It’s here very obvious that we can’t add or subtract the different events with each other. But we do have the operations of set theory at our disposal. For example, if 𝐴 is the event of drawing a red card and 𝐵 is the event of drawing spades ♠, we can use the following notation: Set theory operations

Union: 𝐴 ∪ 𝐵 = {♥, ♦, ♠}, the union of 𝐴 and 𝐵.
The empty set: ∅ = {}, the empty set. A set with no elements.
Intersection: 𝐴 ∩ 𝐵 = ∅, the intersection of 𝐴 and 𝐵.
This means that 𝐴 and 𝐵 have no elements in common. And we say that 𝐴 and 𝐵 are disjoint.
Complement: 𝐴ᶜ = {♠, ♣}, the complement of 𝐴.
Difference: 𝐴 ∖ 𝐵 = {♥, ♦}, the difference of 𝐴 and 𝐵. Equivalent to 𝐴 ∩ 𝐵ᶜ.
The symbol ∈ denotes that an element is in a set. For example, 𝑢₁ ∈ Ω means that the outcome 𝑢₁ is in the sample space Ω. For our example: ♥ ∈ 𝐴 means that the suit ♥ is in the event 𝐴.

Venn diagram

A very useful visualization of set theory is the Venn diagram. Here is an example of a Venn diagram in the picture below:

In the above illustration we have: Ω = {𝟏,𝟐,𝟑,𝟒} and the two events 𝐴={𝟐,𝟑} and 𝐵={𝟑,𝟒}. Notice how the two sets 𝐴 and 𝐵 share the element 𝟑, and that all sets are subsets of the sample space Ω. The notation for the shared element 𝟑 is 𝐴 ∩ 𝐵 = {𝟑}. Useful phrasing

The different set notations may seem a bit abstract at first, at least before you are comfortable with them. Something that might be useful to do is to read them with the context of probabilities in mind. Doing this, we can read some of the different set notations as follows:

𝐴ᶜ, “when 𝐴 doesn’t happen”.
𝐴 ∪ 𝐵, “when at least one of 𝐴 or 𝐵 happens”.
𝐴 ∩ 𝐵, “when both 𝐴 and 𝐵 happens”.
𝐴 ∩ 𝐵ᶜ, “when 𝐴 happens but 𝐵 doesn’t happen”.

The Probability function

Functions map elements from one set to another. In probability theory, we are interested in mapping events to their corresponding probabilities. We do this using what we call a probability function. This function is usually denoted 𝑃 and have some requirements that we will go through in the definition below.

This function take events as input and outputs the probability of that event. For the example of a die throw, if we have the event 𝐴={𝟐,𝟒,𝟔}, then 𝑃(𝐴) is the probability of getting an even number when throwing a fair six sided dice. In this case 𝑃(𝐴)=1/2=𝑃(“even number from a dice throw”), you’ll notice that variations of descriptions of the same event can be used interchangeably.

The Russian mathematician Andrey Kolmogorov (1903–1987) is considered the father of modern probability theory. He formulated the following three axioms for probability theory: Definition 2.2, Kolmogorov’s axioms

A real-valued function 𝑃 defined on a sample space Ω is called a probability function if it satisfies the following three axioms:

𝑃(𝐴) ≥ 𝟎 for all events 𝐴.
𝑃(Ω) = 𝟏.
If 𝐴₁, 𝐴₂, 𝐴₃, … are disjoint events, then 𝑃(𝐴₁ ∪ 𝐴₂ ∪ 𝐴₃ ∪ …) = 𝑃(𝐴₁) + 𝑃(𝐴₂) + 𝑃(𝐴₃) + …. This is called the countable additivity axiom.

From these axioms it’s implied that 𝑃(𝐴) ∈ [𝟎,𝟏], which makes sense since things aren’t less than impossible or more than certain. As a rule of thumb, when talking about probabilities, we move within the range of 0 and 1. This lets us formulate the following theorem: Theorem 2.1, The Complement and Addition Theorem of probability

Let 𝐴 and 𝐵 be two events in a sample space Ω. Then the following statements are true:

1. 𝑃(𝐴ᶜ) = 𝟏 — 𝑃(𝐴)

2. 𝑃(∅) = 𝟎

3. 𝑃(𝐴 ∪ 𝐵) = 𝑃(𝐴) + 𝑃(𝐵) — 𝑃(𝐴 ∩ 𝐵)

Proof of Theorem 2.1

𝑃(𝐴 ∪ 𝐴ᶜ) = 𝑃(Ω) = 𝟏 = 𝑃(𝐴) + 𝑃(𝐴ᶜ) ⇒ 𝑃(𝐴ᶜ) = 𝟏 — 𝑃(𝐴)

This simply proves that the probability of 𝐴 not happening is the same as the probability of 𝐴 happening subtracted from 1.

𝑃(∅) = 𝑃(Ωᶜ) = 𝟏 — 𝑃(Ω) = 𝟏 — 𝟏 = 𝟎

Even though our formal proof required (1) to be proven, it’s also very intuitive that the probability of the empty set is 0. Since the empty set is the set of all elements that are not in the sample space, and the probability of an event outside the sample space is 0.

𝑃(𝐴 ∪ 𝐵) = 𝑃(𝐴 ∪ (𝐵 ∩ 𝐴ᶜ)) = 𝑃(𝐴) + 𝑃(𝐵 ∩ 𝐴ᶜ) = 𝑃(𝐴) + 𝑃(𝐵) — 𝑃(𝐴 ∩ 𝐵)

This can be understood visually by revisiting our Venn diagram. We see that the union of 𝐴 and 𝐵 has an overlapping element 𝟑 shared between them. This means that purely adding the elements of 𝐴={𝟐,𝟑} together with 𝐵={𝟑,𝟒} would double count that shared element, like this {𝟐,𝟑,𝟑,𝟒}, since we have two “copies” of the mutual elements we make sure to remove one “copy” bur removing 𝑃(𝐴 ∩ 𝐵)={𝟑} and we get 𝑃(𝐴 ∪ 𝐵)={𝟐,𝟑,𝟒}. We may refer to this process as dealing with double counting, something that is very important to have in mind when dealing with sets.

Two interpretations of probability that are useful and often used are the frequentist and the subjectivist interpretations. The frequentist interpretation is that the probability of an event is the relative frequency of that event in the long run. The subjectivist interpretation is that the probability of an event is the degree of belief that the event will occur, this is very common in the field of statistics and gambling. For the purposes of study it’s also useful to sometimes consider probabilities as areas and or masses, this is called the measure theoretic interpretation. Don’t let that word scare you off, in our context it’s just a fancy way of drawing a parallel between areas and probabilities. Think area under curves, and you’ll be fine.

@ 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

@ 78733875:4eb851f2

"The computer can be used as a tool to liberate and protect people, rather than to control them," as Hal Finney wrote so presciently 30 years ago.[^fn-hal]

The goal of OpenSats is to help build the tools that Hal alluded to. Tools that liberate and protect, rather than systems that control and oppress. Many tools still have to be built. Many tools still need to be improved. However, "the universe smiles on encryption," as Assange so aptly put it.[^fn-assange]

We believe that freedom tech is what carries this smile forward, which is why we are delighted to announce grants for over a dozen projects in the bitcoin & lightning ecosystem.

[^fn-hal]: Hal Finney: Why remailers... (November 1992)

[^fn-assange]: Julian Assange: A Call to Cryptographic Arms (October 2012)

The following open-source projects were selected by the OpenSats board for funding:

• Payjoin Dev Kit
• Bolt12 for LND
• Splicing
• Raspiblitz
• Labelbase
• BTCPay Server
• ZeroSync
• Mutiny Wallet
• next-auth Lightning Provider
• Cashu
• lnproxy
• Blixt Wallet

Let's take a closer look at each to understand their goal and how it aligns with the OpenSats mission.

---

Payjoin Dev Kit

Payjoin brings privacy to bitcoin without changing the way you're used to using it. Payjoin transactions look no different from normal activity on-chain, so they boost everyone's privacy, even those who don't payjoin, and foil chain surveillance.

Payjoin is easy to integrate and falls back to working defaults where it isn't supported, but it can only take off when senders and receivers include standard payjoin support in their software. Payjoin Dev Kit makes it easy for wallet developers to integrate BIP 78 standard payjoins everywhere, having working reference integrations for Bitcoin Core, LND, and BDK.

Repository: github.com/payjoin
License: MIT

Bolt12 for LND

Bolt12 brings a new invoice format, enabling static invoices (offers) as well as recurring payments. It adds support to receive payments in a lightning-native way without using a web server. It also uses Blinded Paths to disguise the destination of a node both when fetching the invoice and when paying. This improves privacy and, therefore, security for the receiver of the payment.

Consequently, Bolt12 makes it much easier to receive and send payments without any third-party infrastructure in a native-lightning way. Static invoices make donations and recurring payments much easier.

Repository: lightningnetwork/lnd
License: MIT

Splicing

Splicing is the ability to resize Lightning channels on-the-fly, giving users of the Lightning Network many additional benefits that were not intuitively obvious at first. Splicing scales Lightning by removing a fundamental limitation. Removing this limitation increases fungibility and lowers blockspace usage, an important step towards maturing the Lightning network and enabling the onboarding of millions, and ultimately billions, of people.

Repository: ddustin/splice
License: BSD-MIT

Raspiblitz

Raspiblitz is a do-it-yourself node stack that allows you to run a Lightning Node together with a Bitcoin Core full node on your Raspberry Pi. While the Raspberry Pi is the most common hardware running this particular software, it was developed to support multiple hardware platforms and can run on bare metal servers too.

The open-source project was started in 2018 as part of a Lightning hackathon in the German Bitcoin space. Since then, it has grown to over 150 contributors and 2000 stars on GitHub. The software integrates dozens of services and tools via its plugin system and sports advanced features like touchscreen support, channel autopilot, backup systems, DynDNS, SSH tunneling, and more.

Repository: raspiblitz/raspiblitz
License: MIT

Labelbase

Labelbase is a label management service for Bitcoin transactions and addresses. It provides features for adding labels, importing and exporting labels, and offers a public API for integration with wallets and existing workflows.

Labelbase supports BIP-329, a format for unifying label data. The goal of the project is to offer a convenient solution for managing labels associated with Bitcoin transactions and addresses across wallets and other tools. By providing a unified label management interface, Labelbase enhances the user experience, improves privacy, and promotes better organization and understanding of Bitcoin transactions.

Repository: Labelbase/Labelbase
License: MIT

BTCPay Server

BTCPay Server is a free, open-source & self-hosted bitcoin payment gateway that allows self-sovereign individuals and businesses to accept bitcoin payments online or in person without added fees.

At its core, BTCPay Server is an automated invoicing system. Merchants can integrate the software with their website or shop, so customers are presented with an invoice upon checkout. The status of the invoice will update according to settlement, so merchants can fulfill the order at the appropriate time. The software also takes care of payment refunding and bitcoin management alongside many other features.

Repository: btcpayserver/btcpayserver
License: MIT

ZeroSync

While ZeroSync is still at an early stage, its promise is to allow verification of Bitcoin's chain state in an instant. It offers compact cryptographic proofs to validate the entire history of transactions and everyone's current balances.

The first application is to "zerosync" Bitcoin Core in pruned mode. The long-term vision for ZeroSync is to become a toolbox for custom Bitcoin proofs.

Repository: zerosync/zerosync
License: MIT

Mutiny Wallet

Mutiny Wallet is a web-first wallet capable of running anywhere, providing instant onboarding and platform censorship resistance. It is self-custodial, privacy-focused, user-friendly, and open-sourced under the MIT license.

The wallet has a strong focus on privacy, scalability, and accessibility. In addition to features that you would expect a regular lightning wallet to have, the team is working to incorporate Nostr-related features into the wallet, such as a feed of friends' Zaps, native Zap sending and receiving, a lightning subscription specification for services such as nostr relays, and a P2P DLC marketplace. The team's goal is to provide users with a seamless experience, combining the power of Bitcoin and Lightning with social media in a way that matches the Bitcoin ethos.

Repository: MutinyWallet
License: MIT

next-auth Lightning Provider

The goal of this project is to implement an authentication provider for next-auth, an authentication provider for the popular open-source framework NextJS. The next-auth framework has nearly 500k weekly downloads and powers the authentication of many modern web, mobile, and desktop apps. Having a plug-and-play Provider for Lightning makes integration easier and more attractive for developers.

Repository: jowo-io/next-auth-lightning-provider
License: ISC

Cashu

Cashu is a Chaumian ecash system built for bitcoin that brings near-perfect privacy for users of custodial bitcoin applications. A Cashu ecash mint does not know who you are, what your balance is, or who you're transacting with. Users of a mint can exchange ecash privately, without anyone being able to know who the involved parties are.

Payments are executed without anyone able to censor specific users. There are multiple implementations of the Cashu protocol. Popular open-source wallets are Cashu Nutshell, Cashu.me, and Nutstash.

Repository: cashubtc/cashu
License: MIT

lnproxy

lnproxy is a simple privacy tool that empowers users of custodial Lightning wallets with better payment destination privacy and sovereign node runners with enhanced receiver privacy. lnproxy works like a "poor man's" rendezvous router, providing privacy for users without taking custody of their funds. The project encompasses an LNURL-style protocol specification and a collection of open-source implementations of lnproxy clients and a relay.

Repository: lnproxy/lnproxy
License: GPL 3.0 & MIT

Blixt Wallet

Blixt is a non-custodial wallet for bitcoiners who want to give Lightning a try. It runs on Android, iOS, and macOS. It is easy to use and straightforward to set up, making it a user-friendly option to get started with Lightning.

Blixt uses LND and Neutrino under the hood, directly on the phone, respecting your privacy. The wallet does not use any centralized servers for doing transactions. Channels are opened automatically on the user's behalf, making it easy to get up and running on Lightning.

Repository: hsjoberg/blixt-wallet
License: MIT

---

In addition to the software projects listed above, three educational initiatives were selected for funding:

• Bitcoin Education in Nigeria is an initiative started and led by Apata Johnson. Apata's project aims to educate youths on bitcoin and the opportunities it brings for the people living in the rural areas of Nigeria.
• 21 Ideas is a project that aims to bring quality Bitcoin education to Russian citizens. Tony and others have been working for many years on translations, original material, and hands-on tutorials for beginners. We believe that education is paramount to proper Bitcoin use, and localization is paramount for everyday citizens to properly grasp the importance as well as the novel concepts of bitcoin.
• CoreDev.tech is organizing recurring developer events, which are all about bringing devs together so that they can hack on Bitcoin Core and related software.

---

We received hundreds of applications in the last couple of months, which is a fantastic signal and something we are delighted about. Some applications are still being reviewed by the OpenSats board, as we try our best to assess feasibility, alignment, and potential impact of each project. We will announce additional grants as applications pass our grant selection process.

Unfortunately, we were unable to fund all of the proposals that were sent to us. Please don't hesitate to apply again in case your application was rejected this time around. The applicant pool was very competitive, which is a great thing to see in and of itself.

Grants for the projects above are funded by contributions to the Bitcoin General Fund. Our operations as well as our grant programs are made possible by generous donors like you. If you want to help fund the Bitcoin ecosystem, please donate to the Bitcoin General Fund.

Our team is screening applications constantly, and we will announce new grants and funding opportunities as they arise. If you are working on an open-source project in and around bitcoin, and you think your work is aligned with the OpenSats mission, please apply for funding.

@ 7488de5d:f556883b

As the digital financial landscape is evolving, Neutronpay’s proud to be among the pioneering companies that are "Lightning the way forward", offering faster and superior payment solutions. We're excited to announce that: Canadian and US businesses can now easily tap into Malaysia's market. Integrate with Neutronpay's API or use our web portal for fast, cost-effective financial solutions!

Revolutionising International Payments The challenges of cross-border payments have historically revolved around delays and exorbitant fees. But with Neutronpay’s Lightning infrastructure, that story is changing. We’re harnessing the Speed of Light to provide instant transactions, completely transforming the realm of international money transfers. No more prolonged waits, just instant transactions.

More Than Just Speed While our commitment to speed is unwavering, Neutronpay’s true distinction lies in our dedication to seamless, simple, and secure transactions. Our platform ensures businesses can execute cross-border payments with competitive fees, making international financial engagements simpler and more affordable.

Strengthening Trade Ties Malaysia has consistently emerged as a linchpin in Canada’s trade ecosystem within the Association of Southeast Asian Nations (ASEAN) region. The 17% surge in bilateral trade in 2022, amounting to $5.7 billion, stands as a testament to their vibrant relationship. With Neutronpay at the forefront as the gateway to SEA & Asia, the horizon for growth and collaboration looks promising.

Conclusion The Comprehensive Progressive Trans-Pacific Partnership trade agreement has further solidified the robust commercial exchanges between Malaysia and Canada. With Neutronpay's innovative approach to money transfers, North American businesses have a streamlined avenue to delve into the Malaysian market, reaping the advantages of faster, superior, and more cost efficient financial solutions.

Join the movement with us, as we continually strive to redefine global payments, embodying the essence of "Lightning the way forward" with top-tier Lightning Payments solutions.

@ 2f7463a4:e92b8023

Dies ist die deutsche Übersetzung von / This is the German translation of :

nostr:naddr1qqxnzd3cxserxdpsxverzwp4qgs87hptfey2p607ef36g6cnekuzfz05qgpe34s2ypc2j6x24qvdwhgrqsqqqa28zcj37a — nostr:npub10awzknjg5r5lajnr53438ndcyjylgqsrnrtq5grs495v42qc6awsj45ys7

Weitere Übersetzungen / Other translations : - Spanisch / Spanish : nostr:naddr1qqx9zat994jhxttgv93xccgzypl4c26wfzswnlk2vwjxky7dhqjgnaqzqwvdvz3qwz5k3j4grrt46qcyqqq823cf6w59v — nostr:npub138s5hey76qrnm2pmv7p8nnffhfddsm8sqzm285dyc0wy4f8a6qkqtzx624

---

Habla ist eine auf Nostr basierende Plattform, mit der du umfangreiche Beiträge erstellen und verwalten kannst. Man könnte es mit Medium vergleichen, aber Habla ist viel mehr als das. Habla ist herkömmlichen Blogging-Plattformen überlegen, weil es auf Nostr basiert. Es ist mit einer Vielzahl anderer Nostr-Apps interoperabel, was die Benutzererfahrung nahtlos und fesselnd macht. Darüber hinaus können deine Inhalte, wenn sie von den Lesern als wertvoll empfunden werden, dank des Lightning-Netzwerkes sofort mit dem besten Geld, das die Menschheit je gesehen hat, belohnt werden: Bitcoin.

Was ist Nostr?

Nostr ist eine neue Art der Online-Kommunikation, die ihren Nutzern zahlreiche Vorteile bietet. Nostr ist für alle kostenlos, man braucht keine ID oder andere Verifizierung durch Dritte, um sich anzumelden, Gleichgesinnte zu treffen und die Community um sich herum zu vergrößern. Nostr wird oft mit einer Social-Media-Plattform verwechselt, ist aber viel mehr als das. Wir empfehlen dir einen Blick auf die hier gesammelten Nostr-Ressourcen zu werfen, um die potenzielle Dimension dieses Tools zu erkennen.

Wie melde ich mich bei Habla an?

Um auf Habla zu schreiben, erstelle einfach ein Habla/Nostr-Konto und melde dich an. Folge diesen einfachen Schritten, um dich zu registrieren, Mehrwert zu bieten und Gegenwert zurückzuerhalten.

Wie verdiene ich mit Habla?

Habla ermöglicht es, Werte direkt von deinen Lesern zu erhalten. Es ist kein Bankkonto oder Ausweis erforderlich. Verbinde einfach deine Lightning-Adresse mit deinem Habla/Nostr-Konto und erhalte Geld direkt auf dein Wallet – ohne Dritte, ohne Warten auf Abhebungen, ohne Stress. Folge diesen einfachen Schritten, um loszulegen.

Warum ist das Publizieren auf Habla anders?

Das Nostr-Protokoll ist sehr schlank, was einige Besonderheiten im Verhalten von Nostr-basierten Anwendungen mit sich bringt. Wir gehen hier nicht auf die technischen Details ein, aber der offensichtlichste Unterschied, den du als Autor bemerken wirst, ist, dass du ein anderes und möglicherweise ungewohntes Textformat für deine Beiträge verwenden musst. Aber keine Angst, Habla bietet Tools, die diesen Prozess einfach und intuitiv machen. Hier ist ein kurzes Video von nostr:npub1wkljx5c6a8uccc5etws8ry0y3r4dgavh2dcav0tal4rtmcdl4z2sfu5u0t, das die Grundlagen des Publizierens mit Habla erklärt (der Leitfaden wurde vor dem Redesign erstellt, ist aber immer noch nützlich):

https://nostr.build/p/nb9474.mp4

Habla (und viele andere Nostr-Anwendungen) verwendet das etablierte Format Markdown. Das gibt es schon seit fast einem Jahrzehnt und wird von den meisten Apps, die du jeden Tag benutzt, unterstützt. Der Grund, warum du vielleicht noch nichts von Markdown gehört hast, ist, dass herkömmliche Anwendungen es normalerweise vor dem Benutzer verbergen, und wir arbeiten daran, dies auch zu tun. Mehr über Markdown kannst du hier herausfinden.

Wo werden meine Inhalte gespeichert?

Herkömmliche Blogging-Plattformen speichern die Inhalte auf ihren eigenen Servern. Das ist ein bequemer und (früher) solider Ansatz, der aber auch kritische Risiken birgt. Wenn du die Früchte deiner Arbeit einer einzigen Partei überlässt, hat diese die vollständige Kontrolle über deine Inhalte. Nostr löst dieses Problem. Jedes Mal, wenn du etwas veröffentlichst, wird dein Inhalt an zahlreiche Relais zur Speicherung und Verbreitung weitergeleitet. Wenn ein Relais-Betreiber deinen Beitrag blockiert oder sich weigert, ihn weiterzuverbreiten, können deine Leser auf andere Relais zurückgreifen, um Zugang zu deinen Inhalten zu erhalten (keine Sorge, wenn das kompliziert klingt, alles geschieht unter der Haube). Auf diese Weise wird sichergestellt, dass du niemals zum Schweigen gebracht wirst. Wir haben uns entschieden, uns auf das zu konzentrieren, was wir am besten können: eine intuitive, effiziente und einfach zu bedienende Blogging-Plattform zu entwickeln, die sich lohnt – und das Speichern und Verbreiten von Inhalten den Profis auf diesem Gebiet zu überlassen.

Wie publiziere ich?

Habla bietet alle Tools, die du brauchst, um eindrucksvolle Artikel zu erstellen, die sich von anderen abheben. Bereite deinen Artikel vor, formatiere deinen Text mit den entsprechenden Tools, füge Medien hinzu und schau dir das Ergebnis vor Veröffentlichung selbst noch einmal an. Alles, was du brauchst, steht dir zur Verfügung, und die Plattform wird von Tag zu Tag besser und benutzerfreundlicher.

Wer kann meine Beiträge auf Habla lesen?

Jeder im Internet kann deine Beiträge lesen. Wenn deine Leser jedoch mit deiner Arbeit interagieren möchten – sei es durch Folgen, Kommentieren oder indem sie dir etwas zurückgeben möchten – sollten sie ein Nostr-Konto einrichten. Wir ermutigen dich, deine Follower einzubeziehen, um eine blühende Community aufzubauen und neue Höhen zu erreichen. Diese Kurzanleitung wird dir und deinen Fans den Einstieg erleichtern.

---

Dieses FAQ befindet sich in ständiger Entwicklung und wird sich in dem Maße ändern, wie Habla und Nostr zu noch leistungsfähigeren Tools werden. Bitte teile mir dein Feedback mit, damit ich es noch besser machen kann.

@ c1a643cc:da9777eb

U2FsdGVkX19ZfmkYwLOwEM3fufb1hNjw5Z0uViA1Pm8EwkdJ/ALRD7hV43AT34jTM5GZQxBUjztdrYVje2KJK5ZrYwddQ96zLIuY1aXhfSHdG74EwLt/xeFTsfJl/n+3BiWTR7c+Yu71ilAcgSxURDqVFiGJ3hCo+V8zngoyWC5EL5s5iVSxvV4k46v28hHY05OT/p26/S61yQvZv3Ybh4UZ1olOr5ExCy/U4axlqg+4Pr99PfcZGWWuMsHefCQi

@ 3bf0c63f:aefa459d

Timeu

Os quatro elementos, a esfera como a forma mais perfeita, os cinco sentidos, a dor como perturbação e o prazer como retorno, o demiurgo que cria da melhor maneira possível com a matéria que tem, o conceito de duro e mole, todas essas coisas que ensinam nas escolas e nos desenhos animados ou sei lá como entram na nossa consciência como se fossem uma verdade, mas sempre uma verdade provisória, infantil -- como os nomes infantis dos dedos (mata-piolho, fura-bolo etc.) --, que mesmo as crianças sabem que não é verdade mesmo.

Parece que todas essas coisas estão nesse livro. Talvez até mesmo a classificação dos cinco dedos como mata-piolho e tal, mas talvez eu tenha dormido nessa parte.

Me pergunto se essas coisas não eram ensinadas tradicionalmente na idade média como sendo verdade absoluta (pois afinal estava lá o Platão dizendo, em sua única obra) e persistiram até hoje numa tradição que se mantém aos trancos e barrancos, contra tudo e contra todos, sem ninguém saber como, um conhecimento em que ninguém acredita mas acha bonito mesmo assim, harmonioso, e vem despida de suas origens e fontes primárias e de todo o seu contexto perturbar o entendimento do mundo pelas crianças.

@ cb084639:2f16502a

Chef's notes

Bone broth 🦴 นั้นจะพูดให้ง่ายมันก็คือน้ำซุปต้มกระดูกสัตว์นั่นเอง สามารถใช้ได้ทั้งกระดูกไก่ หมู วัว ส่วนที่นอกจากนี้ยังไม่รู้จะหาได้จากตลาดหรือไม่ 555 ในที่นี้ที่จะมาทำกันเป็นกระดูกที่หาได้ง่ายตามตลาดทั่วไป หรือจะตามห้างสรรพสินค้า คือกระดูกหมูนั้นเอง 🐖 เอาแบบที่เป็นกระดูกจริงๆ ราราประมาณ 40 บาทต่อ 1กิโลกรัมเท่านั้นเอง การทำ bonebroth นั้นต้องเป็นการต้มด้วยไฟอ่อนเป็นระยะเวลานาน 12ขึ้นไป -24 ชั่วโมง เพื่อให้สารอาหารที่อยู่ในกระดูกละลายออกมาอยู่ในน้ำซุปของเรา ซึ่งเราคงสงสัยกันแล้วใช้มั้ยว่าเราจะทำเจ้า bonebroth กันทำไม bonebroth นั้นกินได้ทุกวัยและกินได้ทุกวัน มีสารอาหารหลายชนิดช่วยบำรุงร่ายกาย และยังเหมาะกับผู้สูงวัยที่อาจจะรับสารอาหารไม่เพียงพอด้วย การกินก็ง่ายๆคือนำมาซดเป็นน้ำซุปเลย หรือจะนำมาเป็นส่วนประกอบในเวลาปรุงอาหารก็ได้ครับ มันจะมีเรื่องหม้อแรงดันอีกถ้าใครมีมันจะช่วยทุ่นเวลาให้เราลงมาอีกครึ่งเลยครับ

Details

• ⏲️ Prep time: 10 min
• 🍳 Cook time: 12-24 hour
• 🍽️ Servings: 4

Ingredients

• กระดูกหมู 1.5 kgs.
• น้ำสะอาด 1 หม้อ เบอร์ 28
• เกลือชมพู 1ช้อนชา

Directions

1. นำกระดูกหมูล้างให้สะอาดมาต้มให้เดือดแล้วทิ้งน้ำไปก่อน 1 รอบ
2. ล้างกระดูกแล้วนำมาต้มในน้ำใหม่ไฟกลางถึงอ่อนยาว 12-24 ชม.
3. เติมเกลือชมพู
4. ถ้ายังไม่ถึงเวลาแล้วน้ำแห้ง เติมได้ตามความเหมาะสม
5. รอจนครบเวลาก็จะได้ bonebroth ไว้กินแล้วครับ

@ 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.

@ 3bf0c63f:aefa459d

Blockchains are not decentralized data storage

People are used to saying and thinking that blockchains provide immutable data storage. Then many times they add a caveat that says blockchains are very expensive, so we can't really store too much data on them, but we can still store some data if we really want and are ok with paying for it.

But the fact is that blockchains cannot ever be used to store anything. The purpose of blockchains is to keep track of some state that everybody must agree upon at all times, and arbitrary data that anyone may have wanted to backup there is not relevant to anyone else[^relevant] and thus there are no incentives for anyone else to keep track of that. In other words: if you backup your personal pictures as OP_RETURN outputs on Bitcoin, people may delete that and your backup will be void[^op-return-invalid-outputs].

Another thing blockchains supposedly do is to "broadcast" something. For example, nodes may delete the OP_RETURN outputs, but at least they have to verify these first, and spread they over the network, so you can broadcast your data and be sure everybody will get it. About this we can say two things: 1, if this happens, it's not a property of blockchains, but of the Bitcoin transaction sharing network that operates outside of the blockchain. 2, if you try to use that network for purposes that are irrelevant for the functioning of the Bitcoin protocol there is no incentive for other nodes to cooperate and they may ignore you.

The above points may sound weird and you may be prompted to answer: but you can do all that today and there is no actual mechanism to stop anyone from broadcasting irrelevant crap!, and that is true. My point here is only that if you're thinking about blockchains as being this data-broadcast-storage mechanism you're thinking about them wrong, that is not an essential part of any blockchain. In other words: the incentives are not aligned for blockchains to be used like that (unless you come up with a scheme that makes data from everyone else to be relevant to everybody), in the long term such things are not expected to work and insisting on doing them will result in either your application or protocol that stores data on the blockchain to crash or in the death of the given blockchain (I hope Bitcoin haters don't read this).

(This is a counterpoint to myself on idea: Rumple, which was a protocol idea that relied on a blockchain storing irrelevant data.)

[^relevant]: For example, all Bitcoin transactions are relevant to all Bitcoin users because as a user the total supply and the ausence of double-spends are relevant, and also the fact that any of these transactions may end up being ancestors of transactions that you might receive in the future. [^op-return-invalid-outputs]: Of course you can still backup your pictures as invalid P2PKH outputs or something like that, then it will be harder for people to spot your data as irrelevant, but this is not a feature, it's a bug of Bitcoin that enables someone to spam other nodes in a way they can't detect it. If people started doing this a lot it would break Bitcoin.

@ 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.

@ d2e97f73:ea9a4d1b

There’s a lot of conversation around the #TwitterFiles. Here’s my take, and thoughts on how to fix the issues identified.

I’ll start with the principles I’ve come to believe…based on everything I’ve learned and experienced through my past actions as a Twitter co-founder and lead:

1. Social media must be resilient to corporate and government control.
2. Only the original author may remove content they produce.
3. Moderation is best implemented by algorithmic choice.

The Twitter when I led it and the Twitter of today do not meet any of these principles. This is my fault alone, as I completely gave up pushing for them when an activist entered our stock in 2020. I no longer had hope of achieving any of it as a public company with no defense mechanisms (lack of dual-class shares being a key one). I planned my exit at that moment knowing I was no longer right for the company.

The biggest mistake I made was continuing to invest in building tools for us to manage the public conversation, versus building tools for the people using Twitter to easily manage it for themselves. This burdened the company with too much power, and opened us to significant outside pressure (such as advertising budgets). I generally think companies have become far too powerful, and that became completely clear to me with our suspension of Trump’s account. As I’ve said before, we did the right thing for the public company business at the time, but the wrong thing for the internet and society. Much more about this here: https://twitter.com/jack/status/1349510769268850690

I continue to believe there was no ill intent or hidden agendas, and everyone acted according to the best information we had at the time. Of course mistakes were made. But if we had focused more on tools for the people using the service rather than tools for us, and moved much faster towards absolute transparency, we probably wouldn’t be in this situation of needing a fresh reset (which I am supportive of). Again, I own all of this and our actions, and all I can do is work to make it right.

Back to the principles. Of course governments want to shape and control the public conversation, and will use every method at their disposal to do so, including the media. And the power a corporation wields to do the same is only growing. It’s critical that the people have tools to resist this, and that those tools are ultimately owned by the people. Allowing a government or a few corporations to own the public conversation is a path towards centralized control.

I’m a strong believer that any content produced by someone for the internet should be permanent until the original author chooses to delete it. It should be always available and addressable. Content takedowns and suspensions should not be possible. Doing so complicates important context, learning, and enforcement of illegal activity. There are significant issues with this stance of course, but starting with this principle will allow for far better solutions than we have today. The internet is trending towards a world were storage is “free” and infinite, which places all the actual value on how to discover and see content.

Which brings me to the last principle: moderation. I don’t believe a centralized system can do content moderation globally. It can only be done through ranking and relevance algorithms, the more localized the better. But instead of a company or government building and controlling these solely, people should be able to build and choose from algorithms that best match their criteria, or not have to use any at all. A “follow” action should always deliver every bit of content from the corresponding account, and the algorithms should be able to comb through everything else through a relevance lens that an individual determines. There’s a default “G-rated” algorithm, and then there’s everything else one can imagine.

The only way I know of to truly live up to these 3 principles is a free and open protocol for social media, that is not owned by a single company or group of companies, and is resilient to corporate and government influence. The problem today is that we have companies who own both the protocol and discovery of content. Which ultimately puts one person in charge of what’s available and seen, or not. This is by definition a single point of failure, no matter how great the person, and over time will fracture the public conversation, and may lead to more control by governments and corporations around the world.

I believe many companies can build a phenomenal business off an open protocol. For proof, look at both the web and email. The biggest problem with these models however is that the discovery mechanisms are far too proprietary and fixed instead of open or extendable. Companies can build many profitable services that complement rather than lock down how we access this massive collection of conversation. There is no need to own or host it themselves.

Many of you won’t trust this solution just because it’s me stating it. I get it, but that’s exactly the point. Trusting any one individual with this comes with compromises, not to mention being way too heavy a burden for the individual. It has to be something akin to what bitcoin has shown to be possible. If you want proof of this, get out of the US and European bubble of the bitcoin price fluctuations and learn how real people are using it for censorship resistance in Africa and Central/South America.

I do still wish for Twitter, and every company, to become uncomfortably transparent in all their actions, and I wish I forced more of that years ago. I do believe absolute transparency builds trust. As for the files, I wish they were released Wikileaks-style, with many more eyes and interpretations to consider. And along with that, commitments of transparency for present and future actions. I’m hopeful all of this will happen. There’s nothing to hide…only a lot to learn from. The current attacks on my former colleagues could be dangerous and doesn’t solve anything. If you want to blame, direct it at me and my actions, or lack thereof.

As far as the free and open social media protocol goes, there are many competing projects: @bluesky is one with the AT Protocol, nostr another, Mastodon yet another, Matrix yet another…and there will be many more. One will have a chance at becoming a standard like HTTP or SMTP. This isn’t about a “decentralized Twitter.” This is a focused and urgent push for a foundational core technology standard to make social media a native part of the internet. I believe this is critical both to Twitter’s future, and the public conversation’s ability to truly serve the people, which helps hold governments and corporations accountable. And hopefully makes it all a lot more fun and informative again.

💸🛠️🌐 To accelerate open internet and protocol work, I’m going to open a new category of #startsmall grants: “open internet development.” It will start with a focus of giving cash and equity grants to engineering teams working on social media and private communication protocols, bitcoin, and a web-only mobile OS. I’ll make some grants next week, starting with $1mm/yr to Signal. Please let me know other great candidates for this money.

@ 82341f88:fbfbe6a2

There’s a lot of conversation around the #TwitterFiles. Here’s my take, and thoughts on how to fix the issues identified.

I’ll start with the principles I’ve come to believe…based on everything I’ve learned and experienced through my past actions as a Twitter co-founder and lead:

1. Social media must be resilient to corporate and government control.
2. Only the original author may remove content they produce.
3. Moderation is best implemented by algorithmic choice.

The Twitter when I led it and the Twitter of today do not meet any of these principles. This is my fault alone, as I completely gave up pushing for them when an activist entered our stock in 2020. I no longer had hope of achieving any of it as a public company with no defense mechanisms (lack of dual-class shares being a key one). I planned my exit at that moment knowing I was no longer right for the company.

The biggest mistake I made was continuing to invest in building tools for us to manage the public conversation, versus building tools for the people using Twitter to easily manage it for themselves. This burdened the company with too much power, and opened us to significant outside pressure (such as advertising budgets). I generally think companies have become far too powerful, and that became completely clear to me with our suspension of Trump’s account. As I’ve said before, we did the right thing for the public company business at the time, but the wrong thing for the internet and society. Much more about this here: https://twitter.com/jack/status/1349510769268850690

I continue to believe there was no ill intent or hidden agendas, and everyone acted according to the best information we had at the time. Of course mistakes were made. But if we had focused more on tools for the people using the service rather than tools for us, and moved much faster towards absolute transparency, we probably wouldn’t be in this situation of needing a fresh reset (which I am supportive of). Again, I own all of this and our actions, and all I can do is work to make it right.

Back to the principles. Of course governments want to shape and control the public conversation, and will use every method at their disposal to do so, including the media. And the power a corporation wields to do the same is only growing. It’s critical that the people have tools to resist this, and that those tools are ultimately owned by the people. Allowing a government or a few corporations to own the public conversation is a path towards centralized control.

I’m a strong believer that any content produced by someone for the internet should be permanent until the original author chooses to delete it. It should be always available and addressable. Content takedowns and suspensions should not be possible. Doing so complicates important context, learning, and enforcement of illegal activity. There are significant issues with this stance of course, but starting with this principle will allow for far better solutions than we have today. The internet is trending towards a world were storage is “free” and infinite, which places all the actual value on how to discover and see content.

Which brings me to the last principle: moderation. I don’t believe a centralized system can do content moderation globally. It can only be done through ranking and relevance algorithms, the more localized the better. But instead of a company or government building and controlling these solely, people should be able to build and choose from algorithms that best match their criteria, or not have to use any at all. A “follow” action should always deliver every bit of content from the corresponding account, and the algorithms should be able to comb through everything else through a relevance lens that an individual determines. There’s a default “G-rated” algorithm, and then there’s everything else one can imagine.

The only way I know of to truly live up to these 3 principles is a free and open protocol for social media, that is not owned by a single company or group of companies, and is resilient to corporate and government influence. The problem today is that we have companies who own both the protocol and discovery of content. Which ultimately puts one person in charge of what’s available and seen, or not. This is by definition a single point of failure, no matter how great the person, and over time will fracture the public conversation, and may lead to more control by governments and corporations around the world.

I believe many companies can build a phenomenal business off an open protocol. For proof, look at both the web and email. The biggest problem with these models however is that the discovery mechanisms are far too proprietary and fixed instead of open or extendable. Companies can build many profitable services that complement rather than lock down how we access this massive collection of conversation. There is no need to own or host it themselves.

Many of you won’t trust this solution just because it’s me stating it. I get it, but that’s exactly the point. Trusting any one individual with this comes with compromises, not to mention being way too heavy a burden for the individual. It has to be something akin to what bitcoin has shown to be possible. If you want proof of this, get out of the US and European bubble of the bitcoin price fluctuations and learn how real people are using it for censorship resistance in Africa and Central/South America.

I do still wish for Twitter, and every company, to become uncomfortably transparent in all their actions, and I wish I forced more of that years ago. I do believe absolute transparency builds trust. As for the files, I wish they were released Wikileaks-style, with many more eyes and interpretations to consider. And along with that, commitments of transparency for present and future actions. I’m hopeful all of this will happen. There’s nothing to hide…only a lot to learn from. The current attacks on my former colleagues could be dangerous and doesn’t solve anything. If you want to blame, direct it at me and my actions, or lack thereof.

As far as the free and open social media protocol goes, there are many competing projects: @bluesky is one with the AT Protocol, nostr another, Mastodon yet another, Matrix yet another…and there will be many more. One will have a chance at becoming a standard like HTTP or SMTP. This isn’t about a “decentralized Twitter.” This is a focused and urgent push for a foundational core technology standard to make social media a native part of the internet. I believe this is critical both to Twitter’s future, and the public conversation’s ability to truly serve the people, which helps hold governments and corporations accountable. And hopefully makes it all a lot more fun and informative again.

💸🛠️🌐 To accelerate open internet and protocol work, I’m going to open a new category of #startsmall grants: “open internet development.” It will start with a focus of giving cash and equity grants to engineering teams working on social media and private communication protocols, bitcoin, and a web-only mobile OS. I’ll make some grants next week, starting with $1mm/yr to Signal. Please let me know other great candidates for this money.

@ 3bf0c63f:aefa459d

bitcoind decentralization

It is better to have multiple curator teams, with different vetting processes and release schedules for bitcoind than a single one.

"More eyes on code", "Contribute to Core", "Everybody should audit the code".

All these points repeated again and again fell to Earth on the day it was discovered that Bitcoin Core developers merged a variable name change from "blacklist" to "blocklist" without even discussing or acknowledging the fact that that innocent pull request opened by a sybil account was a social attack.

After a big lot of people manifested their dissatisfaction with that event on Twitter and on GitHub, most Core developers simply ignored everybody's concerns or even personally attacked people who were complaining.

The event has shown that:

1) Bitcoin Core ultimately rests on the hands of a couple maintainers and they decide what goes on the GitHub repository[^pr-merged-very-quickly] and the binary releases that will be downloaded by thousands; 2) Bitcoin Core is susceptible to social attacks; 2) "More eyes on code" don't matter, as these extra eyes can be ignored and dismissed.

Solution: bitcoind decentralization

If usage was spread across 10 different bitcoind flavors, the network would be much more resistant to social attacks to a single team.

This has nothing to do with the question on if it is better to have multiple different Bitcoin node implementations or not, because here we're basically talking about the same software.

Multiple teams, each with their own release process, their own logo, some subtle changes, or perhaps no changes at all, just a different name for their bitcoind flavor, and that's it.

Every day or week or month or year, each flavor merges all changes from Bitcoin Core on their own fork. If there's anything suspicious or too leftist (or perhaps too rightist, in case there's a leftist bitcoind flavor), maybe they will spot it and not merge.

This way we keep the best of both worlds: all software development, bugfixes, improvements goes on Bitcoin Core, other flavors just copy. If there's some non-consensus change whose efficacy is debatable, one of the flavors will merge on their fork and test, and later others -- including Core -- can copy that too. Plus, we get resistant to attacks: in case there is an attack on Bitcoin Core, only 10% of the network would be compromised. the other flavors would be safe.

Run Bitcoin Knots

The first example of a bitcoind software that follows Bitcoin Core closely, adds some small changes, but has an independent vetting and release process is Bitcoin Knots, maintained by the incorruptible Luke DashJr.

Next time you decide to run bitcoind, run Bitcoin Knots instead and contribute to bitcoind decentralization!

---

See also:

• How to attack Bitcoin, Anthony Towns' take

[^pr-merged-very-quickly]: See PR 20624, for example, a very complicated change that could be introducing bugs or be a deliberate attack, merged in 3 days without time for discussion.

@ 341db5a7:4c4fc2ef

Chef's notes

I like to fry catfish for friends and family, and sometimes I fry too much. Reheated fried food isn't great, but this is an amazing way to reinvent leftover fried catfish filets as a hearty curry dish. Feel free to substitute for whatever fried fish you have, and of course try different combination of veggies and curries. You can also fry your fish just before cooking, but it actually works better with cold filets, as they break down less in the sauce. Serves well over long grain rice, but Jasmine rice works great too!

Details

• ⏲️ Prep time: 30mins
• 🍳 Cook time: 30mins
• 🍽️ Servings: 6-8

Ingredients

• 1 yellow onion
• 1 bell pepper
• 2 carrots
• 1/2 cup shredded cabbage
• 6oz sliced mushrooms
• 1 stalk celery
• 2tbs garlic ginger paste
• 1/4 cup coconut oil
• 1 can coconut milk
• 5 tlbs curry powder
• 1 lbs leftover fried catfish filets
• salt and pepper to taste

Directions

1. chop all veggies to desired thickness for stir frying
2. heat coconut oil in wok or large skillet
3. add garlic ginger paste and cook til light brown and aromatic
4. add veggies sliced carrots, cook 1 min
5. add bell pepper, cook 1 min
6. add onion, cook 1 min
7. add celery, cook 1 min
8. add mushrooms, cook 1 min
9. add cabbage, cook until all veggies are almost soft
10. add coconut milk and curry powder and cook until boiling
11. add salt and pepper to taste
12. add your leftover catfish. bring back to a boil
13. cook 10 mins. stir cautiously at this point, as your fish filets may break down.
14. serve over rice

@ c1a643cc:da9777eb

Welcome to Tagayasu

This is the note editor, where you can create and edit your content.

To publish a note, make sure to enter a title below, then click Publish!

@ 2863f394:275ed58d

I setup a node or two...spent $400 each for incoming and outgoing and now I can't receive payments anymore. I basically lost $800 on this garbage.

@ 52387c6b:49dbdfb2

Chef's notes

Easy start to the day, can also put some Woostr in your Bloody Mary. Perfect for washing down the toast. Breakfast of champions. If you have some sharp cheddar you can melt this on the toast, altho this may prove too complex for the average bloke, just an option. Be mindful this will add significant prep and cook time. 2-3 minutes

Details

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

Ingredients

• 2 slices of bread
• Butter
• Woostr sauce
• Bloody Mary

Directions

1. Toast bread to your liking, lather a dollop of butter on. Criss cross the toast with a butter knife ( so the woostr dont roll off) and then drizzle on woostr.

@ 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.

@ 75bf2353:e1bfa895

Thank You !

@ 3bf0c63f:aefa459d

A violência é uma forma de comunicação

A violência é uma forma de comunicação: um serial killer, um pai que bate no filho, uma briga de torcidas, uma sessão de tortura, uma guerra, um assassinato passional, uma briga de bar. Em todos esses se pode enxergar uma mensagem que está tentando ser transmitida, que não foi compreendida pelo outro lado, que não pôde ser expressa, e, quando o transmissor da mensagem sentiu que não podia ser totalmente compreendido em palavras, usou essa outra forma de comunicação.

Quando uma ofensa em um bar descamba para uma briga, por exemplo, o que há é claramente uma tentativa de uma ofensa maior ainda pelo lado do que iniciou a primeira, a briga não teria acontecido se ele a tivesse conseguido expressar em palavras tão claras que toda a audiência de bêbados compreendesse, o que estaria além dos limites da linguagem, naquele caso, o soco com o mão direita foi mais eficiente. Poderia ser também a defesa argumentativa: "eu não sou um covarde como você está dizendo" -- mas o bar não acreditaria nessa frase solta, a comunicação não teria obtido o sucesso desejado.

A explicação para o fato da redução da violência à medida em que houve progresso da civilização está na melhora da eficiência da comunicação humana: a escrita, o refinamento da expressão lingüística, o aumento do alcance da palavra falada com rádio, a televisão e a internet.

Se essa eficiência diminuir, porque não há mais acordo quanto ao significado das palavras, porque as pessoas não estão nem aí para se o que escrevem é bom ou não, ou porque são incapazes de compreender qualquer coisa, deve aumentar proporcionalmente a violência.

@ 32e18276:5c68e245

Hey nostr posters,

I'm at Pacific Bitcoin this week! Come say hi if you're in LA! I have a nostr discussion with rockstar at the conference so check that out if you're here. Another fun thing I did this morning was a nostr podcast with Peter McCormack, so keep an eye for that one. I'm getting through some remaining bugs for the 1.6 App Store release, one annoying issue in the last build was that you couldn't update your profile. This has been fixed!

We also fixed some bugs with the clear cache button, it should be more responsive now. Daniel has been doing some great work with reducing the buggyness of the post composition view, so hopefully you should notice some quality of life improvements there. Daniel also improved many bugs with muted users. If you've muted a user that has been reposted in your timeline, damus will now hide those.

Thanks for your patience with this release, integrating nostrdb has been time consuming! Hopefully back to a more regular release schedule after this one.

Check out the full changelog:

Changed

• Improve UX around clearing cache (Daniel D’Aquino)
• Show muted thread replies at the bottom of the thread view (#1522) (Daniel D’Aquino)

Fixed

• Fix situations where the note composer cursor gets stuck in one place after tagging a user (Daniel D’Aquino)
• Fix some note composer issues, such as when copying/pasting larger text, and make the post composer more robust. (Daniel D’Aquino)
• Apply filters to hashtag search timeline view (Daniel D’Aquino)
• Hide quoted or reposted notes from people whom the user has muted. (#1216) (Daniel D’Aquino)
• Fix profile not updating (William Casarin)
• Fix small graphical toolbar bug when scrolling profiles (Daniel D’Aquino)
• Fix localization issues and export strings for translation (Terry Yiu)

@ 3bf0c63f:aefa459d

Problemas com Russell Kirk

A idéia central da “política da prudência[^1]” de Russell Kirk me parece muito correta, embora tenha sido melhor formulada pior no seu enorme livro do que em uma pequena frase do joanadarquista Lucas Souza: “o conservadorismo é importante, porque tem muita gente com idéia errada por aí, e nós podemos não saber distingüi-las”.

Porém, há alguns problemas que precisam ser esclarecidos, ou melhor explicados, e que me impedem de enxergar os seus argumentos como refutação final do meu já tão humilde (embora feroz) anarquismo. São eles:

I Percebo alguma coisa errada, não sei bem onde, entre a afirmação de que toda ideologia é ruim, ou “todas as ideologias causam confusão[^2]”, e a proposta conservadora de “conservar o mundo da ordem que herdamos, ainda que em estado imperfeito, de nossos ancestrais[^3]”. Ora, sem precisar cair em exemplos como o do partido conservador inglês -- que conservava a política inglesa sempre onde estava, e se alternava no governo com o partido trabalhista, que a levava cada vez mais um pouco à esquerda --, está embutida nessa frase, talvez, a idéia, que ao mesmo tempo é clara e ferrenhamente combatida pelos próprios conservadores, de que a história é da humanidade é uma história de progresso linear rumo a uma situação melhor.

Querer conservar o mundo da ordem que herdamos significa conservar também os vários erros que podem ter sido cometidos pelos nossos ancestrais mais recentes, e conservá-los mesmo assim, acusando toda e qualquer tentativa de propôr soluções a esses erros de ideologia? Ou será que conservar o mundo da ordem é escolher um período determinado que seja tido como o auge da história humana e tentar restaurá-lo em nosso próprio tempo? Não seria isto ideologia?

Ou, ainda, será que conservar o mundo da ordem é selecionar, entre vários períodos do passado, alguns pedaços que o conservador considerar ótimos em cada sociedade, fazer dali uma mistura de sociedade ideal baseada no passado e então tentar implementá-la? Quem saberia dizer quais são as partes certas?

II Sobre a questão do que mantém a sociedade civil coesa, Russell Kirk, opondo-a à posição libertária de que o nexo da sociedade é o autointeresse, declara que a posição conservadora é a de que “a sociedade é uma comunidade de almas, que une os mortos, os vivos e os ainda não nascidos, e que se harmoniza por aquilo que Aristóteles chamou de amizade e os cristãos chamam de caridade ou amor ao próximo”.

Esta é uma posição muito correta, mas me parece estar em contradição com a defesa do Estado que ele faz na mesma página e na seguinte. O que me parece errado é que a sociedade não pode ser, ao mesmo tempo, uma “comunidade baseada no amor ao próximo” e uma comunidade que “requer não somente que as paixões dos indivíduos sejam subjugadas, mas que, mesmo no povo e no corpo social, bem como nos indivíduos, as inclinações dos homens, amiúde, devam ser frustradas, a vontade controlada e as paixões subjugadas” e, pior, que “isso somente pode ser feito por um poder exterior”.

Disto aí podemos tirar que, da mesma forma que Kirk define a posição libertária como sendo a de que o autointeresse é que mantém a sociedade civil coesa, a posição conservadora seria então a de que essa coesão vem apenas do Estado, e não de qualquer ligação entre vivos e mortos, ou do amor ao próximo. Já que, sem o Estado, diz, ele, citando Thomas Hobbes, a condição do homem é “solitária, pobre, sórdida, embrutecida e curta”?

[^1]: este é o nome do livro e também um outro nome que ele dá para o próprio conservadorismo (p.99). [^2]: p. 101 [^3]: p. 102

@ 3bf0c63f:aefa459d

Programming quibbles

• About CouchDB
• my personal approach on using let, const and var in javascript
• A crappy course on torrents
• Multi-service Graph Reputation protocol
• The monolithic approach to CouchDB views
• My stupid introduction to Haskell
• The unit test bubble
• There's a problem with using Git concepts for everything
• On the state of programs and browsers
• Rust's .into() is a strictly bad thing

@ 32e18276:5c68e245

Hey gang,

I just pushed Damus build 18 which is the first major nostrdb integration. Now all damus profiles are stored in nostrdb! You will always be able to search profiles from people you've seen in the past.

There are many crash fixes in this build as well, check out the full changelog:

Enjoy!

Added

• Add followed hashtags to your following list (Daniel D’Aquino)
• Add "Do not show #nsfw tagged posts" setting (Daniel D’Aquino)
• Hold tap to preview status URL (Jericho Hasselbush)
• Finnish translations (etrikaj)

Changed

• Switch to nostrdb for @'s and user search (William Casarin)
• Use nostrdb for profiles (William Casarin)
• Updated relay view (ericholguin)
• Increase size of the hitbox on note ellipsis button (Daniel D’Aquino)
• Make carousel tab dots tappable (Bryan Montz)
• Move the "Follow you" badge into the profile header (Grimless)

Fixed

• Fix text composer wrapping issue when mentioning npub (Daniel D’Aquino)
• Make blurred videos viewable by allowing blur to disappear once tapped (Daniel D’Aquino)
• Fix parsing issue with NIP-47 compliant NWC urls without double-slashes (Daniel D’Aquino)
• Fix padding of username next to pfp on some views (William Casarin)
• Fixes issue where username with multiple emojis would place cursor in strange position. (Jericho Hasselbush)
• Fixed audio in video playing twice (Bryan Montz)
• Fix crash when long pressing custom reactions (William Casarin)
• Fix random crash due to old profile database (William Casarin)

@ a012dc82:6458a70d

El BITCOIN es un método muy usado para paliar la crisis en los países donde la inflación es muy alta, tal es el caso de Argentina así como otros países de Centro y Sudamérica, en nuestro podcast abordaremos temas de mucha relevancia en cuanto a la utilización de este método, en la voz de nuestro invitado el Dr. Ricardo Mihura, presidente de la ONG Bitcoin Argentina con quien hablaremos nuevamente en Español.

El invitado de éste podcast, el Dr. Ricardo Mihura, experimentado en su profesión con más de 40 años de carrera, nos hablará acerca de esta ONG y de los objetivos que persigue, entre otros, instruir y capacitar a las personas para el correcto manejo de la criptomoneda, proporcionandoles métodos y estratégias para a futuro poder hacer del Bitcoin su principal fuente de ingresos.

Tabla De Contenidos

• Introducción

• ¿Cómo surge la ONG Bitcoin Argentina?

• ¿De qué trata la ONG y qué actividades organiza?

• ¿Existe una programación constante para las conferencias o es producto de un estudio de mercado para valorar que hace falta abordar?

• ¿Qué objetivos a mediano y largo plazo tiene la ONG?

• ¿Cómo será la adopción del BTC en Argentina?

• Conclusiones

• Preguntas Frecuentes

Introducción

La ONG Bitcoin Argentina, como una organización no gubernamental sin fines de lucro se encuentra en la búsqueda de capacitar a cada vez más personas en este complejo mundo del BITCOIN de manera gratuita, en este podcast conoceremos un poco más del funcionamiento y objetivos de esta organización en la voz de su presidente, el Abog. Ricardo Miura.

¿Cómo surge la ONG Bitcoin Argentina?

La ONG fue creada por 3 visionarios futuristas que han sido reconocidos en el medio de los bitcoin que son Diego Gutierrez Saldivar, Franco Amati y Rodolfo Andragnes, que hace 10 años comenzaron a planear el proyecto y se lanzaron a ejecutarlo. Miura entra en el equipo de trabajo en el 2016 ya estando el grupo bastante sólido y se desarrolló una comunidad armoniosa en la que comenzó a trabajar fuertemente en el proyecto.

¿De qué trata la ONG y qué actividades organiza?

La ONG Bitcoin Argentina, es una organización no gubernamental que busca capacitar y orientar a las personas que tienen la intención de incursionar en Bitcoin, con miras de hacer de esto su estilo de vida. Las actividades que abordamos en mayor medida son conferencias en la que se difunden, capacitan en relación al tema de bitcoin desde un onboarding básico hasta un curso de especialización para abogados. Nuestros eventos son sin ánimo de lucro por lo que son de entrada libre y sin publicidad si no abocada a lo que realmente es.

¿Existe una programación constante para las conferencias o es producto de un estudio de mercado para valorar que hace falta abordar?

Existe de todo, en nuestros planes de estudios tenemos hasta una diplomatura en derecho de cripto, es un programa anual en la que se abordan distintos temas, también tenemos alianzas con distintas instituciones educativas, por ejemplo, tenemos alianza con la universidad de Buenos Aires en la que contamos con una matrícula de miles de alumnos, lo que buscamos es que la UBA así como otras instituciones para lograr que despierten el interés de este tema.

¿Qué objetivos a mediano y largo plazo tiene la ONG?

Los objetivos serían en primera instancia ser percibida como una autoridad seria en la materia de Bitcoin a través del tiempo, en cuanto a los objetivos que queremos lograr pues, queremos que la sociedad logre una aceptación pacífica de bitcoin, y eso requiere de conocimientos, es por eso que trabajamos en ello, para que a largo plazo la sociedad sepa identificar las estafas de las no estafas, buscamos que no caigan en malos comentarios de personas mal intencionadas que quieren manchar el nombre de Bitcoin.

¿Cómo será la adopción del BTC en Argentina?

Trabajamos en lograr la aceptación total, aun falta mucho camino por recorrer, pero existen en Argentina las 2 caras de la moneda, el exchange que confía plenamente en la plataforma y se divierte con ello, como el escéptico que aun no confia, así que según Miuri, aún queda mucho trabajo por hacer en este sentido.

Conclusiones

La ONG tiene como objetivo principal capacitar y concientizar a la sociedad para el uso y manejo del bitcoin, con esto se busca cuidar el dinero de las personas si en alguna ocasión se presenta una situación similar al corralito donde los bancos regulan el manejo del dinero depositado e inclusive en algunos casos personas que perdieron su dinero.

Las regulaciones bancarias del uso de criptomonedas son bastante fuertes, por lo que es estrictamente necesario que la población tenga los conocimientos adecuados del uso y manejo de las criptomonedas, Miura piensa que el BITCOIN es el futuro de la economía minimalismo, es por esto que ellos están enfocados al 100% a capacitar a la poblacion.

Preguntas Frecuentes

¿Cualquier persona puede formar parte de la ONG? Para formar parte de la ONG los únicos factores relevantes son, tiempo y dinero, si se cuenta con esos 2 factores cualquier persona puede incursionar.

¿Cuál es el periodo de un presidente en la ONG? El periodo de un presidente es de 9 años, puede prolongarse por unos meses más o ser reelegido.

¿Cuál es el valor de una conferencia o curso de capacitación dictada por la ONG ? La inversión hasta la fecha es 0, todas nuestras conferencias y cursos son de entrada libre, la única inversión es lo que deben pagar para comprar el capital con el que van a trabajar.

Esto es todo por hoy, nos vemos mañana

Si quereés saber mas, seguinos en:

NOSTR: croxroad@getalby.com

X: @croxroadnews

Instagram: @croxroadnews.co

Youtube: @croxroadnews

Tienda Online: https://croxroad.store

Subscribite a CROX ROAD, el newsletter diario solo sobre Bitcoin

https://www.croxroad.co/subscribe

DESCARGO DE RESPONSABILIDAD: Nada de esto es un consejo financiero. Este boletín es estrictamente educativo y no es un consejo de inversión ni una solicitud para comprar o vender activos ni para tomar decisiones financieras. Tenga cuidado y haga su propia investigación.

@ 1408bad0:4971f2ca

There was a great meme from Wojak about Wen will Bitconi demonitise Gold. This could come quicker than we think, especially even some banks are thinking that there will be a faster Bitcoin adoption than when the Gold ETF was launched.

Gold has around a $12 Trillion market cap according to recent data and it will be interesting to see how quickly Bitocoin erodes into this in the next 2 years.

source

Bitcoin will surely catch up and easily overtake Gold's marketcap in the next few years in my opinion, especially with the mediocre returns from holding gold, just look at Peter Schiff. The real test will come however when it comes to real estate.

Real estate is another beast from gold though and it will not go down without a fight. According to the Bitcoin Prague presentation by Michael Saylor, the real estate market is worth over $330 Trillion, which is a massive number in magnitude to that of gold.

The other thing to remember is that real estate is used by the fiat central bankers as a faucet to pump more fiat debt into the system. If this faucet starts to dry up, they would need to resort to more imaginative ways to indebten people or the whole system could start to collapse.

There are many tax benefits given to those who take on debt to buy real estate in many countries. Many people can write off the interest payments on their tax bills, other can avoid capital gains taxs by hodling real estate. This causes people to take on large amounts of debt and pump up the price of housing and cause huge bubbles that the next generation are supposed to take on and keep the system going.

In the slide by Michael Saylor, he predicts Bitcoin could take maybe 15% of the real esate market cap and has the potential to take half of it, which would be huge from where we currently are.

50% of $330 Trillion would add $165 Trillion to Bitcoins market cap and it would be hard to put a price on a Satoshi if that happens, let a lone a full Bitcoin.

Would there be some reaction from the Banks when they lose a major fiat debt faucet though? How would they react and would they try to make taking on debt for houses even more attractive than the ultra-low rates we have had in recent years?

If Bitcoin starts making inroads into people investing in Bitcoin instead of taking debt to buy real estate, it could possibly trigger a huge deflation in the fiat world for real estate as people abandon buying extra apartments to rent out and instead and less liquidity would be flowing in the system.

What are your thoughts on how Bitcoin will affect the real estate market?

Thanks for reading.

Let's connect : mypathtofire

@ fac513a1:d4f407a5

You’re walking down the street.

People are flowing by you.

Tall.

Small.

Smilling.

Crying.

Whatever the case might be, what would happen if you stopped each one of them, and asked a simple question:

“What is your goal?”

Chance’s are, most people would have the same response.

“I don’t know”

Or if they did have an answer, maybe it’s…

“Get my hair cut”

A little better would be…

“Grow my wealth”

Point being, we charge around through life without properly taking the time to set effective goals.

Could we be more productive?

Could we be happier?

Could we be better at realising our dreams?

I am just embarking on a personal development course with our wonderful osteopath Sharizaar.

She is an alumni of the Proctor-Gallagher institute, an organisation founded by a guy called Bob Proctor, a disciple of Napoleon Hill’s almost century old book “Think and Grow Rich”.

In one of the early lesson’s Bob points out brilliantly how directionless most of us are.

We haven’t set strategic goals.

And without good goals we’re doomed to mediocrity.

It really resonated.

In particular he unpacked the different types of goals he see’s.

A, B, and C type goals.

Let’s dissect them.

An A-type goal is a goal you already know how to do.

Let’s say my goal is to buy a new BMW X5.

Sounds nice.

But if I already own a BMW X5, which I bought 2 years ago new, then my goal is something I already know how to do.

If you already understand how to do it, then it doesn’t force you to learn or test yourself, so there is no personal growth attached to it.

On reflection, many of the goals I have are like this…

A B-type goal requires a little more thinking.

It’s a goal that you know, should you collect together lots of information, speak to that person, go to that place, buy that thing, then you’re confident you can get there.

You have a mind map of how to achieve a B-type goal.

Sure, attainment of the goal might be a good thing, but you’re simply collecting resources together.

There is no creativity involved in pulling all that together.

The problem with a B-type goal: you will get bored.

As I think through this, we’ve just made the decision to go and spend a month in Byron bay, so I set this as a goal.

I’ve booked a property, paid for flights, found a way to get a car and dog up there, all of which I knew I could achieve.

I am not bored.

But it’s a case of curating a bunch of things that I already know how to do.

Which brings me to a C-type goal.

As Bob brilliantly points out, this type of goal is more like a vision, a fantasy, a dream come true.

He encourages you to get creative.

Sit down.

Breathe.

Feel.

What is it that you’ve always really wanted?

Fly a helicopter.

Speak fluent French.

Climb Mt Everest.

Just some fun things that spring to mind.

The key here is to be almost irrational, conjure up things that one immediately rejects as impossible, something that initially scares you.

Go on a silent retreat.

Swim the English Channel.

Write a book.

Even those aren’t truly scary enough!

I am thinking on the fly here… Arguably this is best done with nothing in mind.

Create a sustainable source of energy that is costless.

Time travel.

Go to Mars.

That’s better.

Those are terrifying!

What I like here though, it really resonates, is that “you are your thoughts”.

If we set a C-type goal well, sure we don’t know how to achieve it, but once we set our mind on it then the creativity flows.

“When there is a will, there is a way.”

Bob quotes Napoleon Hill “imagination is the most marvellous, miraculous, inconceivably powerful force the world has ever know”.

Well this is a fun way to start the day!

Pumped.

I am inspired to spend more time spitballing terrifying ideas that could become a goal.

Admittedly Sharizaar did help me to set a C-type goal lately, which is poignant if only for the fact it’s the first time in my life I set a goal that didn’t include something to do with money, which should actually just be the output of a good goal.

Each mornign and evening I say to myself: “I’m so grateful and happy, now that I give myself permission to live everyday as an open space of discovery, fulfilment, and wonder.”

Cheesy.

Yes.

Spiritual.

Yes.

Fun first attempt.

For sure.

Where is this all taking me?

Time will tell.

But with a renewed vigour to utilise goal setting I am confident of a happier, healthier, and wealthier future.

What goals do you have?

Best, Jake

Ps - until the last year I was very bad at spending money on myself. Sure, I’ve invested in other people, I’ve travelled a lot, and been very fortunate in general, but I am guilty of poor self-care. Massage? No thanks. Osteo session? No thanks. Meditation? Don't have time… With the beautiful influence of my wife, a bio-hacker if ever there was one, I am quickly improving. One of the area’s I am most excited about, and have already felt benefits from, is paying up for personal development coaching. I encourage you do consider doing the same! As always, DM open, as I’d love to hear from you.

@ 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

@ d830ee7b:4e61cd62

A Show for Thai Nostrs That Aligns with Austrian Economics

The initiative behind the specific program #สภายาม่วง (The Purple Council, hosted by nostr:npub1ejn774qahqmgjsfajawy7634unk88y26yktvwuzp9kfgdeejx9mqdm97a5) emerged from blending various concepts together. My objective is thus diverse and dynamic.

Benefits to the Community

• Supporting Austrian Economic Principles: When you create value out of self-interest, leading to genuine benefits to the community, you deserve to be rewarded.
• Open to All: This space is for everyone in our community who contributes value through their proof of work, expecting more than just personal gain.
• Opportunity for Recognition: Individuals can voluntarily reveal their stories, helping the community to appreciate and understand different aspects of their identities.
• Promoting a Culture of Respect and Admiration: We push a new culture where value creation is not seen as futile or ignored.
• Accessible to All, Not Just Influencers: The platform is for anyone who deserves it, even if the positive value they bring is just making others laugh.
• Inspiring Community Engagement: Motivating everyone to benefit others without expecting anything in return other than personal satisfaction, while respecting each other through creative and positive contributions.
• Fostering a Positive Community Atmosphere: Connecting values and interactions among community members.
• Self-Value and Pride in the Community: Encouraging unity and cooperation to achieve greater things in the future.
• Content Rich in Value: Easygoing and comfortable viewing culture, full of warmth and fun, with a free and interactive chat environment.
• Unique Experiences with Influencers: Exclusive content on Nostr that differs from mainstream media, offering new experiences and fun.
• Space for Special Agendas and Topics: A place for sharing knowledge, experiences, and discussions beneficial to the community, not necessarily requiring interviews.

Benefits to Individuals (Crew, Guests, Audience)

• Freedom of Speech: Discuss topics that are hard to find a platform for, without self-censorship (while still being responsible for one's actions). Allows for full expression of personality (if distributed further, some parts may be cut to prevent negative impacts on the speaker and our community).
• On-Camera Presence in Live Shows: Practice real-time, unscripted interaction. Mistakes and slip-ups are allowed, fostering a more relaxed expression without the pressure of production quality expectations. This leads to habituation in public speaking and skill development.
• Spontaneous Interaction: As I am the only one aware of the content and the identity of the guests in each episode, other participants must respond spontaneously to unforeseen situations (known at the same time as the audience). It's a practice in handling unprepared presentations, unexpected questions, and developing quick thinking, reducing panic in similar future scenarios (especially for my team members).
• Listening Skills Development: Cultivate mindfulness, attention, and the ability to think, analyze, and discern. Design approaches to respond to unscripted events and create content with a forward-thinking approach, while considering the experiences and values the audience will gain.
• Boost in Self-Confidence: Pride in handling unforeseen events effectively, overcoming fears and perceived obstacles.
• Learning Responsibility: Understand the consequences of actions, decisions, and immediate responses, as well as the digital footprint created. These experiences are valuable for personal development.
• For the Audience: Enjoy uncensored, friendly, and relaxed content (even if some topics are mentally challenging). The informal setting allows for engaging and entertaining discussions in chat, alleviating loneliness.
• Using Satoshi through Zaps: A beneficial use-case for both giver and receiver. It allows one to appreciate and marvel at the value of their choices. Receivers gain pride and recognition for their contributions, supported by positive reinforcement. Givers feel fulfilled, contributing to the community's value creation.
• Inspiration for Self-Improvement: Encourages bold suggestions for both the program and the platform, aiming for future improvements. Participate in the development of these improvements.

My Contribution to the Global Nostr Community

One thing I believe I have contributed to the global Nostr community is bringing into practical use the creations of developers. By implementing these developments, I have helped realize beneficial use-cases that genuinely add value in various aspects. Moreover, I strive to demonstrate that these contributions significantly benefit a large number of people, creating a ripple effect that extends both within and beyond the community.

---

There are many things in my mind, but let me just share a part of it. I hope this gives you some understanding of my intentions behind producing this program.

Although I don't have enough time to personally acknowledge everyone who contributes value extensively (and there are many who are not comfortable being in the media - no problem there), as long as this Purple Field exists, there will come a day when I can express my appreciation to everyone.

If there is anyone you would like to know more about, I am more than willing to listen to suggestions and invite these individuals to join and share their value in future episodes of The Purple Council.

Another thing I want to emphasize about the value of this program (even if it seems self-praising) is that I've never intended to appear in the media or any programs before. It's still the same today, except for very important and necessary occasions.

This program is the only one I've chosen to be a part of, to show the "price" of the value created here, to demonstrate how much I value this principle and love our Purple Field community.

Please continue to follow The Purple Council. If there's anything I can improve or develop, don't hesitate to give your suggestions.

Thank you. 🙏

P.S. We now have #Siamstr Radio on #Nostrnest operating 24/7. It's a similar space for our Purple Field community. You can join and have fun with friends there without having to wait for The Purple Council.

I've been quite busy with various tasks lately and haven't been as active in the Purple Field as before. I apologize for this.

@ 8d9d2b77:86dd65fa

Chef's notes

When I make this creamy taco soup, I don't really measure anything, so this will be approximate measurements. The recipe is very forgiving, and you can add or delete to your taste. The cream cheese is the key ingredient to make this soup creamy, and in my opinion the cilantro is a must.

Details

• 🍳 Cook time: 30 minutes
• 🍽️ Servings: 8

Ingredients

• 2-3 lbs ground beef
• 1 whole onion
• 1 head of fresh garlic
• 2-3 8oz packages cream cheese, depending on your taste
• Beef bouillon, 2-3 cubes
• Chili powder to taste
• Salt and pepper to taste
• Cumin to taste
• Cayenne pepper, optional
• Fresh cilantro to taste
• I can fire roasted, diced tomatoes

Directions

1. In a large cookpot, brown meat.
2. Add onions and garlic, simmer for 5 mins
3. Add diced tomatoes and cream cheese.
4. Add all seasonings
5. Add cream cheese, allow to melt and stir.
6. At this point you might want to add a bit of water or milk, depending on how thick you want the soup.
7. Let simmer for 10 min.
8. Add cilantro and let it wither, about 3 mins
9. Thats it! If you wish, you can top with shredded cheese or avocado.

@ 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.

@ 3bf0c63f:aefa459d

A command line utility to create and manage personal graphs, then write them to dot and make images with graphviz.

It manages a bunch of YAML files, one for each entity in the graph. Each file lists the incoming and outgoing links it has (could have listen only the outgoing, now that I'm tihnking about it).

Each run of the tool lets you select from existing nodes or add new ones to generate a single link type from one to one, one to many, many to one or many to many -- then updates the YAML files accordingly.

It also includes a command that generates graphs with graphviz, and it can accept a template file that lets you customize the dot that is generated and thus the graphviz graph.

rel

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

@ 3647c6df:10d67610

Velocity of money refers to how much monetary energy can be harnessed as money flows. It is often wrongly interpreted as simply how fast or how often money moves from one place to another, but the actual benefit of velocity of money is in the work it does on the way from one place to another. How many jobs can it perform and how many productive activities can it sustain along the way?

It is analogous to a mountain lake where a vast amount of water is contained but unproductive. By building a trench to move some of that water to a small garden "productivity" is increased, and the velocity of the water is increased. A water wheel or turbine could be placed in the stream to spin a mill or generate electricity, increasing the velocity of the water and maximizing its productive use. Other energy sources can be combined with the water to create additional forms of energy that can drive increasing innovation. Such as heat for steam power or the cool water can be run through a house for cooling and washing prior to is use as irrigation. Without these systems, the energy and usefulness of the waters "velocity" is simply wasted and never recovered. The possibilities are only limited by the tools used to harvest the potential energy, The distance over which the water travels and imagination. It is not the movement alone of the water that is desired but the effects of the movement that offer endless possibilities, the flow is a means.

Similar to how water nourishes the physical landscape and stores energy to generate work, money nourishes the economic landscape and stores energy to generate work. Money is a natural part of economic landscapes which arise anytime trade needs to be facilitated. The brilliant cult classic film "Idiocracy" serves as an interesting counter-analogy for this concept. In the film, a society has become convinced that using a colored high-sugar sports drink (Brawndo) on crops is "What plants crave". However, the protagonist suggests trying water instead, and the society is saved.

The point of the Brawndo storyline seems to be a commentary on special interests, the sports drink manufacturers. Being able to seize control of the narrative and create artificial demand for their product in a context where it was actually harmful to the ecosystem. Isn't the same true with fiat currency? It has no historical use, attributes of good money, or spontaneous emergence. It is simply decreed by those in power. "Fiat, it’s what economies crave."

Many have become convinced that a proprietary patented, yellow #5, high fructose corn syrup money equivalent is what we need to grow our economies. The problem is that our ability to create monetary velocity is stifled by using a proprietary system because our use of it is limited by the owners of it. ("Sorry, Brawndo is not permitted to pass through a turbine. You need a license for that.")

When the forms of money needed to expand our economies physical and digital have emerged spontaneously and without decree, we just need to figure out how to use them. We can do this by not simply building a stack but stacking functions. Creating the tools and systems that can allow us to capture the energy as the money moves. In the digital realm bitcoin has emerged as the base layer of money, the stored energy, the actual water. Channels (lightning) have now been constructed to efficiently move bitcoin in large volumes for lower cost between pools. We seem to be at the water wheel invention phase where ecash mints of various types will be able to tap into channels and generate new forms of economic energy.

A quite interesting case study of stacking monetary functions and attaining high monetary velocity is in various forms of traditional life insurance contracts. Each monetary unit that is placed in the contract performs the following functions simultaneously: preservation of life value/life insurance, savings/retirement funds and collateral assets. The funds locked into the contract grow but can also be borrowed against. Instead of canceling the contract and taking the cash and missing out on future growth (interrupting the compounding growth), the owner can borrow against the cash value for personal investment, business ventures, paying off high-interest debt, etc., for any reason really and all contractually guaranteed. These contracts predate the fiat monetary system and worked on gold and silver standards in the past.

The insurance companies that are the longest lived and most financially sound operate as Mutual companies meaning the policy/contract holders are the shareholders; there are no third parties that have ownership in the assets of the mutual insurance company. Some are nearly 200 years old, which rivals the oldest banks in the world. Even today these contracts are quite attractive in terms of control over funds and the yields aren't bad in fiat terms.

The problem is that in order to keep up with inflation people have to take more risk and give up more financial sovereignty to chase yields. We can see that using this pre-fiat financial instrument, each monetary unit can accomplish 3 “jobs” at the same time: generate insurance, save for retirement, obtain a collateralized loan. This is only one example of using and harnessing monetary velocity. What we really need to do is break free from the fiat mindset that tells us there's only one way to go about solving financial problems and start thinking creatively about how to move money to places where it is most needed and likely to generate a return.

In relation to Bitcoin, when I first heard about Fedimints, my mind went straight to the mutual insurance company structure. A group of known and vested guardians is entrusted to provide specific contractually guaranteed benefits. Who wouldn't want a bitcoin service that would allow anyone to generate an uninterrupted compounding yield on bitcoin, allow borrowing against it at a competitive market rate, and pay out a large settlement to heirs in the event of death – all denominated in bitcoin. Without ever giving up full custody of the asset.

Underlying funds would all be on-chain, investments would be in lightning liquidity and infrastructure. Loans would be given to policy owners via ecash or lightning depending on the use case. Or something completely different. It's almost impossible to see how something like this would actually work until it is tried and iterated. Innovation always comes with unforeseen problems and eucatastrophes. The possibilities that will be made available in the years to come are exciting but will require an immense investment of time and energy, the pay off is escaping from the Idiocracy.

@ 3bf0c63f:aefa459d

There's a problem with using Git concepts for everything

We've been seeing a surge in applications that use Git to store other things than code, or that are based on Git concepts and so enable "forking, merging and distributed collaboration" for things like blogs, recipes, literature, music composition, normal files in a filesystem, databases.

The problem with all this is they will either:

1. assume the user will commit manually and expect that commit to be composed by a set of meaningful changes, and the commiter will also add a message to the commit, describing that set of meaningful, related changes; or
2. try to make the committing process automatic and hide it from the user, so will producing meaningless commits, based on random changes in many different files (it's not "files" if we are talking about a recipe or rows in a table, but let's say "files" for the sake of clarity) that will probably not be related and not reduceable to a meaningful commit message, or maybe the commit will contain only the changes to a single file, and its commit message would be equivalent to "updated <name of the file>".

Programmers, when using Git, think in Git, i.e., they work with version control in their minds. They try hard to commit together only sets of meaningful and related changes, even when they happen to make unrelated changes in the meantime, and that's why there are commands like git add -p and many others.

Normal people, to whom many of these git-based tools are intended to (and even programmers when out of their code-world), are much less prone to think in Git, and that's why another kind of abstraction for fork-merge-collaborate in non-code environments must be used.

@ 3bf0c63f:aefa459d

Trello Attachment Editor

A static JS app that allowed you to authorize with your Trello account, fetch the board structure, find attachments, edit them in the browser then replace them in the cards.

Quite a nice thing. I believe it was done to help with Websites For Trello attached scripts and CSS files.

• https://github.com/fiatjaf/trello-attachments
• https://fiatjaf.github.io/trello-attachments/#/login

See also

• Temperos

@ 3bf0c63f:aefa459d

A prediction market as a distributed set of oracle federations

See also: Truthcoin as a spacechain.

This is not Truthcoin, but hopefully the essence of what makes it good is present here: permissionless, uncensorable prediction markets for fun, profit, making cheap talk expensive and revolutionizing the emergence and diffusion of knowledge in society.

The idea

The idea is just to reuse Fedimint's codebase to implement federated oracle corporations that will host individual prediction markets inside them.

Pegging in and out of a federation can be done through Lightning gateways, and once inside the federation users can buy and sell shares of individual markets using a native LMSR market-maker.

Then we make a decentralized directory of these bets using something simple like Nostr so everybody can just join any market very easily.

Why?

The premise of this idea is that we can't have a centralized prediction market platform because governments will shut it down, but we can instead have a pseudonymous oracle corporation that also holds the funds being gambled at each time in a multisig Bitcoin wallet and hope for the best.

Each corporation may exist to host a single market and then vanish afterwards -- its members returning later to form a new corporation and host a new market before leaving again.

There is custodial risk, but the fact that the members may accrue reputation as the time passes and that this is not one big giant multisig holding all the funds of everybody but one multisig for each market makes it so this is slightly better.

In any case, no massive amounts are expected to be used in this scheme, which defeats some of the use cases of prediction markets (funding public goods, for example), but since these are so advanced and society is not yet ready for them, we can leave them for later and first just try to get some sports betting working.

This proto-truthcoin implementation should work just well enough to increase the appetite of bitcoiners and society in general for more powerful prediction markets.

Why is this better than DLCs?

Because DLCs have no liquidity. In their current implementations and in all future plans from DLC enthusiasts they don't even have order books. They're not seen very much as general-purpose prediction markets, but mostly as a way to create monetary instruments and derivatives.

They could work as prediction markets, but then they would need order books and order books are terrible for liquidity. LMSR market makers are much better.

But it is custodial!

If you make a public order book tied to known oracles using a DLC the oracle may also be considered custodial since it becomes really easy for him to join multiple trades as a counterpart then lie and steal the money. The bets only really "discreet" if they're illiquid meaningless bets between two guys. If they're happening in a well-known public place they're not discreet anymore.

DLC proponents may say this can be improved by users using multiple oracles and forming effectively a federation between them, but that is hardly different from choosing a reputable oracle corporation in this scheme and trusting that for the life of the bet.

But Hivemind is better!

Yes.

@ dbe0605a:f8fd5b2c

Nostr for The Great Orchestra of Christmas Charity

This Sunday, 28.01.2024 at 18:00 - 19:00 UTC we're inviting you to take pare in a very unique #zapathon

Nostrians taking part in this special zapathon that will play in tune with thousands of people playing together with The Great Orchestra of Christmas Charity on their 32nd Grand Finale! Hence the name #orchestrathon

The goal of #orchestrathon is to support the goal of this years Grand Finale, which is: funding equipment for diagnosing, monitoring and rehabilitating lung diseases of patients in pulmonology wards for children and adults in Poland

That means all bitcoin from zaps will be converted to PLN and donated to The Great of Christmas Charity foundation.

What's The Great Orchestra of Christmas Charity? What is the 32nd Grand Finale?! You'll find all of those answers on Geyser project story, or a few paragraphs below 👇 Now coming back to #orchestrathon...

What Is #Orchestrathon

This Nostr account is a was generated on Geyser and is tied to Geyser project: Bitcoiners support The Great Orchestra of Christmas Charity

That means all zaps sent to this account are at the same time funding Geyser campaing.

So not only you will contribute to the goal in the project, also all the zap comments will be visable there.

Ain't that crazy? We can use this campaign as one giant #orchestrathon client!

Rules are simple:

1. On Sunday at 18.00 - 19.00 we all connect to our relays to join the #orchestrathon
2. For the whole hour - you can zap this profile, our posts or comments as crazy!
3. At 19.00 it's culmination of both #orchestrathon and Grand Finale

All Nostrians who zap will receive special badges, depending on the zapped amount (in total):

On Sunday there will be lot's of concerts and events happening all day, culminating with Grand Finale closing at 19.00. We will try to launch a stream on zap.stream, so we can enjoy Grand Finale and concerts together!

This #orchestrathon and Geyser fundraise is organised by Dwadzieścia Jeden, a community of polish Bitcoiners. More about us and Proof of Work in the project story 👇

We're not only Bitcoiners, are also Nostrians, follow us: Dwadzieścia Jeden account: @npub1cpmvpsqtzxl4px44dp4544xwgu0ryv2lscl3qexq42dfakuza02s4fsapc

Saunter: @npub1m0sxqk5uwvtjhtt4yw3j0v3k6402fd35aq8832gp8kmer78atvkq9vgcru

Fmar: @npub1xpuz4qerklyck9evtg40wgrthq5rce2mumwuuygnxcg6q02lz9ms275ams

JesterHodl: @npub18s59mqct7se3xkhxr3epkagvuydwtvhpsacj67shrta8eknynegqttz5c3

Tomek K: @npub14wxtsrj7g2jugh70pfkzjln43vgn4p7655pgky9j9w9d75u465pqvagcye

Tom Chojnacki: @npub1m0sxqk5uwvtjhtt4yw3j0v3k6402fd35aq8832gp8kmer78atvkq9vgcru

Gracjan Pietras: @npub1trkudtnp7jg3tmy4sz8mepmgs5wdxk9x2esgts25mgkyecrse7js6ptss5

Tomek Waszczyk @npub1ah8phwmfyl2lakr23kt95kea3yavpt4m3cvppawuwkatllnrm4eqtuwdmk

Original Geyser project story

Saving Lives and Preserving Health

Dwadzieścia Jeden a polish node in decentralised bitcoin communities network Twenty One, is proud to facilitate bitcoin fundraising for the biggest, non-governmental, non-profit, charity in Poland — The Great Orchestra of Christmas Charity.

For the past 31 years, GOCC continuously fundraises money for pediatric and elderly care in Poland. Each year, a culmination of the raise occurs during the last Sunday of January in the shape of The Grand Finale — a joyful day that when tens of thousands volunteers worldwide, especially kids and teenagers, go on the streets to gather money for the cause, giving donors hear-shaped stickers with logo of the foundation. If you're in Poland on that day, basically every person you'll meet on the street will proudly wear GOCC heart.

The same hear-shaped stickers can be seen in every hospital in Poland on thousands of high quality medical equipment bought by The Great Orchestra. There is not a single polish family that hasn't benefited in some way from this equipment, and it saved thousands of lives, especially the little ones.

32nd Grand Finale Goal

This year, 32rd Grand Finale will take place on 28th of January. The aim of the 32nd Grand Finale is post-pandemic lung diseases — the raised funds will be used to purchase equipment for children's and adults' respiratory units.

The Foundation plans to purchase:

• equipment for diagnostic imaging, i.a. MRI and ultrasound equipment,

• equipment for functional diagnosis, i.a. polysomnographs and portable spirometers,

• equipment for endoscopic diagnosis, i.a. navigational bronchoscopy systems and bronchoscopes

• equipment for rehabilitation - equipment for pulmonary rehabilitation used in the treatment of patients after lung transplantation

• equipment for thoracic surgery, e.g. electrocoagulation systems and cryoprobes.

The Great Orchestra of Proof of Work

• 31 years of non-stop fundraising for state-of-the-art saving life equipment, running medical and educational programmes and humanitarian aid

• 2 billion PLN or ~11,781 BTC raised in total

• Areas of help: children's cardiac surgery, oncology, geriatrics, neonatology, children's nephrology, children's and young people's mental health services, ambulances for children's hospitals, volunteer firefighters & search & rescue units

• Last year Grand Finale raised over PLN 240 million (1,410 BTC) for a goal to fight sepsis

• You can check how money from 2022 report (224 376 706 PLN or ~1,321.69 BTC) raise were spent here (although it's in polish)

• In addition to work focused on Poland, GOCC fundraised money for hospitals in Ukraine and provided substantial humanitarian aid for Ukrainian refugees, Polish-Belarusian border crisis, Turkey earthquake victims and more

• GOCC is the most-trusted Polish organization and is at the top of the list as the most trusted public entities in Poland

What We'll Do With Gathered Funds

Gathered bitcoin will be converted to PLN by a polish exchange Quark and donated to The Great Orchestra of Christmas Charity after The Grand Finale which takes place on January 28th.

Dwadzieścia Jeden Proof of Work

We're a group of polish pleb Bitcoiners that started organising ourselves about 2 years ago.

Our activities include:

• organising regular bitcoin meetups in several cities in Poland, also Nostr meetup in Warsaw

• organising Bitcoin FilmFest and European Halving Party in Warsaw

• orangepilling and maintaining map of polish bitcoin merchants in Poland on btcmap.org

• translating bitcoin FOSS to polish language

• writing and translating articles to polish

• giving talks on bitcoin

• volounteering for helping with bitcoin payments and running bitcoin workshops on non-conferences (eg. Weekend of Capitalism)

• working in human rights centered NGOs and promoting bitcoin as a tool for protecting human rights

• ...and we're just starting!

Find Out More

• Official GOCC website

• Wikipedia page about GOCC

Gallery

@ 3cd2ea88:bafdaceb

🚨 Entra su CandyBomb, la piattaforma di airdrop di Bitget, e preparati a immergerti in un mondo di opportunità per guadagnare AVA, il token di Travala. Ecco come partecipare e vincere:

🚨 1. Trading Spot Coinvolgente: Effettua emozionanti operazioni di trading Spot di AVA e accumula biglietti per il Pool di Trading Spot. Ogni trade ti avvicina a guadagnare la tua parte dei 30.000 AVA messi in palio.

🚨 2. Depositi Netti Vincenti: Fai crescere il tuo tesoro personale con depositi netti di AVA. Ogni deposito ti avvicina al Pool di Depositi Netti, dove sono pronti ad assegnare 3.333 AVA a chiunque dimostri il suo impegno.

🚨 3. Totale del Bottino: 33.333 AVA! Concludi attività di trading e depositi netti per guadagnare biglietti e competere per una parte del ricco totale di 33.333 AVA.

🚨 Partecipa e Vinci: Il periodo di questa incredibile promozione è dal 24 gennaio alle 12:00 al 31 gennaio alle 12:00 (UTC+1). Non perdere l'opportunità di accumulare AVA e godere dei vantaggi sulla piattaforma Travala.

🚨 Sii parte della rivoluzione del trading e delle criptovalute con Bitget e Travala. Non aspettare, inizia a fare trading e a depositare ora!

🚨 E con il Referral 6w5d, il 10% di sconto sulle fee a vita!

@ 3bf0c63f:aefa459d

GraphQL vs REST

Today I saw this: https://github.com/stickfigure/blog/wiki/How-to-(and-how-not-to)-design-REST-APIs

And it reminded me why GraphQL is so much better.

It has also reminded me why HTTP is so confusing and awful as a protocol, especially as a protocol for structured data APIs, with all its status codes and headers and bodies and querystrings and content-types -- but let's not talk about that for now.

People complain about GraphQL being great for frontend developers and bad for backend developers, but I don't know who are these people that apparently love reading guides like the one above of how to properly construct ad-hoc path routers, decide how to properly build the JSON, what to include and in which circumstance, what status codes and headers to use, all without having any idea of what the frontend or the API consumer will want to do with their data.

It is a much less stressful environment that one in which we can just actually perform the task and fit the data in a preexistent schema with types and a structure that we don't have to decide again and again while anticipating with very incomplete knowledge the usage of an extraneous person -- i.e., an environment with GraphQL, or something like GraphQL.

By the way, I know there are some people that say that these HTTP JSON APIs are not the real REST, but that is irrelevant for now.

@ 32e18276:5c68e245

I thought it might be interesting to do a quick technical writeup of nostrdb and the new nostrdb profile searching. This is the first text search index within nostrdb, if you're interested in the nitty gritty details of things, this article is for you!

For the most part, nostrdb has been a copy of the design of strfry, in terms of its indices and multi-process architecture. strfry doesn't support search (yet), so this is a novel feature of nostrdb. What is strfry? If it weren't for strfry, nostr wouldn't work. It is simply the best way to implement a nostr database and relay. SQL servers are just too slow to serve dynamic queries at scale.

I wanted something like strfry that I could embed into native nostr clients like Damus, this is how nostrdb was born!

First, let's look at how nostrdb at a high level.

nostrdb

nostrdb is an embedded library for native nostr clients. It uses the Lightning-mapped database (LMDB) for very efficient querying. This allows it to skip SQL query parsing and query planning. We don't really need all that with nostr. nostr search filters are a bit more restrictive, so we can build custom indices for the most common nostr queries. This is a huge win CPU-wise, nostr queries can be very dynamic, and skipping the query parsing and planning saves CPU and battery.

Before we get into any of that, let's look at how you would use the library from the highest level. The entrypoint for notes in nostrdb is the ndb_process_event function. When you receive nostr events from another relay, this function is called for each event.

Event processing

ndb_process_event('["EVENT","subid",{kind:1, ...}]')

We begin by queueing the event for processing in the multi-threaded ingester. This allows it to return immediately and not block the client.

The ingester is multi-threaded because validating note signatures can be pretty slow. We want note processing to be as quick as possible so nostrdb doesn't have a bottleneck here.

nostrdb is very smart about not burning CPU when it doesn't need to. The custom json parser will stop when it finds the note ID field, lookup that note in the database to see if we already have it, and then stop JSON parsing if we do. This saves CPU for large notes like contact lists, and skips the need to re-validate the signature as well. Even strfry doesn't make this optimization, so nostrdb has a speed, cpu, and battery life advantage here.

During the processing step, nostrdb will detect different note types such as profile metadata. It will look at the name and display_name field and add a custom index for searching user profiles. Since keys in LMDB are lexicographically sorted and support range queries, our profile search indices is simply (name + pubkey + created_at). This allows you to do a ranged key-lookup on "jb" and it will position the db cursor to the first record that starts with jb. LMDB uses a b+ tree, this is not a linear scan, so it is very fast! Eventually this index will be used for implementing nip-50 search on the nostrdb relay interface, which is coming sometime in the future.

Once we're done writing the indices and validating the note, we store nostr notes in a custom, compact binary format that is easy to access directly in memory from any programming language. We also do this with profile records by leveraging flatbuffers.

So in the end, what does this achieve? It enables you to store as much nostr data as you want with near zero query and serialization overhead. Since the data stored in nostrdb is just flatbuffers, you can access data directly from the operating system's page cache (just a pointer to memory) and from any programming language via flatbuffer's schema and codegen tools. It's so fast it will be guaranteed once of the fastest things in your codebase. You can even run it in your main UI thread so you can worry about other things such as UX and design without introducing complex async logic in your user interface.

What's next

nostrdb is already partially integrated into Damus iOS. Damus uses nostrdb's compact note format for storing notes in memory, but eventually everything will be switched to use nostrdb directly. The next version of Damus testflight will remove the in-memory and core-data profile cache and switch to nostrdb profiles. Damus currently has a complex in-memory trie data structure for profile searches, but it only knows about profiles it has seen during the current session. This is a common source of confusion, sometimes Damus doesn't auto-complete profiles it has already seen sometime in the past. nostrdb profile searches will allow @ mentions and user search to find every profile it has ever seen in realtime. This will be a huge usability win for Damus and other clients looking to adopt nostrdb.

Right now nostrdb exposes its functionality via direct function calls: ndb_get_profile, etc. The plan is that most of these calls won't be necessary. Once nostrdb has nostr filter parsing, it will be able to support dynamic queries of the kind you would expect from your typical nostr relay. This will turn nostrdb-powered clients into relays themselves.

Once nostrdb is more relay-like, then we will be able to leverage strfry's negentropy set-reconciliation queries to only fetch notes that we don't already have. This will be insanely useful for reducing bandwidth usage when querying strfry relays. Eventually it may make the most sense to just let nostrdb do all the websocket querying behind the scenes, becoming a kind of local multiplexing relay.

The future of nostrdb is very exciting. I plan on using it in Damus NoteDeck and Damus Android, why duplicate all this work in every client? nostrdb will make developing native clients much easier.

Support

Damus and nostrdb are mainly supported by donations. nostrdb is open source, MIT-licensed. Damus is GPL. We are dedicated to building the best and most free open source tech on nostr. If you would like to support our work, please consider buying our merch !

Thanks for getting this far! Until next time...

@ 3f770d65:7a745b24

For Bitcoin enthusiasts seeking a haven for like-minded individuals and a chance to experience Bitcoin adoption in its purest form, El Salvador and Bitcoin Beach often come to mind. This is no coincidence, given El Salvador's pioneering role in making bitcoin legal tender. However, the Bitcoin ecosystem extends beyond national borders, with vibrant communities emerging around the world where bitcoin thrives in everyday transactions. One such example is the inspiring grassroots movement of Bitcoin Jungle in rural Costa Rica. Driven by a shared passion for Bitcoin and the "pura vida" spirit, a group of Bitcoiners has established a thriving community centered on a circular Bitcoin economy. This is the essence of Bitcoin Jungle.

https://i.nostr.build/DkD9.jpg

What is Bitcoin Jungle?

Bitcoin Jungle is an open-source community project focused on bringing the Bitcoin ecosystem to life in Costa Rica, particularly in the "Golden Triangle" area – Dominical, Uvita, Ojochal, Platanillo, and Tinamaste. Their mission is to build a circular bitcoin economy and a thriving community centered around bitcoin.

Focus:

• Bitcoin adoption: Encourage businesses and individuals to accept and use bitcoin as a form of payment.
• Education and resources: Provide educational materials and resources about Bitcoin and the Lightning Network to both businesses and individuals.
• Community building: Create a strong and supportive community of Bitcoin enthusiasts in Costa Rica.
• Boost to local economy: Increased tourist and resident spending through Bitcoin adoption to benefit local businesses.
• Financial inclusion: Bitcoin's borderless nature and ease of use offers financial inclusion for unbanked or underbanked populations.

Achievements:

• Bitcoin Jungle app: Developed a mobile wallet app built on the Bitcoin Lightning Network, facilitating easy bitcoin transactions within the community for both Android and iOS.
• Business adoption: Helped over 250 businesses in the "Golden Triangle" accept Bitcoin payments.
• Map and directory: Created a map and directory showcasing businesses accepting bitcoin in the area.
• Grassroots movement: Established a strong community identity around bitcoin and "pura vida" values.
• Integrate Sinpe: Allow sending of bitcoin payments to 90% of the Costa Rican population, both individuals and businesses.

Who's behind Bitcoin Jungle?

https://i.nostr.build/jDWV.jpg

The success of Bitcoin Jungle can be attributed to the convergence of two crucial drivers: passionate Bitcoin enthusiasts and skilled community leaders. Each individual, attracted by the unique allure of the "Golden Triangle" in Costa Rica, brought their diverse skillsets and collective ambition to the table, resulting in this organically developed and thriving hub of Bitcoin adoption. These skillsets ranging from technical, to personal, to community outreach, to spiritual and more, are a synergistic blend of expertise and shared vision, serving as the foundational layer for Bitcoin Jungle's continued progress.

Bitcoin Freedom Festival

Building upon the momentum of their inaugural Nostr unconference held at Awake in Uvita, Costa Rica, in March 2023, Bitcoin Jungle successfully hosted their first Bitcoin conference, the Bitcoin Freedom Festival, last week at the same venue. This conference took place during January 18-21, 2024, bringing together Bitcoiners and like minded, freedom loving folks from across the world.

The inaugural Bitcoin Freedom Festival, hosted by Bitcoin Jungle, offered a diverse and engaging lineup for attendees. Participants delved into the world of Bitcoin through a variety of talks, panels, and workshops catering to both technical and non-technical audiences. Attendees engaged in interactive sessions on building sustainable Bitcoin economies, fostering inclusivity within the ecosystem, and navigating the legal landscape of Bitcoin businesses. Speakers explored the potential of Bitcoin beyond finance, delving into its impact on social change, environmental sustainability, and spiritual connections. Beyond Bitcoin related themes, attendees were graced with various cultural sessions and ceremonies from local indigenous tribes and family-friendly events such as fruit tasting, hot chocolate creation, and hula hooping. For those that wanted to add decentralized communication talks to their schedule, attendees joined a Nostr panel hosted by yours truly along with several other Nostriches.

https://i.nostr.build/oJzl.jpg

Awake describes themselves as "a catalyst for humanity's awakening, celebrating life and serving as a community, retreat center, and hub for individual and collective growth" or the spiritual arm of Bitcoin's ethos, connecting human's together and to nature. Awake is essentially a Bitcoin Citadel.

Bitcoin transcends the function of a mere currency to symbolize the primal layer of existence that harmonizes our myriad experiences. It illuminates our collective path, encouraging truth, integrity, and unity, as we rise above the inner and outer forces that have historically suppressed the individual and humanity.

It seems poetic and fitting that Awake is located in the heart of Bitcoin Jungle, their co-founder Govinda, is also one of the founding members of Bitcoin Jungle, and Awake hosted both Nostrica and the Bitcoin Freedom Festival.

Bitcoin Marketplace

Beyond the conversations of conferences and networking opportunities, the Bitcoin Freedom Festival offered a taste of the future with its bustling Bitcoin Marketplace. This dedicated area brought together dozens of local merchants and vendors from the neighboring Bitcoin farmers' market, showcasing the possibilities of Bitcoin in everyday life. HODLing bitcoin is cool, but the real super power unlocks when you spend your bitcoin for everyday goods.

From delicious tropical fruits and local treats to handcrafted snacks, clothing, jewelry, artwork, and trinkets, the vendors represented the early adopters of Bitcoin Jungle's initiative. In collaboration with Bitcoin Jungle, each vendor utilized a compact mobile Point of Sale system powered by BTCPay server. These user-friendly devices, complete with thermal receipt printers, empowered vendors to seamlessly accept bitcoin payments, directly deposited to their Bitcoin Jungle wallets.

https://i.nostr.build/J7aP.jpg

This wasn't just a marketplace; it was a living, breathing testament to the growing acceptance of bitcoin within the local community. Attendees could witness firsthand the ease and convenience of using bitcoin for everyday purchases. The atmosphere buzzed with a sense of shared purpose and enthusiasm as vendors and customers alike embraced the innovative power of Bitcoin. From buying the freshest mango from a local farmer to picking up a unique handcrafted souvenir, participants experienced the thrill of being part of a pioneering community actively shaping a new economic landscape, all from within the Costa Rican jungle.

Where can you spend Bitcoin in Costa Rica?

https://i.nostr.build/MrM5.png

Bitcoin adoption in Costa Rica extends beyond the "Golden Triangle", encompassing over 250 locations spread across the country. While the densest concentration lies within Uvita, the beating heart of Bitcoin Jungle, businesses accepting Bitcoin can be found throughout the nation.

These locations are conveniently accessible on the Bitcoin Jungle map, both within the mobile app and on their website. You may browse Bitcoin Jungle's interactive map to discover various businesses and locations that accept bitcoin, searching by category and location.

https://i.nostr.build/9n9G.png

Rest assured, you won't be scrambling for mobile reception in most cities and towns. For example, Uvita and Dominical boast excellent mobile coverage with major carriers like Claro blanketing the area, providing your mobile bitcoin transactions the bandwidth they need. While mobile data is readily available, many cafes, restaurants, and shops in both towns offer free Wi-Fi for even greater connectivity. This connectivity extends across most of Costa Rica too, with many local businesses boasting high speed fiber connections.

If you happen to visit a business that isn't directly using the Bitcoin Jungle app or accepting bitcoin, there's a high probability that they're using Sinpe. This will indirectly allow you to spend your bitcoin virtually anywhere in Costa Rica.

What is Sinpe Movil?

Sinpe serves as the backbone of Costa Rican mobile payments, enabling instant transfers between bank accounts, individuals, and certain businesses. With an impressive 90% penetration rate, Sinpe has become the dominant payment method for everyday transactions.

https://i.nostr.build/2WO5.png

Thanks to Bull Bitcoin, the Bitcoin Jungle app now supports Sinpe, allowing you to convert your bitcoin into Costa Rican colones directly within the Sinpe network. This means you can seamlessly top up your Sinpe wallet with bitcoin or send bitcoin to an existing Sinpe wallet, effectively spending bitcoin and having it being converted to fiat for the local merchant on the fly.

Do you need the Bitcoin Jungle app?

The short answer: No! You can use whatever you want!

When it comes to spending your Bitcoin in Costa Rica, you have two primary options: utilizing the Sinpe mobile payment system through the Bitcoin Jungle app, or conducting direct Lightning Network transactions at participating businesses.

https://i.nostr.build/Z6V9.jpg

• Over 250 locations in Costa Rica accept Bitcoin payments directly through the Lightning Network. Here, you can utilize your preferred Bitcoin Lightning wallet for seamless and instant transactions.
• The Bitcoin Jungle app is required if you want to convert your bitcoin to colones and utilize them within the Sinpe network. This opens up a wider range of spending options throughout Costa Rica, as Sinpe boasts a 90% penetration rate.

Not everyone will be able to install the Bitcoin Jungle application. For example, if you are visiting Costa Rica from the USA, with a USA phone, there's a high probability that you will not be able to install the Bitcoin Jungle application via Google Play Store or Apple App Store due to region locking. You may have to manually install the Android APK or join Apple's TestFlight program.

https://i.nostr.build/0lOv.png

While the Bitcoin Jungle app offers a convenient gateway for spending bitcoin with Sinpe in Costa Rica, its requirement for mobile phone number registration might deter some privacy-conscious users, particularly experienced Bitcoiners accustomed to self-custody solutions. Fortunately, for those seeking a purely pseudonymous experience, an array of robust mobile Lightning wallets exist and all work as expected.

Personal Experiences

My wife and I first explored Bitcoin Jungle in March 2023, witnessing the early stages of Bitcoin adoption. Now, upon my return for the Bitcoin Freedom Festival, I was astounded to find the number of accepting businesses almost doubled. This remarkable growth, directly attributed to the previous "Nostrica Unconference" with its near 300 Bitcoin enthusiasts, fuels my optimism for an even greater surge following this recent event. Witnessing firsthand the enthusiastic response of local merchants reaffirms my belief in Bitcoin.

https://i.nostr.build/Z6Bx.jpg

This trip, eager to share this experience with family, I brought my wife and children, armed with four Bitcoin Lightning wallets connected to my Lightning node at home. We embarked on a family vacation, using the Lightning Network exclusively for day-to-day purchases from breakfast treats to souvenirs. From coffee for my wife and pipa fria for my son to fresh fruit for my daughter and delicious meals for all of us, each transaction was seamless and effortless. This culminated in a memorable visit to Seba's, Uvita's premier restaurant, where we enjoyed both food and adult beverages – all paid for with bitcoin.

https://i.nostr.build/4lz4.jpg

This experience wasn't just about personal convenience; it was a testament to the growing acceptance and integration of bitcoin within the local community. Witnessing how families, from coffee shops to fine dining, can seamlessly operate, empowers me to envision a future where Bitcoin flourishes.

https://i.nostr.build/4lxL.jpg

Reaching Bitcoin Jungle involves some planning due to its distance from San Jose Airport. The journey takes approximately 3.5-4 hours by car, offering the most flexibility for exploring the region, attending excursions, and maximizing your itinerary. Car rentals are readily available, though ride-sharing, buses, and even small plane flights are alternative options, depending on your budget and preferences. While Uvita's downtown area features walkable access to many amenities, having a rental vehicle is recommended for exploring the full scope of the Golden Triangle's attractions. For example, my family visited jungle canopy zip lines, jungle cacao tours, waterfalls, and multiple beaches.

Conclusions

Bitcoin Jungle is a successful community-driven, grassroots project, showcasing the potential of Bitcoin adoption and integration beyond El Salvador. We often hear about Bitcoin Beach or how El Salvador is "Bitcoin Country", but I'd wager that Bitcoin adoption is on par or even higher with local merchants in Bitcoin Jungle.

Bitcoin Jungle is a beautiful paradise showcasing freedom at every corner, allowing you to spend bitcoin at nearly every corner. If you're a Bitcoiner seeking a vibrant, welcoming community and a real-world Bitcoin experience, look no further than Bitcoin Jungle. I highly recommend it. Pura vida!

https://i.nostr.build/Qr2v.jpg

@ c8df6ae8:22293a06

"Each proposal must be weighed in the light of a broader consideration: the need to maintain balance in and among national programs, balance between the private and the public economy, balance between the cost and hoped for advantages, balance between the clearly necessary and the comfortably desirable, balance between our essential requirements as a nation and the duties imposed by the nation upon the individual, balance between actions of the moment and the national welfare of the future."

— President Eisenhower

63 years ago, President Eisenhower, gave a stern warning to the nation on his farewell address. He specifically identified two threats to the American society: - We must guard against the acquisition of unwarranted influence, whether sought or unsought, by the military-industrial complex. - Public policy could itself become the captive of a scientific-technological elite.

Every American should listen to Eisenhower's warning words. Every school should teach its students this address. But they don't.

The nation didn't listen and his fears have fully materialized. The military-industrial complex owns the Federal budget and the food, healthcare, and pharmaceutical industries control the regulatory agencies for their benefit.

---

The speech

Good evening, my fellow Americans.

First, I should like to express my gratitude to the radio and television networks for the opportunities they have given me over the years to bring reports and messages to our nation. My special thanks go to them for the opportunity of addressing you this evening.

Three days from now, after half century in the service of our country, I shall lay down the responsibilities of office as, in traditional and solemn ceremony, the authority of the Presidency is vested in my successor. This evening, I come to you with a message of leave-taking and farewell, and to share a few final thoughts with you, my countrymen.

Like every other -- Like every other citizen, I wish the new President, and all who will labor with him, Godspeed. I pray that the coming years will be blessed with peace and prosperity for all.

Our people expect their President and the Congress to find essential agreement on issues of great moment, the wise resolution of which will better shape the future of the nation. My own relations with the Congress, which began on a remote and tenuous basis when, long ago, a member of the Senate appointed me to West Point, have since ranged to the intimate during the war and immediate post-war period, and finally to the mutually interdependent during these past eight years. In this final relationship, the Congress and the Administration have, on most vital issues, cooperated well, to serve the nation good, rather than mere partisanship, and so have assured that the business of the nation should go forward. So, my official relationship with the Congress ends in a feeling -- on my part -- of gratitude that we have been able to do so much together.

We now stand ten years past the midpoint of a century that has witnessed four major wars among great nations. Three of these involved our own country. Despite these holocausts, America is today the strongest, the most influential, and most productive nation in the world. Understandably proud of this pre-eminence, we yet realize that America's leadership and prestige depend, not merely upon our unmatched material progress, riches, and military strength, but on how we use our power in the interests of world peace and human betterment.

Throughout America's adventure in free government, our basic purposes have been to keep the peace, to foster progress in human achievement, and to enhance liberty, dignity, and integrity among peoples and among nations. To strive for less would be unworthy of a free and religious people. Any failure traceable to arrogance, or our lack of comprehension, or readiness to sacrifice would inflict upon us grievous hurt, both at home and abroad.

Progress toward these noble goals is persistently threatened by the conflict now engulfing the world. It commands our whole attention, absorbs our very beings. We face a hostile ideology global in scope, atheistic in character, ruthless in purpose, and insidious in method. Unhappily, the danger it poses promises to be of indefinite duration. To meet it successfully, there is called for, not so much the emotional and transitory sacrifices of crisis, but rather those which enable us to carry forward steadily, surely, and without complaint the burdens of a prolonged and complex struggle with liberty the stake. Only thus shall we remain, despite every provocation, on our charted course toward permanent peace and human betterment.

Crises there will continue to be. In meeting them, whether foreign or domestic, great or small, there is a recurring temptation to feel that some spectacular and costly action could become the miraculous solution to all current difficulties: a huge increase in newer elements of our defenses; development of unrealistic programs to cure every ill in agriculture; a dramatic expansion in basic and applied research. These and many other possibilities, each possibly promising in itself, may be suggested as the only way to the road we wish to travel.

But each proposal must be weighed in the light of a broader consideration: the need to maintain balance in and among national programs, balance between the private and the public economy, balance between the cost and hoped for advantages, balance between the clearly necessary and the comfortably desirable, balance between our essential requirements as a nation and the duties imposed by the nation upon the individual, balance between actions of the moment and the national welfare of the future. Good judgment seeks balance and progress. Lack of it eventually finds imbalance and frustration. The record of many decades stands as proof that our people and their Government have, in the main, understood these truths and have responded to them well, in the face of threat and stress.

But threats, new in kind or degree, constantly arise. Of these, I mention two only.

A vital element in keeping the peace is our military establishment. Our arms must be mighty, ready for instant action, so that no potential aggressor may be tempted to risk his own destruction. Our military organization today bears little relation to that known of any of my predecessors in peacetime, or, indeed, by the fighting men of World War II or Korea.

Until the latest of our world conflicts, the United States had no armaments industry. American makers of plowshares could, with time and as required, make swords as well. But we can no longer risk emergency improvisation of national defense. We have been compelled to create a permanent armaments industry of vast proportions. Added to this, three and a half million men and women are directly engaged in the defense establishment. We annually spend on military security alone more than the net income of all United States corporations.

Now this conjunction of an immense military establishment and a large arms industry is new in the American experience. The total influence -- economic, political, even spiritual -- is felt in every city, every Statehouse, every office of the Federal government. We recognize the imperative need for this development. Yet, we must not fail to comprehend its grave implications. Our toil, resources, and livelihood are all involved. So is the very structure of our society.

In the councils of government, we must guard against the acquisition of unwarranted influence, whether sought or unsought, by the military-industrial complex. The potential for the disastrous rise of misplaced power exists and will persist. We must never let the weight of this combination endanger our liberties or democratic processes. We should take nothing for granted. Only an alert and knowledgeable citizenry can compel the proper meshing of the huge industrial and military machinery of defense with our peaceful methods and goals, so that security and liberty may prosper together.

Akin to, and largely responsible for the sweeping changes in our industrial-military posture, has been the technological revolution during recent decades. In this revolution, research has become central; it also becomes more formalized, complex, and costly. A steadily increasing share is conducted for, by, or at the direction of, the Federal government.

Today, the solitary inventor, tinkering in his shop, has been overshadowed by task forces of scientists in laboratories and testing fields. In the same fashion, the free university, historically the fountainhead of free ideas and scientific discovery, has experienced a revolution in the conduct of research. Partly because of the huge costs involved, a government contract becomes virtually a substitute for intellectual curiosity. For every old blackboard there are now hundreds of new electronic computers. The prospect of domination of the nation's scholars by Federal employment, project allocations, and the power of money is ever present -- and is gravely to be regarded.

Yet, in holding scientific research and discovery in respect, as we should, we must also be alert to the equal and opposite danger that public policy could itself become the captive of a scientific-technological elite.

It is the task of statesmanship to mold, to balance, and to integrate these and other forces, new and old, within the principles of our democratic system -- ever aiming toward the supreme goals of our free society.

Another factor in maintaining balance involves the element of time. As we peer into society's future, we -- you and I, and our government -- must avoid the impulse to live only for today, plundering for our own ease and convenience the precious resources of tomorrow. We cannot mortgage the material assets of our grandchildren without risking the loss also of their political and spiritual heritage. We want democracy to survive for all generations to come, not to become the insolvent phantom of tomorrow.

During the long lane of the history yet to be written, America knows that this world of ours, ever growing smaller, must avoid becoming a community of dreadful fear and hate, and be, instead, a proud confederation of mutual trust and respect. Such a confederation must be one of equals. The weakest must come to the conference table with the same confidence as do we, protected as we are by our moral, economic, and military strength. That table, though scarred by many past frustrations -- past frustrations, cannot be abandoned for the certain agony of disarmament -- of the battlefield.

Disarmament, with mutual honor and confidence, is a continuing imperative. Together we must learn how to compose differences, not with arms, but with intellect and decent purpose. Because this need is so sharp and apparent, I confess that I lay down my official responsibilities in this field with a definite sense of disappointment. As one who has witnessed the horror and the lingering sadness of war, as one who knows that another war could utterly destroy this civilization which has been so slowly and painfully built over thousands of years, I wish I could say tonight that a lasting peace is in sight.

Happily, I can say that war has been avoided. Steady progress toward our ultimate goal has been made. But so much remains to be done. As a private citizen, I shall never cease to do what little I can to help the world advance along that road.

So, in this, my last good night to you as your President, I thank you for the many opportunities you have given me for public service in war and in peace. I trust in that -- in that -- in that service you find some things worthy. As for the rest of it, I know you will find ways to improve performance in the future.

You and I, my fellow citizens, need to be strong in our faith that all nations, under God, will reach the goal of peace with justice. May we be ever unswerving in devotion to principle, confident but humble with power, diligent in pursuit of the Nations' great goals.

To all the peoples of the world, I once more give expression to America's prayerful and continuing aspiration: We pray that peoples of all faiths, all races, all nations, may have their great human needs satisfied; that those now denied opportunity shall come to enjoy it to the full; that all who yearn for freedom may experience its few spiritual blessings. Those who have freedom will understand, also, its heavy responsibility; that all who are insensitive to the needs of others will learn charity; and that the sources -- scourges of poverty, disease, and ignorance will be made to disappear from the earth; and that in the goodness of time, all peoples will come to live together in a peace guaranteed by the binding force of mutual respect and love.

Now, on Friday noon, I am to become a private citizen. I am proud to do so. I look forward to it.

Thank you, and good night.

---

Notable notes

nostr:note1rv8es4utkz9l7ql0q6kye6ug8c4kcf23rwyagxz6j2w2gm7kdgasqa72th

---

Recommendations

Alex Gladstein

Bitcoin is a human right and Alex is busy showing people why.

You can follow him here

---

What did you think of today's newsletter?

Your feedback helps me create the best newsletter possible for you.

Please leave a comment and checkout comments from other subscribers and readers. I love hearing from the Bitcoin For Families community ❤️ 🙏🏻

---

See you again next week! — Alejandro

This newsletter is for educational purposes. It does not represent financial advice. Do your own research before buying Bitcoin.

@ d4338b7c:f1d23a5b

Chef's notes

Similar to a traditional Manhattan. The specs remain the same 2:1 Rye Whiskey to Sweet Vermouth. Except we are supplementing the vermouth out for Averna.

Details

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

Ingredients

• Rye
• averna
• angostura bitters
• orange bitters

Directions

1. add ingredients to a mixing glass
2. add large cubes
3. stir for 45 seconds
4. serve up in a coupe
5. skewered luxardo cherry garnish
6. cheeers

@ 3bf0c63f:aefa459d

A flexibilidade da doutrina socialista

Os fatos da revolução russa mostram que Lênin e seus amigos bolcheviques não eram só psicopatas assassinos: eles realmente acreditavam que estavam fazendo o certo.

Talvez depois de um tempo o foco deles tenha mudado mais para o lado de se preocuparem menos com a vida e o bem-estar dos outros do que com eles mesmos, mas não houve uma mudança fundamental.

Ao mesmo tempo, a doutrina socialista na qual eles acreditavam era enormemente flexível, assim como a dos esquerdistas de hoje. É a mesma doutrina: uma coleção de slogans que pode ser adaptada para apoiar ou ir contra qualquer outra tese ou ação.

Me parece que a justificativa que eles encontraram para fazer tantas coisas claramente ruins vem dessas mesma flexibilidade. Os atos cruéis estavam todos justificados pela mesma coleção de slogans socialistas de sempre, apenas adaptados às circunstâncias.

Será que uma doutrina mais sólida se prestaria a essas atrocidades? Se concluirmos que a flexibilidade vem da mente e não da doutrina em si, sim, mas não acho que venha daí, porque é sempre o socialismo que é flexível, nunca nenhuma outra doutrina. Ou, na verdade, o socialismo é tão flexível que ele envolve e integra qualquer outra doutrina que seja minimamente compatível.

Talvez a flexibilidade esteja mesmo na mente, mas existe alguma relação entre a mente que desconhece a coerência e a lógica e a mente que se deixa atrair pelos slogans socialistas.

@ c5d54dd3:e4a3dfc6

We've all been been there, a channel gets closed, no-matter yet if it was a cooperative or force-closed, but somehow the close transaction hangs around and doesn't get confirmed. You want to clear the house, or need the pending onchain sats, but wonder how to go about it? Follow this guide and you'll hopefully find remedy.

But before, read this article from LND. Then read it again. Once you think you understand it, read it again. It's not super cohesive, since a number of things from the top need to be understood to grasp the section Channel closing, so ensure you spend some time in there.

Situation

This is written for LND, but similar methodologies are applicable for CLN. Eclair folks know their way around anyway. You identified a channel-close, either in one of the GUIs you use, or from a Bot notification. But it doesn't confirm. First thing to do is SSH into your node via ssh user@node-ip and get an overview of all pending (open, and close) with lncli pendingchannels[^1]. terminal { "channel": { "remote_node_pub": "123456789889786857463636288291929458767688493999392324", "channel_point": "dhksfkeh8458734kldjfksd39393932033fkk3003022244:1", "capacity": "10000000", "local_balance": "9999711", "remote_balance": "70137", "local_chan_reserve_sat": "10053", "remote_chan_reserve_sat": "10053", "initiator": "INITIATOR_REMOTE", "commitment_type": "ANCHORS", "num_forwarding_packages": "2", "chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator" }, "limbo_balance": "9999711", "commitments": { "local_txid": "eeof599490930002dcc0db3bfa789eb4afbd89a37794a4c49a5f529ddb1b23e85b3", "remote_txid": "ta48849fkkek39947uuc80371ec96a88297465821ee79ff0b85f8624f83a7455f1cc", "remote_pending_txid": "", "local_commit_fee_sat": "2510", "remote_commit_fee_sat": "2510", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "eeof599490930002dcc0db3bfa789eb4afbd89a37794a4c49a5f529ddb1b23e85b3" What we see here is that our LND sees that channel as borked, we have a an opening_tx (channel_point:vout), a local_tx and a remote_tx. What's usually the next step, we wonder why it's not closing, so we copy the "closing_txid": "eeof599490930002dcc0db3bfa789eb4afbd89a37794a4c49a5f529ddb1b23e85b3" and copy it into our favorite mempool tool. Just for guiding sake, we check with mempool.space, and now it's the time to split into two scenarios

Scenario 1: mempool.space shows the closing-tx, but it's unconfirmed and the fee is too low

What many runners don't know, mempool.space runs with a mempool-size of 2GB, while most standard node-systems run with just 300MB. This is usually enough, but not in high fee environments. So let's check if your local mempool has it: bitcoin-cli getrawtransaction eeof599490930002dcc0db3bfa789eb4afbd89a37794a4c49a5f529ddb1b23e85b3 error code: -5 error message: No such mempool or blockchain transaction. Use gettransaction for wallet transactions. In this case your mempool probably purged the transaction, or LND never published it due to it's low commitment fee. Let's jump to the next section to see what we can do about it.

Scenario 2: mempool.space shows Transaction not found

Okay, we can assume that your closing-tx probably never hit the public-mempool, we can cut things short here and move to the next section, but just to be safe, let's check if our local bitcoin-mempool has it bitcoin-cli getrawtransaction eeof599490930002dcc0db3bfa789eb4afbd89a37794a4c49a5f529ddb1b23e85b3 error code: -5 error message: No such mempool or blockchain transaction. Use gettransaction for wallet transactions.

Complication

Why are there transactions of channel-closes with too low fee? Can't LND figure out what fee is necessary and get things just out there? I want my funds! Well... and this is already way better than earlier last year

Let's assume best intend, no-one built that protocol to make things intentionally complicated. But since you have two parties involved in the process, and we should assume no-trust between those, we need to install processes to keep things fair, balanced and transparent. Read up on the HTLC-detail guide from Elle Mouton to make yourself more familiar with the details.

In short, we have 2 (out of 3) possible ways for a channel-close:

1. cooperative-close, where both parties are online, one of the two sends a channel-close signal, and then both nodes get to court and negotiate a closing price. Since only the opener pays for the closing-cost, it's imminent it's not sky high. There are settings in lnd.conf like coop-close-target-confs=100 which help to keep things rational from your side if the other side triggered the close.
2. force- or uncooperative-close, where either one of the two parties is unresponsive / offline, or other protocol / node-OS disagreements happen (like expiring HTLCs). In either case one of the two parties force-close, there is no court-negotiation, but based on the last channel_commit agreement the two nodes handshaken on, will be used for the closing-fee. Those agreements are also based on a few lnd.conf settings, like max-commit-fee-rate-anchors and bitcoind.estimatemode[^2].

Either have their intricacies, but when the channel-close is not in your local mempool, or too low fee in the public mempool, you can't get the channel closed and the onchain-sats stay locked away.

Proposed Solutions

We won't outline every possible scenario, but a couple of most happening ones. Some will work, others not. To avoid this article becoming a master-class, let's go through a couple of those which are doing no-harm, but helping you worse case to get some more information what's happening.

For each of those attempts, prepare a second terminal window to your node, and filter (grep) the channel-point and pubkey of the channel, so you'll be more informed after of what's happening. This terminal will monitor your lnd.log and show only entries where either the Pubkey of your to be closed channel-peer, or your mutual channel-point is triggered. sudo tail -f .lnd/logs/bitcoin/mainnet/lnd.log | grep -e 'PUBKEYOFCHANNELPARTNER|CHANNELPOINT:VOUT'

While Terminal 2 stays open, let's move to Terminal Window 1 for the next couple of commands. We'll try one after the other, and this guide will be verbose if there's risk or sat-spending involved. It's sorted from lowest risk / spend to highest, top down.

1. Reconnect

Many coop-close attempts fail, because when both nodes go to court, there is a possibility to not find consensus on the closing fee. Let's see if this is the reason, you'll see entries like commit-fee proposal staggering up, and whether you'll find consensus lncli disconnect PUBKEY && lncli connect PUBKEY@ADDRESS:PORT If the closing attempts fail, you'll see that each time, the delta between your node and your channel-peer will get closer. Eventually it'll work, if not, check your lnd.conf settings and eg change bitcoind.estimatemode=ECONOMICAL to bitcoind.estimatemode=CONSERVATIVE.

2. Restart LND

Sometimes closing attempts miss a broadcast due to a missing connection to bitcoind. Restarting LND rebroadcasts every pending channel-close and sweeps, so give this a shot and check your terminal 2 while LND is taking it's time to come back up. Really, you need some patience here.

3. Reinitiate coop-close (and force-close)

Try to close the channel again, in rare cases this would solve something which 1. didn't: lncli closechannel --chan_point CHANPOINT:VOUT --sat_per_vbyte XX. This may offer some more insight in your Terminal 2 window. You can do the same for the force-close, just need to adjust the command slightly. For the record, I never had this situation, but it's not doing any harm in case you know it's a force-close anyway: lncli closechannel --chan_point CHANPOINT:VOUT --force. We can omit the target sat/vbyte setting since force-closes use the last agreed commit-fee of both you and your peer.

4. Increase local Mempool size

This solves for a couple of things, both Scenario 1 and Scenario 2 above, at least as a preparation. Open your bitcoind-configuration with sudo nano .bitcoin/bitcoin.conf to lookup and edit the following entry to 2000, which increases it to 2GB: ```

Increase Mempool size

maxmempool=2000 `` Restart bitcoind (typicallysudo systemctl restart bitcoindto take this setting into effect. And either LND already restarted by itself, or trigger a manual restart withsudo systemctl restart lnd`. Watch Terminal 2, to see whether your 300MB previous mempool was too limited to accept your LND-closing. With 2GB, that limitation is lifted (a little) and potentially allows your LND to broadcast the closing-tx.

5. Manually broadcast the closing-transaction

Eventually 4. allows your local mempool to pick up the closing transaction. Sometimes it doesn't. Or your mempool has it, but the public mempool didn't. Without either your bitcoind node, or the public mempools knowing about this tx, your channel can't get closed. In this event, let's look at how to broadcast it manually and see what response we get in both Terminals.

1. Local Mempool check: Follow Scenario 1.
2. If it's a No, does mempool.space have it? Then open the tx there, and grab the RAW-tx by appending the txid here: https://mempool.space/api/tx/[TXID]/hex. Copy the whole long string, and execute the local broadcast in your Terminal 1 with lncli wallet publishtx RAWTX.
3. If that's a No too, check your LND, it should have it (only in rare circumstances, like SCBs, LND doesn't have the raw-tx: lncli listchaintxns --start_height 818181 --end_height -1. Substitute 818181 with the current mempool height to filter the transaction output showing only not confirmed pending transactions (utxos). You'll get the raw-tx there, and can use it with lncli wallet publishtx RAWTX as above.
4. If your local Mempool has it, but mempool.space doesn't, there is no harm broadcasting it there as well. Follow Scenario 1 to retrieve the raw-txid from your local mempool, and copy it in here.

6. Increase the closing-fee

So mempools know about your closing-tx, but it's way too low. Let's assume it hangs at 10sat/vbyte (like many pending closing-tx these days), but let's also assume we won't see <30sat/vbyte anytime soon. Because you'd always have the option to wait for 10sats, your tx will eventually confirm. But you don't want to wait, then you'll need to pay up. Disclaimer: This one is costing you. No matter who the opener of the channel was (who always pays for both un- and cooperative-closings), the next step costs You. So be concious about it.

The LND Guide linked above has a succinct closing channels section. And since you inhaled that guide, you'll know the next steps:

1. For Coop-Closes, you can lncli wallet bumpfee -h to make yourself familiar with the options. It's pretty self-explanatory, lncli wallet bumpfee --conf_target 6 CHANPOINT:VOUT will ask your local mempool for a sat/vbyte target and set the new closing fee. With lncli wallet bumpfee --sat_per_vbyte 36 CHANPOINT:VOUT, you can set a confident 36 sats/vbyte yourself. Watch Terminal 2 and see what lnd.log tells you.

2. For Force-Closes, you need a so called CPFP (Child Pays For Parent) transaction, which will become a child of your existing closing fee, and at the same time expensive enough, that both parent + child and their fees will be attractive enough for a miner to pick up and mine it. You can either do some pre-calc with a helper script, or try current mempool medium fee x 2. Not a problem if you don't start high enough, you can follow step 1. above here with this new child-transaction and bump it's fee with RBF any time later: lncli wallet bumpclosefee -h for the options:

3. lncli wallet bumpclosefee --conf_target 6 CHANPOINT:VOUT will ask your local mempool for a sat/vbyte target and set the fee for the child-tx.

4. lncli wallet bumpclosefee --sat_per_vbyte 100 CHANPOINT:VOUT will set the child-tx at 100, presumably ending up with 50 sats/vbyte effective rate for both your parent and your child to be mined.

Note that none of this works if your local mempool doesn't have that txid. So follow steps 1-5 before trying this one. Now but if it worked, you'll be prompted with a new txid for your child, which you can later check in your local mempool, and ideally it'll land in the public mempools to be mined as well. If it ended up too low, bump it with RBF (replace by fee) described in point 1, but targeting your child.

7. Go out of band

Just for completion, there are various miners who offer their mining service for your tx for a hefty cost. This sometimes might be necessary, eg for your channels where the other side force-closed on you, but you only have a static channel-commitment. If your peer is unresponsive or not cooperative to do a CPFP on their side, you'll wait until forever. Check your favorite search engine, ViaBTC or mempool.space for their acceleration services.

Hope you enjoyed this article. Please do share feedback and suggestions for improvement. If this guide was of any help, I'd appreciate if you share the article with others, give me a follow on X or nostr, perhaps even donating some sats to hakuna@getalby.com

I'm also always grateful for incoming channels to my node: HODLmeTight

See the gist of it on my github.

[^1]: For umbrel, you need to jump through some loops for the command lncli and bitcoin-cli. You need to add this whole string before: ~/umbrel/scripts/app compose lightning exec lnd lncli and ~/umbrel/scripts/app compose bitcoin exec bitcoind bitcoin-cli respectively. To simplify things, create a temporary alias with alias lncli="/home/umbrel/umbrel/scripts/app compose lightning exec lnd lncli" and alias bitcoin-cli="~/umbrel/scripts/app compose bitcoin exec bitcoind bitcoin-cli", then all of the above commands should work. [^2]: Wonder what your channel-peers current commit-fee is? And whether they use anchors or static channel-fee commitments? Check out this bash-script, among other Node-Tools available as open-source.

@ 2863f394:275ed58d

The factors influencing the promotion of proficient employees are multifaceted and vary across organizations. In engineering, for example, a typical structure might include roles like Engineer I, II, III, and Senior Engineer. Initial promotions in such a structure are relatively attainable, but ascending to higher levels becomes increasingly challenging. Even in companies with a separate technical track, such as Google or IBM, the hierarchical pyramid becomes narrower at the top.

In smaller companies, promotion opportunities are often contingent on the availability of vacancies. Regardless of an employee's competence and the company's desire to promote them, the lack of available positions can create a metaphorical "glass ceiling" for all employees. Although larger companies might have more frequent openings, this issue can still be prevalent.

A significant consideration is the need to fill the vacated role when an employee is promoted. Some employees are so skilled in their positions that finding a suitable replacement can be a daunting task. Ironically, these highly effective employees might be contributing more value to the organization than their managers, yet they receive less compensation and recognition.

It's important to recognize that management roles differ significantly from the roles of those they manage. For instance, front-line supervisors need strong interpersonal skills to handle worker interactions, conflict resolution, and problem-solving. Middle managers require organizational skills for scheduling and coordination, while upper management must focus on strategic thinking and long-term planning. Excelling in one role does not necessarily translate to proficiency in another, a concept highlighted by the Peter Principle.

Nevertheless, good organizations understand that expertise in a specific task, such as welding, does not automatically qualify an individual for managing others in that field.

Beyond these factors, there are additional reasons why more qualified employees might be overlooked in favor of their colleagues:

• Office politics play a significant role, where individuals who excel in taking credit for others' work or navigating the corporate hierarchy often advance quicker.
• Some employees are promoted for being perceived as "safe" choices – less likely to challenge the status quo or propose innovative ideas that might overshadow their superiors.
• Promotions influenced by Equal Employment Opportunity Commission (EEOC) guidelines are particularly common in government sectors.
• Being in the "right place at the right time" can also be a decisive factor.

Conversely, there are instances where employees express dissatisfaction with the lack of advancement opportunities despite doing nothing beyond basic job requirements and maintaining punctuality.

In summary, the dynamics of employee promotion are complex and influenced by a variety of organizational, personal, and situational factors.

@ 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/

@ 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

@ 3bf0c63f:aefa459d

A estrutura lógica do livro didático

Todos os livros didáticos e cursos expõem seus conteúdos a partir de uma organização lógica prévia, um esquema de todo o conteúdo que julgam relevante, tudo muito organizadinho em tópicos e subtópicos segundo a ordem lógica que mais se aproxima da ordem natural das coisas. Imagine um sumário de um manual ou livro didático.

A minha experiência é a de que esse método serve muito bem para ninguém entender nada. A organização lógica perfeita de um campo de conhecimento é o resultado final de um estudo, não o seu início. As pessoas que escrevem esses manuais e dão esses cursos, mesmo quando sabem do que estão falando (um acontecimento aparentemente raro), o fazem a partir do seu próprio ponto de vista, atingido após uma vida de dedicação ao assunto (ou então copiando outros manuais e livros didáticos, o que eu chutaria que é o método mais comum).

Para o neófito, a melhor maneira de entender algo é através de imersões em micro-tópicos, sem muita noção da posição daquele tópico na hierarquia geral da ciência.

• Revista Educativa, um exemplo de como não ensinar nada às crianças.
• Zettelkasten, a ordem surgindo do caos, ao invés de temas se encaixando numa ordem preexistentes.

@ 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

@ 2edbcea6:40558884

Happy Sunday #Nostr !

Here’s your #NostrTechWeekly newsletter at the nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk written by nostr:npub1r3fwhjpx2njy87f9qxmapjn9neutwh7aeww95e03drkfg45cey4qgl7ex2

NostrTechWeekly is a weekly newsletter focused on the more technical happenings in the nostr-verse.

A lot of foundational work happening in the nostr-verse and quite a bit of new projects shipped this week. Let’s dive in!

Recent Upgrades to Nostr (AKA NIPs)

1) NIP 75: Zap Goals ⚡

Zapping has been such an integral part of what makes Nostr what it is. Earning for your content or contributions. Zaps for memes. Zaps as a way to boost the signal. It’s a growing concept as well.

NIP 75 was merged this week, with the goal of introducing the ability to set a “Zap Goal” which is similar to a fundraising goal. Users can zap the “goal” event directly and help the progress bar go up. Whatever the cause.

Interesting to see if this will stay simple and decentralized or if this will be the foundation of a GoFundMe type platform via Nostr using exclusively Bitcoin.

Author: nostr:npub107jk7htfv243u0x5ynn43scq9wrxtaasmrwwa8lfu2ydwag6cx2quqncxg

2) (Proposed) NIP 79: Digital contracts on Nostr ✍️

Think Docusign, but on Nostr. This NIP would introduce support for various kinds of digital agreement (contracts, covenants, agreements) which serve various purposes.

These agreements would all be unencrypted markdown, so the purpose is likely more for non-secret agreements so that they can be cited by all parties in public.

Author(s): https://github.com/xemuj nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

3) (Proposed) NIP 34: Improved media attachments to notes 📎

Attaching media to notes in a way that is handled well on a majority of major clients is still more of an art than a science and nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6 is determined to introduce a better pattern 💪.

This NIP introduces the pattern of using an explicit set of “media” tags on any note so that media that should accompany the note can be explicitly linked without clients needing to parse the content of the note to make the url of the media in the note a hyperlink.

Author: nostr:npub108pv4cg5ag52nq082kd5leu9ffrn2gdg6g4xdwatn73y36uzplmq9uyev6

4) (Proposed) Improvements to reddit-style moderated communities 💬

This proposed improvement to NIP 72 introduces the concept of a post (within a moderated community) that is exclusively posted to a specific community. Think about posting something that can make the front page of reddit versus a post that is intended solely for a subreddit. Seems like a welcome addition to NIP 72 👍

Author: https://github.com/vivganes

Notable projects

A nostr Wiki

The start of a truly open wiki.

Wikis are used for a lot of things: corporate intranets and documentation, fandoms managing information about their universe, and Wikipedia which may be one of the greatest repositories of knowledge on Earth. The main downside to Wikipedia is that it may be crowdsourced but it is centralized, seeking one version of each article (and therefore determining what is true).

This wiki (in the spirit of Nostr) allows people to create any number of articles on the same subject to offer different perspectives. At scale this could become something where people read various perspectives and determine the truth for themselves.

Author: nostr:npub1q7klm2w94hyq3qdm9ffzpahrrq0qcppmjrapzhz0rq6xgq3fdrnqr6atmj

Oxchat

Oxchat is a secure, private group chat experience for iOS and Android with a great UX 🙌.

Nostr needs its own standalone chat app that can stand up to the capabilities and ease of use of Signal, Telegram, WhatsApp, etc. And Oxchat may be that app! Looking forward to using it more.

Author: nostr:npub10td4yrp6cl9kmjp9x5yd7r8pm96a5j07lk5mtj2kw39qf8frpt8qm9x2wl

Nostrnet.work

A web-based dashboard for Nostr, it’s a webpage that is a configurable hub for all the Nostr apps you want to have available quickly. You can log in with your Nostr account, and configure it to your liking.There’s a section for managing your profile (including your relays), as well as for taking notes, all of that on top of the list of Nostr apps for quick access.

Nostrnet.work seems to be evolving into almost a web-based browser of the nostr-verse. You can manage the apps that are on the dashboard Nostrnet.work via the basic/open app store from nostr.band. There’s endless possibilities for users to discover what Nostr has to offer and use those offerings from one unified interface.

A recent addition to the Nostrnet.Work interface is an area for “Nostr AI'' which is meant to allow users to utilize Data Vending Machines (explored in the Latest Conversations section). Data Vending Machines (or DVMs) are something that I think is unique to Nostr, and it's a product/ecosystem that may be the killer unique offering people come to Nostr to try out.

Author: nostr:npub1cmmswlckn82se7f2jeftl6ll4szlc6zzh8hrjyyfm9vm3t2afr7svqlr6f

w3.do url shortener

URL shorteners are a stable web util. In fact,

We started using w3.do because the tool we use to draft/publish this newsletter as a long form note will send Nostr links and embed the note instead of just linking to the note. So a url shortener is enough to trick the tool so we get fewer embeds and more links! Thanks nostr:npub1alpha9l6f7kk08jxfdaxrpqqnd7vwcz6e6cvtattgexjhxr2vrcqk86dsn !

Latest conversations

Data Vending Machines (DVMs)

“Data Vending Machines are data-processing tools. You give them some data, a few sats, and they give you back some data.” source: vendata. A practical example is a recent DVM published by Pablo: FOMOstr. You put up some sats, you’ll get back content on Nostr that you may have missed.

The concept seems to be that people need help from machines. And right now, the most common way for people to get that help is to pay a company for that help (email provider, calendar management, group chats, entertainment, etc).

These are great for more complex digital products, but what if you just have a question? Maybe you just want to generate an image. Or maybe just extract text, and then maybe translate it. These are most efficient as pay-as-you-need-it products. That’s where DVMs shine (on the long tail of needs).

You can put up a certain amount of money and people who have created algorithms or AIs that can accomplish these tasks will compete to do the job for the lowest price (and therefore win the money). This is the foundation of an economy of people who need jobs done and people who want to make income by creating the best DVMs for the jobs people need done.

DVMs that help you discover people and content on Nostr will be a god-send for improving the experience for people using Nostr while maintaining decentralization. This will certainly evolve over time, but it seems this could become an integral part of the Nostr ecosystem as well as become a unique service that can only be found on Nostr (attracting a new set of users).

Events

Here are some upcoming events that we are looking forward to! We keep a comprehensive list and details of Nostr-related events that we hear about (in person or virtual) that you can bookmark here NostrConf Report

1. Nostrasia Nov 1-3 in Tokyo & Hong Kong
2. Nostrville Nov 9-10 in Nashville, TN, USA
3. NostrCon Jan 12, 2024 (online only)

Until next time 🫡

If you want to see something highlighted, if we missed anything, or if you’re building something I didn’t post about, let me know, DMs welcome.

nostr:npub1r3fwhjpx2njy87f9qxmapjn9neutwh7aeww95e03drkfg45cey4qgl7ex2 or nostr:npub19mduaf5569jx9xz555jcx3v06mvktvtpu0zgk47n4lcpjsz43zzqhj6vzk

Stay Classy, Nostr.

@ 6871d8df:4a9396c1

One of my favorite Christmas movies is 'It's a Wonderful Life.' The end is so heartwarming, and being such a Bitcoiner, I find it interesting that the movie's premise centers around the issues of fractional reserve banking. Bedford Falls reminds me of where I grew up in a small town in Massachusetts. I also resonate with George Bailey as I felt the same way about leaving my small town growing up. Unlike George Bailey, however, I got out; it has been a decade since I lived there, though every year at Christmas, I make it back and stay with family.

This year is the first year that felt different. This trip was the first year where each time I went to go to an old stomping ground, I had to first think of whether it was still in business. It was the first time I noticed that a very high proportion of buildings that used to be small businesses had wood in their windows. The buildings that did seem upgraded changed to cannabis dispensaries. It was the first time I sat back and thought, 'What is happening here?'

In talking to friends and family about work, I became disheartened by how many either now worked for the government or the majority of their business came from steady government contracts. Those who worked in local education institutions regularly complained about how administrations had gotten out of control or dysfunctional due to lousy leadership or bloat. In one case in particular, leadership got so bad, but nothing could be done because he "wasn't white" and "firing a Latino president would look bad." It seemed difficult to imagine how these institutions would right the ship.

In short, I couldn't help but think that my small town was becoming Pottersville, where the government was Potter. Everyone of that age was concerned that a malicious businessman would come in and ruin their town, but that is not what happened. When constituents of a small town do not service it themselves, the soul of it disappears. Businesses will start to feed vices versus adding value. When small business owners have a greater interest in the long-term health of their small town, they will add value in more moral ways. Short versus long-term time preference matters for small towns. Interestingly, as citizens start to worry more about "how will I put food on the table?" rather than "how will I add value to my community?" things go downhill quickly. The community will start to look to Potter to solve their problems — in this case, the government — rather than each other.

This is, of course, only one anecdote, but I find it hard to believe that small towns aren't taking a beating like this everywhere. What are the consequences of something like this? What do we need to do to turn it around? Do we need or want to turn this around? As I leave the place where I grew up, these are the questions that are rattling around my head, along with "How much longer will I be able to come back and recognize it?"

@ 3bf0c63f:aefa459d

microanalytics

A replacement for Google Analytics that run inside a CouchDB, when CouchDB still was a potential platform for hosting of simple apps and easily distribution of apps with data.

It also had a CLI app for browsing the data with nice CLI charts.

• https://github.com/fiatjaf/microanalytics
• https://github.com/fiatjaf/microanalytics-cli

See also

• About CouchDB
• trackingco.de

@ 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

-

@ af9c48b7:a3f7aaf4

Chef's notes

This recipe has been passed around our family from different generations. It can be modified to your liking.

Details

• ⏲️ Prep time: 15
• 🍳 Cook time: 30 minutes active cook time followed by 4-6 hours crockpot simmering
• 🍽️ Servings: 10-12

Ingredients

• 1lb ground beef
• 2 packages of dry taco seasoning
• 2 (15.5 ounce) cans of Pinto Beans
• 2 (10 ounce) cans of Diced Tomatoes with Green Chiles
• 2 (15 ounce) cans of Yellow Corn
• 1 package of dry ranch dressing seasoning
• Bag of Shredded Cheese (we use mexican mix, but whatever you prefer)
• Sour Cream
• Large Bag of Corn Chips or Tortillia Chips

Directions

1. Brown ground beef in skillet and drain off excess liquid, then add 1 package of taco seasoning mix into ground beef following the instructions on the package.
2. In a crockpot (preferred) or large pot, add the 2 cans of pinto beans, 2 cans of diced tomatoes with greeen chilies, 2 cans of yellow corn, 1 package of dry taco seasoning, and 1 package of dry ranch dressing seasoning stirring gently mixing all ingredients thoroughly.
3. Add in the browned, seasoned, ground beef prepared in step 1. Then add two or three can (30 to 45 ounces) of water and stir gently.
4. Allow to cook on high in the crockpot for 4 to 6 hours.
5. Serve over corn chips/tortilla chip and garnish with shredded cheese and sour cream.
6. Garnish with jalepenos, avacado, lime, or whatever you like.

@ 78733875:4eb851f2

After announcing our first wave of grants for bitcoin[^fn-btc] and nostr[^fn-nostr] projects, we are pleased to announce an additional wave of grants for open-source projects in the space:

[^fn-btc]: First Wave of Bitcoin Grants [^fn-nostr]: First Wave of Nostr Grants

• BDK
• LNbits
• Watchdescriptor
• Stratum V2 Testing \& Benchmarking Tool
• Fedimint Modules and Resources
• Amber: Nostr Event Signer
• Nostr UI/UX Development
• Nostr Use-Case Exploration \& Education

The first five grants are sourced from our General Fund, the last three—being nostr projects—from our Nostr Fund. This brings the total number of OpenSats grants to 41, adding to the grants we previously announced in July.

Once again, let's take a closer look at each of the projects to see how they align with the OpenSats mission.

---

BDK

Bitcoin Development Kit (BDK) is a set of libraries and tools that allows you to seamlessly build cross-platform on-chain bitcoin wallets without having to re-implement standard bitcoin data structures, algorithms, and protocols. BDK is built on top of the powerful rust-bitcoin and rust-miniscript libraries and adds features for managing descriptor-based wallets, syncing wallets to the bitcoin blockchain, viewing transaction histories, managing and selecting UTXOs to create new transactions, signing, and more. The core BDK components are written in Rust, but the team also maintains Kotlin and Swift language bindings for use in mobile projects. There are also Python bindings, and React Native and Flutter support is being actively developed.

Repository: bitcoindevkit/bdk
License: Apache 2.0 / MIT

LNbits

LNbits is used by a multitude of projects in the bitcoin space, especially as part of their lightning payments stack. Being easy to build on through its extension framework, LNbits has been pioneering various cutting-edge solutions and experiments in the world of bitcoin, lightning, and nostr.

The project has a thriving maker community building various hardware devices such as Lightning ATMs, point-of-sale devices, DIY hardware wallets, and nostr signing devices. The modular design of LNbits makes it attractive to users and tinkerers alike, as its plugin architecture makes it easy to extend and understand.

Repository: lnbits/lnbits
License: MIT

Watchdescriptor

watchdescriptor is a CLN plugin written in Rust that connects a business's treasury wallet to its CLN node. It utilizes cln-plugin and the BDK library to track coin movements in registered wallets and report this information to the bookkeeper plugin.

The plugin enables businesses to design a complete treasury using Miniscript and import the resulting descriptor into CLN. Since bookkeeper already accounts for all coin movements internal to CLN, this plugin is the last piece businesses need in order to unify all their bitcoin accounting in one place. This enables businesses to account for all inflows and outflows from their operations, streamlining tax reporting and financial analysis.

The watchdescriptor project is part of a broader vision to transform the lightning node (particularly CLN) into a financial hub for businesses, enabling them to conduct operations without reliance on any third parties.

Repository: chrisguida/watchdescriptor
License: MIT

Stratum V2 Testing & Benchmarking Tool

The Stratum V2 Testing & Benchmarking Tool allows the bitcoin mining industry to test and benchmark Stratum V2 performance against Stratum V1. The tool supports different mining scenarios to help miners make informed decisions and evaluate their profitability. The goal of the project is to motivate miners to upgrade to Stratum V2, increasing their individual profits and making the Bitcoin network more resilient in the process.

Repository: stratum-mining/stratum @GitGab19
License: Apache 2.0 / MIT

Fedimint Modules and Resources

Fedimint is a federated Chaumian e-cash mint backed by sats with deposits and withdrawals that can occur on-chain or via lightning. It can be understood as a scaling and privacy layer as well as an adoption accelerator for Bitcoin.

The goal of this particular project is to improve the Fedimint UI and develop free and open resources for developers and "Guardians" to enable more people to run and develop on Fedimint.

Repository: fedimint/ui @EthnTuttle
License: MIT

Amber: Nostr Event Signer

Amber is a nostr event signer for Android. It allows users to keep their nsec segregated in a single, dedicated app. The goal of Amber is to have your smartphone act as a NIP-46 signing device without any need for servers or additional hardware. "Private keys should be exposed to as few systems as possible as each system adds to the attack surface," as the rationale of said NIP states. In addition to native apps, Amber aims to support all current nostr web applications without requiring any extensions or web servers.

Repository: greenart7c3/Amber
License: MIT

Nostr UI/UX Development

The goal of this project is to help improve the UI/UX of major nostr clients, starting with Gossip and Coracle, emphasizing the onboarding process as well as usability and accessibility. One part of onboarding is solving the discoverability problem that nostr has in the first place. Solving the problem of jumping in and out of the nostr world is what motivated the development of njump, which was redesigned as part of these efforts and is now live at nostr.com.

In addition to client-specific improvements, generic design modules and learnings will be incorporated into the Nostr Design project for others to use.

Activity: github.com/dtonon @dtonon
License: MIT

Nostr Use-Case Exploration & Education

As of today, most nostr clients implement social media applications on top of the nostr protocol. However, nostr allows for various use cases, many of which go beyond social media. Two examples are Listr and Ostrich, a list management tool and job board, respectively.

In addition to use-case exploration, this project will continue to educate users and developers alike, be it via Nostr How or various video series, e.g., explaining how to build upon NDK.

Activity: github.com/erskingardner @jeffg
License: MIT / GPL-3.0 / CC BY-NC-SA 4.0

---

We have more grants in the pipeline and will provide funding for many more projects in the future. Note that we can only fund those projects which reach out and apply. If you are an open-source developer who is aligned with our mission, don't hesitate to apply for funding.

@ 46fcbe30:6bd8ce4d

Opinion about Mycelium Wallet

test

#WalletScrutiny #NostrComment

join the conversation!

@ 9ecbb0e7:06ab7c09

Según nos reporta y documenta la familia, la niña pequeña de 3 años de edad Leadi Kataleya Naranjo, hija del preso de conciencia Idael Naranjo Pérez, ha sido citada para mañana por la Seguridad del Estado de #Cuba. La citación no ofrece duda e indica los dos nombres, apellido y la dirección de la abuela paterna, donde entregaron la citación, y la abuela también ha sido citada y amenazada de desobediencia. Si la niña no se presenta, amenazan de acusarla igualmente de "desobediencia". La abuela se preocupó, les dijo la edad, y aún así entregaron la citación y se fueron. Que "debían presentarse". Nada más. Desalmados son, pero... ¿Qué clase de locos de atar están al mando en #Cuba? ¿Qué pretenden citando y amenazando a una niña de 3 años? Esa niña no puede ir a esa ignominiosa citación. ¿A oír qué? ¿A responder qué? El tema da ASCO. La familia no quiere llevar a la niña, y necesitan todo el apoyo para que esta locura se aclare y se detenga. Desgraciadamente hemos visto cosas iguales o peores. Niños amenazados, separados por la fuerza de sus padres, menores torturados... El régimen de Cuba da mucho asco, por todos lados rezuma repugnancia y degradación. Todo lo que sucede en Cuba clama al cielo, y estas barbaries son distópicas. ¡MANTENGAN AL MARGEN A LOS NIÑOS, DESALMADOS ENFERMOS! Bastante daño causan con la Ley de los 8 años que tiene a miles de niños huérfanos, separados forzosamente de sus madres para castigarlas a ellas por no doblegarse a trabajar en las misiones médicas esclavas de Cuba en el exterior, como sentenció el Comité de los Derechos del Niño. ¡BASTA YA!

11jul #11j #11jCuba #CubaEsUnaDictadura #UNICEF @uniceflac @unicefenespanol

@ 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"

@ 3bf0c63f:aefa459d

IPFS problems: Community

I was an avid IPFS user until yesterday. Many many times I asked simple questions for which I couldn't find an answer on the internet in the #ipfs IRC channel on Freenode. Most of the times I didn't get an answer, and even when I got it was rarely by someone who knew IPFS deeply. I've had issues go unanswered on js-ipfs repositories for year – one of these was raising awareness of a problem that then got fixed some months later by a complete rewrite, I closed my own issue after realizing that by myself some couple of months later, I don't think the people responsible for the rewrite were ever acknowledge that he had fixed my issue.

Some days ago I asked some questions about how the IPFS protocol worked internally, sincerely trying to understand the inefficiencies in finding and fetching content over IPFS. I pointed it would be a good idea to have a drawing showing that so people would understand the difficulties (which I didn't) and wouldn't be pissed off by the slowness. I was told to read the whitepaper. I had already the whitepaper, but read again the relevant parts. The whitepaper doesn't explain anything about the DHT and how IPFS finds content. I said that in the room, was told to read again.

Before anyone misread this section, I want to say I understand it's a pain to keep answering people on IRC if you're busy developing stuff of interplanetary importance, and that I'm not paying anyone nor I have the right to be answered. On the other hand, if you're developing a super-important protocol, financed by many millions of dollars and a lot of people are hitting their heads against your software and there's no one to help them; you're always busy but never delivers anything that brings joy to your users, something is very wrong. I sincerely don't know what IPFS developers are working on, I wouldn't doubt they're working on important things if they said that, but what I see – and what many other users see (take a look at the IPFS Discourse forum) is bugs, bugs all over the place, confusing UX, and almost no help.

@ 1bc70a01:24f6a411

The following is a baseline FAQ intended to be copy / pasted / modified into clients Help section to get people familiarized with some terms. Some of the information may not be totally accurate, or can age very quickly due to the rate of development on nostr. If you have anything you'd like to add or correct, please leave a comment.

If you have any further questions, use the #asknostr hashtag for help. Keep in mind, some of this information may become obsolete since the protocol is under constant development.

What is nostr & how does it work?

Nostr stands for Notes and Other Stuff Transmitted by Relays. It is an open, permission-less protocol that aims to provide censorship-resistance and interoperability. It can be used to create social networks or just about any other type of app (other stuff part of the acronym). It is not a single website or app, but the glue that holds together many apps (clients).

At its core, nostr consists of relays and events. A person does something (event) and this event is sent to a relay. The relay stores the event, then waits for another person to request it. The most common types of events are notes and reactions - the stuff social media is made of, but there are many other types of events. It works very similar to how any other app would work with a database, except in nostr there is no single database, rather a large number of relays that store the events.

What’s the big deal?

The big deal is that anyone can build on top of nostr and access the same user base. Prior to this companies relied on APIs which require permission to use. This means apps live in silos and can dictate everything a user does. It also means they can de-platform anyone at any time for any reason. On nostr, a person cannot be de-platformed or silenced. Since anyone can run a relay, everyone can have a backup of their own stats (followers, notes, etc) and can make that available to any app that requests it. If one app bans the user, they’ll still be found in another. Since there is no single database, it is very difficult to silence anyone.

For the first time ever, creators can own the relationship with their followers and take it anywhere they wish to go. Speech is protected the way it should have been but hasn’t until now.

Why do I keep seeing “nostr” when I am using an app by a different name? Your app (also called client) is just how you access the nostr protocol. It’s a bit like email - you use your email app to send email over SMPT, and people can read that email in an app of their choice.

There are many apps which can access the same protocol.

What is a relay & how do I join them?

A relay is just a server that stores events (data such as notes). When a person writes a note, they broadcast it to their relays. Another person who is connected to at least one of the same relays then sees that note and can re-broadcast it further. This is how notes spread on nostr.

Most apps (clients) will automatically connect to a handful of relays when you start. You can discover other relays by inspecting people’s profiles and adding missing ones to your list. Some clients may also connect you to relevant relays automatically so you don’t have to think about that.

How many relays should I have?

On average, a person is able to reach a lot of their followers with 10-15 relays. Some clients will show the recommended relays shared by your followers so you can always be in touch.

Is one relay better than another?

The goal of nostr is to enable censorship-resistant speech. This means notes need to be on as many relays as possible. However, since most people will have 10-15 relays on average, some relays are going to be more popular than others. Having a few large ones in your list is a good idea, but broadcasting to other small ones is important.

In terms of quality, relays with good uptime, willingness to accept your notes, and close proximity should be prioritized.

Where can I find new relays?

1. Client settings. Some apps will recommend some relays in their settings. 2. Automatically connected. Some apps will automatically connect you to relays so you don’t need to worry about them at all. 3. Via other user relay settings. If you browse a profile of a person you follow, you will see their relay list and can add any missing ones to your list. Remember, it’s not Pokemon, you don’t need to catch them all!

Where do I find new people to follow?

It depends on the client being used. Some may have more functionality than others. Here are some possible places to discover new people to follow: 1. Trending users 2. Trending notes 3. Trending hashtags 4. Popular hashtags 5. Suggested follows 6. Followed by friends 7. Conversations - simply engaging in conversations and following interesting people. 8. Global (not recommended, but if you must).

What is a client?

A client is just another name for an app. They are called clients because they act as one - fetching data from relays.

What are private and public keys?

In nostr there are no databases and therefore no place to create an account. Instead, the protocol uses public-key cryptography to generate “keys”. It’s all very technical and is based on algorithms and math, but at the core you generate a key pair - a public key and a private one. These more or less act as username / password. You can think of a public key as your username (except anyone can access data associated with your username), and a private key as password. To post a note, you need to “sign it” with your key that proves you actually hold this secret key.

Anyone can see your public key (often called npub). But only you have the password - the secret key (often called nsec) which authorizes you to publish as yourself. It’s a good idea to keep the private key safe - hence “private”.

NEVER SHARE YOUR PRIVATE KEY. ONCE LEAKED, ANYONE WILL BE ABLE TO ACCESS YOUR PRIVATE MESSAGES AND POST AS YOU, FOREVER. THERE IS NO WAY TO RESET A KEY!!

How should I manage my keys?

Your nsec (private key) is your super secret piece of information. Never disclose your private key! It is not possible to “reset” it. Once leaked, that key pair is done and you have to start over with a new one. There are some services that can help transfer your data from the old key to a new one, but they are still in development.

NEVER input your private key into a website. Websites can leak data. Instead, use a signing extension where you add your key once and let the “signer” do the job of authorizing events such as notes on your behalf.

Popular signer extensions: - Alby (Chrome) - Nos2X (Chrome) - Nostr Connect (Chrome & Firefox) - based on Nos2X - Amber (on Android) - Nostore (on iOS Safari)

So, I can access any nostr app with my keys?

Yes, your private key is all that is needed to “sign in” to any app on nostr. You don’t need to re-register every time. This is one of the interesting things about nostr!

How come I don’t use an email to sign up or log in?

Email-based accounts rely on gated databases. Your email address is just a lookup field for your password. In nostr, there are no central databases hence no emails or passwords. You interact with the protocol with your public and private keys.

Why are my follower numbers inconsistent?

Different relays may have different information about your followers. It can be difficult for clients to get the accurate number since it is so dispersed. Some people find this to be a fun feature and not a bug.

What is a nostr address, do I need one? Where can I get it?

In traditional social media, users get “verified” by proving their identity with some state-issued document. The company confirms it and gives them a verified badge. This tells their followers they are who they say they are.

Nostr does not require identification - it is pseudonymous. Since there is know KYC (know your customer) process, it is up to the user to prove their identity if they wish to.

It is entirely possible to have 10 people with the same name and the same “handle” on nostr. 

Elon @elon Elon @elon Elon @elon Etc... 

A nostr address is a unique human-readable identifier that can help prove your identity. It looks like this:

bob@mydomain.com

There can only be one bob@mydomain.com hence why it is unique. Any new Bob that registers on that domain will be Bob2, Bob3 or whatever name they choose.

If you choose to have a nostr address, it’s an easy way to share your profile with people, but also to indicate to everyone that you are the real you and not an impersonator.

Before nostr address: Elon @elon With nostr address: Elon elon@x.com

The nostr address is entirely OPTIONAL. You do not need to have one to use nostr. However, it is available as a free service and people register one just to prove it’s them.

A nostr address is not a scam-proof method of identification for reasons too lengthy to discuss here.

Am I anonymous on nostr?

No. While you can post under a pseudonym and never share your identity, relays are able to see your IP address which could in theory be used to identify you in combination with some other things. It is best to use a VPN that is also not tied to you via any identification if you wish to remain anonymous.

What is “global”?

Global is just the feed where all notes go by default. It’s usually a mess, but can be interesting. While nostr is growing, seeing the global chat can be a good way to discover content, but as nostr matures it may become less useful.

How do I minimize spam?

The simple way to minimize spam is to not visit Global. Once you’ve found some people to follow, browse through their following lists and discover new people through conversations to expand your network.

Some nostr clients also utilize Web of Trust (WoT) scoring to minimize spam.

Why are some relays paid? Are they worth it?

Relays are the backbone of nostr. Without relays, nostr simply won’t work. Since there is no central company paying for all the infrastructure, relay costs are incurred by their operators. It is a good idea to help cover some of those costs by becoming a paid relay user. Paying for relays keeps the network functioning and healthy.

Besides good will, paid relays can minimize spam and offer other services such as advanced filtering and translation. If you use nostr extensively, consider paying for a few relays, we’ll all be better for it.

How do I edit or delete a note?

You can’t. Once posted, notes are there to stay. They cannot be edited or deleted. This is because notes are sent to relays and there is no way to control what a relay does. The only thing one can do on some clients is to request deletion, but it’s up to relays to honor that request.

How can I delete my account?

The simple answer is you can’t because there is no “account”. Once a key pair is generated it will remain forever. The only thing you can do is remove your keys from a client.

Your data can disappear if all the relays you published to decided to drop your data after some period of time to save on storage costs, so in a way that would “delete” your “account”.

How does muting work?

Mostly the same as any other social network. Once you mute a person, you will not see their notes in your feed. But, if someone else you follow posts, and the muted person replies, you will see a notice that there’s a muted reply. The same goes for the muted person replying to your note. You can still choose to view the reply, or skip it.

I'll add more info about zaps and wallets later.

@ 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

Castas hindus em nova chave

Shudras buscam o máximo bem para os seus próprios corpos; vaishyas o máximo bem para a sua própria vida terrena e a da sua família; kshatriyas o máximo bem para a sociedade e este mundo terreno; brâmanes buscam o máximo bem.

@ 44dc1c2d:31c74f0b

Chef's notes

This bread is super simple to make and takes a bit to dial in.

The only real notes I have here is you can use whatever round pan you want to bake it in. Or use a square one, just make sure the walls of the pan are high.

Less is more with this bread. You really don't want to over knead the bread here. If you're used to making bread that need a lot of kneading, this will feel odd.

Details

• ⏲️ Prep time: 27 hours
• 🍳 Cook time: 50 to 60 min
• 🍽️ Servings: 1 loaf

Ingredients

• 1-1/2 teaspoons active dry yeast
• 1-3/4 cups warm water (110° to 115°)
• 3-1/2 cups plus 1 tablespoon all-purpose flour, divided
• 2 teaspoons salt
• 1 tablespoon cornmeal or additional flour

Directions

1. In a large bowl, dissolve yeast in warm water. Using a rubber spatula, stir in 3-1/2 cups flour and salt to form a soft, sticky dough. Do not knead. Cover and let rise at room temperature 1 hour.
2. Stir down dough (dough will be sticky). Turn onto a floured surface; with floured hands pat into a 9-in. square. Fold square into thirds, forming a 9x3-in. rectangle. Fold rectangle into thirds, forming a 3-in. square. Place in a large greased bowl, turning once to grease the top. Cover and let rise at room temperature until almost doubled, about 1 hour.
3. Punch down dough and repeat folding process. Return dough to bowl; refrigerate, covered, overnight.
4. Grease the bottom of a roasting pan with sides at least 4 in. high; dust pan with cornmeal. Turn dough onto a floured surface. Knead gently 6-8 times; shape into a 6-in. round loaf. Place into prepared pan; dust top with remaining 1 tablespoon flour. Cover pan and let rise at room temperature until dough expands to a 7-1/2-in. loaf, about 1-1/4 hours.
5. Preheat oven to 500°. Using a sharp knife, make a slash (1/4 in. deep) across top of loaf. Cover pan tightly with foil. Bake on lowest oven rack 25 minutes.
6. Reduce oven setting to 450°. Remove foil; bake bread until deep golden brown, 25-30 minutes. Remove loaf to a wire rack to cool.

@ 3bf0c63f:aefa459d

Channels without HTLCs

HTLCs below the dust limit are not possible, because they're uneconomical.

So currently whenever a payment below the dust limit is to be made Lightning peers adjust their commitment transactions to pay that amount as fees in case the channel is closed. That's a form of reserving that amount and incentivizing peers to resolve the payment, either successfully (in case it goes to the receiving node's balance) or not (it then goes back to the sender's balance).

SOLUTION

I didn't think too much about if it is possible to do what I think can be done in the current implementation on Lightning channels, but in the context of Eltoo it seems possible.

Eltoo channels have UPDATE transactions that can be published to the blockchain and SETTLEMENT transactions that spend them (after a relative time) to each peer. The barebones script for UPDATE transactions is something like (copied from the paper, because I don't understand these things):

OP_IF # to spend from a settlement transaction (presigned) 10 OP_CSV 2 As,i Bs,i 2 OP_CHECKMULTISIGVERIFY OP_ELSE # to spend from a future update transaction <Si+1> OP_CHECKLOCKTIMEVERIFY 2 Au Bu 2 OP_CHECKMULTISIGVERIFY OP_ENDIF

During a payment of 1 satoshi it could be updated to something like (I'll probably get this thing completely wrong):

OP_HASH256 <payment_hash> OP_EQUAL OP_IF # for B to spend from settlement transaction 1 in case the payment went through # and they have a preimage 10 OP_CSV 2 As,i1 Bs,i1 2 OP_CHECKMULTISIGVERIFY OP_ELSE OP_IF # for A to spend from settlement transaction 2 in case the payment didn't went through # and the other peer is uncooperative <now + 1day> OP_CHECKLOCKTIMEVERIFY 2 As,i2 Bs,i2 2 OP_CHECKMULTISIGVERIFY OP_ELSE # to spend from a future update transaction <Si+1> OP_CHECKLOCKTIMEVERIFY 2 Au Bu 2 OP_CHECKMULTISIGVERIFY OP_ENDIF OP_ENDIF

Then peers would have two presigned SETTLEMENT transactions, 1 and 2 (with different signature pairs, as badly shown in the script). On SETTLEMENT 1, funds are, say, 999sat for A and 1001sat for B, while on SETTLEMENT 2 funds are 1000sat for A and 1000sat for B.

As soon as B gets the preimage from the next peer in the route it can give it to A and them can sign a new UPDATE transaction that replaces the above gimmick with something simpler without hashes involved.

If the preimage doesn't come in viable time, peers can agree to make a new UPDATE transaction anyway. Otherwise A will have to close the channel, which may be bad, but B wasn't a good peer anyway.

@ af9c48b7:a3f7aaf4

Chef's notes

This recipe was published by a local chef who prepares it on a weekly basis at a small boutique restaurant located above a bookstore.

Details

• ⏲️ Prep time: 15 minutes
• 🍳 Cook time: 30 minutes
• 🍽️ Servings: 8-10

Ingredients

• 3 tablespoons olive oil
• 2 medium onions, chopped
• 1 tablespoon minced garlic
• 3/4 pound smoked, baked or country ham cubed
• 2 (14.5-ounce) cans of turnip greens, undrained (recommend Glory Brand turnip greens if available)
• 2 (15.5- ounce) cans great northern beans
• 2 red potatoes, diced
• 4 (14.5-ounce) cans chicken broth
• Salt and ground pepper to taste
• Cajun seasoning to taste
• 2 tablespoons of granulated sugar

Directions

1. In a soup pot, sweat olive oil, onions, garlic, and ham on low heat.
2. Add turnip greens, beans, potatoes, chicken broth, and bring to a boil on high heat.
3. Once boiling, turn down to medium heat. Add salt, pepper, cajun seasoning, and sugar.
4. Simmer for appoximately 30 minutes.
5. This recipe makes a large quantity and can be cut in half. Serve with cornbread.