@ 1beecee5:d29d2162

@ 6b0a60cf:b952e7d4

nostr:nevent1qqspynu0th85xlczqgnafy2na46mg276u0c5dmpd9utcz36npmqdmpsunn5rl nostr:nevent1qqs06cvm4qq9ymt2j58u0p7c46j2atxevjkp5vpezvlzesxcp7v03fqm0tp5k nostr:nevent1qqs8vjpu7wd5h7p0elysezzml7wzhaxgjwnp5h7yst0uudyy8pjt3pckcapzl nostr:nevent1qqswmpc5vghej8uz5mk8nta2szx3ejdsvdrvxtspmc3mld683j53mfsf0ujes nostr:nevent1qqs9cwaua4gvrxms3qz8rntj7jmuyvv953sm9lcwk5j4p8jfc4qxpgc7sfhw2 nostr:nevent1qqsx4f2m3njh0cpgqe376xpqde65ujq0aq50nj45ttfqls3yzluqujgpuum60 nostr:nevent1qqsrx7q02xfyak54zcmh233trqtpw725ywasfyg9dz08prxdvcnnuhqdnymnw nostr:nevent1qqsdllaud8mjpfhfzgu9nxjgvys5g08eu344909nyekrrn92pzhpxac56vtuj nostr:nevent1qqsxhx3skvs8xeddpwvhct3yhp02vgmdu90my67ttlj70muhcu3malqjadl5f nostr:nevent1qqs2k5q965ppnvxs7tna9wwx3njtp9r40ur4ahud8ykug85vth03haqe6m4py nostr:nevent1qqspzh3q002ssre56emu2kkhel82sd9j2sacd75fm998km8p6cxn8gg7agpxy nostr:nevent1qqsy8v9vj7u3jfnmhl6867n847d2gs7gpvdn5zdnm98nes9zlgu3rnqjkwmt9 nostr:nevent1qqsq559y4mj940540zhzxa9teknz74l9d6tqptste7l4lqu5yfvu2tg74dky7 nostr:nevent1qqs8gq3t2wk6qluhcjqy5cp8v3y20wmtw3uyfujmga7njpq3fe76pcgtgp34k nostr:nevent1qqsztaj9ut2lxru8la8lcs95lgyrpypwhgx92jc74r5nj7ss8tf9fvsr70m5v nostr:nevent1qqsghxwhmfywe40sdrq2cw750ug5f62nfh2u3jwe476zj6s0xmgcgpchj5qwx nostr:nevent1qqsdaw986p4qwujz99a0eg0yqtpjqhl6rcamxa0hn0yyg8pcwch6cysmans7p nostr:nevent1qqsyh8g0et5catuar388v56eahc4qmf7l6t79cs6scuuqa72vxj5lxq7de8wr nostr:nevent1qqszvxdc8vf2tjlayf7qf839p2j245nt7447ytqnju65s4ypz402gecrcsp8q nostr:nevent1qqspyx8mxme44n9vjspewch8s2tmtezt3z87kpytzetn68m39f0yhfsskl808 nostr:nevent1qqsdu6r2sf6npr3xn5gwkdc6st62zvy6r6r8u7sh078rjd7cjvy5jdcy8crru nostr:nevent1qqsrc0j0xa769ymehgxjem3lchwccndwj3ms922ltu7r7sy567lyzncddqjsv nostr:nevent1qqs0gcr269zzgcmrq6fjyzgqh7lqerhqqaknfrd5k563xnr9vanmtgcfzza5l nostr:nevent1qqsru4vxn5sw02zq4v44xtcpkt0qxqp9yc6gyy5pyavvvwa96dxyzscp3apme nostr:nevent1qqsp0ajlpxnvu64recf69efhxzv6sgu7yk235u59nj2v529dq92x2wgvcna9c nostr:nevent1qqsdmcrqmdkzf9tptgh5mytuan9q3ur7l50a5kjfrskfr54gxqq5k0szyhfsj nostr:nevent1qqsfk0duvuamrutcpansw3hqarnmhcr4vp0zt9r8pta9zlycma2jscs5wz0fm nostr:nevent1qqs82xxv600mtzxhhped2vn9yw7aer487ws8yy5hk5ppyuzxjw92hzs06hxp6 nostr:nevent1qqsfs96nd96mvulw9yp0dyygdtsegxkmnvytkq5xgmepkrh0504x0ns0rnm60 nostr:nevent1qqspa5f2fc5w4f9ghq2eryjnc44hs3grmaq6eyrx4s7ggkpjdmx2gjckswv0a nostr:nevent1qqs96s99kv7h207twu8s9mhmms7e5ck2s9qhndnp0m2w3uqpsh724ysnd6esu nostr:nevent1qqs8z5jzrlmeenpst0xtrm336tt0racrx63cnchskgs2d9cgmrtugdgmluxwa nostr:nevent1qqs9aqladqaf2jvanehny0mhd6mq9cdrgwr838z68p8h9clmcgf0zygqfvdd9 nostr:nevent1qqsd2m5tlpztgfqhzhc09upzzc876j6s60299m9lha2sxvnyjrvfasctaurj9 nostr:nevent1qqsg2yq7mw55vqnjmrfetc453v3z6vzzynmevt2ljgg4yppn5m2ry3ce2jlfe nostr:nevent1qqsr3vckac3re8ayyhv3m3g5s8a4rat5720un7qle8am2lfn7ew3magu6vk8f nostr:nevent1qqsg73fke3mszmuz0nh7r34sl3jlgdx70npfjc5almxrpycykhvnersq3rfaq nostr:nevent1qqsr73gdk6n0dgvg7nv6c390qf0c2j80t7qf99nftmze3dlr7k3nhpsfhl2ql nostr:nevent1qqs2mfw8a5vz3tjrnuerw6vxge0t6kd6snyeaj5jpfye7jvkqyqsv8cdw09np nostr:nevent1qqsr3qpal7xkhkttp4jrmjehm86ulh8hzarusgnyhhuf4ttdkqq0vhg7279w0 nostr:nevent1qqs0m4l3rza008tax28s3mh0tpexeqpzk8y2hlx2h8dgaqcft4rvm5c8xz2sq nostr:nevent1qqszt96jl70h9ku86s8mldsa8vk7m2vtwgfc2sksxcqfmkl2dksjntsjhz5zx nostr:nevent1qqsqdhulqcal3edfn2tu5lsj2tcgyq73zft3z6sa0xaqt4rd7m2gq4qpgs30l nostr:nevent1qqsygu35a9rrlh8ld5nuucjj9nw4up0d8mx6dmq98hqpj7j2kc6w7ts44y0wh nostr:nevent1qqsfnzz55mveegemu9nmqvfvm4wyarpevh29m778946lphw4wya23ms7z8ll2 nostr:nevent1qqs02ft4599adqeu9v3ny04k5x3mdued0rnj2hgg5lsg82xmqnpgxvsr48clp nostr:nevent1qqstkr7gr3flahhe9e6gl70sudqm5qz23rq2f2q9as3ys9s6l9c06lsgrduvd nostr:nevent1qqsqzmjj8rn6pl8wrn5km7an00cfhy5wzqzz9nlne5hzhktwlnsp0ag0qd665 nostr:nevent1qqsfc2x5vx23yyztnvr3n59dv9kyw64jc88pxxfgawt4c8m32qq5ekqqe4neh nostr:nevent1qqs0f7fkwlky42jxsdgr33xttz3rkg7gk200qkmv2rulrlauqwee7ts7mzn5q nostr:nevent1qqsg3c8qyp4n86qdtkyzcnk6kr7gnmad3sd2vhel52m3r64ala9rqugrcnnv6 nostr:nevent1qqsw9dn2cuhe4xu76z2xyugh8gaah92rdyazyg0s2mvkll0qrll02gs4uvvvk nostr:nevent1qqsv0pymkvfqz53jyqwqjj5wypp375ljlstav67zzpdlq536xpm8d6snawjc0 nostr:nevent1qqs20fpumlhmzs49mlsvd2f0s7kfgjq68auzkfvf6s3yr7a0njy782qv778m2 nostr:nevent1qqswqq7pl8g5redm0t82k4ys50w65z03m5xl6ayr374c2vknqfwjcrgguyt5s nostr:nevent1qqsp0fn3adqdq3jvcna0vwkwjnaq32lx6ac7qzpquvdt8zpugx5gvhshhkgez nostr:nevent1qqsvtd6surkas9nrvnlndk3r53aqq82dedmm8ayf2zhrv9w9lf90g8gslhagd nostr:nevent1qqsqw56qfhvkv56ss5r066yrf2hnwchcn4ldav576ldhvk3jk543clcsayyfz nostr:nevent1qqsxq9faxju2wp9zl5gw7usu00rkm7n0x9ylnlujsjjn323wppqpausm4etyu nostr:nevent1qqsrl7gdwgd5mqf3s3ygn2e5j34qnjxeldr99qwn7lge3ncfdwhf4usl70dm2 nostr:nevent1qqsd2a32drg7teet8fnkauxede52lyrau8ey24dzzqflu7pad2fhsvsdgtyr4 nostr:nevent1qqsv5uqj4zxhdtdapzk44tfuxyft55tlp900r4l7rf9vtma8d6cgjms2hjwde nostr:nevent1qqszcepleg57p2k03e06et848frekk79x3f523nmx8t3guxmuyfgsyqeat4pt nostr:nevent1qqsvklay6j4ukvc0w9n74u5hzselsrmclm9jfmezrztqf3xf74522ac0rlcen nostr:nevent1qqs909ldkkvchacs32hpj4zphwxdyxtnvv2nz0wdk7d26ec25j7xyfcsx997r nostr:nevent1qqs0nyvnc4j8xen06z9t784htam8e9jsucpm7g0xq2cdtenxrcx4qdgmgtj8q nostr:nevent1qqsfq3gqv98x97s0wu2cyenz5ng0v52fsv8erzyuj8q7ls9kwaaafggwt30r0 nostr:nevent1qqs2pu4lcqakjgkx524jvd967vk2fkuw6urtp7tw38q3accra6hf0xqd99kc3 nostr:nevent1qqsvgwlfeju2qsnllqgexscdrta9lnqamxlq2kvansadmhyy0g0eqhg02dpeg nostr:nevent1qqsvveq4k9cz0t3xh55cudydkweh58aekjrmqh6zut7ekqsnuv3hfyqdrru6x nostr:nevent1qqsfn29l63mfggnvq2j3ns9u09su2zrsahrxmczh4mk6q8mq45lxkps5alh6e nostr:nevent1qqszg3s0jdwj4qug6plqe865ul8zh6j60gue9c5f897dclmvu5xc2zqv77xmu nostr:nevent1qqswla2n4l5cu2z3czyt8vyawylv2hxj2avjg0lx6lnl7cw9p3kn5ac9nf5u8 nostr:nevent1qqsf8qufcluup4tl8rcngu5z8tarzxl7the3wfe0xnfdyjht9rzvpaqyzcn57 nostr:nevent1qqs8turf9zhsjc7uunw8wgqtd7dc5wtlrgxf2wrvsnw2cgz534wd6sghzcgw4 nostr:nevent1qqsqwngx9nxgf7slse6yeh9uvnpmwz3exa95qyh6x3ez00z72y2jvwsrfqdhk nostr:nevent1qqsv8z7leemtzl5cfexxynl7243uqd4nr7kacdaumyx8rq46kune2psgz47rc nostr:nevent1qqsp0ttn3kcnds34zjew7w7e8hwnaa8hwx29t3tej2guawf8pdt9csgz4m9nv nostr:nevent1qqszy0yufenkexssavnv0p5k98e3vu77f4r4tze5v6p94gmgcrgpx4qd27h77 nostr:nevent1qqs2xj626q46rpzwnas5259t5ywpwzltnvj3pwvrjcqseddtyu500qg5rn883 nostr:nevent1qqsw02jdkpg2vzs5k5c3ymvndsrkje6uwkxf0dqmz0yvycfwt6lvq6qjqgfgz nostr:nevent1qqs2d237yzkmuxl82fc2u7wdpzxyvjw2gje6vgadtw4dzmnp483jgrcval8vd nostr:nevent1qqsrwqj390vqwp7e6nwu3k8m6h4luks86gq3sql99k5tnvy4w52kamqp73nl8 nostr:nevent1qqstdtqpxl78ecn9x8dzylvzul0cfsxh64gfunzts72l3sqmvzt0ylqwp9c8n nostr:nevent1qqswcvajl70frlhwtuch6cwlsehl0u7f2hfw27vhxvzwhzatm2ugjss4zle92 nostr:nevent1qqszfrq6zdsclykmeke3a7znqgp7y975mslf5w0fk0hfujajj9jh4hssc4s7f nostr:nevent1qqsp253cwmp33yedu7asa6k2f09w08j34zcky52ks6jh97msqsrh9nqylwer9 nostr:nevent1qqsd3u0gms7u8gqkvhpfqlvk2jrttjzs5zuvc8qdl3g5pse4dt8ugcsqcez79 nostr:nevent1qqsxq8t0u67schrxvv0dtuf2j6nlvqytkez42f0jmhpjtnkap5ssvsgm7pdcc nostr:nevent1qqsvp878n0zlqkge6famsdwcqp8k92flz2wf97c0emxlsrf7f6gqt8gyzkgp8 nostr:nevent1qqsx3xnxupzzfvws2etneycjyvcx0n7mcqru09gyym5x20s3n9ewcrgcsetd6 nostr:nevent1qqsf666tlstrgssclusaam50nfk0xjs7m849f70fuv5hw9h7tsmqpegaduhy9 nostr:nevent1qqs23eqhwhvah5yjn54m7n5klw4e5efg8s6994pamz5ejcgnsq4d2wss89y7y nostr:nevent1qqs2q84pdl6qvf8h7yu9g6hfvfzj49z28ea5m6k4lpmwvl86tnuedxqkxxajr nostr:nevent1qqsyf0quzl6ttedn7qftse9386uh0pvp8795egxumyvs8sjckm8xgxs2srhmy nostr:nevent1qqsf7n8rqr2wsjpcuczlcee85227rylnv0kanj4mca0hllptyerd8csnyspns nostr:nevent1qqsycgshmjcqsr76tlhuppp23a49zy4e995lj5wnqm8jkz5vmv9l55cjpughr nostr:nevent1qqsp4vwephtxxlv2pjgupymfl6k288qh6gdzsy8qesmu0natsh095tsnfrpnk nostr:nevent1qqs297q9e00dpmj78rdx2qrjg3hva5ye9p7nke8avagn844jxucudwg2mtxgq nostr:nevent1qqs9c08g0fxv3vy7v5c9gsme0jx6fujkv88k3rtnmxjcd89ejpy72hcadrjas nostr:nevent1qqsvmwsetretl7dm42c3g690llwylyn37cunkauepzj3le3qhaytrjsh2ga9h nostr:nevent1qqsgyqu6zjppqek23fgpzlmg7hqfl4knryjvuflx54ypx70m58gt6rs5s9dms nostr:nevent1qqspxcsk7g56qhapmzek243az6zhv9v5hwupnyg4nn352kvc2z0fw7qklkcv7 nostr:nevent1qqsxwe7u49q4yc4ney5kt6gkfep0v9jlx68r5u0uf9upl7u9mcfxpkcqpu7z8 nostr:nevent1qqsrmyeh30f4kfdleq23w9vgcx9jcqgkv3stg9au5m593tlywlca0lgylty6g nostr:nevent1qqsg2v2e7tthtd8m39ctt7yyqw0lqkx23s7e2fqt4s2ymlnn33n5axg7fy4da nostr:nevent1qqsvtgfln33c2nllxt2797xfqttcuy6qtlh8we8q9lv9gn7r5jy4ahsfqpyg7 nostr:nevent1qqsz2al0emnaf5cjtrtdfv9c9t5ey8475yx5kp5442cg0afmlys6dgg29jq4x nostr:nevent1qqsg8lvelaeq9uyv7hzrxgpelckuz5hpf5g3ajyghj8nsk2ycckv63sllv797 nostr:nevent1qqsxhp4g53ltg7qjz2puzvsdwxk54xev46n8jmc2tlg2pdp529ckgfg2329m7 nostr:nevent1qqs82j5zgk3plkk8fugmflertrl8uc6x36elfeet643npvyuxr39tvcrr2u63 nostr:nevent1qqsd4vye657t504chaqf2d5gwgd5946t9tfg6aq0fnkjljnnmkfmadg3ss3uw nostr:nevent1qqsxhr5lanyrce0c6amgvxzd77a26fpap505hl74jztuc5svst8dtrcvtcl4f nostr:nevent1qqsrdap3r0ptlwxgd0dav04y53w04x0jzh22d4sxksuzfpetf6j8zwgtmay55 nostr:nevent1qqsvyqj4lr5g5swahxxjrpmga3569qlmd96xk6f4xwm84gmwu7aqw4c69zqtx nostr:nevent1qqsf9dntcjdmmzsu0s2t7pnlx6ver9usvaz53hvgtjggfgn8da6eydc7l5gc2 nostr:nevent1qqs9njwwgechxesqycm29asghutvq0e2fec2v4jc0gvpsk2dsnujq8c9vnuuq nostr:nevent1qqs9ahfkkycdlkemndn0dc7am5djnp8pwjnu72sng2tg0pk5kq7jv2skfv95c nostr:nevent1qqsflgngaeu8w2xz2lkzly5rvr3rudcvq4yyrn2w724dlr32p2mulpqasv6vj nostr:nevent1qqswg7qfwtdj38kr9xfp7f6gfvaxm5kpuwp22ueqny5pp6da7snl92svggqww nostr:nevent1qqs256vewt769a0q8teqh3n5eggjvw0jddl4xzejx4rykhcrrx2k4zcr70g2w nostr:nevent1qqstf7w5lej9qqm63x2r9c5ztc7s9tre65f3e27p5mhqjzy3555856g0lptxq nostr:nevent1qqsfzchhw84ldh2egvqethzychr8jvaaurdacvav3qhgelwzldy7adslwelmw nostr:nevent1qqsqy4uzgsedu94j6jyjpavrmn35khc7nsdmhxnwqehy9umdkgac79skwad40 nostr:nevent1qqsrzxkswpug72gc6eqf4qklemc29quyscds2ftwuqmf0lwvz78fckqxq9r9d nostr:nevent1qqsfzvl36d5k89q0frn9gfepwjrd65cgarh3gtj6gmqffjh9v7ncpesfxuyug nostr:nevent1qqs9vcndnjwtjcg2p5yj2jcktscn8lyf766kqtjef2a3fmyhsga0mgg6d5vp7 nostr:nevent1qqsdf65dzcvx2pkwh297amygfcdypu80g3hc2w0hzl6l8ed8ptcd83ccux9kt nostr:nevent1qqsr69tp6y6dj6agued5vqvv8wrhwngtl9nk6yln2amzg4j0fnxfsksj59765 nostr:nevent1qqs0jjfn0tnjgvech67ks5n3x9zrpredskg67twea7m2x8hvuq3zvvsjdgjcx nostr:nevent1qqs8s9wuwnqmkdjwmrxmqrjyktq3egkxlaqzx7t6q9e53yalga55xuq5ez8ug nostr:nevent1qqste2hugs0txe9xqzle5y60t2m5sakxfcq4flw9e6gtxvdlpuy2qqq3ksyc5 nostr:nevent1qqsxrns3rez8vhnym5qvqkg434w26r2paw8jm9640lzmhzs7jc00r2sk5nqq7 nostr:nevent1qqs05du8xmstnuajfj6cqetxv06xk8xgj23eepfpyjk8hdz3v5hx3hqg7tcwf nostr:nevent1qqswq92249238q2gp6cjcuup5w0e60htyqrp22cepc6uelysmewp46s3n3c76 nostr:nevent1qqspwxsck6zz60gc8tr48l4qqdnlnva0s9gay2hmdckutrz5sk8mnpcueftjt nostr:nevent1qqsywqjwwnuycnzkar8cnua5lerl80kr9wvwdr4yy07k2r7enlup08s0w3tg6 nostr:nevent1qqs87m5zz4x2cctfvxrvxx9546fe9rl5j82dxcrz4s89qzk47huyalgrd3rk7 nostr:nevent1qqst7lun76xhcmaw84s7cwqu9wu5dfterxxhjptlw54gxhnz5duxcaceaky47 nostr:nevent1qqsyexk849hlfxhnqlt4t6y23jshgeevrvtu53dh95w6xfeuuxrvz7c2aj87m nostr:nevent1qqsglmpnfw3jgl9ekwanzlgzhndce6pmncvunkswpc3y2n40vu33m0cwds2v5 nostr:nevent1qqsdaw8rm6yww2ks8300m2xw22c8xdemnkspdvwrjh2jn6hnuvuh9zc6quvml nostr:nevent1qqs0p6d8ny8kunevc8capqu9ntjmd9ze24ql2sjam0j0h8ju0xjydygkm9ffq nostr:nevent1qqswu057ppwc2lars6nu8sc8j4rupnahsrn79a8zktsqawq6p5fh46s5t4yqn nostr:nevent1qqs270vsqqtjwjyswfmqyldjnmnvrrp5g5q7wh3k5qj8cuhljwn0j5c8md0u6 nostr:nevent1qqs2ypcx6p5cqe8dqqmrm36qvgucflgvss885r8czcal6zv0axqdr7sn0x2df nostr:nevent1qqsqvf477f73gm2qfkuly89sy4sadju6wh4t6dcqgh4zwr8ds9g9txg9gppkp nostr:nevent1qqswnmvwph8x9xnqr4n6ytxnfz8nl89a7hfrk2453ldxudtql3j4yns2fj3hs nostr:nevent1qqs2ecqgkcgmlvzj90c8trmw3nld0trtuujnv28f5ezt3huhvvtegmcagpf0y nostr:nevent1qqs9s9zkznyxu6qk7svajntw0v02ldr8462dgt7n5f9slq7aleycsusl96zph nostr:nevent1qqsp7nux9qjzsx4ypcrjexrz25clr9586ar5n5ahc70r7yhakzvaeasd63ulx nostr:nevent1qqsp5gp2xg8lx4kneqrhv990x0velm85s5u2jmggkwwzt8yrxygdc8qgfsp3z nostr:nevent1qqsxdt30myarjhkprzt8xx4kfy7fhyjxshaza0z52nq0pkgwkqguhugt0jswa nostr:nevent1qqs2qq3wpva3lt07xrde3y2vehqy0cwyzye52cvhjnlyw5x3rghsgrq93jycs nostr:nevent1qqsw0959762aa5pxz9hhaa6saszqrnqjrr5umtl5kkj00prqka4fc5qnpfek9 nostr:nevent1qqsx5htpawdvx500074r0skyxhrezkfs7rctuu4afp4puykuvth9kksr9dc64 nostr:nevent1qqsf7kexs3s0g0f4dzv9c8qdns6jh6e26qvecu59d579ud0fta8a7ag7pss04 nostr:nevent1qqszkphl8n8vtgfnrpkudwe8nsm47pm95ajy9a7cdaz3k7shadjynaccpqzv6 nostr:nevent1qqsgrperqd4nrjegephrrdcj0qwkk22glfeq3msumte2evup3f5f29cv9e5vq nostr:nevent1qqsqueyp46tjgh4s6fc7af8r6nnpdetrutmemalfkk0ruqp93zt4ltc3hdj29 nostr:nevent1qqsd34zcm5gm0aws879q9t7sdm7r7rvd75sj4uzxxslwa25ffay3pnc4x9wmg nostr:nevent1qqsz233vcgpjrtkn03kh2wv93jwt0m042jpqp06uank9vfummhdrqxgvq0hnj nostr:nevent1qqsxdtchwzjvxvml4h27ta75542vgc6zpdtzeuma4hrz55v9trswdns9dpxna nostr:nevent1qqs922qlylqjrmr3uaj0f29s82smytg67cxcl208memnktx4h7fhhxqd2wzwc nostr:nevent1qqsrpzxupddee90chcj8psnlhhd8s2r68tvz5u09u7u46wj5a0hyyvs98d2z7 nostr:nevent1qqsfkl9ukp2gss96ut95rwyg3gfcdft4qnkzjc6mg2x4dnpxsezwx3g7dl4fg nostr:nevent1qqs03mv7zygd5stzm6mlh3v57mszuhvnumwfpa94m2axlwqhrtyjfacm9hfaj nostr:nevent1qqsg0k2f4l79804jydkq3ryekkjk95rcysswg02ktrg3cftwq5jnvdc6pcn0x nostr:nevent1qqsw8fnh3x09dj7m4w0engzftejh5pq0dgjzcr23erpg38kyvgz6taq9hg083 nostr:nevent1qqsycaw0y5z5te9r8m3sx8cngczuc0dtzcltf6khwgwhls4y3vxv7wcehkkgx nostr:nevent1qqswpdv0jy9ag757st0c29efprl6jttz3jvrgaxg382txm4r38shhcgfnzhvu nostr:nevent1qqswzt4yac0p8536j4venvexgt03shq94xnsp7lmxuy0vq9wl9dj69qqtr6tg nostr:nevent1qqsw5p0cm9wxvwjlv3z2kewze2t4lw073h7x5lql0g3az7h7jnd0pagxxsmwp nostr:nevent1qqsz92z4pa6zdhhchrygypy39x3j8u4mv98dflxmsw39dyuerfgy2xsp7rg2g nostr:nevent1qqsqur6s28xh68lzft7k6suklrv5knjp4hysunyr7g79caucc8vt7yq6kl0zd nostr:nevent1qqsf02sunq6yqjcpjlm8a4ku8txkyte68gmtvmhyez0lx424cxk65zsv6gk3q nostr:nevent1qqspexe5ew6dt7g3ps9tk2cd345y3jd0asfuyj8pgxv4m5ywqw990lqyhzv9m nostr:nevent1qqsyedkwvv6u4ludqgz623ftuj4mncn5c3tzf533q6xgc4k5xgn435s62yr3l nostr:nevent1qqs0qr3al6we2zeqr4lrkz6nk9cp7cvf9ymt06khw7d4377k7ar5n2gxtem3f nostr:nevent1qqsg5x0qrjk38xpmxh83n2wspg32gwwr4hxqjsc6xz60wess9efy4eg6cpn6v nostr:nevent1qqs9swl3twdd9zjr55gsq43gctczv4cjn0an58gn83wf3ujquu0l7lcff4ma9 nostr:nevent1qqsv9sc8m3e36a253p4jg5am9ay92ncjnx9nttsh5ss37ndr4znu97g0lg0hz nostr:nevent1qqs90fava6xzrjhdpkwld3utw3xl6ghddfmlu9ceql8p82mkv6luvwswptxe2 nostr:nevent1qqsrx0h5jz7vjv7ul0w30rjqzg0eey8r0ff0k9cf8jfcjjr5a57kg8s8tz2qy nostr:nevent1qqsfwln27aduh4yw80cqwml5f7vh5z6v7q80gxmrv3a97x8zfw0a7us40qsmx nostr:nevent1qqsyyl03g27p9ekau4v483800dwc02sfeay8txxn67mr3h3zt476sdqv7dc0g nostr:nevent1qqsgup96lkscndr7jdze308kt495s65uura9vjl8yucfcd0depzpe8cdvlxjr nostr:nevent1qqs0c0zwxpfv4krj0vfku448tl3jpudw56nw4wr4whlje7cexauhd0g6zqjxn nostr:nevent1qqs0dvc82lc2mmzvkmqtcua7kt0vwz4am48kj9sq0rk8xpsxjxw5pgg4qe329 nostr:nevent1qqsxzttj97g67mag82fww0aglmvt5qwvk59e7euswn3nmjtpx5j6thg6c3nz7 nostr:nevent1qqs0gxfve8yz6m93jaseldl8xzhsmpt7k3gkqlv8xlje4q6aqjnna0gezcl83 nostr:nevent1qqspj6puxtaj06z2shd9nr82t2rwwmh6mszapee4gjyj7vra6pwfj4q22x99e nostr:nevent1qqspcrj2zg0jyy7ardz4kt4d5n95wz84jl65hmrdxum7nneeglwtnzcxxzdt7 nostr:nevent1qqsd4ddx493uj3wuxscwfjl9le3f7t2f78yh385666knu26vr9luz4gwa0w24 nostr:nevent1qqsx4w8ztgk5m3wz59mm0sqr7nyzx9hzu005vae6kqaepnpxqw0svwqaq9le0 nostr:nevent1qqsztgtzz4nqf8znh8u3q5fwtnx84mzrjur8gq6dmg3mj2kn3ugx2xca4g2nv nostr:nevent1qqsv6m42nk6uerh02wnflytfvj4nuj0sp43s9lzuvd5thprz9k7jjgqgywnf9 nostr:nevent1qqsvennjay5vvk40t99jwnuefa4lw6zuhya4mg74fsd0klrwyfwjjus0atnfx nostr:nevent1qqs8awph7hzu76df5w8k4xx6j5wmc8tnddxa4sfwnuruea78wr4tg8c47rsa3 nostr:nevent1qqst2222z58smd36lltudxlme8fpyupg8t2c34z803n668t5pmt0ypgsv3ryg nostr:nevent1qqsvjphy6fz8ae244jzdha9xxmz2jcy0pz6zfcse626t9ms5xlcyeecmpdyt6 nostr:nevent1qqs93ghgzxt4ywr404yn4jm5lx8m7l964mmgqtl55khza7jfwsk3klcyup39u nostr:nevent1qqsq0lhuuwewq2kgtjk44z8wnuhv9x0lrvym08dk5p70zk3l9gupp3sv3dlrp nostr:nevent1qqsyq8u0tnangar2w7ft0cfzwglxmwk7kkczpj8k7wqjnasz3sq2sgqssvy50 nostr:nevent1qqsyh3f6lhft7mxmf57v68ypfa4j5fdkuvf43c9q0g5w83jtzwsg86gwhjqtp nostr:nevent1qqsysgrlqjk2wayzw0dymw0r0wv30lk0c5qeagc8h7lmulyffj75clg4t4anr nostr:nevent1qqswcpe2hfr6zk46p0jv65kl3wtp63smv6uxe6j4evsav9dlcpe7xmcx9kqrq nostr:nevent1qqsxv5tuzmfjm3dcz05xng5e9gl6e7vqx84h37p83d6qstzx3hwqwlqtw59hv nostr:nevent1qqs86k2c9akxtzvw7upchwu4pnesj4ds3d3fsg8m76mjdpvj38zwcac6vud53 nostr:nevent1qqszltfvvs22flkqd2v9jzuu222nq9jud78z5sjk8z6y7jmqnd3f3fgme3yek nostr:nevent1qqsrglucq53e84kgkaa2hsq6a5xahraethlykzx6znymtg4gvxenkssx4un3a nostr:nevent1qqsvaq0lwefwnrfkvmrul84fneecua2g7eg8henlkuht0r8u0sp79cqqwt7s8 nostr:nevent1qqsfrah0av2l3dc7valuqklryz2a687t7cenharuq7r6xelm0e0yv4s494vpz nostr:nevent1qqsrt7uykaetqwl2q90x6kd5xhgh6apn8kz7gvy6hgsa42xe6qmqgxcmyll46 nostr:nevent1qqsgl80erg8t5cqdz3wnxzd2g6ekhdtm7rt3nxszzvzxft7v7x8lqgc084p04 nostr:nevent1qqs8gsthklfdzy6fku378tf6807qk86kjcgrgaavrjtdffh2e57la8cwltl53 nostr:nevent1qqswjgler7slw0lncaxhtne5kz3np3tu5umdef2aqavy5atq0tvgm9gns8h40 nostr:nevent1qqsr2ka8n6zv0z4mk6ty9nztqd9qz8rkgt6cjck4ce6mtpm8sxupmsqj7s257 nostr:nevent1qqsrudy60t40q9vup3p0kxrrnlllwnwnyh8kt4x623d3f74jctpnrvsmd8zam nostr:nevent1qqsqskyce40lmwc9v94tkxy5phnzf4p55q090g02wt0x40czw8mkk4svtu7a2 nostr:nevent1qqs24dsj4x02x80lvgtj3khkcqpqv6qyypfse2676et46phrztxs75shwde3x nostr:nevent1qqs2cyspyllevj6ahmzep5jhlnnfc8448uh3jn5m2qfmn8y3dma2qggcrtvve nostr:nevent1qqs0k044ntscwad95k8347wuflpchrl0aszzltfyp2nxpv3g6kr2cass8k459 nostr:nevent1qqsqq9cce7umtkm9e3588n7nl4y3dktlskssapph5z6004hqg9setaq4zcqr3 nostr:nevent1qqsdsxzfqhwxg42a652t4234z7p703lwrulfnz9drsus8erjvnag74c3606pt nostr:nevent1qqs0wjxh4ze8xfk7sec3zu4cepwtwexqty80qpvp5nxxgvutk9lqydch9jzp4 nostr:nevent1qqsgavz69cxs6mx2y42j4qnqn7q5xdwvmnaae2tj2px8zdep0j8rs6g87hl3t nostr:nevent1qqsru6z84jtjmycunulyzf5ns3rq0dweseseyq5rxmuzvcs7ylenu9sykk9re nostr:nevent1qqs2kxhn4sl0p8wyxzcv4gpqqwztky37p2j22qhpjqgn0cy407yn03qmsctfx nostr:nevent1qqsf7ug82cd5c02jkm7uahc4p7kc8j32q2dgvuun46ywmlfmrwu6xns3r0egn nostr:nevent1qqszckunp53566u6grgw75gy2c9ce6902zd3jp9cfg20paq66lxxdjs9l259l nostr:nevent1qqs07qw0kashdjyxgj6w92p44hnd3l9jeamxhc63fkdz9cr8na85pwgqlset5 nostr:nevent1qqsga4g5haatk09u4vkm6nfmw6ngctg6p5jzam5kax27lcnc74vcsdc5fwjjf nostr:nevent1qqs8uu57ukvxfvve900uvynudvazpu8xuw7zvexkctm62rdgtpu600qcdwg0y nostr:nevent1qqsgdc297tvnh06kqrg3e68ftyu6prwjqtvxj782f549jugart2jc5gqcqjyp nostr:nevent1qqsqkus0qg7nnl5jkjzhugjpd6vfn70m0r7xtpyz3mhq9k49unuwg6shprvut nostr:nevent1qqsgxaedjvy4s3rlfg8235c7yh0uxc0e7n967p9j6uuz90tzvafzy6qrmcrwe nostr:nevent1qqsv2j2dchuyajecmrqxv9pra3cju03fwkes5qy3xrjtf55twjmx64cjvx347 nostr:nevent1qqsqmnnasdsf5zmqlq3alycl5r2uestvx5mshvnl56fdjk0qx4t2hkgnzn7ww nostr:nevent1qqsvdm79znu685uehrmmegcmq836jj3qeqtym8cv356wx8y5tscjg9c0dvw4y nostr:nevent1qqsy8wx4ujy7z3e6svmz72zaapu7xqx7y4xsuthuk6ynwkzfl9u92nsl42f8c nostr:nevent1qqswccl50t2p57wdfam07p2lvdqzxeg6dzm72vrjsf0xjl88uk03m4gzx25jj nostr:nevent1qqstv4gslzxfte85yckx07fdn5phluvcnj7a7pf28j7hgthkngs7fgqhl5fay nostr:nevent1qqspeada7h3749ex026n4gp60pkv7rtt5nzn4p76dyz9vfzyhxp5puqw6uech nostr:nevent1qqs88tlgk2gd2dsf3mre36e5nurg8afmynkafwlj59p5295wq2dycccjtp7l7 nostr:nevent1qqstu5z907epgq3rechx0ezqyge3uj7nm2j2ty93hj9rwuxxzrljffc4zr0qc nostr:nevent1qqs2r67wggz466rv4kh3vrhyl8e4t26a5s4tq7wgfrglghnhcw47n6q9mhltw nostr:nevent1qqszerzkulum87k7ykzzg0t7wa2lww8ttt7xlu6m385hl5p07lsk9ych3s90p nostr:nevent1qqs804wfmxcdt6gev9qmyasz7mxq6m8k287ulsfz39umqcgpqqf2jnca7xk42 nostr:nevent1qqsgusg06zl58x44778cskde5n8uudgwwajfdq28nvq38kt8nwsyu8qyw6hhx nostr:nevent1qqsy8ecclr3p6s9r7d0ge060fsc6qveuj8509nkndq9stzp4aslejuqw9j892 nostr:nevent1qqsyxns5ze0qm54f3nhpc0dygqnq60e2nmmgpvlhkg99zt2fp7umedc7latuk nostr:nevent1qqs27g6c4vaqxkc2gvnvuged60095fwdsk4e4ze77ylazg9lgz0mlng67q65m nostr:nevent1qqswcy0v5pn5v9wx6uzln6nr4nl4w5d0c688gx5z3qhepswmhu4zgdcrvux38 nostr:nevent1qqst3l22tc9thmnks3nxa9lqdtejktk44ved3xkyqy34dzuzcz92npcdvgtlr nostr:nevent1qqs0jnryazxjjl8g3hxw2xh4fastfy9cu47lpm2qgh2fc6tf4d78sqcphuvzg nostr:nevent1qqsva8k2qn9pjm4wpg879k37f9hxtrpa6twa4ck9uf33e4udzq308rsavs72j nostr:nevent1qqsggahcy8q0zgyvjdpxpljykjahjsx4tkg7z8qr6m28y0hjvfkredsyu0tfj nostr:nevent1qqspayr6m5dcevp96sgew5zn7dye0gm2lrvwmlhr0nlv8kcayarlp9qlntm3p nostr:nevent1qqsdssqj635ee355wdugls0lr7hgfwjjxdzr3appz2pc0wrsp228wrghtxuzg nostr:nevent1qqs0end22ejwqry63pt4yq99ez2jsxj2d35kpy3dfnkmsdx8pk53pjcw2qdwy nostr:nevent1qqsw5t6gr0svp9wefrve6przj6hqlkp7ma787ac8tauxwtc53ws2a8sru5vm9 nostr:nevent1qqsr53vq37g7mm6chgsafpgn9hscgaku6m00mu96d05lryqx285k0yq7ujhye nostr:nevent1qqs8w3ds968pe2jeazwt3ra5y6r3dlgxqgt0an7fd0zy7wm2lkgc2ucahcjqq nostr:nevent1qqs26szux5exxukg7ht579uytrcs72j2j9h2xf4dwvz044jpntsynagqv9sdz nostr:nevent1qqsrej9r6kazt3eda4hhu70tkax4j5ft9l3ve4apnh5u8p9ltj6allgmn68a7 nostr:nevent1qqsq64h92pdffc50xvmlwdfyms802x029qf5pe8fwlu9n4v4rg93t8gfa7kee nostr:nevent1qqs8hhmaww599xz682l2hx0uvn4sfluc6aa7lydk4nugxejqjeaqeugyg0glt nostr:nevent1qqs832edsy9yxhq765zfummutc0r54zc4xj7n9lcuwcf60c66q494zc7tlqgx nostr:nevent1qqs8etkcd8f2aw2s7efjdsj8w5ch8r8ej9capyx976w343ps9sm7s4g0l37gr nostr:nevent1qqsfwaetdhzn3z6fqs50usmktug5v4stcet3lus70p5hffjq8kcpuhqpu5ef4 nostr:nevent1qqswnvtzachtgqc9gwqvcu4s0mtmwxnl78v544p22u6cuud95s2jgmgaz5glx nostr:nevent1qqspmckx784xjj7mkn70tu6rfnyq0kmpcg4p8jr6dmlh98um8dcqnvgj8n426 nostr:nevent1qqsdxeatzq42tstmculgf62rhj84mpgfzsa54gjsh4hrl6e64jv3wfcvr8fec nostr:nevent1qqspcksa07zqnc0xf9h57mpvna4ke5fd5g8lw0v6wycf980lhh9fzes3k5t94 nostr:nevent1qqsy8kvy6s5spzhyfjvj6lzesj0ynnp5d30pqzuwe93d2t3xmrl77dcjz5sfg nostr:nevent1qqsyh342up3pkjfkvzr0yjaxtu4qg5syquz93xyd6fgatdwqxy8e7mgklaf0f nostr:nevent1qqsyp94g3puhpz0k9vaft8tvpqew024n3asxpklgnax6fdsu2mu4kcqkq7fqz nostr:nevent1qqsznp4zqx06tjmplxdr0q548f3kcn7pj4hvf4g4rgm74yk62c59lnswzsdn4 nostr:nevent1qqs29ffntcwt0t5zv7ecrzjgpd6v2r0nqwg9ymm5luhehgrzhlr4f4shqhwee nostr:nevent1qqsfrn6h3hjk4zrs6pamcdzapap0gvemrm2akxlur005chgh4vaps9sx4y5sl nostr:nevent1qqsql32xdfshaa73ex68fz8e4r6e0lhpcgsgdhczwfsq6e7lqqt703cuhue8l nostr:nevent1qqs952dv2ycq0a2tdvyj7st7sd87pxzh7hceth96hhhwjq7gs95m5ccdf764h nostr:nevent1qqs29kzdduhtv7v2gr40nhzkykls6pwmn9maspl2qs83gqkk23ql42cmxwq3n nostr:nevent1qqspwpz06fysr7xqyjfxg296e5d7hcycp3wkmladpe39tkwtmyyaprgycny5j nostr:nevent1qqswsj30jgpyt623gqpy5gk434xeff94cwqrpzpm2tdznhqlvs6dghcuxdx4l nostr:nevent1qqsvty7umlq35gydcj4n2tmzv334yuf5dnw9p662q22rzfq5yhwpk4gz7fnyp nostr:nevent1qqsppkpezwkyfezakg9se8uzvx8j6z33e7k3f4xrpad378m5jua5z4cms7k8m nostr:nevent1qqsykvscexq75xect594xvyp0yzlstagqa62kmpwr94wl7q0exg8h9cwfxcmz nostr:nevent1qqstfqwlc8rmrqrhdt7zdd082eehssdt4r66h3j3ns42cxvnzjegfrc7qr8wd nostr:nevent1qqs0prhhhyvtz3fwwsu93ndvc6ye32zp885eyg6rkxldc37f0jck2eqe3kqr2 nostr:nevent1qqsvr4nsccw9dehyettdc0tr4t3yycvldjxka6cte8uth5r6xz8vhxcat20d4 nostr:nevent1qqsfkxvh4h3ga60l3w3x5ngu777up09sxrqdjgkrnv3yzdhdn2ljsnsylcsge nostr:nevent1qqsfc83pkdtd4jph9r4hjyc4xqczdcem3ytkvp732zalqkl8jhxaq6c26cp54 nostr:nevent1qqszd2hpl8h2uljcgqe0r4zqrk9v0us4nwu5x03v02cx52hkgrlykjqehsv2d nostr:nevent1qqsdz3m0pc789hk8vv7ldhwnz2ydj93qatn5t6g995y9nqkylcfh8hsex7w94 nostr:nevent1qqsvpr85pg2gammm3fqzhw8lme342mplaau3zeeku0up372eps75cfssvpzkt nostr:nevent1qqsq8j9f0vg5an20rdxfpgylaslpf6nt33srglu9f2pthesfqhjgy4s8w3qmn nostr:nevent1qqsyxu3dg4fprxjc4rneslkgucnwx5h4sc7zvd0w0yydkv2hzymletcksa04g nostr:nevent1qqs08n09gvne3d46y8dhxhv68duzvlkwmg9mnv7467cz4x5utgu3rmc0dcuny nostr:nevent1qqs8tcakcm8dqnzef535ylh8j7m5n98s5qu2zydj9w8d2kfa5mgsv2ccpxcqw nostr:nevent1qqs2sm3kfej6t258k6su7krggu362slve3m9gayjyskgvwt0m49ahdsgdmjnm nostr:nevent1qqs8dvmywjutfgx5cw3r9h355dmfufsxwse495svdx79kq820g2u9fgap3umm nostr:nevent1qqsdqram3x44q994z4e93ufqqav5dwa2la28j4fmwqr5swympy5k8esk2py04 nostr:nevent1qqst0vhcp4sy6h7h6c3cfe957z9pj48ujvhw7yhmgjjmqe0d4u5x3hq45hqan nostr:nevent1qqs28z599avfsddedq8dwulzhyhqggs9wukc6jqdp60fp0kcruck7gg048zc5 nostr:nevent1qqsptwc7rfkt7lhkvwz0h2hrrwxj9v0kak9dqg0lph3pfsxq4mna8ac38gqdm nostr:nevent1qqs04rh8vcey9p78kjugs9xvlmyl5m6043n6turhg0d6xrnn745y5fcqkes8f nostr:nevent1qqs0j9h04kfesvcqeax0ynawe7g7j62jhdanmzp0eal57ayqhgn67qqvs8d6h nostr:nevent1qqsrg4gvrwhvj3np8hqyyl6nsz4twjnxdy3wtd99try3t5pkz07e3pc3sn26m nostr:nevent1qqsga3tc0kc02g726fwrwrjm2e5x7tl3vzmv80sd2as9ywht58gcztcgfcrad nostr:nevent1qqsr5srauwprlzlfl0gxnfkaya0rlqwusqnrnkjzmta03kqxx2xc25s5ctflc nostr:nevent1qqs0fjpmu9w0dgc4a808vvals2j23ny6lrp0u0dz89w5mn9749xsalqva29uj nostr:nevent1qqstrrhjlp5h0qetmyll3dzg95yj4rr0m7rzfvp4f0yla2f3g5uj7hcdkkep0 nostr:nevent1qqs9p5z3djta5r223lpdvjgrcc9y9vcm4lsvj69zqfuhrgw3zqeapccfk9dcw nostr:nevent1qqsfrz8sp6sk0u75zwfskwxqgk2t495ymf5fqtalwdptagrx85d0yhsnejvgv nostr:nevent1qqs9a6ujeew8mzmuh8tewk89cv53fahgwyl552hq2qd5zjp5dccc3uq34j4s4 nostr:nevent1qqs8rhur5klw8pfu32nrqh0cp8n6fwgppvpjzpf9q437csc48x5gmmsngq8hr nostr:nevent1qqspr3sgff05240mlyg9y0j7x45qck8x7edzfeqrdafc9l3jwl490wsm4ll68 nostr:nevent1qqs2vzfrp2082gm88uc34zh7pe5zqypgsxkhed4f2aluep2265955vsatghhe nostr:nevent1qqsfjfaz8932tlxz9gqppvmvk9jpqclp6ejg6cdk488xexp5l8jn44gslrmke nostr:nevent1qqs06kyqpy4y6p24p8rpjc728hzn5cu5yvg57nl393t3hzhs4zrhmdgx7s02z nostr:nevent1qqsw5ez3ew4jmeuvz5tg2whsggqfn4097du4jspawxpun375njduxxq4s79hy nostr:nevent1qqsxrrmedupcnyjkv9azw656c0h70x7allk6kv3wqcqq2enar97xc0qmfsdgd nostr:nevent1qqsf88gx3w544ukdxz6wsr70vnhx42ruf7mn6p93e57jqpff4ty3adcgsu5sq nostr:nevent1qqsg7tef7jx07yp4udwnr3mhk4zc9ckdymqsre2xcjcu8y3ejszk0yqes906u nostr:nevent1qqswmqh45286p5uw83kcy38e0qz65xycn06xlwwg48g99kn6mkmmh4sn4nudp nostr:nevent1qqsdgdmdrnk6mf4rcfnqanjtptkazlkry3dnv5wt49znt4xn2ycyvvq2hp8ke nostr:nevent1qqswyueph6kfgwacrdhttat5pnk732m7qcsqt59sptu3cux9hzjw3scte3kfv nostr:nevent1qqs9gw4n83hgclvurawkhpqwtfdqm257kgkzve9gf6gx6n8p0k46acclzglst nostr:nevent1qqsvf9heuqcsxw05uhmnu67884h73mhq27rcv46lhdjhvly9e5eq4lgsalqhu nostr:nevent1qqs0s3mu4k6wey5zjj7rrff26q7nxpt8r2d3qex5mww00dpfqdltpvq56r5nj nostr:nevent1qqsty4e39zsmsax4m5m06wmw3fe05tlkqujk05k9d0sdz053zguagtstnfgu0 nostr:nevent1qqs9rz3at95dava3wnp05wdp7f6s7kl0rzfzpmm04ahk7a38akspzdqw7slkq nostr:nevent1qqs0vwqx7edy8z7m6sr4tjqjscgqf2fmqynkqequq6cp2cw98te5ags908vau nostr:nevent1qqspf7ms32mqyzt46jss7e2eurk66p2j0kdjt4mxx840e4fnfmd0fpgpnanv3 nostr:nevent1qqsfjtqrw4wmzc926gzkmval7s99p0m36vkkag206y25r0yevaw5dqcvk53zu nostr:nevent1qqsdhhmptxgvjxv30r3zkg48kjangs9u9yyfncjs7j26y3xq04r0e6sgktj68 nostr:nevent1qqszzmmc2krvwn6auf9nvhr9uwau66kymjajwzlfukq7evfyee4ukecs0kgyy nostr:nevent1qqst6w7u8lhjzat6vdl5ys7m4dpr2dp07kqrw6qzflehkd2chhu3u6qlwvdha nostr:nevent1qqsgl48cu28690ns7endh3es2ydjv5wjeexv5gqhjmhmgj2alp352tgdzzss3 nostr:nevent1qqs2dzyjlj99mhxznnuvhlqrn9rma6ydatj63umwaxw7yzvlltafyqcv3f9mz nostr:nevent1qqsgu088v434nqvnnqrsltnuvhh68698gm5acgmne3k67lh48au8vtc6ys0jz nostr:nevent1qqsvvp5wg5mrnc4226c9ukl7kydyd4v0zgte24nff9l7qad4wx7xpqgc2x3h2 nostr:nevent1qqsfwqwgttstups774qu448437tn6wx9ffw7l5w5fu5ljs5s7efh0zq7csjfn nostr:nevent1qqs0n9gqdjrant7lx2vd77023kh9csr256apwv2f7lsucewuz0kzwzgtmxda2 nostr:nevent1qqsreqlk6ncm7j0zsy7ym2kthv0mc93vgjl5l5jkn3s083ztswsujfszcyhyw nostr:nevent1qqsznlsfkf7ptq4rnegqsd0uvz38mmtk2eeshkmw4y7z2klupzrmgqc2rhluu nostr:nevent1qqstfheaq9cfq96w8kyvwc4herjnt5ehru3zen2yjfh4muc8zx9kmtgehnpyc nostr:nevent1qqs8ac3g79el94kgudcce80h6j6u3nnwagh2rgh87fu0ffky09tx6ugsyxd7g nostr:nevent1qqs0vvczfx44sk9vx7f7fd0l5d8nu9jp9mgv8n0n4rx03ytsx9rh64cml8am0 nostr:nevent1qqsyrk88pql3s2ue85cuwr56pude6f7ay67ylymmtezxdl855tu0pfc2sdwre nostr:nevent1qqs06nhur8vlwf2evmjt2fujamcka38v5krpzfs0yh0n7lk25vtj03ct8nxy4 nostr:nevent1qqsdetdugy6me4l44svtrsy4nc6lsvy8fha9824lca5v9ejdfdasclqd9jf2t nostr:nevent1qqs22th6z0g63dswxjxfwnk92tmpzafec4p9j93cw99tvelervzj2ys3lrsgf nostr:nevent1qqswyktlpagzpjfmv7ldtgkpdzt93zt76s04sa96ngkl976wjpm3dagat2pny nostr:nevent1qqs9pv0457acvajt7ln7tlq39nhlt7tcn4u2l8pvmtjm0f3n3ueuvggxtjsq4 nostr:nevent1qqsztv6rh9s3mx3h237nywtz3z86w6ydsynyp9nzyu43qhuejx5kj5cmc4sv4 nostr:nevent1qqsdu6aqu9y06pw9uk5zah408f5whnuunc3eafmemh5pfeyh20gwc9gr2m00g nostr:nevent1qqsdctkdrz4d0vnendwrekj9uhfw4lkxfjny2gnyrmjvgn0huj3u2xc3aavvw nostr:nevent1qqsp477v4mk2d4qvpj4xt6ua43rj53eqs48qk6jh7lm4c300fq6nm2qxmqz68 nostr:nevent1qqsfgl3x0mv25ytjtr0p5vq2acm4hhnmuxynwxe9a0whvvylsff9ajg0r6du2 nostr:nevent1qqsyvy3qd2hg5tmatgzgzrw9nuqk7tnqtuzzvxhfj7cf9mn06nsq3psxv56se nostr:nevent1qqsgx7lwjaj65ey59m42lvquam85l0vxvx9fcky43nhff3fxy8t7a4su60nr7 nostr:nevent1qqsv6g20rdeq229sfanduu2c497gp9gttejyd9hcpalm4u2f6af3gjc8ynpjf nostr:nevent1qqsqqrmzka388vxuq3ly3urust3svxr7lewxjnhul6v2f9na0xwr3ncxu638f nostr:nevent1qqsxdx9heupdzvhepkq52j0655p94j5w5z72hsy9dcst8h9dgcnq82qwssgfj nostr:nevent1qqsrdvpmljkwdxf4m8jj3ju63w7f42cy869ukwhmgxk5u47vr9q4vsgg54903 nostr:nevent1qqswyy7rwkrfv0q98tdhv43sln0m6gt2yy585m5km70ylxds76g9shst6r9e8 nostr:nevent1qqsw2e5a6hn8hca8xe0aywrgrgd89800xy8680f7cmwc9vtnag47jwqxplvu0 nostr:nevent1qqsywxjm4ay8lcxqvrxqvfgfcfsck29w67uf6fpwas0u2vvm5e772dq6unz4j nostr:nevent1qqsxa9w7lyydy3kxwnnm0a8w2vzjt2px7xklegw2apyvr68wgeepq6qjvmm32 nostr:nevent1qqszt2x6zft0f39yxu2er5qhh7z09xh67kcas9cunwshx7pz3w2xlzg8w6yyx nostr:nevent1qqsvj9q04sw0hlwvfc9ul7yufjd8uy9v0zlhlplr36u9r9t37ffl3ggtx7ard nostr:nevent1qqsgwj2umphzxm82njqzqhm3ujhyept9wd5pvxyzl0u8yctvh4feugcl83uh6 nostr:nevent1qqs93wup3yx2l85rs427uzucujaym9xpkrq6frnhyl8cd9rl8atp6hsak3a3t nostr:nevent1qqs22gxegsg8jwqzptdu9v0m0z9a33tnr42asuujp880qegvakdfasqzzz8tn nostr:nevent1qqsvx3na0fj2k5z9n9jjmcfnxjscq4j58mhpk9yd5ga29z7tq5rayug2pd030 nostr:nevent1qqsgalz2tjnszu03qja9tqmh3fnfhmpmdav9khcwh9506wq9dx50s0gqxe550 nostr:nevent1qqstd0rl52dcjacw8v072e40kc54nyygv436fkja6k2npka0h4x8qhgg87n9y nostr:nevent1qqsyj0hhcgdj3s97zvdnlpwktru2e0f6g002674spyyektxqxky5mpsqym78u nostr:nevent1qqs8tyugskp6gyl89qeynpjp485vsfpltyqx0v5d6cvuacv773q9eqquleude nostr:nevent1qqst2u3y6w830ef6a3sp66gxceryenl3k36ch36mvl9e2d6jwfmgkwqkv4v3e nostr:nevent1qqsy8qhhxhh36xq4kaksyhxm2vy7vuyujrjdxu9m80mw889wx0va3eghz6xc6 nostr:nevent1qqsz7spxfkrzawcwge0hqt9l2q6kc5fc3s5h7pcwj8kqmdtgwsft56q32ezp9 nostr:nevent1qqsrtj4xvtx6tdjv4zmm6axugf29t8xrzp2nmdyh09rzfmaukzp79nckyr3p6 nostr:nevent1qqsrthfeuwsw8ty32lgk6jxqnt2mcr2g7sajze29tyztzys0lxavhkgn609w9 nostr:nevent1qqs8afxujdxjw2jcdjtfsmux72xufzwhhvtc6f44e4yawlcygu9mhvckpdr2f nostr:nevent1qqsfuz3xezyq9e3y99wz6u4z68e09ult0urcyk80rrd4w38jxrcp08gh2hp8f nostr:nevent1qqsrc9nth6vef28sylzxsp7a7ydzqq3slsuas2ydcm4chz76erzpy3qu52mes nostr:nevent1qqsvqr903utwyynxkqyt3nf4jd3gtk355t0rfj6vec6yfp5huqvu39g5tt923 nostr:nevent1qqsgs0alua2ftak3yjp2dkvaxtxk59q8jr6fl3z02z9dt5ecalgjsmqyvpnz8 nostr:nevent1qqsx7sg2tshm7fgku6y86krp2sfvk7evua8mzy86agqfrwphtf5zk9q0rszzc nostr:nevent1qqs95ztf6g0w0k88d8ts5zcc72sw2f0lc0anhcp0f590sxrya70vlas3p0fzr nostr:nevent1qqsq4fsrzz7r60qk7lhmpq9j3e38edee4uuuhqnlpgw90dmqyz3jkscwh3emm nostr:nevent1qqsgnsekfcu53ser5pdnrfpwghsjl57r69xdgjnrn0qxflrvwhv0yxcnw8yyu nostr:nevent1qqswwf3wnj082vrpdjzjd8th0lkes6rdvtzgx0wfftn9398hajvypqc7fvpxs nostr:nevent1qqsyjdhjarz0dmpzpqd0ywhmnyenhmmy28lwj8nkca9av3fxme3s4xsc459u8 nostr:nevent1qqsyqkuylp78memrx58atm4pjggfjpnqmv2z6u0unngpgm89xrp7wtg0qtdus nostr:nevent1qqsv9sdnzjpk98ezcldylxmp7cr5207uxq3em0qdq4mxlc9rw3uflzgsra6wt nostr:nevent1qqsqalxng8fyvyzm5x9rvmu8f6g2mc4fvl42s8qks3v23admjjva9rst7th07 nostr:nevent1qqs245rsx9q22ycamy0dcm6p8gmawzlwj8eq9lp6v0kw96ssdzs2zxswfywrz nostr:nevent1qqsxjvyqjmy9h42kz5pud7uhl87kj3ceagdv4pseyjgrst9aj4r45nqxpwv47 nostr:nevent1qqsr97gg0jm0f87dqvt5dq97jx32uj004lkvapvkqy59wspuytup8zq6skp4k nostr:nevent1qqsy7xuzq5dewwfwrvwannr6vvdxhkxg7njjhqd435nq2k4vcm2ecns4d0agk nostr:nevent1qqs9e5ztm2fhqzm0283u2mzkvgnuv94cvx2h8p0946ch75g03lwr7xsg8mqt7 nostr:nevent1qqs0fvyf9w00k7cfdr7r8hptptx5t7q9gchw40twx24l4e7jcuv605gq34ugz nostr:nevent1qqs9zswmvckn4tke053m9tvhurpf7pwuc3kq82evun9vmvczdz9r5ec95k43c nostr:nevent1qqsrxpxjylc2fjtvwjvt7grk5ae5mwtsp9frkemm2lygfhqurfnfqwcm9k48f nostr:nevent1qqsw6p2j9g9yq0lh3d794nt20flzms2nyvq2752ypfwj2rnlx5sw4tghd5rvx nostr:nevent1qqswrv27dzmtavpcz6d9aphrg8anarhv7jvzfw3twfu43j03qahuc7g3j7pu7 nostr:nevent1qqsvqjgqkw0nfj0yph2ahgfhutw28u5ntyv6s8sz7lxn4jyg6mtw99ga78gwz nostr:nevent1qqsgp93wmz9uyzmzwunh8zvaz8wndg36x04kryw565fwgs6glprlfjqxu537m nostr:nevent1qqszrqjw83xkxdwkp9k45e5fnulp7gjf9ct5zqwxuy8e0mdx2r9fsrcdyay6n nostr:nevent1qqsdyvrhkvdwz6m73sckckr4esauq09u9dhphskxa22kl408gkpmdmg4f85pz nostr:nevent1qqs9g7dhjwlnludgsnkutdf2mnuc4tvagn4jcg7z4uufr3h2w9jd5zsv777kv nostr:nevent1qqsgdwljd9dynp9zd6c2c5l6fyy0j8sh5c44tv55rn5l24lfcq0pz3q2r0hmw nostr:nevent1qqs2atfxw3lzqtawhksqdvzqx7qw3xgp30knlks6lp0rtzhhdczafdqugctck nostr:nevent1qqstr87at5uetk975gwa26evejf9uuhdja84uc602dq7u3ktgfculkc8z948c nostr:nevent1qqsw6kt9s9hqc0p6cd97gxgfdgntdc4kwsf06t8r5q8k7syllr5nffc3e2ved nostr:nevent1qqs2vvsyxxsf73g68nnfkpskyjrhd655852w9w39m4t9yfxk70t2amsqtvlc8 nostr:nevent1qqs9qha3elys5qneel0rlt0s5ch6y6hytt8umpp25knpfu5lm3kvs8snxet5m nostr:nevent1qqs2gkprq3kd4dqf7lzqhg9mgqa9dnagjgaresvgcv63syf0zma0jagdcykl0 nostr:nevent1qqsdn093lcfapk0ke2zqe0982yx66auxvnjklq0ytsxmv7txsn5l06q76jefa nostr:nevent1qqsx2yxa4y7u4trxgtkyvp4jfssdm3lfrtkk7cpkewnpuflq522mkccttn0m9 nostr:nevent1qqsfpphq39tphc0znfdvzty88fdejm4wjr5l0n7ksld3vff0kuhak2cas8yhv nostr:nevent1qqsfvzmk7cfanupzthrjh0t600z6szxj0mz40hrrm4rd7kwqqcehrec27k2qw nostr:nevent1qqsqamgz56h7lqg96p3a42mhr9f7rxjprpsaawz9n2uhgh8n7kaukvglw2xvy nostr:nevent1qqsqt3wp8htyhre4d9n22ldml7k9vs655h55n8758yeenwnc2c8yxmc4fn77d nostr:nevent1qqsrurt0gcz8jzlkyqahz288ex3mqwu8tyh0rcpwlrmu5jckhj3wg5sd6m3a8 nostr:nevent1qqsrsz2uyqvakvwpkne2aqhl3d9yjjyzz2wemsj6vv63rcvcylra6cge70xu7 nostr:nevent1qqs93dzpp2acdw7aq9nwtjg4ap6ytjrc6z99mz0x4l6gq2arpd4r8nq3vzw6u nostr:nevent1qqsvam60cggvxtgxdelm4ja6n8wkqjlsdvwau4yqpr67q85jrc8fmcs6tud72 nostr:nevent1qqsztc59n4p23tw3zwewzn88nz99pwal0fh37aw3gg3ymzlg8np5ghguh0r69 nostr:nevent1qqs9p8k384u2qmugnzusxnna2ge3wldg4rvs895zu5pq6l9df24h0ygrytc6v nostr:nevent1qqsvh2lfpxvp7x7cs9d8ttr9ra9m6xl5405lal7x6f2uf5xymlz6j9gqp4ut3 nostr:nevent1qqspndcrk2lxd86tvdy3yd5gqmytvr543pa2cpsgmjylprk33zcsk3crx34t7 nostr:nevent1qqspr3nmus3ch4zy8js73gvqxyz5p5ed8ch6rxl4ymqs2x9fql4ys8gn9x9qw nostr:nevent1qqspslhp7kzfgu0t8rgf0nhm0s4rgnj9rx329vuze8f62r0qmtpx8xcm0tprj nostr:nevent1qqsg3hk5mdre8ny2fpp5xwct7cary359ld8cx97f5h388epg9flwgeqfuzwzy nostr:nevent1qqs9d7dqsqfp2cv3mstn7fnwdsemtct44wan43uy4kkfchd49l65lxg5h2cjz nostr:nevent1qqszn7ycnfn9suns5xxam2207v70ast0w07yq9shwzv6e9cuvz2w0vq22kafd nostr:nevent1qqsdyfrj2n0mxtkgmdy562qdahj8vzrt8drjphvw4cfgp45qvwq06lgu8tzea nostr:nevent1qqs0tja3rdn95q3plklyvz2swkyj8wmfnf5sese5882mh40yj85mdkgcx9sdt nostr:nevent1qqsdfj4zf20wpg8ldkdt2pdnr0tjmjfgc0mz8e2t7l4kf7syrelxhnqnplcq8 nostr:nevent1qqsp9wva4ujkvzyl7ve05h95quq6shnvsgexkw6n588n8wym6tutujcrmdcp8 nostr:nevent1qqs2f6t7et6tag8qms6vkzwpw9tn3fvxqp86hh7dxrr4pxfeeunge6cgaykdg nostr:nevent1qqs0lnhgz0khlsjjq6404p2hug3pwvcqt6x2x6l7yfmfqwzxf364y2gawq8xh nostr:nevent1qqspj2ar7xc4zs3catcks73ppvs77sj59zfdd6vu0h99ukqdt7wf0cgpdcq7s nostr:nevent1qqsyytgaxazjm8gnj64g5l4hushyu9040r336xs4sl0s79jet77esyspcmfel nostr:nevent1qqsw0jdhk5sytywvpn4gzfy6ahrjsmarellyjwy6vm4t82l83x9h4zca63vzu nostr:nevent1qqsgs9q52e920wx0gsy29egqch5x6aey9mtt3jl8kv340uw7lmcgceg43ecjv nostr:nevent1qqsdj0awygazadajkysga3anet6s38vrxrvj55kvhyguvyagqxk2z3sjla65v nostr:nevent1qqsypmjgxeqt9rah3sfxraudpdfhfj0k0sut39n07e4xwtpw5fmju8qfdh234 nostr:nevent1qqspaqxwrg9trpcg4sp2gtjjw6jw6u2rj9yu8al2hscdfdv8ra60f2s5z56vf nostr:nevent1qqsdp3kg2f7ena80zkpw68uc8x4fatccul56jf5j87nhzaqk8mwgsccczcc57 nostr:nevent1qqs9p8wdx53y57ysg39jjgzt5gu67ntqq0u8zv7gsgp3v3xsxw6ta4ssvh6vp nostr:nevent1qqsppejxz438ummams5427fzzfg4lnuswfww6ha2yapf4kkl73mhm6sjtlans nostr:nevent1qqsfewzswnqzwkp76qp7rga0007v2er0s797eqcd2z8cee57u74xv0cn290jt nostr:nevent1qqsq9vjah3gtma3gz99y4m7ey6df8p34n8u572cmaqzwq95xl9xm72gwfrqg8 nostr:nevent1qqsw2qm4664k4f6633j57t7vrwxn9rht6x0sf2suaejjgttrgxm52ccvv9lrj nostr:nevent1qqsplx6sls8ga3eez376m6umwszjj6lmuardvzs72pyekgzyanf0c5s5d5q2r nostr:nevent1qqs8cast93yvaxl0zj20aakl6h4hz6wx8vr7sv4cy4sz20frpdj9ezslrvq4s nostr:nevent1qqswku45leeulqe574ustynud357jwneu3t02qatw0atr3zyclxzaqscxj0sj nostr:nevent1qqsfmsqlukjx47aumecfhq979c53mmyv99ftfgj2luz9h8fe54m9x7sg0jcy9 nostr:nevent1qqsyquj9cquhsmzescerqjyur4cct2eatd6yrp7cxlfjzr0502s7fccyggrwq nostr:nevent1qqsxxurfn8xd83nz52jw2z37cvc3pdnsxvtp6fn9wkzysezh600wl0qs3mdws nostr:nevent1qqsdalre0nscl5mcg8z5tj2rwc08qpjphzvdy56fqvshtuuuvaqgjtskgr03s nostr:nevent1qqszln2q627ef64djy5pn05jzuh8alnuurl4z67fagtehucfg24pkscrgnnth nostr:nevent1qqs0ztxssvt4kt7kuwyts6z4pm7k46undqpccfvn6r54snuzax66z8qw8fyvk nostr:nevent1qqsw8h3n6xc6f5tpqtcqud68tdczruae32hqwdenes34k5dup6kqxqgnwawsu nostr:nevent1qqswjh2qdz0dgmj3va747seu5eu9lnr49zt9kws4lx8lczw74x5gj0c70r6lg nostr:nevent1qqswvkdqtkxy627hvxue8jsam0m93scj7p6jjgqh0mn2r6m9u4pfq9g6q882j nostr:nevent1qqsd4uhh42gq9sj4vtwcr6cnkpwd9k3mzm0g8myakg9ynglfkxyvlqca64zcs nostr:nevent1qqs8wnayqec04sqvl6rt9kyylty09jng6g4ktv8h594x95vn352a43suhqvtu nostr:nevent1qqsfsguft8a77ttqff88emq8dfrvqs8v8lc8ka5d2pjt57wesq6tk8cz4a84y nostr:nevent1qqsf99szvuzldnvgg49dnvlttttd89xpkc9rhfn4wghsfwalrsplesqvw5tpd nostr:nevent1qqsv4vptazj68zgxvf8z5zy3ptz8vwfgkq99a65l2s7hslc5y8vafequjwp3t nostr:nevent1qqsqa5zjxcdu3t7qxlqnrgcgyvftwr8adns8eq6anevwalawpshjs2g48e9gl nostr:nevent1qqsx92uj3cg62w3fsnys7vepwvf9x347hdm3cgww4nvqetdc8h6y5aszzrs7z nostr:nevent1qqs97wu7kt8g3u9sp06rduksjh22uz28etjv7d9fqccfzh2rcajc5ssx6660y nostr:nevent1qqszrjy9qltpxrmqelm39s8f68p3mzq3mz6hy535kt576ryd4xj45rc6m42vz nostr:nevent1qqsz3tzzg2cp2qqu0wpcvg3lgdz7t5jalrl3z9vnhh4qxacx3mt370gma2eur nostr:nevent1qqs8ys6zj6ta8c9m4f47g04tyc4s0uk3rzlj8nzyvn88rqjsak8d3acd9m46w nostr:nevent1qqszc99x43vh4y6g6ufa6s4ffrppjgjmun27je898u90fdml6p2hz8g3dtnhp nostr:nevent1qqs8k903clgruktvagvadtf5huyx4leedd0w9shcrgwyg90y0g7tzmck89mzp nostr:nevent1qqsydxc8mzmsf0qyx8paweap69qaw8fgssz56xmg5q6grxqee2uz75gszqegy nostr:nevent1qqsdscwrfvt0fr0847qd2edna8lduuh7fk2g8jhktvr0r3gmrs7l4kgw08n9r nostr:nevent1qqsrf7tduyxx0h3ywed0pfjtnf7wxjde6xqzeu9qczwar50ptql64uc2cytg3 nostr:nevent1qqstnwlulgt689cwygappskjlexnt3ejzlh380w6gsx93e4mg2smt8gdrz8l9 nostr:nevent1qqsdmke8e87qvy54lz0u3twz36wsz02t8cp0qp5v5hepwd2nf4lfg3seyp84n nostr:nevent1qqszrr2k94yve0v5lxnm82x55vkwu3g36eqf8nya5cgxz9utwc7tlvccuu63k nostr:nevent1qqswgyad2qu6ltmnfasetun80hctvkx5npnwqamse33auvpm2tev5usvx5xd2 nostr:nevent1qqs9cxp7w8tjzed2aaxfscglmac4ddcqzmt667pv2qxck6zmfs7gmkcdxpzps nostr:nevent1qqsgdknwqqa6gkr0x403s6eh3xxjxqd0gy8hxp9mkxkuffaxqmffk9gya2fhh nostr:nevent1qqs0rq7r8s56jhnrysnkg4k99f0q96uphl7vjvjexaazufpzmjl2ldc8ppz5l nostr:nevent1qqsx24ratma6qgt65vj30k5vtcf8ls5l9swrxhe82t3f7xev92n2ckgxepk7g nostr:nevent1qqs06jpjgw56t0xuuu82td6sd8yjnpu9d78z4vvxc6q9gxq5axh0n6spryvch nostr:nevent1qqspa75xvvkw6zpavvrgp3mk30y6shjsg43v0yekk2nqf582xek3mvqr4vjw4 nostr:nevent1qqsvlz88ahc6uq7yqfuuus2vgk035ywa582amt3umaxq0a4hw7sdvzchnavfj nostr:nevent1qqs908tjsfvv9hwn64v800da3p2lkgwcwv695eksc6hhkavgqk6wleg3ue08p nostr:nevent1qqs97hyy2zm3lsah7r3d6u536xf5wn2w8afyqlz7zgqwmaqsn0flsnczp2q4f nostr:nevent1qqsg2hatn34sm5qpsxsykdk35nwrp68n5ggjlgac2qrhjxrzp6vgvlc8v8nuj nostr:nevent1qqsyu8evwrh0kagzjcpcfy8nhdvt5gdnf5q0pex7vukagnm3llzljycp4d3h0 nostr:nevent1qqsvj2hnvgme0zzf8p6u0ehlk27z5yn4zwlravn9ft3smgks77gnxnst533zf nostr:nevent1qqszhfx4aq8qllq3xd2cnyqyenwzu0gysqr9fdrwsx73zp5rv9uflegmeqz70 nostr:nevent1qqsqmga4dkcqkw8tzugg23p7qck622wlgxhhtfshppuzpt8a8xpneac9avf4s nostr:nevent1qqsp3tf4vamjezdpcc4d9jxjrqj6mpunehw4n0p0m6cwdzxy2rgllyqeves5g nostr:nevent1qqs8vnfc2uuvsce0c88kyz5qpn954zv5wqdksprq20c84x0m8axndlg3wc3v2 nostr:nevent1qqsgvctjju645q2yuleqmmt7ku4pwjrf0pjgher4um87k6t33h4yycg5ewtzj nostr:nevent1qqs0ud2vpw9mp59dq5pm9hyxhu6vye9z68k9syrhfjsdqed89zhureqycl52m nostr:nevent1qqszkwqymc8xhvn0afnw9j4ax3dts6e7rv5v9n5zhqmxuxgqmv09kns8rjn00 nostr:nevent1qqs8e6kcap8ae2es6t34053pfvpkeucpt34ve6hhrfgnvh7j2fa4u7qnxaaw0 nostr:nevent1qqsvjd08zysyj93ypsze3jraww4hjdqgr25kzee86c2mutz08rzjgac4k4ef0 nostr:nevent1qqsqqgqnayjy80wfa3qkws83a0ef2rxfnpdet5f33ph0csz3gcqap8gjjnyf8 nostr:nevent1qqsp5m8ar6rsuaah2s8mz8knsq7fm3vlqk60pkvs9xvgugxt99c46wq8va8vg nostr:nevent1qqszptmufg2y38v2cy6v57ptnf27mg7kvh5hmp8uhk9cjwl9m8zrnqc6vf5dx nostr:nevent1qqsg9jl952dq4qvzyfklverpt5aqkp6lmw04kzz6z3zz3n9qg5unt7qjchphg nostr:nevent1qqs9e8jgsv4kyulgz0r7x5z3mxuw2l5ya8las4tkf5z8sy97elvud8qq9s88n nostr:nevent1qqsw0w3f0jvx6pa203kqm8lmhaf2qq69tvnt0f7pedp8ksmtazmjunqzvz5d5 nostr:nevent1qqs25shxc9l6mcudx8su646etmfmx7ywv87dcewjxu87qax49lnkylglpk47n nostr:nevent1qqsfj00j5sk7fuxuxxt8wpf9d60vysfqk0mz53478tfvccx4s4ys7rc2l0uzj nostr:nevent1qqsfwdnw4qfc7j3hnhcrxdu7ecxvgpjmveftu9g29fxg4ra7k9vvehgd744hs nostr:nevent1qqsfqm6phetgyjr7f5zt67gq6k8dv2lgh7j4leax75wk0ry4wfral4sp9pv56 nostr:nevent1qqsrtl8wtsxcrmncwkjrshm3d7ys633zswz5y7r530ywlfpsjk8qtpsprkh4r nostr:nevent1qqs2mqqlpq3s5scaz9dsvn4vnqwzyyp8wtxe43k2pmlfvn9qk9ck8ksts3ll3 nostr:nevent1qqsyl7rhny5et457dm6l23z6hercuvv5hch7pm5xs4v2ekn44c27zaqjpx0r2 nostr:nevent1qqsp3yaj6hzzfd840kmvsct9nw7y94c7pdfw2cnkdgqwaswx2xr0wcqeusc5d nostr:nevent1qqs2ze6chukganrfwmnspce3nuu02zmh0r4nn3z5ed62xx8qtvdjfzsyzp75l nostr:nevent1qqs0kq8eevn32v0karl0naywzeqck2m9sqsync2p0z4phc2tdx2mf2cqer0ws nostr:nevent1qqs9h77g2c3t72q4l9n7e76me8488qkdxyjw2l95nztx36kzxd73tjq973dat nostr:nevent1qqszq5lza048954nq30pwfmqaapentajp7zjqmjtw8zvh0zunt662vsvuqzz5 nostr:nevent1qqsxwhlaqhtkhpsn209e0a7lla3upc0gyse4pyg9np44lc7vg0nuzhcjtljuf nostr:nevent1qqsg2a04k9r6mggptyxjjt9d5whjull77d3aw8xfel8e29eeje8ugzqd8frp4 nostr:nevent1qqs8sk0p79mn9cgcjgxhycyrtq0fxzxepvlnd706mfyrhyyj7jqyk5qhuqfpw nostr:nevent1qqsx9t68ffff4cnz2z36n52eezk6ayqefud340j5thdft7fjt2upd3q0vyzc7 nostr:nevent1qqsw6cn4w95ku93u9atcrduz6st8vuwf9zf4qjge3w6xkpa8lp6rzesufawc4 nostr:nevent1qqsv9yjmw4gq3xgxy4fq02rqk8gsqxk7wyh4uvhppezxrcp7utacdyq233x8j nostr:nevent1qqsrlgvn2uu0zueultxv7stkaalw7vdu2z2ukvttfdw5sj2y865g50gws5cds nostr:nevent1qqsgarz5ppp3mn4m77t2xzzjqq0tps5sjxuve3k2w0ylf55vd4a4uqsxvd9xj nostr:nevent1qqs95z85mhl75j27g5aqw8s3ntm5kasmlglsg3w3u2h6lncyrg0rvkqc5zgjf nostr:nevent1qqspdzkrtk8h8h67egltafs7s32j9vvzxcpycm8dd689e572atr8xfg30a8ce nostr:nevent1qqsq2kd7c2flkrwqz4344gpwx4al4ekrr9wxe3kt7rjz7amcutnzcpsej2atv nostr:nevent1qqsfhz5rx22f5m3x60dpe08fjjpu7mrkeqpq0z2jjn54yh3uzdw257gpws5nq nostr:nevent1qqszc7l3tp70y0ml3zvppuyj2kvs07knxq6d8je3saemv2pgthc2hgczy6pw9 nostr:nevent1qqsta6ec23jz9jpxg8cfy0ae84xcqrcka6u7vsknjfwsq7ec9cx2k2gyfmgup nostr:nevent1qqsyad6h6dpykmhehuaseh2cu53reqf4q5ff7g0k494jvqwjua2dmesxdjwtq nostr:nevent1qqs0g5nm4jajj9rfzd42cueqhakyevs0zg3zsmnv2y6va6dqfnzx79cds0u6e nostr:nevent1qqs8kzvkgq7judfywvt6vaekwn9azslavl75xe40t8wnzhtar24p3kcndx7ld nostr:nevent1qqs24ynaypvt745e0nmdux5cjt57fxs9wtda3p7nnn5jslmxv9g9q4g2zt603 nostr:nevent1qqsp2nujt5m6ypp5cn4yauz58stjn4m3jguecklw7hgyjdg73zc4ddsdz32p3 nostr:nevent1qqsx9sqkyv5afv03mdc2w0ay3t0u872nme3c6ryvs48r5hd7gjg6raq9qa7sq nostr:nevent1qqsv0jsyde7lndup8czlzft8dw9mg06w3evmhtz4ezj2zteepzxacwgdsv7jw nostr:nevent1qqsdu644w6mrn3u468vzuhprckkc8xjqznev2h602ft74c76vx2350cgrqv3a nostr:nevent1qqsg6v7z35vjrfrqkly6fewjjk0yxd5rwdepp28t9ghnt3s9kpdynhce8w5t9 nostr:nevent1qqs9l446svwqwr5h54ygrceqvf20guta566ezwkneu2hx49ha5vdalcjevmxl nostr:nevent1qqsfurxh37ap65w8c87ju4pr4jr9245drjf3ua4l7hc29429cse7e5cw46m4c nostr:nevent1qqs2q76mjpqq8p9kz86869gs65ccrjye2uml887tdau9znqg43k7phg0mzlx2 nostr:nevent1qqsdq24a356ep48la4yt74tcyt5as37ux0ejxfzpthzd5y85ws0n4xqars3lu

@ 82b30d30:40c6c003

[3]

[4]

[5]

[6]

[7]

[8]

[9]

[10]

[11]

[12]

[13]

[14]

[15]

[16]

[17]

[18]

[19]

[20]

[21]

[22]

[23]

[24]

[25]

[26]

[27]

[28]

[29]

[30]

[31]

[32]

[33]

@ 3f770d65:7a745b24

At the recent Launch Music Festival and Conference in Lancaster, PA, featuring over 120 musicians across three days, I volunteered my time with Tunestr and Phantom Power Music's initiative to introduce artists to Bitcoin, Nostr, and the value-for-value model. Tunestr sponsored a stage, live-streaming 21 bands to platforms like Tunestr.io, Fountain.fm and other Nostr/Podcasting 2.0 apps and on-boarding as many others as possible at our conference booth. You may have seen me spamming about this over the last few days.

V4V Earnings

Day 1: 180,000 sats

Day 2: 300,000 sats

Day 3: Over 500,000 sats

Who?

Here are the artists that were on-boarded to Fountain and were live streaming on the Value-for-Value stage:

nostr:npub1cruu4z0hwg7n3r2k7262vx8jsmra3xpku85frl5fnfvrwz7rd7mq7e403w nostr:npub12xeh3n7w8700z4tpd6xlhlvg4vtg4pvpxd584ll5sva539tutc3q0tn3tz nostr:npub1rc80p4v60uzfhvdgxemhvcqnzdj7t59xujxdy0lcjxml3uwdezyqtrpe0j @npub16vxr4pc2ww3yaez9q4s53zkejjfd0djs9lfe55sjhnqkh nostr:npub10uspdzg4fl7md95mqnjszxx82ckdly8ezac0t3s06a0gsf4f3lys8ypeak nostr:npub1gnyzexr40qut0za2c4a0x27p4e3qc22wekhcw3uvdx8mwa3pen0s9z90wk nostr:npub13qrrw2h4z52m7jh0spefrwtysl4psfkfv6j4j672se5hkhvtyw7qu0almy nostr:npub1p0kuqxxw2mxczc90vcurvfq7ljuw2394kkqk6gqnn2cq0y9eq5nq87jtkk nostr:npub182kq0sdp7chm67uq58cf4vvl3lk37z8mm5k5067xe09fqqaaxjsqlcazej nostr:npub162hr8kd96vxlanvggl08hmyy37qsn8ehgj7za7squl83um56epnswkr399 nostr:npub17jzk5ex2rafres09c4dnn5mm00eejye6nrurnlla6yn22zcpl7vqg6vhvx nostr:npub176rnksulheuanfx8y8cr2mrth4lh33svvpztggjjm6j2pqw6m56sq7s9vz nostr:npub1akv7t7xpalhsc4nseljs0c886jzuhq8u42qdcwvu972f3mme9tjsgp5xxk nostr:npub18x0gv872489lrczp9d9m4hx59r754x7p9rg2jkgvt7ul3kuqewtqsssn24

Many more musicians were on-boarded to Fountain, however, we were unable to obtain all of their npubs.

THANK YOU TO ALL ZAPPERS AND BOOSTERS!

Musicians “Get It”

My key takeaway was the musicians' absolute understanding that the current digital landscape along with legacy social media is failing them. Every artist I spoke with recognized how algorithms hinder fan connection and how gatekeepers prevent fair compensation for their work. They all use Spotify, but they only do so out of necessity. They felt the music industry is primed for both a social and monetary revolution. Some of them were even speaking my language…

Because of this, concepts like decentralization, censorship resistance, owning your content, and controlling your social graph weren't just understood by them, they were instantly embraced. The excitement was real; they immediately saw the potential and agreed with me. Bitcoin and Nostr felt genuinely punk rock and that helped a lot of them identify with what we were offering them.

The Tools and the Issues

While the Nostr ecosystem offers a wide variety of tools, we focused on introducing three key applications at this event to keep things clear for newcomers:

1. Fountain, with a music focus, was the primary tool for onboarding attendees onto Nostr. Fountain was also chosen thanks to Fountain’s built-in Lightning wallet.
2. Primal, as a social alternative, was demonstrated to show how users can take their Nostr identity and content seamlessly between different applications.
3. Tunestr.io, lastly was showcased for its live video streaming capabilities.

Although we highlighted these three, we did inform attendees about the broader range of available apps and pointed them to nostrapps.com if they wanted to explore further, aiming to educate without overwhelming them.

This review highlights several UX issues with the Fountain app, particularly concerning profile updates, wallet functionality, and user discovery. While Fountain does work well, these minor hiccups make it extremely hard for on-boarding and education.

• Profile Issues:
• When a user edits their profile (e.g., Username/Nostr address, Lightning address) either during or after creation, the changes don't appear to consistently update across the app or sync correctly with Nostr relays.
• Specifically, the main profile display continues to show the old default Username/Nostr address and Lightning address inside Fountain and on other Nostr clients.
• However, the updated Username/Nostr address does appear on https://fountain.fm (chosen-username@fountain.fm) and is visible within the "Edit Profile" screen itself in the app.
• This inconsistency is confusing for users, as they see their updated information in some places but not on their main public-facing profile within the app. I confirmed this by observing a new user sign up and edit their username – the edit screen showed the new name, but the profile display in Fountain did not update and we did not see it inside Primal, Damus, Amethyst, etc.
• Wallet Limitations:
• The app's built-in wallet cannot scan Lightning address QR codes to initiate payments.
• This caused problems during the event where users imported Bitcoin from Azte.co vouchers into their Fountain wallets. When they tried to Zap a band by scanning a QR code on the live tally board, Fountain displayed an error message stating the invoice or QR code was invalid.
• While suggesting musicians install Primal as a second Nostr app was a potential fix for the QR code issue, (and I mentioned it to some), the burden of onboarding users onto two separate applications, potentially managing two different wallets, and explaining which one works for specific tasks creates a confusing and frustrating user experience.
• Search Difficulties:
• Finding other users within the Fountain app is challenging. I was unable to find profiles from brand new users by entering their chosen Fountain username.
• To find a new user, I had to resort to visiting their profile on the web (fountain.fm/username) to retrieve their npub. Then, open Primal and follow them. Finally, when searching for their username, since I was now following them, I was able to find their profile.
• This search issue is compounded by the profile syncing problem mentioned earlier, as even if found via other clients, their displayed information is outdated.
• Searching for the event to Boost/Zap inside Fountain was harder than it should have been the first two days as the live stream did not appear at the top of the screen inside the tap. This was resolved on the third day of the event.

Improving the Onboarding Experience

To better support user growth, educators and on-boarders need more feature complete and user-friendly applications. I love our developers and I will always sing their praises from the highest mountain tops, however I also recognize that the current tools present challenges that hinder a smooth onboarding experience.

One potential approach explored was guiding users to use Primal (including its built-in wallet) in conjunction with Wavlake via Nostr Wallet Connect (NWC). While this could facilitate certain functions like music streaming, zaps, and QR code scanning (which require both Primal and Wavlake apps), Wavlake itself has usability issues. These include inconsistent or separate profiles between web and mobile apps, persistent "Login" buttons even when logged in on the mobile app with a Nostr identity, and the minor inconvenience of needing two separate applications. Although NWC setup is relatively easy and helps streamline the process, the need to switch between apps adds complexity, especially when time is limited and we’re aiming to showcase the benefits of this new system.

Ultimately, we need applications that are more feature-complete and intuitive for mainstream users to improve the onboarding experience significantly.

Looking forward to the future

I anticipate that most of these issues will be resolved when these applications address them in the near future. Specifically, this would involve Fountain fixing its profile issues and integrating Nostr Wallet Connect (NWC) to allow users to utilize their Primal wallet, or by enabling the scanning of QR codes that pay out to Lightning addresses. Alternatively, if Wavlake resolves the consistency problems mentioned earlier, this would also significantly improve the situation giving us two viable solutions for musicians.

My ideal onboarding event experience would involve having all the previously mentioned issues resolved. Additionally, I would love to see every attendee receive a $5 or $10 voucher to help them start engaging with value-for-value, rather than just the limited number we distributed recently. The goal is to have everyone actively zapping and sending Bitcoin throughout the event. Maybe we can find a large sponsor to facilitate this in the future?

What's particularly exciting is the Launch conference's strong interest in integrating value-for-value across their entire program for all musicians and speakers at their next event in Dallas, Texas, coming later this fall. This presents a significant opportunity to onboard over 100+ musicians to Bitcoin and Nostr, which in turn will help onboard their fans and supporters.

We need significantly more zaps and more zappers! It's unreasonable to expect the same dedicated individuals to continuously support new users; they are being bled dry. A shift is needed towards more people using bitcoin for everyday transactions, treating it as money. This brings me back to my ideal onboarding experience: securing a sponsor to essentially give participants bitcoin funds specifically for zapping and tipping artists. This method serves as a practical lesson in using bitcoin as money and showcases the value-for-value principle from the outset.

@ 06639a38:655f8f71

https://ccns.nostrver.se is a (Drupal powered) website that I started to build in January 2024 (source on Github and Gitlab). It's a fork of an earlier (abandoned) project https://cchs.social/.
Currently CCNS is a link aggregration website and for now it's only my who is using it to save and share Nostr related links. When you post a new link, you have the option to cross-post it as a Nostr note (example here).

Kind 39700

Last month Jurjen and Abir have started to work on a social bookmark client built with Nostr (inspired by Del.icio.us from the past). Earlier this month they changed to event kind 39700 for broadcasting the Nostr event with the bookmark / link data accross the network. They did this because Sep already created a social bookmark like client called Pinja when fiatjaf raised this idea.

With these developments to me it was very obvious to integrate the feature that new created CCNS links are now also published as kind 39700 events to the Nostr network. This means that links are now also distributed on multiple relays as kind 39700 events and are accessible in multiple clients (Yumyume and Pinja).

Here you can see the same data, from left to right:

• CCNS
• Pinja
• Yumyume
• njump

Structure

The current data structure for the 39700 kind looks as follow:

• "id": "event_id"
• "pubkey": "pubkey author"
• "created_at": unix_timestamp
• "kind": 39700
• "tags":
  • "description", "description text here"
  • "d", "unique-slug-value"
  • "t", "hashtag"
• "content": "https://book_mark_url"  
• "sig": "signature"

As there is no NIP (yet) for this event kind, I see some possible improvements:

• Use the bookmark URL as d tag so it can be used as a unique identifier for every client
• Use the content field for the description
• Use the a tag for an addressable event following NIP-01: ["a", "39700:pubkey_of_author:", recommended_relay_url_optional]

On short-term I don't have any plans to developer CCNS further, as most of my attention goes to the development of the Nostr-PHP library and Drupal related contribs using that library. That said, CCNS is a Drupal project but all the Nostr stuff is done client-side (Javascript) with NDK and Nostr-PHP is not used (maybe this will change in the future).

@ 83279ad2:bd49240d

Hello

@ 84b0c46a:417782f5

nostrリンクテスト

web+nostrリンクテスト

x-ukagaka-linkテスト

x-ukagaka-linkテスト2

nostalk

@ 2cb8ae56:84d30cba

どうも、Nostrまとめ(2024)ぶりですね。

記事として出すのはかなりお久しぶりかも、お名前変わりまして「フェゼレント」でございます。 意味としては以下の通りです

1.Fezer（フェザー）という英単語 2.ent（エント）という造語 2-1. netを崩した形、よくこれに打ち間違えます。 2-2. Entertainment（エンターテイメント）の略語、なんか娯楽とか話題を生み出せる人になりたいですね。

1と2をｶﾞｯﾀｲ!!!(トムブラウン風)しまして、フェゼレントです。

なんとググってみますと、Fezerent及びフェゼレントの検索結果が0。 これは...一種のチャンスでは！？と思って、使っています。

さて、そこで出てくるのが「薄味のキャルピス」と「IVstrook」の今後ですよね。 後者に至っては3年分の料金を払ってドメインまで取っているわけですし、前者はかなりネットとかラジオでも浸透しています。

というわけで、こんな風に置き換えます。

Nostr、YT、Discordはフェゼレント及びFezerentを使用します。 それ以外（ラジオを含む）では薄味のキャルピス、IVstrookを使用します。 そして、NHKなどAM波を使用して放送を行っているラジオ局用で使用していた「テックジャンカー」ですが、使用を停止します。 あんま浸透しなかったわけですからね

そんな感じでやっていきます 最後に、記事最後に使用する署名のような奴ですが、そちらは変更なく「IVstrook」単体で行います。

また、ニコニコ動画及び各種ポッドキャストサービスにて配信しておりました「Small Room Space」ですが、今後はzap.streamというNostrのシステムを使用したサービスを用い、番組名の変更は行わないものとします。 zap.streamでの配信開始は「4月7日」 ちょうど#1が公開されてから1年が経過した日です

重ねて、当名義を使用したニコニコ動画への投稿は「3月8日」をもって終了とし、zap.streamへ移行します。

以上、今年に入ってからまともにニコニコ動画で投稿できていませんでしたが、そのような運びとさせていただきます。

2025/03/06 IVstrook

@ ec42c765:328c0600

test

test

@ ec42c765:328c0600

test

@ ec42c765:328c0600

カスタム絵文字とは

任意のオリジナル画像を絵文字のように文中に挿入できる機能です。
また、リアクション（Twitterの いいね のような機能）にもカスタム絵文字を使えます。

カスタム絵文字の対応状況（2025/02/06）

カスタム絵文字を使うためにはカスタム絵文字に対応したクライアントを使う必要があります。

※表は一例です。クライアントは他にもたくさんあります。

使っているクライアントが対応していない場合は、クライアントを変更する、対応するまで待つ、開発者に要望を送る（または自分で実装する）などしましょう。

対応クライアント

• Amethyst
• FreeFrom
• nostter
• Rabbit
• Lumilumi
• Nos Haiku
• Snort
• noStrudel

ここではnostterを使って説明していきます。

準備

カスタム絵文字を使うための準備です。

• Nostrエクステンション（NIP-07）を導入する
• 使いたいカスタム絵文字をリストに登録する

Nostrエクステンション（NIP-07）を導入する

Nostrエクステンションは使いたいカスタム絵文字を登録する時に必要になります。

また、環境（パソコン、iPhone、androidなど）によって導入方法が違います。

Nostrエクステンションを導入する端末は、実際にNostrを閲覧する端末と違っても構いません（リスト登録はPC、Nostr閲覧はiPhoneなど）。

Nostrエクステンション（NIP-07）の導入方法は以下のページを参照してください。

ログイン拡張機能 (NIP-07)を使ってみよう | Welcome to Nostr! ～ Nostrをはじめよう！ ～

少し面倒ですが、これを導入しておくとNostr上の様々な場面で役立つのでより快適になります。

使いたいカスタム絵文字をリストに登録する

以下のサイトで行います。

emojito

右上のGet startedからNostrエクステンションでログインしてください。

例として以下のカスタム絵文字を導入してみます。

実際より絵文字が少なく表示されることがありますが、古い状態のデータを取得してしまっているためです。その場合はブラウザの更新ボタンを押してください。

generalJP | カスタム絵文字

• 右側のOptionsからBookmarkを選択

これでカスタム絵文字を使用するためのリストに登録できます。

カスタム絵文字を使用する

例としてブラウザから使えるクライアント nostter から使用してみます。

nostter

nostterにNostrエクステンションでログイン、もしくは秘密鍵を入れてログインしてください。

文章中に使用

1. 投稿ボタンを押して投稿ウィンドウを表示
2. 顔😀のボタンを押し、絵文字ウィンドウを表示
3. ＊タブを押し、カスタム絵文字一覧を表示
4. カスタム絵文字を選択
5. : 記号に挟まれたアルファベットのショートコードとして挿入される

この状態で投稿するとカスタム絵文字として表示されます。

カスタム絵文字対応クライアントを使っている他ユーザーにもカスタム絵文字として表示されます。

対応していないクライアントの場合、ショートコードのまま表示されます。

ショートコードを直接入力することでカスタム絵文字の候補が表示されるのでそこから選択することもできます。

リアクションに使用

1. 任意の投稿の顔😀のボタンを押し、絵文字ウィンドウを表示
2. ＊タブを押し、カスタム絵文字一覧を表示
3. カスタム絵文字を選択

カスタム絵文字リアクションを送ることができます。

カスタム絵文字を探す

先述したemojitoからカスタム絵文字を探せます。

例えば任意のユーザーのページ emojito ロクヨウ から探したり、 emojito Browse all からnostr全体で最近作成、更新された絵文字を見たりできます。

また、以下のリンクは日本語圏ユーザーが作ったカスタム絵文字を集めたリストです（2025/02/06）

※漏れがあるかもしれません

日本ユーザー作 カスタム絵文字

各絵文字セットにあるOpen in emojitoのリンクからemojitoに飛び、使用リストに追加できます。

---

以上です。

次：Nostrのカスタム絵文字の作り方

Yakihonneリンク Nostrのカスタム絵文字の作り方

Nostrリンク nostr:naddr1qqxnzdesxuunzv358ycrgveeqgswcsk8v4qck0deepdtluag3a9rh0jh2d0wh0w9g53qg8a9x2xqvqqrqsqqqa28r5psx3

---

仕様

NIP-30 Custom Emoji

NIP-30 カスタム絵文字（和訳）

@ ec42c765:328c0600

てすと

nostr:nevent1qqst3uqlls4yr9vys4dza2sgjle3ly37trck7jgdmtr23uuz52usjrqqqnjgr

nostr:nevent1qqsdvchy5d27zt3z05rr3q6vvmzgslslxwu0p4dfkvxwhmvxldn9djguvagp2

test

てｓ

@ ec42c765:328c0600

カスタム絵文字とは

任意のオリジナル画像を絵文字のように文中に挿入できる機能です。
また、リアクション（Twitterの いいね のような機能）にもカスタム絵文字を使えます。

カスタム絵文字の対応状況（2025/02/06）

カスタム絵文字を使うためにはカスタム絵文字に対応したクライアントを使う必要があります。

※表は一例です。クライアントは他にもたくさんあります。

使っているクライアントが対応していない場合は、クライアントを変更する、対応するまで待つ、開発者に要望を送る（または自分で実装する）などしましょう。

対応クライアント

• Amethyst
• FreeFrom
• nostter
• Rabbit
• Lumilumi
• Nos Haiku
• Snort
• noStrudel

ここではnostterを使って説明していきます。

準備

カスタム絵文字を使うための準備です。

• Nostrエクステンション（NIP-07）を導入する
• 使いたいカスタム絵文字をリストに登録する

Nostrエクステンション（NIP-07）を導入する

Nostrエクステンションは使いたいカスタム絵文字を登録する時に必要になります。

また、環境（パソコン、iPhone、androidなど）によって導入方法が違います。

Nostrエクステンションを導入する端末は、実際にNostrを閲覧する端末と違っても構いません（リスト登録はPC、Nostr閲覧はiPhoneなど）。

Nostrエクステンション（NIP-07）の導入方法は以下のページを参照してください。

ログイン拡張機能 (NIP-07)を使ってみよう | Welcome to Nostr! ～ Nostrをはじめよう！ ～

少し面倒ですが、これを導入しておくとNostr上の様々な場面で役立つのでより快適になります。

使いたいカスタム絵文字をリストに登録する

以下のサイトで行います。

emojito

右上のGet startedからNostrエクステンションでログインしてください。

例として以下のカスタム絵文字を導入してみます。

実際より絵文字が少なく表示されることがありますが、古い状態のデータを取得してしまっているためです。その場合はブラウザの更新ボタンを押してください。

generalJP | カスタム絵文字

• 右側のOptionsからBookmarkを選択

これでカスタム絵文字を使用するためのリストに登録できます。

カスタム絵文字を使用する

例としてブラウザから使えるクライアント nostter から使用してみます。

nostter

nostterにNostrエクステンションでログイン、もしくは秘密鍵を入れてログインしてください。

文章中に使用

1. 投稿ボタンを押して投稿ウィンドウを表示
2. 顔😀のボタンを押し、絵文字ウィンドウを表示
3. ＊タブを押し、カスタム絵文字一覧を表示
4. カスタム絵文字を選択
5. : 記号に挟まれたアルファベットのショートコードとして挿入される

この状態で投稿するとカスタム絵文字として表示されます。

カスタム絵文字対応クライアントを使っている他ユーザーにもカスタム絵文字として表示されます。

対応していないクライアントの場合、ショートコードのまま表示されます。

ショートコードを直接入力することでカスタム絵文字の候補が表示されるのでそこから選択することもできます。

リアクションに使用

1. 任意の投稿の顔😀のボタンを押し、絵文字ウィンドウを表示
2. ＊タブを押し、カスタム絵文字一覧を表示
3. カスタム絵文字を選択

カスタム絵文字リアクションを送ることができます。

カスタム絵文字を探す

先述したemojitoからカスタム絵文字を探せます。

例えば任意のユーザーのページ emojito ロクヨウ から探したり、 emojito Browse all からnostr全体で最近作成、更新された絵文字を見たりできます。

また、以下のリンクは日本語圏ユーザーが作ったカスタム絵文字を集めたリストです（2025/02/06）

※漏れがあるかもしれません

日本ユーザー作 カスタム絵文字

各絵文字セットにあるOpen in emojitoのリンクからemojitoに飛び、使用リストに追加できます。

---

以上です。

次：Nostrのカスタム絵文字の作り方

Yakihonneリンク Nostrのカスタム絵文字の作り方

Nostrリンク nostr:naddr1qqxnzdesxuunzv358ycrgveeqgswcsk8v4qck0deepdtluag3a9rh0jh2d0wh0w9g53qg8a9x2xqvqqrqsqqqa28r5psx3

---

仕様

NIP-30 Custom Emoji

NIP-30 カスタム絵文字（和訳）

@ ec42c765:328c0600

カスタム絵文字とは

任意のオリジナル画像を絵文字のように文中に挿入できる機能です。
また、リアクション（Twitterの いいね のような機能）にもカスタム絵文字を使えます。

カスタム絵文字の対応状況（2024/02/05）

カスタム絵文字を使うためにはカスタム絵文字に対応したクライアントを使う必要があります。

※表は一例です。クライアントは他にもたくさんあります。

使っているクライアントが対応していない場合は、クライアントを変更する、対応するまで待つ、開発者に要望を送る（または自分で実装する）などしましょう。

対応クライアント

• Amethyst
• FreeFrom
• nostter
• Rabbit
• Snort
• noStrudel

ここではnostterを使って説明していきます。

準備

カスタム絵文字を使うための準備です。

• Nostrエクステンション（NIP-07）を導入する
• 使いたいカスタム絵文字をリストに登録する

Nostrエクステンション（NIP-07）を導入する

Nostrエクステンションは使いたいカスタム絵文字を登録する時に必要になります。

また、環境（パソコン、iPhone、androidなど）によって導入方法が違います。

Nostrエクステンションを導入する端末は、実際にNostrを閲覧する端末と違っても構いません（リスト登録はPC、Nostr閲覧はiPhoneなど）。

Nostrエクステンション（NIP-07）の導入方法は以下のページを参照してください。

ログイン拡張機能 (NIP-07)を使ってみよう | Welcome to Nostr! ～ Nostrをはじめよう！ ～

少し面倒ですが、これを導入しておくとNostr上の様々な場面で役立つのでより快適になります。

使いたいカスタム絵文字をリストに登録する

以下のサイトで行います。

emojito

右上のGet startedからNostrエクステンションでログインしてください。

例として以下のカスタム絵文字を導入してみます。

実際より絵文字が少なく表示されることがありますが、古い状態のデータを取得してしまっているためです。その場合はブラウザの更新ボタンを押してください。

generalJP | カスタム絵文字

• 右側のOptionsからBookmarkを選択

これでカスタム絵文字を使用するためのリストに登録できます。

カスタム絵文字を使用する

例としてブラウザから使えるクライアント nostter から使用してみます。

nostter

nostterにNostrエクステンションでログイン、もしくは秘密鍵を入れてログインしてください。

文章中に使用

1. 投稿ボタンを押して投稿ウィンドウを表示
2. 顔😀のボタンを押し、絵文字ウィンドウを表示
3. ＊タブを押し、カスタム絵文字一覧を表示
4. カスタム絵文字を選択
5. : 記号に挟まれたアルファベットのショートコードとして挿入される

この状態で投稿するとカスタム絵文字として表示されます。

カスタム絵文字対応クライアントを使っている他ユーザーにもカスタム絵文字として表示されます。

対応していないクライアントの場合、ショートコードのまま表示されます。

ショートコードを直接入力することでカスタム絵文字の候補が表示されるのでそこから選択することもできます。

リアクションに使用

1. 任意の投稿の顔😀のボタンを押し、絵文字ウィンドウを表示
2. ＊タブを押し、カスタム絵文字一覧を表示
3. カスタム絵文字を選択

カスタム絵文字リアクションを送ることができます。

カスタム絵文字を探す

先述したemojitoからカスタム絵文字を探せます。

例えば任意のユーザーのページ emojito ロクヨウ から探したり、 emojito Browse all からnostr全体で最近作成、更新された絵文字を見たりできます。

また、以下のリンクは日本語圏ユーザーが作ったカスタム絵文字を集めたリストです（2024/06/30）

※漏れがあるかもしれません

日本ユーザー作 カスタム絵文字

各絵文字セットにあるOpen in emojitoのリンクからemojitoに飛び、使用リストに追加できます。

---

以上です。

次：Nostrのカスタム絵文字の作り方

Yakihonneリンク Nostrのカスタム絵文字の作り方

Nostrリンク nostr:naddr1qqxnzdesxuunzv358ycrgveeqgswcsk8v4qck0deepdtluag3a9rh0jh2d0wh0w9g53qg8a9x2xqvqqrqsqqqa28r5psx3

---

仕様

NIP-30 Custom Emoji

NIP-30 カスタム絵文字（和訳）

@ 1bc70a01:24f6a411

Untype Update

I cleaned up the AI assistant UX. Now you can open it in the editor bar, same as all other actions. This makes it a lot easier to interact with while having access to normal edit functions.

AI-generated content

Untype uses OpenRouter to connect to various models to generate just about anything. It doesn't do images for now, but I'm working on that.

Automatic Title, Summary and Tag Suggestions

Added the functionality to generate titles, summaries and tags with one click.

A Brief Preview

Here is a little story I generated in Untype, ABOUT Untype:

This story was generated in Untype

Once upon a time, in the bustling digital city of Techlandia, there lived a quirky AI named Untype. Unlike other software, Untype wasn't just your everyday article composer — it had a nose for news, quite literally. Untype was equipped with a masterful talent for sniffing out the latest trends and stories wafting through the vast digital ether.

Untype had a peculiar look about it. Sporting a gigantic nose and a pair of spectacles perched just above it, Untype roamed the virtual city, inhaling the freshest gossip and spiciest stories. Its nostr-powered sensors twitched and tickled as it encountered every new scent.

One day, while wandering around the pixelated park, Untype caught a whiff of something extraordinary — a scandalous scoop involving Techlandia's mayor, Doc Processor, who had been spotted recycling old memes as new content. The scent trail was strong, and Untype's nose twitched with excitement.

With a flick of its AI function, Untype began weaving the story into a masterpiece. Sentences flowed like fine wine, infused with humor sharper than a hacker’s focus. "Doc Processor," Untype mused to itself, "tried to buffer his way out of this one with a cache of recycled gifs!"

As Untype typed away, its digital friends, Grammarly the Grammar Gremlin and Canva the Artful Pixie, gathered around to watch the genius at work. "You truly have a knack for news-sniffing," complimented Grammarly, adjusting its tiny monocle. Canva nodded, painting whimsical illustrations to accompany the hilarious exposé.

The article soon spread through Techlandia faster than a virus with a strong wifi signal. The townsfolk roared with laughter at Untype’s clever wit, and even Doc Processor couldn't help but chuckle through his embarrassment.

From that day on, Untype was celebrated not just as a composer but as Techlandia's most revered and humorous news-sniffer. With every sniff and click of its AI functions, Untype proved that in the world of digital creations, sometimes news really was just a nose away.

@ 21ac2956:09d1e2df

kakoi の仕様についてのメモ

キーボード操作

• 左手での操作に最適化

| キー | 動作 | |:-|:-| | ESC | 設定画面 | | F1 / F12 | ポストバーの表示と非表示 | | F2 | 時間の表示と非表示 | | F3 | ユーザーアイコンの表示と非表示 | | F4 | 名前の表示と非表示 | | F5 | Geminiによるタイムラインまとめ画面を表示 | | F9 / Z | コンテンツの折り返し表示の切り替え （余白ダブルクリックでも動作） | | F10 | ユーザーリストとキーワード通知の設定画面 （余白右クリックでも動作） | | F11 | メイン画面の表示と非表示 （ポストバー表示） | | Shift + W | イベント最上行へ移動 | | W / ↑| イベント選択上移動 | | S / ↓ | イベント選択下移動 | | Shift + S | イベント最下行へ移動 | | A / ← | Webビューを開く （イベントを右クリックでも動作） | | F / → | リアクションを送信 （イベントをダブルクリックでも動作） | | 1 ～ 0 | リアクションを選択 | | R | 返信 | | B | リポスト | | Q | 引用 | | C | Webビューを閉じる | | Ctrl + Shift + A | メイン画面をアクティブにする |

タイムライン

• kind:1, 6, 7, 16を取得して表示する
• フォロイーの名前の前には * が付く

フォローリスト（kind:3）

• 参照のみで更新はしない

• F10 で開くユーザーリストでユーザーを選択し petname セルをクリックすることで未フォローユーザーにもペットネームを設定可能（ローカル保存）

プロフィール（kind:0）

• F10 で開くユーザーリストでユーザーを選択し picture セルをクリックすることでユーザーのアイコン表示を変更可能（ローカル保存）

返信（NIP-10 kind:1）

• kakoi のタイムラインに流れるすべてのイベント種に返信可能とする
• スレッドを考慮せず、単一イベントへの単発返信とする
• e タグは marker と返信先 pubkey は設定していない。 relay-url には空文字を設定

json ["e", "返信先 event-id", ""]

• p タグは 返信先 pubkey ひとつだけを指定

リポスト（NIP-18 kind:6 , 16）

• kakoi のタイムラインに流れるすべてのイベント種をリポスト可能
• kind:1はkind:6。その他はkind:16でリポストする
• e タグは relay-url に空文字を設定

json ["e", "リポスト元 event-id", ""]

引用（NIP-18 kind:1）

• q タグは relay-url に空文字を設定

json ["q", "引用元 event-id", ""]

@ 1bc70a01:24f6a411

I've been meaning to dogfood my own vibe project for a while so this feels like a good opportunity to use Untype to publish this update and reflect on my vibe coding journey.

New Untype Update

As I write this, I found it a bit annoying dealing with one of the latest features, so I'll need to make some changes right after I'm done. Nonetheless, here are some exciting developments in the Untype article composer:

1. Added inline AI helper! Now you can highlight text and perform all sorts of things like fix grammar, re-write in different styles, and all sorts of other things. This is a bit annoying at the moment because it takes over the other editing functions and I need to fix the UX.

2. Added pushing articles to DMs! This option, when enabled, will send the article to all the subscribers via a NIP-44 DM. (No client has implemented the subscription method yet so technically it won’t work, until one does. I may add this to nrss.app) Also, I have not tested this so it could be broken… will test eventually!

3. Added word counts
4. Added ability to export as markdown, export as PDF, print.

The biggest flaw I have already discovered is how "I" implemented the highlight functionality. Right now when you highlight some text it automatically pops up the AI helper menu and this makes for an annoying time trying to make any changes to text. I wanted to change this to show a floating clickable icon instead, but for some reason the bot is having a difficult time updating the code to this desired UX.

Speaking of difficult times, it's probably a good idea to reflect a bit upon my vibe coding journey.

Vibe Coding Nostr Projects

First, I think it's important to add some context around my recent batch of nostr vibe projects. I am working on them mostly at night and occasionally on weekends in between park runs with kids, grocery shopping and just bumming around the house. People who see buggy code or less than desired UX should understand that I am not spending days coding this stuff. Some apps are literally as simple as typing one prompt!

That said, its pretty clear by now that one prompt cannot produce a highly polished product. This is why I decided to limit my number of project to a handful that I really wish existed, and slowly update them over time - fixing bugs, adding new features in hopes of making them the best tools - not only on nostr but the internet in general. As you can imagine this is not a small task, especially for sporadic vibe coding.

Fighting the bot

One of my biggest challenges so far besides having very limited time is getting the bot to do what I want it to do. I guess if you've done any vibe coding at all you're probably familiar with what I'm trying to say. You prompt one thing and get a hallucinated response, or worse, a complete mess out the other end that undoes most of the progress you've made. Once the initial thing is created, which barely took any time, now you're faced with making it work a certain way. This is where the challenges arise.

Here's a brief list of issues I've faced when vibe-coding with various tools:

1. Runaway expenses - tools like Cline tend to do a better job directly in VSCode, but they can also add up dramatically. Before leaning into v0 (which is where I do most of my vibe coding now), I would often melt through $10 credit purchases faster than I could get a decent feature out. It was not uncommon for me to spend $20-30 on a weekend just trying to debug a handful of issues. Naturally, I did not wish to pay these fees so I searched for alternatives.

2. File duplication - occasionally, seemingly out of nowhere, the bot will duplicate files by creating an entire new copy and attached "-fixed" to the file name. Clearly, I'm not asking for duplicate files, I just want it to fix the existing file, but it does happen and it's super annoying. Then you are left telling it which version to keep and which one to delete, and sometimes you have to be very precise or it'll delete the wrong thing and you have to roll back to a previous working version.

3. Code duplication - similar to file duplication, occasionally the bot will duplicate code and do things in the most unintuitive way imaginable. This often results in loops and crashes that can take many refreshes just to revert back to a working state, and many more prompts to avoid the duplication entirely - something a seasoned dev never has to deal with (or so I imagine).

4. Misinterpreting your request - occasionally the bot will do something you didn't ask for because it took your request quite literally. This tends to happen when I give it very specific prompts that are targeted at fixing one very specific thing. I've noticed the bots tend to do better with vague asks - hence a pretty good result on the initial prompt.

5. Doing things inefficiently, without considering smarter approaches - this one is the most painful of vibe coding issues. As a person who may not be familiar with some of the smarter ways of handling development, you rely on the bot to do the right thing. But, when the bot does something horribly inefficiently and you are non-the-wiser, it can be tough to diagnose the issue. I often fight myself asking the bot "is this really the best way to handle things? Can't we ... / shouldn't we .../ isn't this supposed to..." etc. I guess one of the nice side effects of this annoyance is being able to prompt better. I learn that I should ask the bot to reflect on its own code more often and seek ways to do things more simply.

A combination of the above, or total chaos - this is a category where all hell breaks loose and you're trying to put out one fire after another. Fix one bug, only to see 10 more pop up. Fix those, to see 10 more and so on. I guess this may sound like typical development, but the bot amplifies issues by acting totally irrationally. This is typically when I will revert to a previous save point and just undo everything, often losing a lot of progress.

Lessons Learned

If I had to give my earlier self some tips on how to be a smarter vibe coder, here's how I'd summarize them:

1. Fork often - in v0 I now fork for any new major feature I'd like to add (such as the AI assistant).

2. Use targeting tools - in v0 you can select elements and describe how you wish to edit them.

3. Refactor often - keeping the code more manageable speeds up the process. Since the bot will go through the entire file, even if it only makes one small change, it's best to keep the files small and refactoring achieves that.

I guess the biggest lesson someone might point out is just to stop vibe coding. It may be easier to learn proper development and do things right. For me it has been a spare time hobby (one that I will admit is taking more of my extra time than I'd like). I don't really have the time to learn proper development. I feel like I've learned a lot just bossing the bot around and have learned a bunch of things in the process. That's not to say that I never will, but for the moment being my heart is still mostly in design. I haven't shared much of anything I have designed recently - mostly so I can remain speaking more freely without it rubbing off on my work.

I'll go ahead and try to publish this to see if it actually works 😂. Here goes nothing... (oh, I guess I could use the latest feature to export as markdown so I don't lose any progress! Yay!

@ 84b0c46a:417782f5

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qqs0df2mwnp2q6hm6zjrthkmx3fudwsuwrmgnwrdavpzgjy8nnuqm5cqpd06k

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qqs2muhvnev5367ywuzkhell9my86jlnzhsnuszwl46tnc3fpsx9mtgjkqnu7

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qqsznnkrl8qdwzgp7ry2hc7a77kwhg440gv9xtmvyfawggrpz3rhwvcx4rckf

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qqsyjf80k3djt96qncgvwl2yem09fdqcc0y9l8t657yc9qg2yhmg7kcnua8vn

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qqs0s3lp0w0yclk64j0tpc5fvrulv78g2lfjz3gcgacw9mt6czek26qtqxuck

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qywhwumn8ghj7mn0wd68ytnrdakhq6tvv5kk2unjdaezumn9wsqs6amnwvaz7tmev9382tndv5qjqamnwvaz7tmjv4kxz7fddfczumn0wd68ytnhd9ex2erwv46zu6nsqqs89tst72clc60wse3zq4qfs0976y7areffnhx26atvu6pv58hg6dsxvcc79

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qyxhwumn8ghj77tpvf6jumt9qys8wumn8ghj7un9d3shjtt2wqhxummnw3ezuamfwfjkgmn9wshx5uqpr3mhxue69uhhxun5wfjkccte9e3j6um5v4kxcctj9ehx2aqqyp5k40r3ug02yz5y0tn67tm2lwevuwac54qyw3yyct8n8uzr7pjz2q92pyt

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qyxhwumn8ghj77tpvf6jumt9qys8wumn8ghj7un9d3shjtt2wqhxummnw3ezuamfwfjkgmn9wshx5uqqyp9pennjwq2qk4dxpr440wxqm5cfwah4qccd8la62hantxdelkk82ty9mr8

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qyxhwumn8ghj77tpvf6jumt9qqsz9w30kxzjshwd8sq7jg2hsy2hwqg3zu7gyvxnsyrgfw0ur4rkhsg9v0re4

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qyxhwumn8ghj77tpvf6jumt9qqs8wkx2r8txt9q69c3zvpqs2em2s40nc8tajmcc5l8ngxn8v2ng3sc43xvzu

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qyxhwumn8ghj77tpvf6jumt9qys8wumn8ghj7un9d3shjtt2wqhxummnw3ezuamfwfjkgmn9wshx5uqqyzdkacpjqvv2y79zgvufx9jh39rd7xa8v056rgn4xelmnmrq9u2tuguswek

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qy2hwumn8ghj7mn0wd68ytnyv96xztngv96hxqpqmdtjrs38fv8r20deplrlt8fma54gu43keuzquzks7673a27ud58slunr8y

nostr:nevent1qvzqqqqqqypzpp9sc34tdxdvxh4jeg5xgu9ctcypmvsg0n00vwfjydkrjaqh0qh4qyxhwumn8ghj77tpvf6jumt9qys8wumn8ghj7un9d3shjtt2wqhxummnw3ezuamfwfjkgmn9wshx5uqpr4mhxue69uhkummnw3ezucm0d4cxjmr994jhyun0wghxuet5qqsxzpx2r5hd36pruzn2e58wh947y2t0t205fp5xtstqp5wq0qgcjuq07rqlk

@ 1bc70a01:24f6a411

The heading to be

Testing apps, a tireless quest, Click and swipe, then poke the rest. Crashing bugs and broken flows, Hidden deep where logic goes.

Specs in hand, we watch and trace, Each edge case in its hiding place. From flaky taps to loading spins, The war on regressions slowly wins.

Push the build, review the log, One more fix, then clear the fog. For in each test, truth will unfold— A quiet tale of stable code.

This has been a test. Thanks for tuning in.

• one
• two
• three

---

Listen a chill

Tranquility

And leisure

@ 78b3c1ed:5033eea9

※ライトニングノード保有者向け

Alby Hubをインストールした時なんもわからずポチポチしているとMegatlith LSPノードからインバウンドを購入してチャネルを開くことになります。2万sats(2024/12/4 午後7時時点で三千円ほど)かかります。

そこで誰もが思うに違いない 「高いなぁ。だれかタダで無料で私のHubにチャネル開いてくれないかなぁ...」

その願望をかなえる献身的なノードランナー(笑)がAlby Hubへチャネルを開いてあげるための手順書みたいなものがこの記事です。 ~~ppmをうんと高くしてぼったくってやりましょう！~~

※AlbyHubにオンチェーン資金が無くてもLNDから開く方法を発見しました。末尾に追記しました。

《これはアンカーアウトプットを利用するタイプのチャネル》 条件 ・チャネルを開く側 　Clearnet IPアドレスで着信可能であること。Torノードは不可。ノードURIを公開していなくても良い。AlbyHubでピア登録できるClearnet IPアドレスと着信ポートがあればOK。

・開いてもらうAlby Hub側 　オンチェーン資金25,000sats以上をデポジットしておく。ないと開けません。

手順

1. [Alby Hub側] オンチェーン資金をデポジット Hubログイン後の左メニューからNodeを選択。Saving BalanceのDepositを選択。するとbc1qではじまるオンチェーンアドレスが表示される。ここへ送金してオンチェーンをデポジットしておく。

2. [Alby Hub側] 開く側のノードをピア登録 左メニューからNodeを選択。右上のAdvancedからConnected Peersを選択。 右上のConnect Peerを選択。欄にノードURI (ノードID@IPアドレス:着信ポート番号)を入力してConnect。

3. [開く側ノード] AlbyHubを確認、チャネルを開く ThunderhubやRide-The-Lightningなどを使い、Alby Hubのノードが表示されていることを確認。Hubにエイリアスは無いのでノードIDで表示される。 このノードに対してチャネルを開く。Private channelが望ましいと思われる。 6conf後に開設完了。

終わり！

メモ

• Alby Hubではbase feeは設定可能だがrateが設定できない。そもそもAlby Hubはルーティング向けノードとして設計されてない。セルフカストディアルウォレットです。
• public channelだとchannel_update, channel_announcementがゴシップされるまでHubへ送金できない(no route)。上記の通りウォレットとしてのノードならprivate channelだけにしてルートヒント付きインボイスが発行できるようにしとくのが望ましい。
• LDKにおいて相手からチャネルを開いてもらう場合にオンチェーン資金が必要。相手がチャネルリザーブ無しのチャネルでもOKなら不要。現にメガリスLSPからチャネルを開いてもらう時オンチェーン資金が0satsでも開けているのがその実例。
• オンチェーン資金が必要なのはチャネルタイプがanchorの場合。オンチェーン資金でアンカーアウトプットをCPFPするためみたい。anchorが登場する前のstatic-remotekeyのタイプならオンチェーン資金は不要。

---

＜ここからが追加＞

《これはアンカーアウトプットを利用しないタイプのチャネル》 LNDからチャネルを開くときにstatic remote keyを利用するタイプを指定します。

条件 ・チャネルを開く側　※上記と同様。

・開いてもらうAlby Hub側　無し。 手順 1. [Alby Hub側] 開く側のノードをピア登録 左メニューからNodeを選択。右上のAdvancedからConnected Peersを選択。右上のConnect Peerを選択。欄にノードURI (ノードID@IPアドレス:着信ポート番号)を入力してConnect。 2. [開く側ノード] AlbyHubを確認、チャネルを開く SSHログイン、UmbrelならLightningのターミナルで以下のコマンドを実行します。

<ノードID>は開きたいAlbyHubのノードIDで置き換えてください。 <チャネルサイズ>は開きたいチャネルの金額、例えば20万satsなら200000としましょう。 <手数料率>はチャネル開設のトランザクションに掛ける手数料率です。mempool. spaceなどで手数料水準を確認して指定しましょう。 --channel_type tweaklessがキモです。デフォルトだとanchorになります。RTLやTHで開くとこのanchorになります。なのでlncli openchannelでやります。

lncli openchannel --node_key <ノードID> \ --local_amt <チャネルサイズ> \ --sat_per_vbyte <手数料率> \ --private --channel_type tweakless

終わり！

@ 83279ad2:bd49240d

Test

@ dffd3ffc:5ade7be1

Nostr 利用開始から 1 年を迎えて

はじめに

みなさんこんにちは。おっぱぴぃです。

ハッカーのおもちゃとしての Nostr のススメ と Nostr の面白さをエンジニア目線で解説してみるをみて Nostr にはじめて投稿をしたのが 2024/01/04 09:04:18 でした。

nostr:nevent1qqsd5v80f9zazxd4kq2r2dls5znd40ht6c7cj4slt6wtlv483vkmxdcjvq66c

Nostr で私が 1 年間をどう過ごしてきたか、振り返ってみようと思います。

初投稿日

今見たら 10 リポスト、20 そこそこのリアクションをいただいてたんですね。初投稿というだけでこんなおバズリあそばすことあるんだって思いました。~~みんな年始で暇やったんかな~~

これだけリアクションがあって、フォローもしていただいたおかげで Nostr の印象がよくなったこと、日本人話者にすぐたどり着けてことが Nostr を続けられている要因になっていると思います。あとはエアリプ文化が懐かしい＆近すぎず遠すぎずで居心地がよくて沼ったところがあると思います。

その日はNostr の Scrapbox（現 Cosense）をその日中にざっと読み漁って、記事の誤字修正したり、WoS を設定してみたり、Lightning Address を設定したりしていたようです。

nostr:nevent1qqsxml4ak7g3u8gjcyuhy89sd8vlk3fu6we9ecgey69jltd42dr0etcvt0l3w

~~おまえ、このころから大欲情を…~~

のす会でのオン会（？）

Nostr 日本人ユーザーの集まる Discord サーバとして、「のす会」というものがあります。 過去ログを漁ってるとどうやら 2024/01/15 ごろにボイチャに入りはじめ、

nostr:nevent1qqszm0kv7aulxnmxr2fdxg5cvme7nyv3j6rgfa30cat8cs3npnsep9caz0xyc

その翌日にはのす会にて Geo guesser で遊んだりしていたようです。こじらさんが尋常じゃない強さでどういう事なの…となった覚えがあります。

nostr:nevent1qqs9knrf4ww8g0fsu4l74gxeeh3s9pwpnf47xn8pf5u8pplkz4yatjg03ufd5

こうした経験を経て、徐々に Nostr ユーザーの方と直接会話することのハードルが下がってきた所でした。

初のオフ会参加

2 月頭、TL で話題になっていた火鍋を食べた経験がないなぁ…ということで、2024/02/10、ゴリラ.vim#30~四谷ラボコラボ~の参加と併せて、海底撈火鍋でオフ会を開催したのが Nostr における初めてのオフ会参加＆幹事でした。

この日は中国の春節初日だったのもあって異様に店舗が混んでおり、18:00 に予約したのに一行に案内されず、

nostr:nevent1qqspcttj4gv2ey7vkt0wp2nehqfwxjnp55vm4agnwu9kullep88ysccpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg87v060ssxrpew6a0vrhkcy36hqppvrwjmlqnrgqrrvf8fghgg0pypsgqqqqqqs07ajzp

顔面が痙攣したり、

nostr:nevent1qqs9d5vycslspatsnx6u5qqqwpfmdt33w2v7xkytljzsfwv56acs79czyr0l60lu824k9yc63jcg7z32fzx6w3cr6zx3mmuns69wxr66mea7zp6f7wn

詫び菓子を貰ったり、

nostr:nevent1qqs8a0u47alv9vexd5r5s5vygs77ecadm6dl9vlky32hjywdx8f3gtczyr0l60lu824k9yc63jcg7z32fzx6w3cr6zx3mmuns69wxr66mea7zgjxmhl

病院待合室みたいな場所で検尿コップで水飲んだりと

nostr:nevent1qqsq44zs04g5zng35ks6jrvrv6uel2f9ls26d7nsc6svuggrlfnvtcgzyp4kuxwwg7530jlp8fn7adq982dnq8ncajv3gyl824y4xzyw6cknkvj37gy

トラウマになりそうなオフ会でした。当時の様子はnosli でまとめています。

今振り返ってもくちゃくちゃの体験してるなと思いますが、 ~~クレーターを作りそうな青ウサギがいたものの~~

nostr:nevent1qqsrs8y3phadhcukwjlkjkgdcs43ndkc8a42m88zayfj6p2lex6a6tgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygrtdcvuu3afzl97zwn8a66q2w5mxq083myezsf7w42f2vyga43d8vpsgqqqqqqsyfx7da

誰も怒らないし宴会自体は楽しかったので、Nostr のオフ会の原体験としては良かったな、と感じています。ひどい思い出ほど振り返ったら美化されるやつかもしれない。

各種イベント参加

Nostr には四谷ラボ参加者の方が沢山いらっしゃったこと、お声かけいただいた縁などもあり、いろいろなイベントにスタッフとして参加する経験ができました。例えば…

• Bluesky Meetup in Tokyo Vol.2
• 技術書典 16 ⇒ 関わらせていただいたのぶこ本
• Nostrasia2024

など。

微力ながら、自らの役割に合わせてイベントに貢献させていただけて、とても楽しめました。 自分に自信がなく、私生活では責任が発生する立場を回避しがちであったこともあって、自分としてはこれらのイベント参加はとても貴重な経験になりました。 関係されている方々が思い思いの仕事のやりようでイベントに取り組んでいる様が刺激になったなと思います。

オフ会履歴

私を Nostr でフォローいただいている方であれば、「こいつ、やたらオフ会行ってないか…？」と思われるでしょう。ということで、自分でも一度整理をしてみました。

うわっ...私のオフ会参加、多すぎ…？ ~~1 年間は52週しかないねんぞ~~

このように、火鍋のオフ会を皮切りに、相当な数のオフ会に参加させていただきました。オフ会というかもう普通に Nostr で知り合っただけの友人との集まりみたいな感覚になっているかも。

ちなみに、人単位でお会いした回数もまとめています。

※：Nostrasia などのイベントでお会いした回数は除いています。

こうみるとしおと神（かすてらふぃさん）と会った回数めちゃくちゃ多いですね。28,26回だとほぼ2週に1回ペースですが、過去どんなに親しい友人でもこんな頻度で会ってたことないかも。

思い出深かった出来事

nostr:nevent1qqsyeyycax9qgrr4qvtty4h62x96vc6lydh8yg7jl5er99zg7wlpdrcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygxll5llcw4tv2f34r9s3u9z5jyd5ars85ydrhhe8p52uv844hnmuypsgqqqqqqskevt6r

nostr:nevent1qqs0sqhtzc4p3vysz5k7l29x2lcnedeys55t7mqp2mz7ugrmw0v725cppemhxue69uhkummn9ekx7mp0qgsdllfllsa2kc5nr2xtprc29fygmf68q0gg6800jwrg4cc0tt08hcgrqsqqqqqpaua8e8

この誤字投稿を経て、私の（たまにほかの人も）誤字は大欲情と呼ばれるようになりました。~~毎回思うけど新しく入ってきた人は何だこれってなるよなこれ~~

その後も酔ってる時を中心に結構誤字をやらかすので、那月さんによるまとめが作られています。

名前としては不名誉かもしれませんが、面白いのでOKです。

おわりに

振り返ってみれば Nostr 日本人ユーザーコミュニティの心地良さに浸った 1 年だったと思います。 Nostr の仕組み自体も好きですが、私はコミュニティの方に目が行っている気がします。

Nostr 歴 1 歳になったので、今後は私が Nostr を使う人々に心地良いと思ってもらえるような人になれるとよいなと思います。

これからもよろしくお願いします。

@ 1bda7e1f:bb97c4d9

Tldr

• Nostr is an open and interoperable protocol
• You can integrate it with workflow automation tools to augment your experience
• n8n is a great low/no-code workflow automation tool which you can host yourself
• Nostrobots allows you to integrate Nostr into n8n
• In this blog I create some workflow automations for Nostr
• A simple form to delegate posting notes
• Push notifications for mentions on multiple accounts
• Push notifications for your favourite accounts when they post a note
• All workflows are provided as open source with MIT license for you to use

Inter-op All The Things

Nostr is a new open social protocol for the internet. This open nature exciting because of the opportunities for interoperability with other technologies. In Using NFC Cards with Nostr I explored the nostr: URI to launch Nostr clients from a card tap.

The interoperability of Nostr doesn't stop there. The internet has many super-powers, and Nostr is open to all of them. Simply, there's no one to stop it. There is no one in charge, there are no permissioned APIs, and there are no risks of being de-platformed. If you can imagine technologies that would work well with Nostr, then any and all of them can ride on or alongside Nostr rails.

My mental model for why this is special is Google Wave ~2010. Google Wave was to be the next big platform. Lars was running it and had a big track record from Maps. I was excited for it. Then, Google pulled the plug. And, immediately all the time and capital invested in understanding and building on the platform was wasted.

This cannot happen to Nostr, as there is no one to pull the plug, and maybe even no plug to pull.

So long as users demand Nostr, Nostr will exist, and that is a pretty strong guarantee. It makes it worthwhile to invest in bringing Nostr into our other applications.

All we need are simple ways to plug things together.

Nostr and Workflow Automation

Workflow automation is about helping people to streamline their work. As a user, the most common way I achieve this is by connecting disparate systems together. By setting up one system to trigger another or to move data between systems, I can solve for many different problems and become way more effective.

n8n for workflow automation

Many workflow automation tools exist. My favourite is n8n. n8n is a low/no-code workflow automation platform which allows you to build all kinds of workflows. You can use it for free, you can self-host it, it has a user-friendly UI and useful API. Vs Zapier it can be far more elaborate. Vs Make.com I find it to be more intuitive in how it abstracts away the right parts of the code, but still allows you to code when you need to.

Most importantly you can plug anything into n8n: You have built-in nodes for specific applications. HTTP nodes for any other API-based service. And community nodes built by individual community members for any other purpose you can imagine.

Eating my own dogfood

It's very clear to me that there is a big design space here just demanding to be explored. If you could integrate Nostr with anything, what would you do?

In my view the best way for anyone to start anything is by solving their own problem first (aka "scratching your own itch" and "eating your own dogfood"). As I get deeper into Nostr I find myself controlling multiple Npubs – to date I have a personal Npub, a brand Npub for a community I am helping, an AI assistant Npub, and various testing Npubs. I need ways to delegate access to those Npubs without handing over the keys, ways to know if they're mentioned, and ways to know if they're posting.

I can build workflows with n8n to solve these issues for myself to start with, and keep expanding from there as new needs come up.

Running n8n with Nostrobots

I am mostly non-technical with a very helpful AI. To set up n8n to work with Nostr and operate these workflows should be possible for anyone with basic technology skills.

• I have a cheap VPS which currently runs my HAVEN Nostr Relay and Albyhub Lightning Node in Docker containers,
• My objective was to set up n8n to run alongside these in a separate Docker container on the same server, install the required nodes, and then build and host my workflows.

Installing n8n

Self-hosting n8n could not be easier. I followed n8n's Docker-Compose installation docs–

• Install Docker and Docker-Compose if you haven't already,
• Create your docker-compose.yml and .env files from the docs,
• Create your data folder sudo docker volume create n8n_data,
• Start your container with sudo docker compose up -d,
• Your n8n instance should be online at port 5678.

n8n is free to self-host but does require a license. Enter your credentials into n8n to get your free license key. You should now have access to the Workflow dashboard and can create and host any kind of workflows from there.

Installing Nostrobots

To integrate n8n nicely with Nostr, I used the Nostrobots community node by Ocknamo.

In n8n parlance a "node" enables certain functionality as a step in a workflow e.g. a "set" node sets a variable, a "send email" node sends an email. n8n comes with all kinds of "official" nodes installed by default, and Nostr is not amongst them. However, n8n also comes with a framework for community members to create their own "community" nodes, which is where Nostrobots comes in.

You can only use a community node in a self-hosted n8n instance (which is what you have if you are running in Docker on your own server, but this limitation does prevent you from using n8n's own hosted alternative).

To install a community node, see n8n community node docs. From your workflow dashboard–

• Click the "..." in the bottom left corner beside your username, and click "settings",
• Cilck "community nodes" left sidebar,
• Click "Install",
• Enter the "npm Package Name" which is n8n-nodes-nostrobots,
• Accept the risks and click "Install",
• Nostrobots is now added to your n8n instance.

Using Nostrobots

Nostrobots gives you nodes to help you build Nostr-integrated workflows–

• Nostr Write – for posting Notes to the Nostr network,
• Nostr Read – for reading Notes from the Nostr network, and
• Nostr Utils – for performing certain conversions you may need (e.g. from bech32 to hex).

Nostrobots has good documentation on each node which focuses on simple use cases.

Each node has a "convenience mode" by default. For example, the "Read" Node by default will fetch Kind 1 notes by a simple filter, in Nostrobots parlance a "Strategy". For example, with Strategy set to "Mention" the node will accept a pubkey and fetch all Kind 1 notes that Mention the pubkey within a time period. This is very good for quick use.

What wasn't clear to me initially (until Ocknamo helped me out) is that advanced use cases are also possible.

Each node also has an advanced mode. For example, the "Read" Node can have "Strategy" set to "RawFilter(advanced)". Now the node will accept json (anything you like that complies with NIP-01). You can use this to query Notes (Kind 1) as above, and also Profiles (Kind 0), Follow Lists (Kind 3), Reactions (Kind 7), Zaps (Kind 9734/9735), and anything else you can think of.

Creating and adding workflows

With n8n and Nostrobots installed, you can now create or add any kind of Nostr Workflow Automation.

• Click "Add workflow" to go to the workflow builder screen,
• If you would like to build your own workflow, you can start with adding any node. Click "+" and see what is available. Type "Nostr" to explore the Nostrobots nodes you have added,
• If you would like to add workflows that someone else has built, click "..." in the top right. Then click "import from URL" and paste in the URL of any workflow you would like to use (including the ones I share later in this article).

Nostr Workflow Automations

It's time to build some things!

A simple form to post a note to Nostr

I started very simply. I needed to delegate the ability to post to Npubs that I own in order that a (future) team can test things for me. I don't want to worry about managing or training those people on how to use keys, and I want to revoke access easily.

I needed a basic form with credentials that posted a Note.

For this I can use a very simple workflow–

• A n8n Form node – Creates a form for users to enter the note they wish to post. Allows for the form to be protected by a username and password. This node is the workflow "trigger" so that the workflow runs each time the form is submitted.
• A Set node – Allows me to set some variables, in this case I set the relays that I intend to use. I typically add a Set node immediately following the trigger node, and put all the variables I need in this. It helps to make the workflows easier to update and maintain.
• A Nostr Write node (from Nostrobots) – Writes a Kind-1 note to the Nostr network. It accepts Nostr credentials, the output of the Form node, and the relays from the Set node, and posts the Note to those relays.

Once the workflow is built, you can test it with the testing form URL, and set it to "Active" to use the production form URL. That's it. You can now give posting access to anyone for any Npub. To revoke access, simply change the credentials or set to workflow to "Inactive".

It may also be the world's simplest Nostr client.

You can find the Nostr Form to Post a Note workflow here.

Push notifications on mentions and new notes

One of the things Nostr is not very good at is push notifications. Furthermore I have some unique itches to scratch. I want–

• To make sure I never miss a note addressed to any of my Npubs – For this I want a push notification any time any Nostr user mentions any of my Npubs,
• To make sure I always see all notes from key accounts – For this I need a push notification any time any of my Npubs post any Notes to the network,
• To get these notifications on all of my devices – Not just my phone where my Nostr regular client lives, but also on each of my laptops to suit wherever I am working that day.

I needed to build a Nostr push notifications solution.

To build this workflow I had to string a few ideas together–

• Triggering the node on a schedule – Nostrobots does not include a trigger node. As every workflow starts with a trigger we needed a different method. I elected to run the workflow on a schedule of every 10-minutes. Frequent enough to see Notes while they are hot, but infrequent enough to not burden public relays or get rate-limited,
• Storing a list of Npubs in a Nostr list – I needed a way to store the list of Npubs that trigger my notifications. I initially used an array defined in the workflow, this worked fine. Then I decided to try Nostr lists (NIP-51, kind 30000). By defining my list of Npubs as a list published to Nostr I can control my list from within a Nostr client (e.g. Listr.lol or Nostrudel.ninja). Not only does this "just work", but because it's based on Nostr lists automagically Amethyst client allows me to browse that list as a Feed, and everyone I add gets notified in their Mentions,
• Using specific relays – I needed to query the right relays, including my own HAVEN relay inbox for notes addressed to me, and wss://purplepag.es for Nostr profile metadata,
• Querying Nostr events (with Nostrobots) – I needed to make use of many different Nostr queries and use quite a wide range of what Nostrobots can do–
  • I read the EventID of my Kind 30000 list, to return the desired pubkeys,
  • For notifications on mentions, I read all Kind 1 notes that mention that pubkey,
  • For notifications on new notes, I read all Kind 1 notes published by that pubkey,
  • Where there are notes, I read the Kind 0 profile metadata event of that pubkey to get the displayName of the relevant Npub,
  • I transform the EventID into a Nevent to help clients find it.
• Using the Nostr URI – As I did with my NFC card article, I created a link with the nostr: URI prefix so that my phone's native client opens the link by default,
• Push notifications solution – I needed a push notifications solution. I found many with n8n integrations and chose to go with Pushover which supports all my devices, has a free trial, and is unfairly cheap with a $5-per-device perpetual license.

Once the workflow was built, lists published, and Pushover installed on my phone, I was fully set up with push notifications on Nostr. I have used these workflows for several weeks now and made various tweaks as I went. They are feeling robust and I'd welcome you to give them a go.

You can find the Nostr Push Notification If Mentioned here and If Posts a Note here.

In speaking with other Nostr users while I was building this, there are all kind of other needs for push notifications too – like on replies to a certain bookmarked note, or when a followed Npub starts streaming on zap.stream. These are all possible.

Use my workflows

I have open sourced all my workflows at my Github with MIT license and tried to write complete docs, so that you can import them into your n8n and configure them for your own use.

To import any of my workflows–

• Click on the workflow of your choice, e.g. "Nostr_Push_Notify_If_Mentioned.json",
• Click on the "raw" button to view the raw JSON, ex any Github page layout,
• Copy that URL,
• Enter that URL in the "import from URL" dialog mentioned above.

To configure them–

• Prerequisites, credentials, and variables are all stated,
• In general any variables required are entered into a Set Node that follows the trigger node,
• Pushover has some extra setup but is very straightforward and documented in the workflow.

What next?

Over my first four blogs I explored creating a good Nostr setup with Vanity Npub, Lightning Payments, Nostr Addresses at Your Domain, and Personal Nostr Relay.

Then in my latest two blogs I explored different types of interoperability with NFC cards and now n8n Workflow Automation.

Thinking ahead n8n can power any kind of interoperability between Nostr and any other legacy technology solution. On my mind as I write this:

• Further enhancements to posting and delegating solutions and forms (enhanced UI or different note kinds),
• Automated or scheduled posting (such as auto-liking everything Lyn Alden posts),
• Further enhancements to push notifications, on new and different types of events (such as notifying me when I get a new follower, on replies to certain posts, or when a user starts streaming),
• All kinds of bridges, such as bridging notes to and from Telegram, Slack, or Campfire. Or bridging RSS or other event feeds to Nostr,
• All kinds of other automation (such as BlackCoffee controlling a coffee machine),
• All kinds of AI Assistants and Agents,

In fact I have already released an open source workflow for an AI Assistant, and will share more about that in my next blog.

Please be sure to let me know if you think there's another Nostr topic you'd like to see me tackle.

GM Nostr.

@ 59cb0748:9602464b

Nostrでお世話になっている方も、お世話になってない方も、こんにちは！

タコ頭大吉です！

NIP-23を使った初めての投稿です。

今回は、私がここ数ヶ月中にデザインをした三種類のビタキセケースの紹介記事になります！！

ビタキセを買ったもののあまり自分の好みに合う外観や仕様のケースがなく、いくつかプロトタイプを作りそれなりに時間をかけて考えたケース達です。

これら３シリーズに関しては、FDMタイプの3Dプリンタの精度、耐久性、出力後の作業性を考慮して一つのパーツで完結することに拘って設計をしました。

一定以上の充填率でプリントをすればそれなりに丈夫なはずです。

また、基本的に放熱性と保護性を両立できるように設計をしたつもります。

それぞれのモデルについて簡単に紹介をさせていただきますので、よろしければ各リポジトリに付属のREADMEを読んでいただいて自作、フィードバックをいただけましたら幸いです。

それでは、簡単に各モデルの紹介をさせていたきます。

---

AirLiftFrame

最初に作ったモデルです！ 少し大きいのが難点ですが、分厚めのフレームをベースとし基盤周辺をあえて囲わない設計により、保護性と放熱を阻害しない事の両立を狙っています。

リポジトリへ

---

TwinAirLiftFrame

ビタキセを買い増ししたことにより、複数台をカッコよく運用したいという需要が自分の中に出てきたので、AirLiftFrameを2つくっつけたら良いのではと言うごくごく単純な発想でつくり始めたケースです。 しかし、ただ横並びにしただけでは廃熱が干渉するだけではなく、DCジャックやUSBポートへのアクセスが阻害されるという問題にすぐに気がつきました。 そこで、WebUI上でディスプレイの表示を上下反転出来ることに注目し、2台を上下逆向きに取り付ける事でそれらの問題を解決しました！

リポジトリへ

---

VoronoiShell

AirLiftFrameシリーズのサイズを小型化する事から始めたプロジョクトです。 縦横の寸法の削減だけではなく、厚みを薄くつくリたいという希望がありました。 所が単純に薄くすると、持った時に発熱する背面パーツに手が触れてしまったり、落下などでぶつかった際に背面パーツが破損する懸念がありました。 そこで、(当初は付けたくはなかった)背面保護用のグリルをデザインする必要が出てきました。 初めは多角形でしたがあまりにもダサく、調べている内にVoronoi柄という有機的なパターンに行き付き即採用しました。 結果、ビタキセを取り付けると柄が見えなくなるのが勿体無いぐらい個性的でスタイリッシュなデザインに仕上がりました。

リポジトリへ

---

いずれカスタム方法やインサートナットや増設ファンの選定方法等を紹介したいのですが、今回はNIP-23になれるという意図もあるので紹介に留めます！ また、他の関連OSハードウェアプロジェクトのケースもデザインできたらと思っております！

今後ともタコ頭をよろしくお願いいたします。

@ 84b0c46a:417782f5

• lumilumi The Nostr Web Client.

Lightweight modes are available, such as not displaying icon images, not loading images automatically, etc.

• nostr-share-component Demo

• Nostr Follow Organizer

Follow List ( kind3 ) organization tool.

• NAKE NIP-19, NIP-49 Encode/Decode Tool
• chrome extension
• firefox add-on
• nostviewstr

Addressable or Replaceable Event Editor ( いろんなリストエディター )

• luminostr

Addressable or Replaceable Event Recovery tool ( いろいろリカバリーツール )

• Nostr Bookmark Recovery Tool

Bookmark event ( kind:10003,30001,30003 ) recovery tool ( ぶくま復活させたいやつ )

• Profile Editor

プロフィールを編集するやつ - nostr-bookmark-viewer

Bookmark event ( kind:10003,30001,30003 ) Editor ( ぶっくまーくをみるやつ )

• Nostr Note Duplicater

Broadcast an event from relay to relay ( イベントをブロードキャストするやつ )

• もの画像サイト

• いろいろbotサイト

@ ec42c765:328c0600

この記事は前回の内容を把握している人向けに書いています（特にNostrエクステンション（NIP-07）導入）

前回：Nostrのカスタム絵文字の使い方

手順

1. 登録する画像を用意する
2. 画像をweb上にアップロードする
3. 絵文字セットに登録する

1. 登録する画像を用意する

以下のような方法で用意してください。

• 画像編集ソフト等を使って自分で作成する
• 絵文字作成サイトを使う（絵文字ジェネレーター、MEGAMOJI など）
• フリー画像を使う（いらすとや など）

データ量削減

Nostrでは画像をそのまま表示するクライアントが多いので、データ量が大きな画像をそのまま使うとモバイル通信時などに負担がかかります。

データ量を増やさないためにサイズやファイル形式を変更することをおすすめします。

以下は私のおすすめです。 * サイズ：正方形 128×128 ピクセル、長方形 任意の横幅×128 ピクセル * ファイル形式：webp形式（webp変換おすすめサイト toimg） * 単色、単純な画像の場合：png形式（webpにするとむしろサイズが大きくなる）

その他

• 背景透過画像
• ダークモード、ライトモード両方で見やすい色

がおすすめです。

2. 画像をweb上にアップロードする

よく分からなければ emojito からのアップロードで問題ないです。
普段使っている画像アップロード先があるならそれでも構いません。
気になる方はアップロード先を適宜選んでください。

既に投稿されたカスタム絵文字の画像に対して

• 削除も差し替えもできない → emojito など
• 削除できるが差し替えはできない → Gyazo、nostrcheck.meなど
• 削除も差し替えもできる → GitHub 、セルフホスティングなど

これらは既にNostr上に投稿されたカスタム絵文字の画像を後から変更できるかどうかを指します。
どの方法でも新しく使われるカスタム絵文字を変更することは可能です。
同一のカスタム絵文字セットに同一のショートコードで別の画像を登録する形で対応できます。

3. 絵文字セットに登録する

emojito から登録します。

右上のアイコン → + New emoji set から新規の絵文字セットを作成できます。

① 絵文字セット名を入力

基本的にカスタム絵文字はカスタム絵文字セットを作り、ひとまとまりにして登録します。

一度作った絵文字セットに後から絵文字を追加することもできます。

② 画像をアップロードまたは画像URLを入力

emojitoから画像をアップロードする場合、ファイル名に日本語などの2バイト文字が含まれているとアップロードがエラーになるようです。

その場合はファイル名を適当な英数字などに変更してください。

③ 絵文字のショートコードを入力

ショートコードは絵文字を呼び出す時に使用する場合があります。

他のカスタム絵文字と被っても問題ありませんが選択時に複数表示されて支障が出る可能性があります。

他と被りにくく長くなりすぎないショートコードが良いかもしれません。

ショートコードに使えるのは半角の英数字とアンダーバーのみです。

④ 追加

Add を押してもまだ作成完了にはなりません。

一度に絵文字を複数登録できます。

最後に右上の Save を押すと作成完了です。

画面が切り替わるので、右側の Options から Bookmark を選択するとそのカスタム絵文字セットを自分で使えるようになります。

既存の絵文字セットを編集するには Options から Edit を選択します。

以上です。

---

仕様

NIP-30 Custom Emoji

NIP-30 カスタム絵文字（和訳）

@ 2cb8ae56:84d30cba

ども、薄味のキャルピスでございます。
当記事は、「Nostr Advent Calendar 2024」7日目の記事です。
この記事を読んでいる人でいないとは思いますが、Nostrとはなんぞやとお思いの方は以下をご覧ください。

https://hello.nostrapp.me/

僕は「Nostrで過ごした2024年」というタイトルの通り、一年間を振り返ってみようと思います。

自己紹介

まず知らん人のために軽く自己紹介をします

「薄味のキャルピス」という名前で、色んな所にいるどこかの高校生です。 左利き、箸とベースとお盆は右手。

普段は学業の傍ら、画像を弄ったり作ったりしている上に、イヤホンを集めたりラジオにメッセージを送っています。

コーディングは出来ないテクノロジーまみれのガラクタ人間（→テックジャンカー）です

参加経緯とスタンス

なぜ参加したのかを思い出しながら書いていきます まず、どんな媒体でNostr（ノスター・ノストラ）の存在を知ったのかと言うと、ネットニュースです。

https://gigazine.net/news/20230425-nostr-intro/

こちらの記事で「そんなのあるんだ」と知り、4月1日ついにjoin!!!!

現時点での参加スタンスは「気楽に、素直に」という感じで参加しています

やりたいときにやりたいことをやるって言うリアルでは到底難しいことを、Nostrのなかでやっている気もします。

後述するNostrasia 2024の開催日「9月23日」を持って、Mastodon（マストドン）から乗り換え、上記のスタンスのもと、メインで精力的に活動しています。

Nostr活動年表

2024/04/01 Nostr Join!!!

2024/06/08 人生初オフ会「たくろうさんオフ」参加、LNアドレス追加。

2024/09/23 人生初小規模イベント「Nostrasia 2024」運営メンバーとして参加

2024/10/12 2度目のオフ会「デザイン談義」主催・参加

簡易的に各種紹介！

人生初オフ会「たくろうさんオフ」

渋三魚金でご飯→猿田彦珈琲でリラックス、Linux使ってると話を切り出す（唐突）→スクランブル交差点で解散。 ウォークマンの再生画面を送付した投稿を行う

人生初イベント「Nostrasia 2024」

あ、記事出したので見てください。

初版

第二版

2度目のオフ会「デザイン談義」

秋葉原の「創作空間caféアトリエ あきば店」で行われたオフ会。 ちょくちょく内容を上げているので、見ていってください。 https://nostter.app/npub19ju2u4sduewta4hxl22kke7se8yxm2puytzw47lr6y999pxnpjaqtjjfxj/2024/10/12 終了後、e☆イヤホン 秋葉原店にて、BTR13の在庫状況を確認し、在庫がないため予約しました。 （10月24日到着） 雑多すぎますが、一応こんな感じで大丈夫かな？

まとめ

僕がNostrに出会い、Nostrにのめり込むまでの話はいかがだったでしょうか。 Nostrに入る前、オフ会に参加するまでは「ネットにロクな人なんていない！」と思っていましたが、Nostrは違いましたね。 いい意味で期待はずれ、本当にいい人たちばかりで、とにかく自然体で接することができるSNSであると感じました。 そんな世界にぜひとも一回足を踏み入れてみてはいかがでしょうか？ それではまた、来年のアドベントカレンダー、及び開催されましたら「Nostrasia 2025」でお会いしましょう。

@ ec42c765:328c0600

てすと

nostr:nevent1qqst3uqlls4yr9vys4dza2sgjle3ly37trck7jgdmtr23uuz52usjrqqqnjgr

nostr:nevent1qqsdvchy5d27zt3z05rr3q6vvmzgslslxwu0p4dfkvxwhmvxldn9djguvagp2

@ ec42c765:328c0600

Nostr Advent Calendar 2024 の 12日目の記事です。

昨日の 12/11 は きりの さんの 2024年のNostrリレー運営を振り返る でした。

nostr-zap-view 作った

リポジトリ: https://github.com/Lokuyow/nostr-zap-view/
動作確認ページ: https://lokuyow.github.io/nostr-zap-view/

それ何？

特定の誰かや何かに宛てたZap（投げ銭）を一覧できるやつ
を
自分のWebサイトに設置できるやつ

---

自分のサイトに設置した例 * SNSリンク集ページ（最下部）: https://lokuyow.github.io/
おいくらサッツ（Zap一覧ボタン）: https://osats.money/
今日からビットコ（最下部）: https://lokuyow.github.io/btc-dca-simulator/

なんで作ったの？

私の去年のアドベントカレンダー
【Nostr】Webサイトにビットコインの投げ銭ボタンを設置しよう【Zap】
https://spotlight.soy/detail?article_id=ucd7cbrql/
が前提になってるけど長いので要約すると * ZapするやつはあるけどZap見るやつがないので欲しい * ZapをNostr（の典型的なkind:1クライアント）内だけに留めるのはもったいない * Webサイトの広告うざいからZap（的な何か）で置き換わって欲しい

お前だれ？

非エンジニア、非プログラマー
AIにコード出させてるだけ人

作った感想

できた

作った感想2

完成してから気付いた本当に作りたかったもの
こういうところにそのままZapを表示できる感じにしたい
（ここまでちゃんとした商業ブログでなく）個人のブログやHPの端っこに「Sponsored by」欄があって名前が表示される感じ
もうZapっていう文字もビットコインっていう文字もNostrも出さなくていいし説明もしなくていいのでは感がある
イメージはWebサイトを対象にしたニコニ広告 + スーパーチャット + 祭りとか神社の奉納者一覧

---

で思ったのは
個人からの投げ銭なら推し活的なものにしかならないけど
企業がNostrにアカウントを作ってサイトに投げ銭をしたら企業の広告になるんでは！？
~~企業がNostrにアカウントを！？デリヘルしか見たことない！~~

今後

思いつき、予定は未定
* ボタン→ダイアログ形式でなくバナー、Embed形式にしてページアクセスですぐ見れるようにする * 多分リレーに負荷がかかるのでなんかする * Zapの文字は出さず「Sponsored by」等にする * 単純な最新順でなくする * 少額Zapをトリミング * 一定期間（一か月など）ごとで金額順にソート * 多分リレーに負荷がかかるのでなんかする * 今は投稿宛てのZapをWebサイト宛てのZapと勝手に言い張ってるだけなのでちゃんとWebサイト宛てのZapにする * NIPの提案が必要 * ウォレットの準拠も必要 * リレー（wss://~）宛てのZapもできてほしい

将来

インターネットのすべてに投げ銭をさせろ

---

おわり

明日は mono さんの Open Sats 申請編 です！！

@ f0c7506b:9ead75b8

Abbas Kiarostami

• Bazı şeyleri yapmak, söylemekten daha kolaydır.

• Bütün güzel şeyleri bize toprak verir. Bütün güzel şeyler toprağa geri döner.

• Eğer mevsimlere bakarsanız her mevsim meyve getirir. Yazın meyve vardır, sonbaharda da. Kış farklı meyveler getirir, ilkbahar da. Hiçbir anne çocukları için bu kadar çok çeşit meyveyle buzdolabını dolduramaz.

• Kendimi bu hayattan kurtarmaya karar verdim. Ne için mi? Bu anlamanıza yardım etmeyecektir ve bunun hakkında sizinle konuşamam; anlayamazsınız. Anlamayacağınız için değil; çünkü benim hissettiklerimi hissedemezsiniz. Duygularımı anlayıp paylaşabilirsiniz, bana merhamet gösterebilirsiniz; ama acımı hissedebilir misiniz? Hayır. Acı çekersiniz ve ben de çekerim. Sizi anlarım. Acımı anlayabilirsiniz; ama onu hissedemezsiniz.

• İnsanın devam edemeyeceği bir an gelir.

• Birisine yardım etmek istediğiniz zaman bunu uygun biçimde yapmalısınız, bütün kalbinizle. Bu daha iyidir. Daha adil ve daha makul.

• İntiharın en büyük günahlardan birisi olduğunu biliyorum. Fakat mutsuz olmak da büyük bir günah. Mutsuzken başka insanları incitirsiniz. Bu da bir günah değil mi? Başkalarını incittiğinizde bu bir günah değil midir? Aileni incitiyorsun, arkadaşlarını, kendini incitiyorsun. Bu bir günah değil mi? Size yakın olan insanları incitiyorsanız bu da büyük bir günahtır.

• Yardım, mutlaka karşılığı ödenmesi gereken bir şey değildir.

• Size başımdan geçen bir olayı anlatacağım: henüz yeni evlenmiştim. Belaların her türlüsü bizi buldu. Öylesine bıkkındım ki her şeye son vermeye karar verdim. Bir sabah şafak sökmeden önce arabama bir ip koydum. Kendimi öldürmeyi kafama koydum. Yola koyuldum. Dut ağaçlarıyla dolu bir bahçeye vardım. Orada durdum. Hava henüz karanlıktı. İpi bir ağacın dalı üzerine attım; ama tutturamadım. Bir iki kere denedim ama kâr etmedi. Ardından ağaca tırmandım ve ipi sımsıkı düğümledim. Sonra elimin altında yumuşak bir şey hissettim: Dutlar. Lezzetli, tatlı dutlar. Birini yedim. taze ve suluydu. Ardından bir ikincisini ve üçüncüsünü. Birdenbire güneşin dağların zirvesinden doğduğunun farkına vardım. O ne güneşti, ne manzaraydı, ne yeşillikti ama! Birdenbire okula giden çocukların seslerini duydum. Bana bakmak için durdular. "Ağacı sallar mısın?" diye bana sordular. Dutlar düştü ve yediler. Kendimi mutlu hissettim. Ardından alıp eve götürmek için biraz dut topladım. Bizim hanım hâlâ uyuyordu. Uyandığı zaman dutları güzelce yedi. Ve hoşuna gitti. Kendimi öldürmek için ayrılmıştım ve dutlarla geri döndüm. Bir dut hayatımı kurtarmıştı.

• Bir türk, doktoru görmeye gider. Ve ona der ki: "Doktor bey, vücuduma parmağımla dokunduğumda acıyor, başıma dokunsam acıyor, bacaklarıma dokunsam acıyor, karnıma, elime dokunsam acıyor." doktor onu muayene eder ve sonra ona der ki: "vücudun sağlam; ama parmağın kırık!"

• Hayat dümdüz ilerleyen bir tren gibidir; rayların sonuna geldiğinde son durağa ulaşır. Ve ölüm son durakta bekler. Elbette, ölüm bir çözümdür; fakat ilk olarak değil. Genç yaşta hiç değil.

• Dünya göründüğü gibi değildir. Bakış açınızı değiştirmelisiniz ki dünya değişsin. İyimser olun. Her şeye olumlu tarafından bakın.

@ 4c5d5379:3a4383ee

first header

I'm testing YakiHonne article.

にほんごだよ

header

header

header

header

header

header

ヘッダ

ヘッダ

ヘッダ

ヘッダ

ヘッダ

ヘッダ

@ 6b0a60cf:b952e7d4

ビットコインのウォレットは取引形態によって2種類に分かれます。

オンチェーン(L1)

取引がブロックチェーンに刻まれるタイプ。時間がかかるし手数料が高い。

ライトニングネットワーク(L2)

ブロックチェーンに刻む前の少額決済を目的としたレイヤー。高速で手数料が安い。

NostrでZapを利用する場合はライトニングネットワーク(以下、LNと呼びます)のウォレットが使われますが、さらにその中でもZap対応/非対応で分かれることになります。

また、秘密鍵を誰が管理するかによっても2種類の呼び方に分かれます。

カストディアル

秘密鍵をサービスの運営に預けるタイプ。

ノンカストディアル/セルフカストディアル

秘密鍵(シードフレーズ)を自分で持っておくタイプ。

Nostrで人気があるWallet of Satoshi(以下、WoSと呼びます)はLNのカストディアルウォレットです。 今回はLNのセルフカストディアルウォレットであるPhoenixを使ってみて、その仕組みや注意点など、学んだことを記録したいと思います。

Phoenixでウォレットを作る場合、初回でシードフレーズ(12個の単語)が作られますので、大切に控えておきましょう。

WoSからPhoenixに送金してみる

メイン画面左下にあるReciaveからQRCode表示画面へ遷移します。そこでcopyボタンを押してLightning invoice(text)をコピーしましょう。

次に、WoSの画面からSendを選択し、クリップボードからの貼り付けを選択します。 金額を指定して送金します。

送金した額が満額届いてないんだけど？

下の方にService Feesとありますが、これはPhoenix運営(ACINQ)へのお布施ですね。結構高く見えますが初回だけです。 またMiner Feesという項目は、mempoolのfeeに連動して変わるようですが、これはチャネルを太くする(送受信できる金額の上限を上げる)ために使われる手数料になります。

財布が重たくなると手数料が取られる？

有り体に言えばそういうことになります。以下のように10,000satsをもらう度にチャネル拡張のための手数料が引かれています。

上記の8,000satsを受け取っている時には手数料が発生していませんね。これはチャネル拡張が必要ないギリギリの金額を狙って送金したためです。送金前は8,859satsの余裕がありました。送金後は1,719satsに減っています。(余裕分がぴったり8,000sats減るわけではないようです。このへんの仕組みはよくわかりません。) (画面は左上⚙️マークの設定からPayment channelsから。)

財布が軽くなると余裕が増える？

逆にPhoenixからWoSに5,000satsほど送金してみます。(手数料として24satsほど余計に抜かれました)

余裕(Inbound Liquidity)が5,883satsまで復活しています。受け取るばかりでなく、バランスよく送ることで財布を重たくしなければチャネル拡張せずに使い続けることができそうです。(太くしたチャネルは永遠に残るわけではなく、1年までらしいです)

自動でチャネル拡張にsatsを使われたくない！

自動チャネル拡張を設定で無効化できます。左上⚙️マークの設定からChannel managementから。

これでチャネル拡張が必要なほどの金額を送金しようとするとエラーになり失敗します。

まとめ

セルフカストディアルウォレットならではの概念があり、謎の手数料が発生したりして怖いイメージがありましたが、どういう理由で手数料が発生するのかを知り、設定でのコントロールの仕方を習得することである程度怖いイメージを払拭することができました。 しかしカストディアルウォレット(特にWoS)の使いやすさを再認識することにもなりました。ただ自分で管理することの重要性も理解していますので、徐々に知識を深めていこうと思います。

参考/謝辞

• Phoenix wallet（フェニックスウォレット）の使い方！ビットコインのセルフカストディができるアプリを解説 - 知っとこ！ビットコイン図鑑
• nostr:npub10zeurmg22wc89l8m3npw9cyu45cun0lvs6w3ep69cdpa25pna65s0994qz 様

@ 6bcc27d2:b67d296e

yugoです。 この記事は「Nostrasia2024 逆アドベントカレンダー」10/19の分です。Nostrasiaの当日はリアルタイムで配信を視聴していました。Nostrを使ってアプリケーションの再発明をすべきという発表を聴き、自分だったらどんなものを作ってみたいかを考えて少し調べたり試みたりしたのでその記録を書きます。また、超簡単なものですがおそらく世界初となるvisionOS対応のNostrクライアントをつくってみたので最後の方に紹介します。

アプリケーションを再発明する話があったのは、「What is Nostr Other Stuff?」と題したkaijiさんの発表でした。

Nostrプロトコルを使って既存のアプリケーションを再発明することで、ユーザ体験を損なわずにゆるやかな分散を促すことができ、プロトコルとしてのNostrも成長していくというような内容でした。

自分はまだNostrで何かをつくった経験はなかったので、実装に必要な仕様の知識がほとんどない状態からどのようなアプリケーションをつくってみたいかを考えました。

最初に思いついたのは、Scrapboxのようなネットワーク型のナレッジベースです。自分は最近visionOS勉強会をやっており、勉強会でナレッジを共有する手段としてScrapboxの導入を検討していました。

Nostrコミュニティにも有志によるScrapboxがありますが、Nostrクライアントがあればそれを使うだろうから同じくらいの実用性を備えたクライアントはまだ存在しないのではないかという見立てでした。

長文投稿やpublic chatなどの機能を組み合わせることで実現できるだろうか。そう思っていた矢先、NIP-54のWikiという規格があることを知りました。

https://github.com/nostr-protocol/nips/blob/master/54.md

まだちゃんとは読めていないですが、Scrapboxもwikiソフトウェアだし参考になりそうと思っています。正式な仕様に組み込まれていないようで、採用しているクライアントはfiatjafによるリファレンス実装(?)のwikistrくらいしか見つかりませんでした。

Scrapboxのようなナレッジベースを志向するNostrクライアントがあれば、後述するvisionOS対応クライアントの存在もありアカウントを使いまわせて嬉しいので試してみたいです。もし他にも似たようなサービスをどなたか知っていたら教えてください。

また現在は、勉強会やワークショップ、ハッカソンなどのコラボレーションワークを支援するためのツールを自分たちでも開発しています。Apple Vision Proに搭載されているvisionOSというプラットフォームで動作します。

https://image.nostr.build/14f0c1b8fbe5ce7754825c01b09280a4c22f87bbf3c2fa6d60dd724f98919c34.png

この画面で自分が入りたいスペースを選んで共有体験を開始します。

スライドなどのコンテンツや自らのアバターを同期させることで、遠隔地にいてもまるでオフラインかのように同じ空間を共有することが可能になります。

https://image.nostr.build/cfb75d3db2a9b9cd39f502d6426d5ef4f264b3d5d693b6fc9762735d2922b85c.jpg

ということなので、急遽visionOS対応のクライアントを作ってみました。検索しても1つも事例が出てこなかったので多分まだ世界で実装しているアプリはないのではないでしょうか。

とはいえ、クライアントを名乗っているもののまだ大した機能はなく、リレーからデータを取得するだけの読み取り専用です。

https://image.nostr.build/96e088cc6a082528682989ccc12b4312f9cb6277656e491578e32a0851ce50fe.png

画像では自分のプロフィールデータをリレーから取得しています。

まだどのライブラリもvisionOSに対応していなかったりで手こずったものの仕様の勉強になりました。

ただvisionOSアプリはiOSアプリ同様NIP-7が使えないので秘密鍵を自分で保管しなくてはならず、今後どう対処すべきかわかりかねています。これから時間ある時に少しずつ調べていこうと思っていますが、ネイティブアプリの秘密鍵周りはあまりリソースが多くないようにも感じました。もしどなたかその辺の実装に詳しい方いたら教えていただけると嬉しいです。

準備ができたらそのうちコードも公開したいと思っています。

これから少しずつ色んな機能を実装しながらNostrで遊んでいきたいです！

@ 3bf0c63f:aefa459d

Nostr: a quick introduction, attempt #2

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

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

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

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

@ f240c9c2:6c0c0a86

⚠️一部のクライアントでは表示が崩れている場合があります。HablaやYakihonneから見てください

---

NIP-51のkind:30007に関するPull Requestが承認され、2024/08/20時点で本家NIPsにもマージされました。今後「リポスト」や「リアクション」などの特定のkind^1をミュートするためのセット^2が対応するクライアントで使えるようになります。

kind mute set(kind:30007)にて、"d"タグには対応するイベントの種類の番号(リポストなら"6"、リアクションなら"7")を入れ、"p"タグにはユーザの公開鍵(pubkey)を入れるそうです。

nostrクライアントのnostterは、これに対応したことで、Twitter(現:X)の「リポストをオフのする」機能のように"特定ユーザーのリポストをクライアント上で非表示にする"といったことができるようになりました。リアクションも同様に非表示にできます。 nostterでは、2024/07/29以降、ユーザーのプロフィール画面からこれらの設定を行えるようになっています。

2024/06/22 20時の時点では、nostter上ではこれを設定する画面が用意されていなかったので、別アプリを用いたり、イベントを自分で投げるなどして別途設定する必要がありました。 以下は、別アプリを用いて設定した際の手順です。

手順

kind:30007はのすとびうあというWebアプリで設定しました。 以下のようにのすとびうあのホーム画面「リストの種類」で30007を入力するか、

https://nostviewstr.vercel.app/<npub文字列>/30007にアクセスして設定画面にいけました^3。

左下の方にある≡を押して

ポップアップの「編集」を押して

ここではリポストのミュートのため、IDの欄に対応するイベントの種類の番号である「6」を入れて

右下にある青いボタン押して

Userの欄にリポストをミュートするユーザーの公開鍵のnpub文字列を入れ、public(ミュート状況が公開される)あるいはprivate(非公開)のボタンを押したら

そのユーザーが追加されて設定完了！

この設定を行うことで、入力した公開鍵(ユーザー)のリポストをnostter上でもミュートできました🙌

リポストやリアクションがどのように表示されるかをユーザーがコントロールできると便利なので、今後いろんなクライアントで対応されればいいな〜と思います！

@ 4c96d763:80c3ee30

Changes

Rusty Russell (3):

• Makefile: fix missing dependencies on bolt11 headers.
• bolt11: update to latest version from CLN
• bolt11: remove unneeded fields.

William Casarin (1):

• ndb_filter_from_json

pushed to nostrdb:refs/heads/master

@ 27676f17:0726572a

foobar

@ 3f770d65:7a745b24

Several months ago, nostr:npub1hqaz3dlyuhfqhktqchawke39l92jj9nt30dsgh2zvd9z7dv3j3gqpkt56s and I set out to do tackle a task that had never been done before throughout Nostr's short history. We decided adopt the "go big, or go home" mentality and give our best effort to Purple Pill all of the nostr:npub167n5w6cj2wseqtmk26zllc7n28uv9c4vw28k2kht206vnghe5a7stgzu3r conference.

We couldn't accomplish this monumental task without the help of the Nostr community. From every day Nostriches and plebs, to legendary developers putting their blood, sweat, and tears into building this new protocol, to several companies within the Nostr ecosystem, everyone was going to need to do their part to turn this dream into a reality.

The mission

For the original vision of Nostr at BTC Prague, we planned on supporting the smallest available booth and a small panel on the secondary stage. The plan was for any Nostr developer to contribute what they could and then use the Nostr booth as a central hub to onboard users to their applications, provide support to their users, and meet the community. I embarked on my first crowdfunding journey and was able to initially raise over 10M sats thanks to the greater Nostr community donating towards our efforts.

Shortly afterwards, I was approached by nostr:npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m from Satlantis. He had planned on doing a mainstage presentation at BTC Prague on his new Nostr powered application. He asked me if I wanted to combine our efforts to upgrade the Nostr booth to the largest booth possible to give Nostr an even larger presence. I reached out to Avi and several other trusted Nostriches to see their opinions on this potential upgrade and everyone seemed to agree that we should continue with the "go big, or go home" mentality and try our best to Purple Pill all of Prague.

Now with a larger goal at hand, we were able to garner even more support from the Nostr community in addition by adding Highlighter from nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft and Primal from nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr as larger contributors.

The final tallies for funds raised were 16M+ sats from the greater Nostr community and 38M+ sats raised from Satlantis, Primal, and Highlighter. (We did have to raise a little more than originally anticipated because the Bitcoin 58K Gang made the fiat value of Bitcoin dip down for a bit right when we were trying to finalize payment.)

Putting it all together

This support enabled us to secure one of the four large booths at BTC Prague and a main stage panel. Given that these three companies made significant contributions, enabling our acquisition of the largest booth, we decided that it was logical to feature these companies more prominently. However, it was crucial to strike a delicate balance here. While emphasizing that this booth represented the Nostr community and was a true community effort, we also wanted to acknowledge and showcase those who made it possible. These companies could have opted for smaller individual booths, but their collaboration in a unified space demonstrates Nostr's principles of openness and interoperability—demonstrating that everyone and everything can work together seamlessly.

Therefore, we included as many logos across the Nostr ecosystem as possible throughout our iconography.

And, we also had a dedicated area of the booth highlighting our larger contributors.

The results exceeded all expectations. For three days during the BTC Prague conference, the Nostr booth was continuously bustling with activity. Attendees ranged from individuals who had never heard of Nostr before to those who were curious, active users within the ecosystem, and developers creating the applications we use daily. It was a remarkable community effort, with unexpected volunteers stepping up to onboard new users and provide support. Recognizing our busy schedules and flocks of new Nostriches hatching, they chose to assist in our efforts, offering help, and answering questions. It was a truly inspiring experience. Despite the busyness, the enthusiasm and support of so many people made each day enjoyable and dynamic, ensuring there was never a dull moment and we were always surrounded by friends.

Booth takeaways

As this was our very first attempt at doing something like this, I'd like to do a personal post mortem and highlight many of our successes and even some areas where I feel we can improve upon in the future.

Several Nostriches went above and beyond, helping onboard people and answer questions for three days straight. nostr:npub17plqkxhsv66g8quxxc9p5t9mxazzn20m426exqnl8lxnh5a4cdns7jezx0 nostr:npub1spdnfacgsd7lk0nlqkq443tkq4jx9z6c6ksvaquuewmw7d3qltpslcq6j7 nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1k6tqlj78cpznd0yc74wy3k0elmj4nql87a3uzfz98tmj3tuzxywsf0dhk6 nostr:npub1md39ua3h2s7204a7v5p9sdxmxx9qc7m4kr3r6naeuwfznad6d7nsxpctp9 nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w nostr:npub1zga04e73s7ard4kaektaha9vckdwll3y8auztyhl3uj764ua7vrqc7ppvc were the lifeblood of the booth, always answering questions themselves or referring them to others if they were unable to help, didn't know the answer or were busy at the time. You all put in the work and deserve much credit and thanks. Even nostr:npub1995y964wmxl94crx3ksfley24szjr390skdd237ex9z7ttp5c9lqld8vtf was helping with onboarding!

Additionally, beyond general use case questions, we also had many developers stop by and answer many more technical questions for those wanting to learn a bit more too. nostr:npub1zach44xjpc4yyhx6pgse2cj2pf98838kja03dv2e8ly8lfr094vqvm5dy5 nostr:npub1v0lxxxxutpvrelsksy8cdhgfux9l6a42hsj2qzquu2zk7vc9qnkszrqj49 nostr:npub1arkn0xxxll4llgy9qxkrncn3vc4l69s0dz8ef3zadykcwe7ax3dqrrh43w nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft were often seen answering more technical questions on various developmental topics.

Identifying areas for improvement is challenging, as the entire team of Nostriches performed exceptionally well, exceeding expectations. The event was a whirlwind of activity, with constant engagement and zero downtime. Volunteers seamlessly rotated at the front counter answering questions and distributing items to attendees. (Thanks nostr:npub1cgcwm56v5hyrrzl5ty4vq4kdud63n5u4czgycdl2r3jshzk55ufqe52ndy . Your nostr.how and nostrapps.com business cards were a HUGE help here!)

Full disclosure, I personally didn't leave the booth for three days all that much for two reasons. 1) Because I love to #GrowNostr and talk to people and 2) Because I was worried that the booth would turn into a corporate Primal or Satlantis show. However, this wasn't the case. While these teams did have a large presence with many team members all wearing t-shirts, none of my fears became a reality. If people asked questions about Nostr in general, that was discussed. If people asked questions about Primal or Satlantis, that was discussed. I personally recommended numerous social apps, Damus, Amethyst, Primal, Nostur, Nos.social - all of them. The booth was a true decentralized effort and I absolutely did not need to worry as much as I did, but I felt like I had an obligation to fulfill and I wanted to be there to see it through.

If I had to choose an area that needed improvement, I'd say that the three Satlantis women that nostr:npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m brought with him were supposed to shadow some of us to learn more about Nostr, so that they could then use this information to do the initial intake booth questions before making the referral to those with more information, but this just didn't happen. We were all so busy. Sorry! It was just too hard to coordinate. Maybe in the future we can prepare a bit more in this area. Although, nostr:npub1hz5alqscpp8yjrvgsdp2n4ygkl8slvstrgvmjca7e45w6644ew7sewtysa did a fantastic job, jumping right in there head first!

Secondly, we could have improved our television capabilities. We rotated from showing the live dashboard from the booth's Zap.stream livestream, to showing Primal.net/explore Nostr statistics, to showing nostr:npub1lelkh3hhxw9hdwlcpk6q9t0xt9f7yze0y0nxazvzqjmre3p98x3sthkvyz 's Nostr Documentary on loop, to playing the Satlantis promotional video. The majority of the time our TV was playing the same Nostr Documentary. It's great! I love that video, but we may be able to work out a better schedule and rotation mechanism in the future to showcase more content equally. Plus, I don't want to always be on the TV. I don't want people getting the wrong idea.

Nostr takeaways

After speaking with hundreds of people at BTC Prague, I feel that I've discovered the best way to describe Nostr.

Nostr has a portable digital social identity, allowing you to be in control of your digital social identity for the very first time, allowing you to take your entire social graph with you, every time you use a different application from Nostr's ecosystem.

Nostr is the social glue that binds all of your apps together.

In general, at BTC Prague, while explaining Nostr to people, the digital social identity route was what clicked with the most people. From there, it's not a long stretch to understand building a reputation and web of trust either.

Many people do not use the "Other Stuff" and explaining to them how to use these applications is hard. People want a native application.

Damus, Primal, and Amethyst seem to be the number one apps that people are using, with maybe Primal being the number one altogether? This is probably due to Primal being available on Android, iOS, and the web. Also, many people don't know that Damus still supports Zaps via the Nostr script workaround. I had to show many how to enable Zaps.

Everyone wants Nostr at their conference

There is significant interest in featuring Nostr at various conferences. Although not everyone has reached out, numerous individuals at BTC Prague expressed enthusiasm about incorporating a Nostr booth, along with several Nostr talks and sessions, into their upcoming events. They recognize the critical role Nostr and free speech play globally and acknowledge Nostr's popularity within the Bitcoin community. However, they also understand that more work is needed, and we must continue our efforts to onboard and engage new users.

I have two primary observations on this matter:

• The community effort demonstrated here serves as a blueprint for success. We have proven that this approach to growing Nostr is effective, desired, and necessary. The engagement at our booth and attendance at our panels prove this with ease.

• This fundraising initiative is likely a one-time effort. I cannot, in good conscience, continue to ask the community to bootstrap these endeavors. If we are to sustain these booths and promote Nostr at similar conferences, the conference organizers themselves must provide substantial support or discounts to foster broader Nostr adoption. While I understand that conferences entail significant operational costs, it is not feasible for Nostr developers and the broader Nostr community to finance these efforts continuously. Additionally, I would not feel comfortable requesting financial contributions from you all again for this purpose.

Looking forward

Will we do _this _again? I don't know. While our initial endeavor was a complete success, it would be unfortunate to cease our efforts just as we are gaining momentum.

Avi and I have a lot to discuss between ourselves and a lot to discuss with all of you.

Thank you all from the bottom of my heart. Thank you nostr:npub1dtgg8yk3h23ldlm6jsy79tz723p4sun9mz62tqwxqe7c363szkzqm8up6m nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub16c0nh3dnadzqpm76uctf5hqhe2lny344zsmpm6feee9p5rdxaa9q586nvr for making all of this possible. Thank you to every single Nostrich that donated your hard earned sats to make this possible. Thank you to all of the developers that built all of this to make all of this possible. Thank you to everyone else <3

Keep building.

@ 3bf0c63f:aefa459d

Report of how the money Jack donated to the cause in December 2022 is being spent.

Bounties given

June 2024

• Darashi: 5,000,000 - maintaining nos.today, searchnos, search.nos.today and other experiments
• Toshiya: 5,000,000 - keeping the NIPs repo clean and other stuff

May 2024

• James: 3,500,000 - https://github.com/jamesmagoo/nostr-writer
• Yakihonne: 5,000,000 - spreading the word in Asia
• Dashu: 9,000,000 - https://github.com/haorendashu/nostrmo

February 2024

• Viktor: 5,000,000 - https://github.com/viktorvsk/saltivka and https://github.com/viktorvsk/knowstr
• Eric T: 5,000,000 - https://github.com/tcheeric/nostr-java
• Semisol: 5,000,000 - https://relay.noswhere.com/ and https://hist.nostr.land relays
• Sebastian: 5,000,000 - Drupal stuff and nostr-php work
• tijl: 5,000,000 - Cloudron, Yunohost and Fraidycat attempts
• Null Kotlin Dev: 5,000,000 - AntennaPod attempt

December 2023

• hzrd: 5,000,000 - Nostrudel
• awayuki: 5,000,000 - NOSTOPUS illustrations
• bera: 5,000,000 - getwired.app
• Chris: 5,000,000 - resolvr.io
• NoGood: 10,000,000 - nostrexplained.com stories

October 2023

• SnowCait: 5,000,000 - https://nostter.vercel.app/ and other tools
• Shaun: 10,000,000 - https://yakihonne.com/, events and work on Nostr awareness
• Derek Ross: 10,000,000 - spreading the word around the world
• fmar: 5,000,000 - https://github.com/frnandu/yana
• The Nostr Report: 2,500,000 - curating stuff
• james magoo: 2,500,000 - the Obsidian plugin: https://github.com/jamesmagoo/nostr-writer

August 2023

• Paul Miller: 5,000,000 - JS libraries and cryptography-related work
• BOUNTY tijl: 5,000,000 - https://github.com/github-tijlxyz/wikinostr
• gzuus: 5,000,000 - https://nostree.me/

July 2023

• syusui-s: 5,000,000 - rabbit, a tweetdeck-like Nostr client: https://syusui-s.github.io/rabbit/
• kojira: 5,000,000 - Nostr fanzine, Nostr discussion groups in Japan, hardware experiments
• darashi: 5,000,000 - https://github.com/darashi/nos.today, https://github.com/darashi/searchnos, https://github.com/darashi/murasaki
• jeff g: 5,000,000 - https://nostr.how and https://listr.lol, plus other contributions
• cloud fodder: 5,000,000 - https://nostr1.com (open-source)
• utxo.one: 5,000,000 - https://relaying.io (open-source)
• Max DeMarco: 10,269,507 - https://www.youtube.com/watch?v=aA-jiiepOrE
• BOUNTY optout21: 1,000,000 - https://github.com/optout21/nip41-proto0 (proposed nip41 CLI)
• BOUNTY Leo: 1,000,000 - https://github.com/leo-lox/camelus (an old relay thing I forgot exactly)

June 2023

• BOUNTY: Sepher: 2,000,000 - a webapp for making lists of anything: https://pinstr.app/
• BOUNTY: Kieran: 10,000,000 - implement gossip algorithm on Snort, implement all the other nice things: manual relay selection, following hints etc.
• Mattn: 5,000,000 - a myriad of projects and contributions to Nostr projects: https://github.com/search?q=owner%3Amattn+nostr&type=code
• BOUNTY: lynn: 2,000,000 - a simple and clean git nostr CLI written in Go, compatible with William's original git-nostr-tools; and implement threaded comments on https://github.com/fiatjaf/nocomment.
• Jack Chakany: 5,000,000 - https://github.com/jacany/nblog
• BOUNTY: Dan: 2,000,000 - https://metadata.nostr.com/

April 2023

• BOUNTY: Blake Jakopovic: 590,000 - event deleter tool, NIP dependency organization
• BOUNTY: koalasat: 1,000,000 - display relays
• BOUNTY: Mike Dilger: 4,000,000 - display relays, follow event hints (Gossip)
• BOUNTY: kaiwolfram: 5,000,000 - display relays, follow event hints, choose relays to publish (Nozzle)
• Daniele Tonon: 3,000,000 - Gossip
• bu5hm4nn: 3,000,000 - Gossip
• BOUNTY: hodlbod: 4,000,000 - display relays, follow event hints

March 2023

• Doug Hoyte: 5,000,000 sats - https://github.com/hoytech/strfry
• Alex Gleason: 5,000,000 sats - https://gitlab.com/soapbox-pub/mostr
• verbiricha: 5,000,000 sats - https://badges.page/, https://habla.news/
• talvasconcelos: 5,000,000 sats - https://migrate.nostr.com, https://read.nostr.com, https://write.nostr.com/
• BOUNTY: Gossip model: 5,000,000 - https://camelus.app/
• BOUNTY: Gossip model: 5,000,000 - https://github.com/kaiwolfram/Nozzle
• BOUNTY: Bounty Manager: 5,000,000 - https://nostrbounties.com/

February 2023

• styppo: 5,000,000 sats - https://hamstr.to/
• sandwich: 5,000,000 sats - https://nostr.watch/
• BOUNTY: Relay-centric client designs: 5,000,000 sats https://bountsr.org/design/2023/01/26/relay-based-design.html
• BOUNTY: Gossip model on https://coracle.social/: 5,000,000 sats
• Nostrovia Podcast: 3,000,000 sats - https://nostrovia.org/
• BOUNTY: Nostr-Desk / Monstr: 5,000,000 sats - https://github.com/alemmens/monstr
• Mike Dilger: 5,000,000 sats - https://github.com/mikedilger/gossip

January 2023

• ismyhc: 5,000,000 sats - https://github.com/Galaxoid-Labs/Seer
• Martti Malmi: 5,000,000 sats - https://iris.to/
• Carlos Autonomous: 5,000,000 sats - https://github.com/BrightonBTC/bija
• Koala Sat: 5,000,000 - https://github.com/KoalaSat/nostros
• Vitor Pamplona: 5,000,000 - https://github.com/vitorpamplona/amethyst
• Cameri: 5,000,000 - https://github.com/Cameri/nostream

December 2022

• William Casarin: 7 BTC - splitting the fund
• pseudozach: 5,000,000 sats - https://nostr.directory/
• Sondre Bjellas: 5,000,000 sats - https://notes.blockcore.net/
• Null Dev: 5,000,000 sats - https://github.com/KotlinGeekDev/Nosky
• Blake Jakopovic: 5,000,000 sats - https://github.com/blakejakopovic/nostcat, https://github.com/blakejakopovic/nostreq and https://github.com/blakejakopovic/NostrEventPlayground

@ 3c984938:2ec11289

The Chamorros: People of my island They islanders for centuries took care of the island. They fished, farmed, hunted, voyaged, made tools, art, had stories, had marriages within clans. Then, the Spanish came. When they first came, the Chamorros boarded their boat to greet the weird people(I'm sure they thought they were weird too). It started peaceful until the Spaniards coffer's slowly dried up. This led to the occupation of the island and grew oppressive. Eventually, The Spanish lost the war to the Americans. Guam was then sold to the American gov't as spoils of war, trading one oppressive regime for another.

The TakeOver Process-1

The TakeOver Process-2

The TakeOver Process-3

Get a job, you lazy islanders. We need to tax you, come work for us. This was the price to become American to the indigenous islanders.

Then the war came. close up

Guam was hit first before Pearl Harbor(The international Date line puts Guam timezone first ahead) but after this, The Japanese invaded and then occupied the island. Note at the bottom, The American Naval governor surrendered. This led to the islanders thus to become slaves to the Japanese Empire.

Recall "Day of Infamy" by FDR

Life under Japanese Rule Note Northern Marianas islands are the smaller islands above Guam. See the next image below.

Map of the island geography. Guam is referred as NYC in the Marianas. The rest are really, really small.

Nearly 16k of indigenous islander died, by the end of the war less than 6kish Chamorro survived.

The Federal Government then claimed parts of the land and since then and haven't returned it. They've returned some of it. This was a long time ago, I think it's time to let it go. Some islanders demand war repatriations. It makes zero sense to demand money from future Americans to pay for those war repatriations. The enemy is not the people, it's those that wield the pen to create unreasonable bills and the ones that enforce it.

Final Words. The islanders lived peaceful. There was no room to be a bad person of the colony because that person was risked getting shunned. Often, they sent the bad natives (thus becoming 2nd class citizens) inland, barring them from getting access to the ocean. But the land is rich and fertile. Instead of saltwater fish, they had fresh water 🐟fish, 🐍eel, 🦐shrimp and 🦞crawfish and plenty of fruit to eat and farm.

They didn't ask to become Spanish or American. It was this way or the highway. When countries want to expand they need more territories, land, money and human capital(your life energy). History doesn't repeat, it just rhymes.

🦋The best way to combat this is go back to a similar economy that is less corruptible. I believe Bitcoin can do this. History gives clues. Don't trust, verify.

Thank you for joining me on this walk (lol, reading) through the museum, please comment if you enjoyed this.

@ 4c96d763:80c3ee30

Here's a quick script for generating git shortlog longform notes on git push. It currently powers the Damus Code nostr account:

Let's say you are hosting a bare git repository on a server at git/project. You can add a post-receive hook that generates a longform note when you push to the server:

In server:git/project/hooks/post-receive:

```bash

!/usr/bin/env bash

commit_body="" last="" project="my-project" # update this with your project name sec="abcdef..." # update this with your secret key branch="master"

while read oldrev newrev refname; do branch=$refname last=$newrev relays="wss://relay.damus.io wss://nos.lol" commit_body=$(git shortlog $oldrev..$newrev | awk -f /home/user/markdown-shortlog.awk) done

if [[ $branch == "refs/heads/master" ]]; then

nostril --content "# Changes

$commit_body" \ --envelope \ --kind 30023 \ --tag title "$project" \ --tag summary "Latest codebase changes to $project" \ --tag t gitlog \ --sec $sec \ | nostcat --connect-timeout 1000 $relays fi ```

you'll need nostril, nostcat, and markdown-shortlog.awk:

```awk /^[^ ]/ { if (author) { print "" } author = $0 print "## " author }

/^ / { print "-" substr($0, 6) } ```

Now when you push, it will generate a longform note that looks something like this:

Example

William Casarin (10):

• fix warnings
• readme: add usage
• textmode: fix coloring of abbreviated names
• profiling: update puffin version
• refactor: move note into its own widget
• refactor: rename widgets to ui
• ui: simplify note widget
• get all missing ids from all timelines
• initial inline note previews
• fix until filters

kernelkind (6):

• Add custom visual themes
• Add modular custom text styles
• Apply app style to AccountLoginView
• Add MobileAccountLoginView
• Refactor 'ui tests' conception to previews
• Use custom style in app

@ f77dfdcf:17e93422

Proof of Work เป็น concept ที่คนที่เคยศึกษาการทำงานของ bitcoin อาจจะเคยได้ยินผ่านหูมาบ้าง แต่จริง ๆ แล้ว สิ่งนี้สามารถนำมาประยุกต์ใช้กับชีวิตประจำวันของเราได้อย่างเป็นธรรมชาติมาก

Proof of Work สำหรับ bitcoin เอาแบบสั้น ๆ คือ การที่เราเจอ ตัวเลขที่ถูกต้อง (Proof) ซึ่งได้จากการขุด ที่จะเกิดขึ้นได้โดยการใช้พลังงานและเวลาของเครื่องขุดในการคำนวณตัวเลข (Work)

ยิ่งมี Proof of Work ใน chain เยอะขึ้น ก็ทำให้ transaction มี confirmation มากขึ้น

ถ้าจะให้เขียนให้ครบจบตรงนี้ คนอ่านน่าจะตาลอย แนะนำให้ลองอ่านต่อใน Inventing Bitcoin ดูครับ

พอเราซูมออกมาเป็นภาพกว้าง ๆ Proof of Work จะหมายถึง “หลักฐาน” ที่เกิดขึ้น จากการทำ “งาน”

งาน (Work)ในที่นี้ คือ การลงทุนทาง “เวลา” ไปกับการทำส่ิง ๆ หนึ่ง ซึ่งจะได้ผลตอบแทนเป็น Proof of Work ในรูปแบบใดรูปแบบหนึ่ง

Proof ที่พูดถึง ไม่จำเป็นต้องเป็นชิ้นงานที่มองเห็นหรือจับต้องได้ มันอาจจะหมายถึงทักษะ ความรู้ หรือ ประสบการณ์ ก็ได้

ตัวอย่างในชีวิตประจำวันชัด ๆ เลยก็อย่างเช่น

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

แต่มันมีข้อสังเกตอยู่อย่างหนึ่ง คือ เราต้องมองให้ออก ว่าอะไรเป็น Proof of Work จริง ๆ ของแต่ละสิ่ง

อย่างบางที เราบอกว่า เราเข้าใจเรื่องนี้นะ เพราะเราเคยเรียนคลาสนี้มา และเราอาจจะคิดว่าเอารูปถ่ายหรือประกาศนีย์บัตรมันเป็น Proof of Work ได้ แต่จริง ๆ แล้วไม่น่าใช่ มันคือ Proof of อะไรไม่รู้

อ่ะ ๆ มันอาจจะเป็น Proof ว่าเราเคยไปเรียนมาจริง อันนี้ยอมรับได้ แต่ไม่ใช่ว่ามันจะเป็น Proof ว่าเราเข้าใจเรื่องนั้นได้โดยตรง

เพราะ Proof ของ Work ที่เรากำลังพูดถึง มันคือ knowledge ที่อยู่ในหัวเรา ถ้าเราอยากโชว์ว่ามี Proof of Work จริง ๆ เราต้องเอาสิ่งที่ได้เรียนรู้ มาแชร์ให้คนอื่นฟังได้

และสังเกตดี ๆ จะเห็นว่า Proof of Work ที่ได้พวกนี้ มันเป็นสิ่งที่จะติดไปกับตัวเราทั้งหมดเลย มันจึงเกิดเป็น quote ที่ว่า

“You are your Proof of Work”

ซึ่งสื่อว่า สิ่งที่เราเป็น ล้วนเป็น Proof of Work มาจากสิ่งที่เราทำทั้งสิ้น และยิ่งเรามี Proof of Work เยอะขึ้น เราก็จะยิ่งเติบโตขึ้นเรื่อย ๆ

บางทีเราสามารถมองได้ด้วยตาเปล่าด้วยซ้ำ ว่าใครมี Proof of Work ที่มากหรือน้อย เพราะมันจะมันสะท้อนออกมาในรูปแบบของความมั่นใจ

พอรู้จักสิ่งที่เรียกว่า Proof of Work แล้ว สุดท้าย เราต้องกลับมาถามตัวเอง ว่าสิ่งที่เราทำอยู่ มันกำลังให้อะไรกับเรา กำลังสอนอะไรกับเรา หรือมันจะมอบ Proof of Work ที่เราต้องการ สำหรับเป้าหมายของเราในอนาคตหรือเปล่า

พิจารณามันให้ดี และอย่าลืม

หมั่นสร้าง Proof of Work ให้กับตัวเอง

Reference

https://youtu.be/E0LYMhjHnBU?si=AY6ySrTy5t-OgYFT

@ 7bdef7be:784a5805

I wrote Oracolo (see the announcement below) because I was brainstorming about Nostr "long format" and thinking about how to promote it. There seems to be little love for this format, why?
Long posts should have interesting value because the author usually put effort into them, and are produced for a long-term fruition. In the end, blogging was one of the most productive strands on the web, and still holds considerable importance.

But in standard (kind-1) social clients they are rather hidden. I think many people don't even know they exist, they probably intuit something just because they see a particular formatting. This is quite evident if you compare the responses/zaps/reactions of the short notes with the long ones, the latter have far fewer interactions, a fact that I read as less exposure to readers.

Interlude: don't know what this "long format" stuff is?
Check https://habla.news or https://highlighter.com

I think the situation can be largely improved with some adjustments in kind-1 clients:

• Add a tab/section to the user's profile, next to the usual posts/responses, that lists only the long format notes;
• Highlight/pinning recent long notes in the user's profile to give them visibility; the user picture could also have a special mark that alerts about fresh content available;
• In the feed show the preview of long notes with a special design, and allow the user to read them in a separate/immersive view (or just link to njump.me);
• In an appropriate context (es. at the footer of a long note) invite the user to discover long format and post his own content;
• Offer a filtered feed that display only long format notes;

Finally, we should probably also evaluate and agree on a new labeling in clients, because “long notes” is self-explanatory but also a bit confusing next to "plain notes”. Perhaps “articles” might be a better term.

If clients bring more interaction on articles, content creators are naturally incentivized to invest their time in this area, thus increasing the production of in-depth content that may be of interest even to those who are not as involved in social media dynamics.

Memo for kind-1 clients: interoperability is our superpower and currently your are the main entrance to Nostr, so don't be fearful or lazy, please embrace it.

nostr:nevent1qqsrrcl7sfaxd505lyezj7u54tpdg93x0swpcpe0xj5adax5l6xz3yspzamhxue69uhky6t5vdhkjmn9wgh8xmmrd9skctcpr3mhxue69uhkxmm4de68y6t9wvhxv6tpw34xze3wvdhk6tcppemhxue69uhkummn9ekx7mp0aagyzp

nostrdesign

@ 6ad08392:ea301584

Release announcement & short overview

Two years, six drafts, and 125,000 words later, and The Bushido of Bitcoin is almost complete. 

Before the book’s release in Q3 of this year I will be doing a few things: 

1. Making it available for pre-order on Geyser. For the general paperback, digital and audio copies, it will save you roughly 50%. I will also include some limited edition options, like a short run of 21 leather-bound versions of the book. More on that in the coming weeks.
2. Drip-feeding snippets from the book, in the form of quotes, lessons, etymology progressions and insights, across all my socials. On Substack I’ll do longer form posts, on Twitter & Nostr, I’ll keep them more succinct, and finally, I’m reviving my Instagram to wrap the insights in beautiful, shareable, bite-size visuals. 
3. Jumping on a bunch of podcasts, both Bitcoin and not Bitcoin-related to dig into the content of the book. I’ve recorded with Breedlove already. Many more to come - and who knows, I may even revive my old Wake Up Podcast and do a few short episodes there too.

I want to treat this book as both an ongoing work and a piece of art. So alongside the book, I’m also going to produce some pieces of visual and physical art. The video trailer, alone, I promise will blow your mind., as will the warrior-samurai artwork I’m going to have commissioned in collaboration with some soon-to-be-announced artists. I’ll probably even do a tradings cards pack with Bitcoin Trading cards next year, and some other collaborations along the way. 

In any case, it’s been an incredible journey writing this book and I’m honoured to have had people like John Carter help me edit it, and Ross Stevens agreeing to do the foreword. I can’t wait to have the final version completed and in your hands.

For those who might be wondering what I am talking about…

**What is The Bushido of Bitcoin? **

This is a book I’ve been writing for almost two years now. Its genesis was a conversation I had with Erik Cason on my old Wake Up Podcast - also called “The Bushido of Bitcoin.” It was Episode 65: you can check out here. The inspiration for that episode came from a shared love of the book by James Clavell, called: Shogun (now a HBO series - which it seems they didn’t make woke..thank God), and of course we related the idea of Bushido (Way of the warrior: Code of Virtue) back to Bitcoin.

I felt that this was a seed of an idea, well worth watering. So after that, I decided to go on a history binge and start collecting ideas. What ensued was a real journey. I must’ve listened to a thousand hours of history books and Dan Carlin podcasts in the first six months and the concept began to form. But before I tell you what the concept is - let me tell you what it’s not.

This is NOT another book about the history of money, nor does it make an Austrian case for sound money, or an economic case for Bitcoin as sound money. Neither is it concerned with how Bitcoin works, or any of the technicals. We have enough of those books, and I don’t think I will add anything new to that corpus of knowledge. What this book IS about, is something so much deeper and more profound: The behaviour, virtue, culture and civilisation of greatness.

The book seeks to answer the question: “What happens when Bitcoin wins?”   What happens to those who rise to the top, and become the socio-economic elite of the world? 

• Will we become a new parasitic class? 
• Will we become self-indulgent degenerates? Or.. 
• Will become men and women of virtue?

The latter is not a given, and it’s certainly not enough to just say “Bitcoin Fixes This.” To become men and women of stature and character requires actively developing the virtues which give rise to a culture of excellence. This is the only way to reclaim and rebuild civilisation - complaining and wishing about the past won’t cut it.

Over the coming weeks, I will introduce you to the Ten Virtues that make up The Bushido of Bitcoin. The book of course is more complete, but I will hold nothing back. We’ll follow the historical and etymological genesis of these virtues with an in-depth analysis on how they were embodied by the greatest leaders and warriors throughout history. We’ll also draw lessons from this analysis that will help us navigate the road ahead.

What lies before us may be a “clown world” but hope is far from lost. We’ve been here before. Many times, and against greater odds. This is our generation’s opportunity for a re-conquista. 

The Bushido of Bitcoin is written to remind you there is something greater inside of you, and the only way through hell, is forward. I hope you find value in the up-coming content, and that should you pick up a copy of the book, it greatly inspires you. 

Thankyou Aleksandar Svetski

Per-order the book here: https://geyser.fund/project/bushidoofbitcoin Get a free introductory chapter here: BushidoOfBitcoin.com Follow my work here: Linktree.com/Svetski

@ 362ebffa:492e2719

Consciousness is the subjective experience arising from the brain (as the viewer, the beholder) While reality encompasses both the objective external world and our subjective perception of it.

The two are deeply interconnected, with consciousness shaping our experience of reality and reality influencing the state and content of our consciousness.

Therefor we do live in various bubbles of reality, my reality (my perception of reality) is my own.

What do you think?

@ 2ecde0a6:10022dcb

Opinion about KeepKey (hardware)

KeepKey is a hardware wallet with a high level of security and supports more than 40 different crypto assets.

The device provides a PIN code and recovery seeds. It has a feature where it switches your PIN code numbers from time to time, making it impossible for malware to copy our code. Also, the device has a system for trade where you have to press and hold to confirm the transaction to avoid external hacks.

KeepKey has only one button to manage it. This button is used for turning the device on and off. All the other processes can be managed through the mobile app. That includes entering your PIN code and setting up the recovery seed, which makes it very simple to use, unlike other complex wallets. The device has a wide screen that allows you to see the entire cryptocurrency address without the need to scroll back and forth. But it's easy to break or scratch if you don't have a protecting casing.

Its price is around $80.

But you have to remember that the device is a little big and heavy, compared to other hard wallets, so it's difficult to carry around with it.

WalletScrutiny #nostrOpinion

Join the conversation!

@ 3bf0c63f:aefa459d

About Nostr, email and subscriptions

I check my emails like once or twice a week, always when I am looking for something specific in there.

Then I go there and I see a bunch of other stuff I had no idea I was missing. Even many things I wish I had seen before actually. And sometimes people just expect and assume I would have checked emails instantly as they arrived.

It's so weird because I'm not making a point, I just don't remember to open the damn "gmail.com" URL.

---

I remember some people were making some a Nostr service a while ago that sent a DM to people with Nostr articles inside -- or some other forms of "subscription services on Nostr". It makes no sense at all.

Pulling in DMs from relays is exactly the same process (actually slightly more convoluted) than pulling normal public events, so why would a service assume that "sending a DM" was more likely to reach the target subscriber when the target had explicitly subscribed to that topic or writer?

Maybe due to how some specific clients work that is true, but fundamentally it is a very broken assumption that comes from some fantastic past era in which emails were 100% always seen and there was no way for anyone to subscribe to someone else's posts.

Building around such broken assumptions is the wrong approach. Instead we should be building new flows for subscribing to specific content from specific Nostr-native sources (creators directly or manual or automated curation providers, communities, relays etc), which is essentially what most clients are already doing anyway, but specifically Coracle's new custom feeds come to mind now.

---

This also reminds me of the interviewer asking the Farcaster creator if Farcaster made "email addresses available to content creators" completely ignoring all the cryptography and nature of the protocol (Farcaster is shit, but at least they tried, and in this example you could imagine the interviewer asking the same thing about Nostr).

I imagine that if the interviewer had asked these people who were working (or suggesting) the Nostr DM subscription flow they would have answered: "no, you don't get their email addresses, but you can send them uncensorable DMs!" -- and that, again, is getting everything backwards.

@ 126a29e8:d1341981

Esta es la traducción de una carta de Ross Ulbricht que se publicó en su blog en Septiembre de 2019. Podéis leer el artículo original aquí: https://rossulbricht.medium.com/bitcoin-equals-freedom-6c33986b4852

Algo especial sucedió en el primer año después de que Satoshi nos regalara Bitcoin. Algo que nadie esperaba y que muchos pensaban que era imposible. Intenta imaginar Bitcoin en aquel entonces, antes de que pudieras comprar cosas con él, antes de que hubiera un tipo de cambio, antes de que nadie supiera realmente qué pasaría con él, si es que pasaba algo. Bitcoin no empezó como dinero. Se convirtió en dinero, pero lo hizo de forma distinta a cualquier dinero anterior. A pesar de todas las cosas que Bitcoin ha hecho posibles, a pesar de todas las formas en que está cambiando nuestro mundo, no apreciamos plenamente o ni siquiera entendemos lo que sucedió en aquellos primeros días, cuando era sólo un juguete para geeks.

Cualquier otro dinero anterior al Bitcoin -en la larga historia de la civilización humana- se valoraba por razones distintas a su uso como dinero. El ganado en África, los sellos de correos en las prisiones, las conchas marinas y los metales preciosos se han utilizado como dinero y encajan en este patrón. La única excepción es el dinero fiduciario -algo declarado como dinero por una autoridad-, pero incluso las monedas fiduciarias nacionales estuvieron en su día respaldadas por algo con valor previo, como el oro.

Bitcoin cambió todo eso. Bitcoin no tenía ningún valor previo y nadie estaba obligado a utilizarlo, pero de alguna manera se convirtió en un medio de intercambio. Las personas que no entienden y se preocupan poco por Bitcoin pueden, sin embargo, aceptarlo como pago porque saben que puede ser utilizado para pagar por otra cosa o ser intercambiado por dinero convencional.

La gente suele mencionar las pizzas que se compraron por diez mil bitcoins y, en retrospectiva, se burlan del tipo que se comió lo que se convertiría en un almuerzo multimillonario. A mí me interesa más la persona que renunció a dos pizzas en perfecto estado por meros bitcoins. ¿Qué vio en esos bits y bytes, en esa firma digital de algo que la gente llamaba cadena de bloques? Lo que motivó al vendedor de pizzas pudo haber llamado también la atención de los primeros mineros, que no podían vender pero acumulaban alegremente. Quizá inspiró a los que simplemente regalaban bitcoins por miles. Fuera lo que fuese, era algo nuevo.

La teoría económica clásica dice que un intercambio no se produce a menos que ambas partes valoren más lo que reciben que lo que entregan. Entonces, ¿de dónde viene el valor? Bitcoin nunca debería haber despegado, pero lo hizo. Incluso un producto nuevo tiene algún tipo de valor, y los primeros en adoptarlo corren el riesgo de no obtener el valor de su dinero, pero aún así esperan ganar con el intercambio.

En cambio, los primeros usuarios de Bitcoin no tenían ni idea de lo que sabemos ahora. Todo lo que tenían era un sueño, una convicción y el entusiasmo suficiente para convertir un artilugio digital en un fenómeno multimillonario del que sólo estamos empezando a ver los efectos.

Te diré lo que creo que pasó, aunque lo cierto es que nadie lo sabe. Es casi magia que Bitcoin pudiera surgir de la nada y, sin valor previo ni decreto de autoridad, convertirse en dinero. Pero Bitcoin no se originó en el vacío. Fue la solución a un problema con el que los criptógrafos llevaban lidiando muchos años: Cómo crear dinero digital sin autoridad central que no pudiera falsificarse y en el que se pudiera confiar.

Este problema persistió durante tanto tiempo que algunos dejaron la solución a otros y soñaron en cambio con cómo sería nuestro futuro si el dinero digital descentralizado llegara a existir de alguna manera. Soñaban con un futuro en el que el poder económico del mundo estuviera al alcance de todos, en el que el valor pudiera transferirse a cualquier lugar con sólo pulsar una tecla. Soñaban con que la prosperidad y libertad dependieran únicamente de las matemáticas de una encriptación robusta.

Bitcoin nacía pues en terreno fértil y era reconocido por quienes lo habían estado esperando. Fue un momento histórico para ellos, mucho más importante que las pizzas o las facturas de la electricidad generadas por la minería. La promesa de libertad y el encanto del destino dieron energía a la comunidad inicial. Bitcoin se adoptó consciente y espontáneamente como dinero mientras nadie lo veía, y nuestro mundo nunca volverá a ser el mismo.

https://freeross.org

@ 3c827db6:66418fc3

With the previous articles, we found the disconnect between paid-for work and paid-for time. We also understood that if you want to get paid you have to provide work that is valuable for others. So when the person consumes the benefit of your work, the exchange happens value for value - work for sats. But what happens if the benefit that the consumer experiences is not a momentary but a continuous process? There are a few examples of this. I will start with the one that is not that captivating but still valuable.

Streaming services, like other industries, grapple with the limitations of the fiat payment system. The burden of fees and the absence of suitable technology for streaming payments have compelled them to adopt similar mitigations as other industries. This translates to charging users on a monthly basis.

With the Lightning Network, we have the technology to stream sats for content. No longer confined to monthly subscriptions, you pay for what you consume in real time. Whether you watch sporadically or binge extensively, streaming payments allow for a more personalized and efficient payment model. This way the creator of the content and the user have a direct connection for each minute the content is broadcasted. With streaming payments now you can say goodbye to subscription payments.

Unveiling A New Era Of Fair Compensation And Accountability In Movie Production

Imagine you've created a movie or documentary. Traditionally, you'd charge people for a ticket, essentially asking them to pay upfront for future value, creating a slight disconnect. Now, with streaming payments using sats, consumers can pay as they watch. If your movie sucks, they might only pay for the first 30 minutes. However, you still receive value, and viewers won't feel overcharged for something they didn't enjoy. If your movie is great they not only stream sats the whole time but at the end, they leave a tip.

On the receiving side of the movie most people involved in it received a salary for doing their job. As we already know this is not aligning the whole structure in the same direction. Some people do not care at all how good the movie is if they have already been paid and do not receive a bonus further. Some people might care about reputation in the market but very few just want to do the best job. Again, we went through this, and as you are guessing you just do a split payment in the backend where all the people in the credits actually receive sats or even milisatoshis based on their contribution. This was something I did not expect that Bitcoin would disrupt. This way the reputation is directly linked to the payment and a lot more people will fight to have the best movie. You can be someone who contributed to a project and wants to stay anonymous for whatever reason but still receive money - Lightning instant settlement is the way to do it.

These concepts should not be new if you read through the last 3 articles. In addition, people in the Bitcoin space are familiar with the Value for Value (V4V) podcasting and that is very close to what I am describing above. While the technology for podcasting is already in place, it's surprising how few podcasts leverage this technology to implement split payments effectively. They give that responsibility to some hosting service that decides to take a 5% split for themselves and the other 95% goes to the wallet of the show. Why not do the split the proper way? The hosting service provides value so they should get a percentage but if you are 3 people involved in the production of the podcast you should have that 95% split so it goes to those individuals. There's no excuse, especially for Bitcoin podcasts, not to make this effort and implement split payments appropriately.

The Dynamic Future Of Pay-as-you-go In Content Consumption

In this example, the pay-as-you-go model holds true for continuous experiences, like streaming. Now, let's revisit the movie example. If you're a theater, you are essentially the hosting provider for the movie. The quality of the theater experience can vary; one theater might have uncomfortable chairs, while another boasts luxurious massage chairs. The theater with subpar seating might receive a 3% share of the movie's streaming sats revenue, while the one with comfortable massage chairs might earn 5% for each sat stream paying for the movie. Furthermore, if a viewer activates the massage function of the chair, additional sats are streamed for each second that the function is on. I do not know the exact payment dynamics between theaters and movie studios but I bet there are prepayments and funds held at multiple points in the fiat payment process. With the adoption of the Lightning Network, theaters no longer have to prepay for movies to be projected on their screens. They can now observe which movies are most popular in real time and adjust their projections accordingly to optimize revenues. This benefits the consumer and optimizes profits for themselves and the creators of the movie.

Now you see the content gets its value stream for the continuous experience and everyone in the film industry will fight to give the best experience for the most amount of time. The better the experience the more sats flow their way. Due to the highly subjective nature of content, where one person might deem a movie subpar, another might label it as their favorite. This subjectivity is why I believe most content streaming will not have a predetermined price. Even movies may adopt the V4V model, similar to what Adam Curry is pioneering in podcasting. For instance, you watch a movie, and during the credits, a prominent QR code appears, allowing you to decide how much you want to send to the creators of the movie. You will listen to a song or a podcast the same way. Whether you predefine a streaming rate per minute or request payment at the end, both options are technically possible. However, the market will ultimately determine which option prevails as the better one.

Also, why not have a bidding competition for any event that has assigned seats? The person who bids the most for a ticket gets to be in the first row of the concert or a sports stadium. This way the subjectivity is left for all the viewers to decide how valuable it really is. This way it ensures a full stadium also because if there is no value in attending the event people are not going to bid for the seats or just pay 1 sat for it.

Revolutionizing Taxi Transactions For Drivers And Passengers Alike

The continuous experience or service for streaming could be anything in the physical realm. I will take a look at how instant settlement could look like in transportation services. One such transportation service is the taxi service. Even though Uber decentralized the taxi companies which is great they did nothing about decentralizing the payment process. Lightning Network fixes that and more.

With a streaming payment option for each meter of movement, taxi drivers no longer need to wait until the end destination to receive their payment. In a world of instant settlement, payment occurs as you go, eliminating the risk for the taxi driver regarding whether the passenger will pay at the end of the journey. While this might not be a groundbreaking improvement, there are several additional benefits to consider.

Why do most taxis operate with cash? Taxi drivers in most places need a POS device for the customers to be able to pay for a better user experience (UX). It may be a better UX but on the other hand, it creates problems for the drivers either way:

• They have to acquire clunky devices.
• They must pay payment processing fees, negatively impacting their margins.
• Operating solely with cash exposes them to the honeypot problem, carrying a substantial amount of money, and making them vulnerable to theft.

With an app tailored for the taxi experience and integrated with the Lightning Network, these issues become irrelevant. There is no need for additional equipment, no payment processing fees for receiving money, and no exposure to visible cash, reducing the risk of being a target for theft. Now you can have a better UX with better security and better margins - an additional benefit is that it will be paid with Bitcoin. Not only that but just like the example with the movie theater chairs drivers will be incentivized to make the travel experience even better. They can offer - to watch a movie, video games like PlayStation, or massage chair. If you choose to use those extra experiences on top of the travel experience you have to increase the sats streaming their way.

An additional benefit for the travel experience of customers arises when multiple passengers in a taxi have different destinations. Traditionally, the taxi meter ticks for the entire journey, and when the first person is dropped off, determining a fair amount for their portion becomes complex. However, with the Lightning Network, it's conceivable to streamline this process. Imagine a scenario where three passengers enter a taxi, each with distinct destinations. Each person scans a QR code upon entering, linking their streaming sats to the taxi app. The app manages split-receiving, dynamically adjusting the distribution of streaming payments based on how many people are in the taxi. As passengers are dropped off one by one, the app seamlessly adjusts the split-receiving, providing a fair and efficient payment solution for each individual's share of the journey.

Optimizing City Transportation With Streaming Sats

The proposed model of split-receiving through QR codes and streaming sats can extend beyond taxi services to other modes of transportation, such as buses. The idea is to calculate the average cost per mile (or meter/foot) for providing the transportation service, including factors like fuel, maintenance, and driver salary, and add a margin for profit. Passengers entering the vehicle scan a QR code, and the app dynamically adjusts the streaming payments based on the number of people on board.

For buses, this model allows for real-time adjustment of streaming payments as passengers enter and exit. If there are 30 people on the bus the split is between them. At the next stop, 10 people are dropped off and 5 people get on board - now the sats stream is divided by 25 people. As the number of people on the bus changes at each stop, the streaming sats are proportionally divided among the passengers. This approach can lead to more efficient and flexible city transportation. Late-night buses will be more expensive for the passengers because of the fewer riders, while buses during peak hours may offer a more cost-effective traveling experience as payments are shared among more passengers.

This system encourages transportation optimization around events, such as concerts or sports games, where private buses or minivans wait to fill up before departing. Routes can be dynamically adjusted because you will have a system tracking how many people are in the vehicles at what time and at what location on the map. Importantly, this data remains anonymous, as no KYC information is required for the Lightning Network payments.

The Streamlined Pay-from-a-distance

Now with this streaming money feature, it can be applied differently. Let’s go back to the taxi service for a moment. The pay-from-a-distance feature that is available in the Lightning Network can significantly enhance the experience of ordering a taxi. Instead of the traditional model where drivers wait patiently and charge fixed fees when passengers enter the car, this model introduces streaming sats from the moment the passenger accepts the ride. Here's how it works:

• The passenger places an order in the app, specifying the destination. Nothing new here.
• Drivers see the order and can apply for it, similar to platforms like Uber.
• Streaming sats start the moment the passenger accepts the driver, and streaming payments commence. This fee will be less than the actual transportation but the user is still paying for the service of the car coming to him and not the other way around.
• The taxi arrives at the passenger's door, and the streaming payments continue. There is a fee for waiting at the door per minute.

By shifting the waiting cost to the passenger, there's a strong incentive for both parties to be prompt, and the system becomes more efficient. Additionally, the passenger's responsibility to follow the car reduces operational costs related to alerting passengers via message or a call. Any inefficient time management becomes a cost for the passenger. This model aligns incentives for both drivers and passengers, creating a more seamless cost and time-effective taxi experience.

The concept of paying from a distance can be creatively applied to various scenarios, providing convenience and peace of mind. For instance, when it comes to sending your child somewhere with a taxi, traditional concerns about trusting them with money or the driver's reliability may arise. However, with the ability to stream sats for the ride, you gain real-time visibility on your device, tracking your child's journey and ensuring they reach the intended destination safely. This pay-from-a-distance feature extends beyond transportation and can be applied to other continuous services. For example, daycare services charge per minute, allowing you to stream payments in real-time, ensuring accurate and fair compensation for the duration your child spends there. Additionally, you can send a present to a friend, such as a massage session, and pay for it in a streaming fashion, covering the cost continuously based on the duration of the service. The flexibility of streaming payments not only offers real-time tracking and control but also opens up new possibilities for various services where charging per minute or duration is relevant. Those services can be paid on the spot or from a distance. image2

I know that now it looks like we are going backwards from the original point of never paying money for time. The key distinction here is that you may be paying for time past for the service but in that time you get a continuous stream of value (work done) so you are streaming value back to pay for it. In some cases the time spent is actually an accurate measure of the work done.

It's true that developing apps with such functionalities is technically feasible, and there might be entrepreneurs and developers willing to explore these possibilities. However, a significant challenge arises when considering custodial control over users' funds. Small startups might find it financially burdensome and complex to operate as custodians, potentially steering away from such responsibilities. This will take not only high responsibility but also a very big financial wall and expertise to obtain the licenses that comply with the ever-changing regulations. On the other hand, large tech companies with substantial resources could afford to take on the role of custodians, presenting both a business opportunity for them and a risk for the users. The move by some tech giants, like X(formerly Twitter), to obtain such licenses can be seen as a strategic measure for self-preservation over their own finances. This is also an opportunity to consolidate control over not only user data but user finances within their platforms.

The Breez SDK offers a powerful solution, empowering developers to create diverse applications without having to worry about payment intricacies. Its non-custodial nature is a key advantage, eliminating the need for licenses. The infrastructure of it is made in such a way that it is peer-to-peer so no one is holding money for someone else. The app developers focus on the experience within the app and just plug in the code. This combination of features gives startups a competitive edge and reverses the advantage held by large tech companies. While they go through the complex process of getting a license the startup can integrate the global payment network (the Lightning Network) in one day. Even if certain tech giants choose to lock users' funds within their applications, alternative options will continue to be developed, and users will have the freedom to opt-out. Just like people are choosing Bitcoin over fiat.

Now who is ready to give all of us those experiences in their app?

@ b804f68e:2fb0fa1f

Consistently writing on SN and Obsidian has underscored for me the critical role of application in the learning process. Writing allows me to visually process, reflect, analyze, and organize the myriad ideas generated within my brain. Through this ongoing practice, I can physically sense my improvement in articulating thoughts to others and myself, both in writing and speech. However, both forms of expression still require significant practice, especially the latter.

Before I began writing regularly, I didn't fully appreciate the importance of purposeful learning. Previously, I viewed reading a book, watching an educational video, or listening to a podcast as the primary components of learning. But these activities are merely the initial stimuli that prepare our brains for deeper engagement, much like a warm-up before a workout. True learning extends beyond passive consumption; it involves actively practicing and applying what we've learned, reflecting on our experiences, and continually revisiting the material to fill in gaps and deepen our understanding. Sharing and discussing our insights with others further enriches this process, as it exposes us to diverse perspectives and feedback we might not have considered on our own. For me, writing acts as the bridge that connects acquired knowledge to practical application.

After writing on SN consistently for over a month, I've come to realize what it truly means to learn and acquire knowledge. Writing daily has exposed gaps in my understanding, often revealing that I lack the depth of knowledge I assumed I had. When I reach the limits of what I know, I'm compelled to research further, which reinforces and expands my comprehension.

Even if you never write publicly, I believe everyone can benefit from the act of writing. The more I write, the more intentional my learning process becomes, and the more organized and structured my thoughts are.

@ 75da9402:77a65b5c

Empezare este articulo indicando que iba hacer publicado como un hilo en Twitter o X o como diablos se llame ahora por que mi intencion era trasmitir a otros que existe algo mucho mejor donde pueden empezar nuevamente a disfrutar de otra forma de comunicarse, pero mi sorpresa fue grande al momento de enviar el hilo de tweets, me salio el mensaje "no se puede enviar" usted debe UPDATE TO PREMIUM para atreverse hacer un post en esta empresa que protege la libertad de expresion...lol...(:-O). Como yo casi ya no escribo nada en X y lo uso solo para informarme de lo que pasa en mi pais, no sabia esta nueva limitacion. Ahora volvi a recordar por que deje de usarlo. Pero bueno, aqui voy a desahogar mi hilo para luego compartirlo en X, por que me van a leer quieran o no, jajaja.

---

Te cuento una pequeňa historia.

Alguna vez me preguntaron por qué me gustaba Twitter (hoy X) más que otras redes sociales ya que yo era un joven audaz que siempre interactuaba ahi jaja. Y mi respuesta fue simple en esos aňos: Twitter es una selva digital donde se genera el debate público e informativo a nivel mundial y aqui puedo decir lo que yo quiera (pobre iluso). Pero luego las cosas fueron cambiando en mi RRSS favorita, en algun momento se convirtio en un hueco lleno de toda clase de basura digital de la cual habia huido siempre, hasta que llego un familiar mio a comprar la empresa y pense: AL FINNN... volveran los dias de gloria, y efectivamente algo parecio mejorar y con eso me conforme, pero aclaro que no me gusto al final el rumbo que tomo la empresa familiar después que mi tío Elon la compró pero es lo que habia en ese entonces y aguante. HASTA AHORA..

Te gusta twitter pero a la vez estás arto de lo mismo?

Hace meses hice 1 post de por qué me gustaba X, pero también explicaba el rumbo que está tomando el mundo de la tecnología con respecto a las redes sociales. Y ahora te explicaré de qué se trata.

Todo ha evolucionado en el mundo de la tecnologia a velocidad vertiginosa, por ejemplo tu tia antes enviaba un Piolin de BUENOS DIAS todas las mañanas en su muro de Facebook a sus amigos y familiares que la seguian, ahora hace lo mismo por el WAZA (grupo familiar que pasa silenciado por siempre) y si ya no lo hace es por que TU eres la TIA del Piolin ahora jajaja, pero volviendo al tema las RRSS no han evolucionado desde hace 20 años, ojo me refiero a la forma de generar contenido, monetizar y consumir, todo es lo mismo que cuando abrí mi cuenta de Twitter hacer 15 años. Han aparecido muchas otras RRSS si es cierto, #tiktok la última. Pero todas hacen lo mismo darte a ti el usuario: entretenimiento, distracción ludica y tal vez “informar”; y esto entre comillas por qué lo que lees, escuchas y te informas es lo que los dueños de estas RRSS, las marcas auspiciantes y quienes pagan su verificación quieren, NO lo que TÚ quieres. Ellos dictan y te “Sugieren el contenido que puedes ver” pero tu no te das cuenta y crees que lo que estas viendo es por que tu asi lo decidiste. Lo cual es una triste y deprimente mentira....

Y no es invento mío, te adjunto una entrevista a Jack Dorsey fundador de Twitter, donde él explica detalladamente por qué sucede esto que afirmó anteriormente. Léelo en tu tiempo libre, no tiene desperdicio. Usa traductor si no le haces mucho al inglés:

https://www.piratewires.com/p/interview-with-jack-dorsey-mike-solana

Y si te preguntas, Alguien está haciendo algo para mejorar esto? SI, un montón de gente (Jack incluido) y otros mas que aportan con muchos recursos: técnicos, económicos, tenologicos y sobre todo tiempo y amor a su profesion. Esta gente está trabajando en cambiar todo esto que esta mal y de ese esfuerzo en conjunto nacieron soluciones como Mastodon, Bluesky y Nostr.

Pero que son Mastodon, Bluesky y Nostr?

Mastodon y Bluesky son básicamente lo mismo, nuevas RRSS donde encuentras de todo. Nacieron con la idea de enfrentar a Twitter la primera, y mejorarlo la segunda como lo explica Jack en su entrevista. Pero al final terminaron teniendo lo mismo, es decir marcas asupiciantes, moderadores verificados y dueños o juntas directivas. Mas de lo mismo....

Nostr en cambio es el giro de tuerca que las RRSS y las comunicaciones humanas necesitan para el futuro, y de hecho Instagram (Threads) y otros ya lo están probando en sus plataformas lanzando puentes desde sus empresas para que sus usuarios tengan interoperatibilidad entre diferentes rrsss del fediverse.

-Y por qué sucede esto con Nostr?

Por qué Nostr no es una RRSS ni una empresa, ni tampoco tiene dueños o moderadores de contenido que dictaminan lo que puedes o no ver, leer, escuchar y consumir en tu feed, ya que es un protocolo de comunicación como los que usas para el correo, para navegar en internet, etc.

-Y que ganamos los usuarios?

Ganamos un largo etc. de beneficios para consumo de contenido REAL, mas humano y mas limpio, pero lo que si diré que NO encontraras es nada de lo que te tiene hastiado de las otras RRSS. Aquí un video que te gustaría ver para entender de lo que escribo:

https://youtu.be/aA-jiiepOrE?si=iaMu5K3qKqh_JxsR

Te interesa usar y aprender que puedes hacer con Nostr?

Te dejo unos link 🔗 para que empieces a explorar una nueva forma de comunicarse entre seres humanos. Usa alguno de estos servicios, pruebalos.

• Lives: https://zap.stream/
• Música: https://wavlake.com/
• Blogs: https://yakihonne.com/
• Podcast: https://www.fountain.fm/

Y muchas más aplicaciones y sevicios en: https://www.nostrapps.com/

Si lo tuyo es consumir contenido en algo como Twitter/X estás apps son para ti:

En iOS: - Primal: https://primal.net/ - Damus: https://damus.io/ - Nostur: http://nostur.com/ - NosSocial: https://nos.social/

En ANDROID: - Primal: https://primal.net/ - Amethys: https://play.google.com/store/apps/details?id=com.vitorpamplona.amethyst&hl=en

En WEB: - Primal: https://primal.net/ - Nostrudel: https://nostrudel.ninja/ - Snortsocial: https://snort.social/ - Coracle: https://coracle.social/

Debes saber que puedes con el mismo usuario y contraseña (en #Nostr se dicen llaves) puedes ingresar a TODAS las aplicaciones mencionadas en este articulo, y esto puede lograrse por que el protocolo es el mismo, es NOSTR.

Ya vas en tendiendo? no hay empresas, no hay dueños..😏, TU eres el dueño del contenido que produces y del contenido que consumes.

Quieres saber mas informacion sobre Nostr, visita estas web. Resolveran muchas de tus dudas.

https://nostr.com/ https://nostr.how/

Para terminar con este pequeño hilo... (te odio Elon) jajaja

Nostr esta empezando y tiene mucho por mejorar pero al dia de HOY ya existen cosas increibles que puedes hacer y son mejores que en otras RRSS y te aseguro algo, TODOS nosotros terminaremos tarde o temprano usandolo en el futuro, es inevitable si queremos evolucionar nuestra forma de comunicarnos.

Si tu quieres ser uno de los primeros en experimentar una nueva era de las RRSS. Anímate y empieza a usar NOSTR como TU quieras. Solo haz lo siguiente:

1. Descarga cualquier aplicacion en tu movil tipo Twitter detallada en este articulo.
2. Crea el Usuario (npub....) llave 1
3. Crea la contraseña (nsec....) llave 2
4. Guarda tus llaves, que no se te olviden. (anótalas)
5. Envia tu primer post colocando al final el hashtag #introductions
6. Y a disfrutar de #nostr

Si te gustó este hilo (Elon de >:{ #$%&) dale RT o cómo diablos se diga ahora 😂 o postealo y compartelo donde quieras para que mas gente lea sobre Nostr. Tal vez a alguien le interese.

Si deseas seguirme en #Nostr •𓅦

primal.net/p/npub1whdfgqn66sytcta0l6c7vlt3h2lg67xcnsmzpk3pyvpmsaaxtdwqr8vs60

Alla nos vemos...escríbeme y pregunta lo que quieras.

Saludos, johnny

@ ec965405:63996966

Re #introductions

For the next couple of months, the team at nos.social, led by @Rabble@nos.social, is supporting me in building engaging social media for my community with their new Nostr client. I'm an activist who is dedicating this season of my life to learning how computers and the Internet work. After stumbling across Nostr last year in search of better social media experiences, I entered a blogging contest with https://nostr.build and won a creator account. My interest and enthusiasm for this protocol has only grown.

RE #introducciones

Durante los próximos meses, el equipo de nos.social, liderado por Rabble@nos.social, me ayudará a crear una experiencia atractiva para mi comunidad con su nuevo cliente de Nostr. Soy un activisa dedicado a aprender cómo funcionan las computadoras y el Internet. Despues de encontrar a Nostr el año pasado en la busqueda de mejores experiencias en las redes sociales, participé en un concurso de blogs con [[nostr.build]] y gané una cuenta de creador. Mi interés y entusiasmo por este protocolo no ha hecho más que aumentar.

Liberation Tech

The world is having a moment right now. Social media is evolving into a tool for collective liberation. It couldn't have come at a better time. We have an opportunity to reconstruct a digital public commons. Tools like Nostr are blueprints for building resilient social media and represent a rejection of the factory of manufactured consent that defines our current political realities. A liberated fifth estate built on open protocols could channel people power into material improvements within our lifetimes. We are not going back to the way things used to be.

Tecnología de Liberación

Actualmente estamos viviendo un momento critical. Las redes sociales se estan evolucionando hacia una herramienta para nuestra liberación colectiva. No podría haber llegado en mejor momento. Tenemos una oportunidad de reconstruir la plaza digital del pueblo. Herramientas como Nostr son modelos para construir redes sociales resistentes y representan un rechazo a la fábrica de consentimiento manufacturado que define nuestras realidades políticas actuales. Un quinto estado liberado, basado en protocolos abiertas podría canalizar el poder del pueblo hacia un cambio material en el transcurso de nuestras vidas.

Explore my Asteroid

I host my main web page from an asteroid with Uberspace, a small team of supportive technologists who provide an affordable Linux server that runs on renewable energy. On it I run a personal relay for on-boarding my community to Nostr as well as learning to code. Find resources and more about what I'm working on at https://miguelalmodo.com.

Explora mi asteroide.

Mi pagina web principal se encuentra en un asteroide con Uberspace, un equipo chiquito de tecnólogos solidarios que ofrecen un servidor Linux barata que funciona con energía renovable. En él, gestiono un relevo personal para incorporar a mi comunidad a Nostr, además de aprender a programar. Encuentra rescursos y mas sobre lo que estoy creando en https://miguelalmodo.com

@ 76c71aae:3e29cafa

The Curious Case of DSNP: Years of Effort, Minimal Output

It's been a while since I looked at DSNP. There’s news that its backer, Frank McCourt, is trying to put together a team to buy TikTok. That’s insane. The DSNP and Project Liberty team are well-meaning, but they’re even less equipped to run a social network or protocol than Elon Musk at his lowest point when he was firing engineers based on how many lines of code they’d written.

To check what’s happened with DSNP since I last looked a year ago, I just read the entire spec, and there's not actually that much to it. The amount of time and money spent on developing so little is quite stunning. While the spec is fine, it is minimal.

Key Features and Odd Choices

DSNP allows users to have a key pair, write content into a datastore, follow people, and sign messages. However, the protocol seems to mix up layers, specifying the wire protocol, signing system, and at-rest specification format that clients and user data servers might use (pds in atproto, instance in fedi, relay in nostr). They use the ActivityStreams 2.0 schema, which is a good choice. Many new protocols have created their own schemas, but I appreciate DSNP's use of the standard. I wish more protocols had not tried to reinvent the wheel in this respect.

Encrypted Direct Messages and Metadata Privacy

There’s mention in the whitepaper about encrypted direct messages, suggesting it’s possible to hide metadata using techniques from Ethereum’s Whisper. Although the specs or code about DMs don't elaborate much on this, it’s good to see an attempt to hide metadata. However, there’s nothing about double ratchet encryption, forward secrecy, or any advanced encryption techniques. So, overall, it feels quite basic.

Data Storage and Interesting Choices

For storing user data and posts, they're using Apache Parquet, a file format from Hadoop. This is probably the only neat or interesting aspect. I've been searching for a supported data format like Parquet for a while because I think it can facilitate privacy-preserving contact discovery, so it’s cool to see its inclusion here.

Minimal Data Types and Following Options

DSNP supports very minimal data types: post, follow, reaction, profile, and, oddly, location. You can follow publicly or privately, the latter being a neat feature that Scuttlebutt had but most of the current generation of emerging social protocols don't.

Lack of Comprehensive Features

There does not appear to be any client app or server code, which might not be needed. There is an SDK for some core functions, but that’s it. Their documentation lacks information on user discovery, algorithms, or anything beyond the basics.

The Verdict: A First Draft After Years of Work

It feels like someone spent millions and ended up with a naive first draft, despite working on this for years. It’s similar to the early sketches of Farcaster and Lens, but those protocols have grown significantly over the past couple of years, with real users, lots of functionality, and apps.

DSNP remains as vaporware today as it was four years ago. These clowns have wasted tens of millions of dollars on nothing. Some academics have happily taken the money to fund their research labs. Consultants have written and thrown away countless prototypes nobody’s ever used.

There are lots of serious projects to build decentralized social media protocols. All these folks had to do was either work with others or even copy them. This stuff is all open source. Yet DSNP keeps sending folks to conferences without talking to anybody or attending any talks.

It’s a shame because they’ve got their hearts in the right place. The Unfinished conferences are really well put together with lots of great speakers. They hired the supremely talented and savvy Karl Fogel and James Vasile to help them make their code and process open, but you can’t fix DSNP.

Fundamentally, software and specs are a social enterprise, even more so if you’re working on social protocols. But these folks… they’ve never figured out how to play well with others. The money and good intentions couldn’t overcome their fundamental failure to have the humility to learn and play well with others.

@ ff517fbf:fde1561b

ビットコインが「最強の担保」と言われる理由

ビットコインは「デジタルゴールド」とも呼ばれることがありますが、実はローンの担保としても最強だと言われています。その理由を、他の資産（株式、不動産、金など）と比較しながら見てみましょう。

• 流動性と即時性：ビットコインは24時間365日世界中で取引されているため、非常に流動性が高い資産です。売買がすぐにできて価格も常に明確なので、担保評価がしやすく、お金を貸す側・借りる側双方に安心感を与えます。一方、株式や不動産は市場が営業時間内しか動かず、現金化にも時間がかかります。不動産は売却に数ヶ月かかることもありますし、金（ゴールド）は現物を保管・輸送する手間があります。ビットコインならネット上で即座に担保設定・解除ができるのです。

• 分割性と柔軟性：ビットコインは小数点以下8桁まで分割可能（1億分の1が最小単位の「サトシ」）なので、必要な額だけ正確に担保に充てることができます。他方、土地や建物を一部だけ担保に入れることは難しいですし、株式も1株未満の細かい調整はできません。ビットコインなら価値の微調整が容易で、担保として柔軟に扱えるのです。

• 管理のしやすさ（マルチシグによる信頼性）：HodlHodlのLendでは、ビットコイン担保は2-of-3のマルチシグ契約で管理されます。これは「借り手・貸し手・プラットフォーム」の3者それぞれが鍵を持ち、2つの鍵の同意がないとビットコインを動かせない仕組みです。このため、誰か一人が勝手に担保を持ち逃げすることができず、第三者（HodlHodl）も単独ではコインを移動できません。ビットコインだからこそ実現できる非中央集権で安全な担保管理であり、株式や不動産を担保にする場合のように銀行や証券会社といった仲介業者に頼る必要がありません。

• 国境を越えた利用：ビットコインはインターネットがつながる所なら世界中どこでも送受信できます。このため、日本にいながら海外の相手とでもローン契約が可能です。たとえば日本の方がビットコインを担保にドル建てのステーブルコインを借り、それを日本円に換えて使うこともできます（為替リスクには注意ですが…）。不動産を海外の人と直接やり取りするのは現実的に難しいですが、ビットコインならグローバルに担保が活用できるのです。

• 希少性と価値の上昇期待：ビットコインは発行上限が決まっており（2100万BTCまで）、時間とともに新規供給が減っていきます。過去の長期的な価格推移を見ると、短期的な変動は激しいものの数年〜十年のスパンでは上昇傾向にあります。一方、法定通貨建ての資産（債券や株式など）はインフレの影響で実質価値が目減りすることがあります。ビットコインは長期保有すれば価値が上がりやすい特性があるため、「今手放したくない資産」として担保に向いています。実際、HodlHodlのチームは「ビットコインはスーパーカCollateral（超優秀な担保）だ」と述べています。

こうした理由から、ビットコインは現時点で考えうる中でも最良の担保資産と考えられています。株や不動産のように書類手続きや名義変更をしなくても、ビットコインならブロックチェーン上の契約でシンプルに担保設定ができる――この手軽さと信頼性が大きな魅力です。

匿名&プライバシー重視：KYC不要のP2Pレンディングのメリット

HodlHodlのLend最大の特徴の一つは、本人確認（KYC）が一切不要だという点です。日本の多くの金融サービスでは口座開設時に運転免許証やマイナンバー提出など煩雑な手続きが必要ですが、Lendではメールアドレスでアカウント登録するだけでOK。これは「匿名性・プライバシー」を重視する人にとって非常に相性が良いポイントです。

• 個人情報を晒さなくて良い安心感：日本では昔から「人に迷惑をかけない」「目立たない」ことが美徳とされ、特にお金の話は他人に知られたくないと考える人が多いですよね。Lendは匿名で利用できるため、借金をすることを周囲に知られたくない人でも安心です。銀行からローンを借りるときのように収入証明や保証人を用意する必要もなく、誰にも知られずひっそりと資金調達ができます。

• ノー・チェック＆ノー・ペーパー：貸し借りにあたって信用審査や過去の借入履歴チェックがありません 。極端な話、今まで金融履歴が全く無い人や、銀行に相手にされないような人でも、ビットコインさえ持っていればお金を借りられるのです。書類のやり取りが無いので手続きもスピーディーです。「印鑑証明や収入証明を揃えて…」という面倒とは無縁で、ネット上でクリックして契約が完結します。

• プライバシーの保護：個人情報を提出しないということは、情報漏洩のリスクも無いということです。近年、日本でも個人情報の流出事件が相次いでおり、不安に感じる方も多いでしょう。Lendではアカウント登録時にメールアドレスとパスワード以外何も求められません。財務情報や身元情報がどこかに蓄積される心配がないのは、大きな安心材料です。

• 国や機関から干渉されにくい：匿名であるということは、極端に言えば誰にも利用を知られないということです。たとえば「ローンを借りると住宅ローンの審査に響くかな…」とか「副業の資金調達を会社に知られたくないな…」といった心配も、匿名のP2Pローンなら不要です。借りたお金の使い道も自由ですし、何より利用自体が自分だけの秘密にできるのは、日本人にとって心理的ハードルを下げてくれるでしょう。

このように、ノーKYC（本人確認なし） のP2Pレンディングは、日本のようにプライバシーや控えめさを重んじる文化圏でも利用しやすいサービスと言えます。実際、HodlHodlのLendは「地理的・規制的な制限がなく、世界中の誰もが利用できる純粋なP2P市場」とされています。日本に居ながらグローバルな貸し借りができ、しかも身元明かさずに済む――これは画期的ですね。

Borrow編：HodlHodlのLendでビットコインを担保にお金を借りる方法

それでは具体的に、HodlHodlのLendでどのようにビットコイン担保のローンを借りるのか、手順を追って説明します。初心者でも迷わないよう、シンプルなステップにまとめました。

1. アカウント登録 (Sign up)

まずはHodlHodlのLendサイトにアクセスし、無料のアカウントを作成します。必要なのはメールアドレスとパスワードだけです。登録後、確認メールが届くのでリンクをクリックして認証すれば準備完了。これでプラットフォーム上でオファー（契約希望）を閲覧・作成できるようになります。

※HodlHodlは日本語には対応していませんが、英語のシンプルなUIです。Google翻訳などを使っても良いでしょう。

2. 借りたい条件のオファーを探す or 作成

ログインしたら、「To Borrow（借りる）」のメニューから現在出ている貸し手のオファー一覧を見てみましょう。オファーには借入希望額（例：$1000相当のUSDT）、期間（例：3ヶ月）、金利（例：5%）やLTV（担保価値比率、例：60%）などの条件が書かれています。自分の希望に合うものがあれば選んで詳細画面へ進みます。条件に合うオファーが見つからない場合は、自分で「○○ USDTを△ヶ月、金利○%で借りたい」という借り手オファーを新規作成することも可能です。

用語補足：LTV（ローン・トゥ・バリュー）とはローン額に対する担保価値の割合です。たとえばLTV50%なら、借りたい額の2倍の価値のビットコインを担保に入れる必要があります。LTVは貸し手が設定しており、一般に30%〜70%程度の範囲でオファーが出ています。低いLTVほど借り手は多くのBTC担保が必要ですが、その分だけ貸し手にとって安全なローンとなります。

3. 契約成立とマルチシグ担保のデポジット

借り手・貸し手双方が条件に合意すると契約成立です。HodlHodlプラットフォーム上で自動的に専用のマルチシグ・エスクロー用ビットコインアドレス（担保保管先アドレス）が生成されます。次に、借り手であるあなたは自分のウォレットからビットコインをそのエスクローアドレスに送金します。

• 📌ポイント：マルチシグで安心 – 上述の通り、このエスクロー用アドレスのコインを動かすには3者中2者の署名が必要です。あなた（借り手）は常にそのうちの1つの鍵を保有しています。つまり、自分が承認しない限り担保BTCが勝手に引き出されることはないのでご安心ください。

ビットコインの入金がブロックチェーン上で所定の承認（通常数ブロック程度）を得ると、担保デポジット完了です。これで契約は有効化され、次のステップへ進みます。

4. 貸し手から資金（ステーブルコイン）を受け取る

担保のロックが確認できると、今度は貸し手がローン金額の送金を行います。Lendで借りられるのは主にステーブルコインです。ステーブルコインとは、米ドルなど法定通貨の価値に連動するよう設計された仮想通貨で、USDTやUSDC、DAIといった種類があります。借り手は契約時に受取用のステーブルコインアドレス（自分のウォレットアドレス）を指定しますので、貸し手はそのアドレス宛に契約どおりの額を送金します。例えばUSDTを借りる契約なら、貸し手からあなたのUSDTウォレットにUSDTが送られてきます。

これで晴れて、あなた（借り手）は希望のステーブルコインを手にすることができました！ あなたのビットコインは担保としてロックされていますが、期限までに返済すれば取り戻せますので、しばしのお別れです。借りたステーブルコインは自由に使えますので、後述する活用例を参考に有効活用しましょう。

5. 返済（リペイメント）

契約期間中は基本的に何もする必要はありません（途中で追加担保や一部返済を行うことも可能ですが、初心者向け記事では割愛します）。期間が満了するまでに、借りたステーブルコイン＋利息を貸し手に返済します。返済も、貸し手の指定するウォレットアドレスにステーブルコインを送金する形で行われます。

• 利息の計算：利息は契約時に決めた率で発生します。例えば年利10%で6ヶ月間$1000を借りたなら、利息は単純計算で$50（＝$1000×10%×0.5年）です。契約によっては「期間全体で○%」と定める場合もありますが、プラットフォーム上で年率（APR）換算が表示されます。

期間内であれば任意のタイミングで早期返済することも可能です。返済期限より早く全額返せば、利息もその日数分だけで済みます（※ただし契約によります。事前に契約条件を確認してください）。HodlHodlでは分割返済にも対応しており、例えば月ごとに少しずつ返して最後に完済することもできます。

6. ビットコイン担保の解除（返却）

貸し手があなたからの返済受領を確認すると、プラットフォーム上で契約終了の手続きを行います。マルチシグの担保アドレスからあなたのビットコインを解放（返却）する署名を貸し手とプラットフォームが行い、あなたの元のウォレットにビットコインが送られます。こうして無事に担保のBTCが戻ってくれば、一連のローン取引は完了です🎉。

もし返済が滞った場合はどうなるのでしょうか？その場合、契約で定められた猶予期間やマージンコール（追加担保のお願い）を経た後、担保のビットコインが強制的に貸し手に渡されて契約終了（清算）となります。担保額が未返済額を上回っていれば、差額は借り手に返ってきます。つまり、返せなかったとしても借り手が担保以上の損をすることはありませんが、大切なビットコインを失ってしまう結果にはなるので注意しましょう。

Borrow（借りる）側のまとめ：ビットコインさえあれば、あとの手続きは非常に簡単です。借入までの流れをもう一度簡潔にまとめると：

1. メールアドレスでLendに登録
2. 借入オファーを探すor作成してマッチング
3. マルチシグ契約が自動生成・BTC担保を自分で入金
4. 貸し手からステーブルコインを受領
5. 期限までにステーブルコイン＋利息を返済
6. ビットコイン担保が自分のウォレットに戻る

第三者の仲介なしに、ネット上でこれだけのことが完結するのは驚きですよね。HodlHodlは「あなたの条件、あなたの鍵、あなたのコイン」と銘打っており、自分の望む条件で・自分が鍵を管理し・自分の資産を動かせるプラットフォームであることを強調しています。

Lend編：HodlHodlのプラットフォームでお金を貸してみよう

次は逆に、自分が貸し手（Lender）となってステーブルコインを貸し出し、利息収入を得る方法です。銀行に預けても超低金利のこのご時世、手持ちの資金をうまく運用したい方にとってP2Pレンディングは魅力的な選択肢になりえます。HodlHodlのLendなら、これもまた簡単な手順で始められます。

基本的な流れは先ほどの「Borrow編」と鏡写しになっています。

1. アカウント登録

借り手と同様、まずはHodlHodlに登録します（すでに借り手として登録済みなら同じアカウントで貸し手にもなれます）。メールアドレスだけでOK、もちろん貸し手側もKYC不要です。

2. 貸出オファーの確認 or 作成

ログイン後、「To Lend（貸す）」メニューから現在の借り手募集一覧を見ます。各オファーには希望額・期間・支払い利率・LTVなど条件が表示されています。「この条件なら貸してもいいかな」という案件があれば選択しましょう。もし自分の希望する利回りや期間が合わない場合は、自分で貸し手オファーを作成することも可能です。「○○ USDTまで、最長△ヶ月、最低利息◻◻%で貸せます」といった条件を提示できます。プラットフォーム上ではユーザーがお互いに条件を提示しあってマッチングする仕組みなので、金利や期間もすべてユーザー自身が自由に設定できます。

3. マッチングと契約開始

あなたの提示した条件で借りたい人が現れたら契約成立です（逆に誰かの借入オファーに応じる形なら、その時点で成立）。システムがマルチシグの担保用BTCアドレスを生成し、借り手がそこへビットコインをデポジットします。借り手からのBTC入金が確認できるまで、貸し手であるあなたは資金を送る必要はありません。担保が確保されたのを見届けてから次に進みます。

4. 資金（ステーブルコイン）の送金

借り手の担保ロックが完了したら、契約で定めたステーブルコインを借り手へ送金します。送金先アドレスは契約詳細画面に表示されます（借り手が指定済み）。例えばUSDCを貸す契約なら、相手のUSDCアドレスに約束の額を送ります。ここで送金した金額がローンの principal（元本）となり、後ほど利息とともに返ってくるわけです。

無事に相手に届けば、あとは契約期間終了まで待つだけです。あなたは担保のBTCに対して鍵を1つ持っている状態なので、万一トラブルが起きた場合でも担保を引き出す権利を部分的に持っています（詳しくは次ステップ）。

5. 返済の受領

契約期間が終わると、借り手があなたにステーブルコインを返済してくるはずです。約束どおり元本＋利息を受け取ったら、それを確認してプラットフォーム上で「返済完了」を操作します。すると担保のビットコインがマルチシグから解放され、借り手に返却されます。これで貸し手としてのあなたは利息分の収益を獲得できました。お疲れ様です！

もし借り手が返済しなかった場合どうなるでしょうか？その場合、所定の猶予期間やマージンコール通知の後、担保のビットコインがあなた（貸し手）に渡されることになります。具体的には、LTVが90%に達するか返済期日から24時間以上滞納が続くと強制清算となり、担保BTCからあなたの貸付相当額が充当されます。担保が十分であれば元本と利息はカバーされ、余剰があれば借り手に返還されます。つまり貸し手側はかなり手厚く保護されており、返済を受け取れない場合でも担保で穴埋めされる仕組みです。

6. 収益を管理・再投資

受け取ったステーブルコイン（元本＋利息）は再度プラットフォームで貸し出しても良いですし、他の用途に使ってもOKです。年利に換算するとだいたい10%前後の利回りになる案件が多く見られます。条件次第では更に高い利率の契約も可能ですが、その分借り手が見つかりにくかったりリスク（担保不足のリスク）が高まる可能性もあります。ご自身のリスク許容度に合わせて運用しましょう。

Lend（貸す）側のまとめ：

• HodlHodlに登録（メールアドレスのみ）
• 貸出オファーを提示 or 借り手募集に応じる
• 契約成立後、借り手がBTC担保を入金
• 貸し手（自分）がステーブルコインを送金
• 期限まで待ち、借り手から元本＋利息を受領
• 担保BTCを返却し、利息収入を得る

銀行預金では考えられないような利息収入を得られるのが魅力ですが、その裏でビットコイン価格変動リスクも担っています。大暴落が起きて担保評価額が急落すると、清算時に元本を割るリスクもゼロではありません（LTV設定とマージンコール制度で極力保護されまますが）。リスクとリターンを理解した上で、小額から試すことをおすすめします。

ステーブルコインの活用：お金持ちは借金で生活する？

ここまで、ビットコインを手放さずにステーブルコインを手に入れる方法を見てきました。それでは、借りたステーブルコインは具体的に何に使えるのでしょうか？いくつか例を挙げてみましょう。

• 日常の出費に充当：ビットコイン投資家の中には「生活費はすべて借りたお金で賄い、自分のBTCはガチホ（売らずに長期保有）する」という方針の人もいます。例えば毎月の家賃や食費をステーブルコインのローンで支払い(これについても今後詳しく解説していきます)、ビットコインは一切使わないというイメージです。こうすれば、手持ちのBTCを売らずに済むので将来の値上がり益を逃しません。また日本では仮想通貨を売却すると雑所得として高率の税金がかかりますが、ローンで得たお金は借入金なので課税対象になりません（※将来的な税務計算は自己責任で行ってください）。つまり、ビットコインを売却して現金化する代わりにローンを使うことで、節税と資産温存のメリットが得られる可能性があります。

• 投資・資産運用に回す：借りた資金をさらに別の投資に活用することもできます。例えば有望な株式や不動産に投資したり、あるいは他の仮想通貨を買うこともできます。極端な例では、ビットコインを担保にUSDTを借りて、そのUSDTでまた別の仮想通貨を買い、それを運用益で返済する…といった戦略も理論上は可能です。ただし、借りたお金での投機はハイリスクなので慎重に！手堅い使い道としては、事業資金に充てるのも良いでしょう。例えば小さなオンラインビジネスを始めるための元手にしたり、新しい資格取得のための学費にするなど、自分への投資に使えば将来的なリターンでローンを返しつつ利益を上げることが期待できます。

• 急な支払いへの備え：人生何があるか分かりません。医療費や冠婚葬祭など急に現金が必要になる場面もあります。そんなとき、ビットコインをすぐ売ってしまうのは惜しい…という場合にローンで一時的にしのぐことができます。後で落ち着いてから返済すれば、大事なBTCを手放さずにピンチを乗り切れます。言わばデジタル質屋のような感覚で、ビットコインを預けてお金を工面し、後で買い戻す（返済する）イメージですね。日本でも昔から「質屋」で着物や宝石を預けてお金を借りる文化がありましたが、HodlHodl Lendはビットコイン版の質屋とも言えるでしょう。

• 市場の機会を逃さない：仮想通貨市場は変動が激しく、「今これを買いたいのに現金が無い！」というチャンスもあるでしょう。例えば「ビットコインが急落したから買い増したいが、現金が足りない」という場合、手持ちBTCを担保にしてステーブルコインを借り、その急落で安く買い増しする、といった動きもできます。そして後日価格が戻したところで返済すれば、差益を得つつBTC保有枚数も増やせるかもしれません。このようにローンを戦略的に使えば、市場の好機を掴む資金余力を生み出すことができます。ただしハイリスクな手法でもあるため、上級者向けではあります。

ここで覚えておきたいのは、「お金持ちは借金との付き合い方が上手い」という点です。日本では借金にネガティブな印象を持つ人も多いですが、世界的な資産家や大企業はしばしばあえて借金をして手元資金を他に活用しています。アメリカのベストセラー『金持ち父さん貧乏父さん』で有名なロバート・キヨサキ氏も「富裕層は他人のお金（借金）を利用してさらに富を築く」と強調しています。例えば彼は借金で高級車を買い、不動産投資にも借入を活用したそう (金持ちは貧乏人より借金が多い | 「金持ち父さん 貧乏父さん」日本オフィシャルサイト)❤️。借金を味方につけて資産運用すれば、自分の持ち出し資金を抑えつつ豊かな生活を実現できる可能性があります。

もちろん無計画な借金は禁物ですが、ローンを上手に使うことは決して悪いことではなく、むしろ経済的戦略として有効なのです。ビットコイン担保ローンはその新しい選択肢として、「お金にお金に働いてもらう」感覚を身につけるきっかけになるかもしれません。

高い金利でもローンを利用するのはなぜ？その理由と戦略

Lendのプラットフォームで提示される金利は、年利換算で見ると10〜15%程度が一つの目安 です。中にはそれ以上の利率の契約もあります。日本の銀行ローン（金利数％以下）と比べるとかなり高利に思えますが、それでも多くの人がこのサービスを利用してローンを組んでいます。なぜ高い利息を支払ってまで借りる価値があるのでしょうか？最後に、その理由と利用者の戦略について考えてみましょう。

• (1) ビットコインの期待リターンが高い：借り手にとって一番の動機は、「ビットコインは将来もっと値上がりするはずだから、多少利息を払っても売りたくない」というものです。例えば年利15%で$1000借りると一年後に$1150返す必要がありますが、もしビットコイン価格がその間に15%以上上昇すれば、利息分を差し引いても得をする計算になります。過去のビットコイン相場は年率ベースで大きく成長した年も多く、強気のホルダーほど利息より値上がり益を優先する傾向があります。「金利よりビットコインの価値上昇のほうが大きい」という自信が、高金利を払ってでも借りる動機になっているのです。

• (2) 課税や手数料の回避：先ほど述べたように、日本ではビットコインを売却すると高額の税金が発生する可能性があります。仮に30%〜50%の税金がかかるのであれば、年利10%前後のローンで済ませたほうがトクだという判断も成り立ちます。また、取引所で売却するときのスプレッドや出金手数料なども考えると、売却コストを回避する手段としてローンを選ぶ人もいます。要するに「売るくらいなら借りた方がマシ」という考え方ですね。

• (3) 自由と速さを優先：従来の金融機関からお金を借りるには時間がかかりますし、使途にも制限があることが多いです（事業資金なのか生活費なのか、といった審査があります）。それに対してHodlHodlのP2Pローンは使い道自由・即日資金調達が可能です。利息が高めでも「今すぐ○○がしたい」「明日までに現金が要る」といったニーズには代えられません。特に仮想通貨業界はスピード命ですから、チャンスを逃さないために高コストでも素早く借りるという選択が生まれます。

• (4) 借金＝時間を買うこと：あるユーザーの言葉を借りれば、「借金をすることは未来の時間を先取りすること」でもあります。例えば住宅ローンがあるからこそ若い世代でもマイホームに住めますし、事業ローンがあるからこそ企業は成長の機会を掴めます。ビットコイン担保ローンも同じで、「今はお金が無いけど将来増やすアテはある。だから今借りてしまおう」というケースもあるでしょう。将来の収入や資産増加を見込んで、時間を味方につけるためにあえて借金をするのです。日本語では「借金してでも◯◯する」という表現がありますが、前向きな借金は将来への投資とも言えるでしょう。

• (5) 非中央集権への支持：もう一つ見逃せないのは、HodlHodlのようなプラットフォームを利用する理由に思想的な支持があります。つまり「銀行や政府に頼らないお金の流れを実現したい」「ビットコインのエコシステムを活性化させたい」というビットコイナーたちです。多少コストが高くても、理念に共感して使っているケースもあります。匿名で自由にお金を借りられる世界を体験することで、金融システムの新たな可能性を感じているのです。

以上のように、高い金利にも関わらずローンを利用するのは明確なメリットや戦略があるからなのです。もちろん全ての人に当てはまるわけではありません。ビットコイン価格が下落局面ではリスクも伴いますし、利息分だけ損になる場合もあります。しかし、それらを理解した上で「自分のお金を働かせる」「資産を手放さずレバレッジを利かせる」手段として活用している人々が増えてきています。

最後に、HodlHodlの公式ブログの一文をご紹介します。

“私たちはビットコインこそがスーパーカ collateral（超優秀な担保）であり、利回りを得るために使うのではなく、それを担保に資金を借りるために使われるべきだと考えています" (The lending is dead, long live the lending | by Hodl Hodl | Hodl Hodl | Medium)。

ビットコイン時代の新しいお金の借り方・貸し方であるP2Pローン。最初は難しく感じるかもしれませんが、仕組みを理解すればとてもシンプルで強力なツールです。日本ではまだ馴染みが薄いかもしれませんが、匿名性を好み、コツコツ資産を増やすのが得意な人にこそフィットするサービスかもしれません。ぜひ少額から試し、自分なりの活用法を見つけてみてください。きっと新たな発見があるはずです。

---

もしビットコイン担保のP2Pローンなどについてもっと深く知りたい、あるいは個別に相談してみたいと思えば、どうぞお気軽にご連絡ください。1対1のコンサルティングも承っています。

サービスには決まった料金はありませんが、ご相談を通じて「役に立った」と思い、お悩みや疑問を解決できたと感じていただけたら、「3つのT」でのご支援（Value for Value）をぜひご検討ください：

• 時間（Time）：この記事をSNSなどでシェアしていただくこと。
• 才能（Talent）：コメントや補足情報などを通じて知識を共有していただくこと。
• 宝（Treasure）：世界で最も健全なお金、ビットコインの最小単位「sats」でのご支援。

もちろん、支援の有無にかかわらず、お力になれればとても嬉しいです。 では、また次回！

@ ff517fbf:fde1561b

はじめに：なぜKYCなしP2P取引か

ビットコインは元々、ピア・ツー・ピア（P2P）の電子通貨システムとして設計されました。サトシ・ナカモトのビットコイン白書でも、「信頼ではなく暗号学的証明に基づく電子決済システム」によって、第三者を介さずに当事者同士が直接取引できることが必要だと述べられています。つまり、本来ビットコインは銀行などの仲介者なしで個人同士が直接送金・売買できる社会的意義を持っているのです。

しかし現在、多くの暗号資産取引所では規制上の理由からKYC（本人確認）手続きが求められ、個人情報の提出が必要です。KYCはユーザーのプライバシー喪失やデータ漏洩リスクにつながりかねず、また口座凍結や資金没収といった中央集権的管理のリスクもあります。経済的にも、第三者を介することで手数料が高くなったり、地域によっては銀行や政府の制限でビットコインの購入が困難になる場合もあります。

こうした背景からノンKYCのP2P取引プラットフォームを利用するメリットは大きいです。例えば HodlHodl(@npub1yul83qxn35u607er3m7039t6rddj06qezfagfqlfw4qk5z5slrfqu8ncdu) は、匿名で世界中のユーザーと直接ビットコインを売買できるグローバルなP2Pマーケットプレイスです。HodlHodlではユーザー同士が直接取引し、サイト運営側はビットコインを一切預かりません。取引はマルチシグエスクロー(2-of-3の多重署名契約)で安全に管理され、取引手数料も最大0.5%と低く抑えられています。プライバシーとセキュリティを確保しながら、銀行口座や身分証なしでビットコインを売買できるため、社会的にも経済的にも大きな意義があります。

本チュートリアルでは、HodlHodlを使ってビットコインを購入・販売する具体的な手順を分かりやすく解説します。また、HodlHodlの安全性（マルチシグエスクローによる非中央集権型の管理）や、他のプラットフォームにはない特徴（本人確認不要、ユーザー自身による鍵の管理、APIやレンディングサービスの活用など）についても説明します。P2P取引に不慣れで不安を感じている方にも安心してご利用いただけるよう、丁寧で親しみやすい言葉で案内していきます。

HodlHodlの基本準備

アカウント登録： HodlHodlの利用を開始するには、まず無料のアカウント登録を行います。必要なのはメールアドレスとパスワードだけで、ユーザー名や身分証の提出は不要です。登録後に届く確認メール内のリンクをクリックすれば、すぐに取引を始められます。

ビットコインウォレットの用意： HodlHodlは取引の際にユーザー自身のビットコインウォレットを使用するノンカストディアル方式です。プラットフォーム上にウォレットは用意されていないため、事前に自分のビットコインウォレットを準備してください。例えばモバイルウォレットやハードウェアウォレットなど、自分だけが秘密鍵を管理できるウォレットを用意しましょう。買い手の場合は購入したビットコインを受け取るウォレットが必要になり、売り手の場合は売却するビットコインを自身のウォレットからエスクローに送金する必要があります。

ビットコインを購入する方法（Buy BTC）

それでは、HodlHodlでビットコインを購入（Buy） する手順を見ていきましょう。以下では、日本円（JPY）を銀行振込で支払ってビットコインを買う例を想定して説明しますが、基本的な流れは他の通貨や支払い方法でも同じです。

1. 「Buy BTC」をクリックする: HodlHodlにログインし、画面上部のヘッダー左側にある「Buy BTC」ボタンをクリックします。これにより、現在出ているビットコイン売り注文（オファー）の一覧ページに移動します。

2. 検索フィルターの設定: オファー一覧ページでは、自分の希望条件でオファーを絞り込むことができます。国、法定通貨、取引タイプ、支払い方法、金額などのフィルター項目があります。例えば日本で銀行振込により購入したい場合、「Country（国）」をJapan、「Currency（通貨）」をJPY、「Payment method（支払い方法）」を Bank Transfer 銀行振込に設定します（他の項目は必要に応じて指定します）。フィルターは任意ですが、自分に合った支払い方法や金額範囲のオファーを探すのに役立ちます。

3. オファーを選ぶ: フィルターを適用すると、条件に合致する売り手のオファー一覧が表示されます。各オファーにはレート（価格）、取引可能額範囲、支払い方法、売り手の評価などが記載されています。希望に合うオファーが見つかったら、そのオファーの詳細をクリックします。例えば「1 BTC = 〇〇JPY」のようなレートで、自分が購入したい額に対応できるオファーを選びましょう。初めて取引する場合は、評価の高い売り手や少額からの取引を選ぶと安心です。

1. 購入量と受取アドレスの入力: オファーをクリックすると、取引の詳細入力画面になります。ここで購入したいビットコインの量を入力します（ビットコイン量あるいは法定通貨換算額のどちらでも入力可能です）。多くの場合、最低・最大取引額が決まっているので、その範囲内で入力してください。また、ビットコインの受取先アドレスを求められます。これは購入後にビットコインを受け取る自分のウォレットアドレスです。アカウントの設定で事前に登録したアドレスがあれば自動で表示されますが、都度指定することも可能です。さらに、支払い方法が複数指定されているオファーでは希望の支払い方法を選択します（例：銀行振込の中でも特定の銀行を指定できる場合があります）。最後に、取引相手（売り手）への伝達メッセージ欄があれば、必要に応じてコメントを記入します。入力が完了したら内容を確認し、「Create contract（契約作成）」 的なボタンを押して取引を開始します。

2. エスクローアドレスの生成: 契約が作成されると、取引画面上にエスクロー（第三者保管用マルチシグアドレス）を生成するための手順が表示されます。ここで 「Generate escrow（エスクロー生成）」 ボタンをクリックし、プラットフォームに登録したペイメントパスワード（支払い用パスワード）を入力します。ペイメントパスワードはHodlHodlで取引の署名に使われる特別なパスワードで、初回取引時に設定しておく必要があります。正しく入力すると、この取引専用のビットコインエスクローアドレスが自動生成されます。あとは売り手がそのエスクローアドレスにビットコインを入金するのを待ちます。画面上に「waiting for deposit（入金待ち）」等のステータスが表示されるので、しばらく待機してください。売り手が約束のビットコイン額をエスクローに送金し、一定のブロック承認（Confirmations）が得られると、取引ステータスが自動で更新されます。

3. エスクロー入金の確認: ビットコインがマルチシグエスクローにロックされ、取引ステータスが「In progress（進行中）」や「Deposited（入金済み）」といった表示に変わったことを必ず確認します。ステータス表示とブロックチェーン上の確認回数が条件を満たしたら、支払いを実行しても安全な状態であることを意味します（エスクローにロックされたビットコインは売り手単独では動かせません。取引ページには売り手が指定した支払い詳細（銀行口座情報など）が記載されていますので、その指示に従って売り手へ法定通貨の支払い（振込）を行います。例えば銀行振込の場合、指定された口座にJPYを送金します。この段階では、必ず取引ページを開いたままにしておきましょう。 支払いが完了したら、取引ページ上の「I’ve sent the payment（送金完了）」ボタンをクリックして、売り手に支払い実行済みであることを通知します。併せて、チャット機能で支払い完了の旨を伝えると良いでしょう。

4. 売り手によるビットコインのリリース: 買い手からの支払いが完了すると、売り手は自分の銀行口座等を確認して入金を検証します。売り手が入金を確認したら、取引ページ上で 「Release Bitcoin（ビットコインをリリース）」 ボタンを押し、ペイメントパスワードを入力してエスクローからビットコインを開放します。これにより、エスクロー上のビットコインが買い手の指定アドレス（先ほど入力した受取用ウォレットアドレス）に送信されます。売り手がビットコインをリリースすると取引ステータスが「Released（解放済み）」に変わり、まもなくブロックチェーン上で買い手のウォレットにビットコイン着金が確認できるでしょう。

5. 取引完了: ビットコインが無事自分のウォレットに届けば取引完了です。取引ページには「Completed（完了）」などのステータスが表示され、双方がお互いを評価できるようになります。初めてのP2P購入、お疲れさまでした！ 🎉

💡 重要な注意事項（買い手向け）: エスクローにビットコインがロックされる前に代金を支払ってはいけません。必ず取引ステータスが「Deposited」や「In progress」になるのを確認してから支払いを実行してください。また、取引には売り手が入金を確認してからビットコインをリリースするまでの制限時間（Payment window）が設定されています。時間内に支払いが完了しないと取引が自動キャンセルされる場合がありますのでご注意ください。困ったことがあれば、取引ページのチャットで相手に連絡することもできます。万一、支払いを送ったのに売り手がビットコインをリリースしない場合は、支払い期限が過ぎてからディスピュート（紛争解決手続き） を開始することも可能です。

ビットコインを販売する方法（Sell BTC）

次に、HodlHodlでビットコインを販売（Sell） する手順を説明します。基本的な流れは購入時と似ていますが、立場が逆になる点（自分がビットコインをエスクローに預け、買い手からの支払いを待つ点）に注意してください。以下では、日本で銀行振込によりJPYを受け取ってビットコインを売る場合を例に解説します。

1. 「Sell BTC」をクリックする: HodlHodlにログイン後、画面上部左側の「Sell BTC」ボタンをクリックします。これで現在出ているビットコイン買い注文（買い手のオファー）一覧ページに移動します。

2. 検索フィルターの設定: 買い手オファー一覧から、自分が対応可能な条件のオファーを探します。フィルター項目はBuyの場合と同様で、国、通貨、支払いタイプ、支払い方法、金額などを指定できます。日本円での銀行振込を希望する買い手を探す場合、国をJapan、通貨をJPY、支払い方法をBank Transferに設定して検索します。

3. オファーを選ぶ: 条件に合致する買い手のオファーが一覧表示されるので、希望に合うものをクリックします。各オファーには買い手が希望するレートや取引限度額、支払い方法、買い手の評価などが記載されています。有利なレートかつ信頼できそうな相手を選びましょう。初取引で不安な場合は、小額で高評価の買い手から始めるとよいです。

4. 売却量と受取情報の入力: オファー詳細画面で、売却したいビットコイン量を入力します（または必要な法定通貨額）。オファーごとに最低・最大額が設定されているので範囲内で入力してください。続いてビットコインの受取アドレス欄がありますが、これは取引完了時に買い手がビットコインを受け取るアドレスです。売り手である自分が入力する必要は基本的になく、買い手側が受取先を指定するか、既に買い手のダッシュボード設定で決まっています。次に、受け取りたい支払い方法が複数記載されている場合は希望の方法を選択します（例えば「Bank Transfer」の中でも特定の銀行名など）。コメント欄があれば取引相手（買い手）へのメッセージを任意で入力します。内容を確認し問題なければ 「Create contract（契約作成）」 ボタンを押して取引を開始します。

5. エスクローアドレスの生成: 契約が作成されると、エスクロー用のビットコインアドレスを生成する段階に進みます。ここで 「Generate escrow」 ボタンをクリックし、ペイメントパスワードを入力します（買い手の手順と同様）。これにより、この取引専用のマルチシグエスクローアドレスが発行されます。次に 自分（売り手）が売却予定のビットコインをエスクローアドレスに送金 します。取引画面上に正確なBTC額と対応するQRコードが表示されるので、自分のウォレットからそのアドレスへ送金してください。送金したら 「I’ve sent the funds（送金完了）」 ボタンを押してビットコインをエスクローに預けたことを通知します。

1. エスクローへのビットコインロック: ビットコインを送金するとブロックチェーン上で一定回数の承認（Confirmations）を経て、エスクローにロックされます。取引ステータスが「In progress（進行中）」や「Deposited」に変わり、買い手は安心して支払いを行える状態になります。あとは買い手からの法定通貨支払いを待ちます。取引画面で支払い期限（Payment window）内に買い手が支払いを完了し、「支払い送信済み」のボタンを押すとステータスが「Paid（支払い済み）」に変わります。

2. 支払いの受領確認: ステータスが「Paid」になったら、買い手が送金を完了したことを意味します。すぐに自分の銀行口座など該当の支払い方法で入金を確認しましょう。金額が全額正しく受け取れたことを確認できたら、取引ページ上で 「Release deposit（デポジットを解放）」 ボタンをクリックし、ペイメントパスワードを入力してエスクローのビットコインを開放します。これにより、エスクローにロックされていたビットコインが買い手に送付されます。

3. 取引完了: ビットコインをリリースすれば取引完了。ステータスが「Completed」に変わり、買い手は間もなく自分のウォレットでビットコインを受け取るでしょう。最後にお互いを評価して取引終了となります。初めてのP2P売却、お疲れさまでした！ 🎉

💡 重要な注意事項（売り手向け）: 支払いを受け取る前にビットコインをエスクローから**絶対にリリースしないでください。買い手からの入金を自分の銀行口座等で確実に確認できてから、ビットコインを解放するようにしましょう。また、もしビットコインをエスクローに送金した後で買い手から支払いが行われず期限切れ（Payment window経過）になった場合、取引をキャンセルしてエスクローのビットコインを自分に返還することができます。取引中は常に取引相手とのチャットで連絡を取り合い、不明点を確認するよう心がけましょう。

HodlHodlの安全性：マルチシグと非カストディアル設計

● マルチシグエスクローによる資金保護: HodlHodl最大の特徴は、2-of-3のマルチシグエスクロー(multisignature escrow)によって取引資金を保護している点です。取引が成立すると、自動的に3つの秘密鍵が関与するビットコインアドレスが生成されます。この3つの鍵のうち2つの署名があれば資金を動かせる仕組みになっており、鍵の配分は「売り手」「買い手」「HodlHodl運営」の三者にそれぞれ1つです。取引中、ビットコインはブロックチェーン上のエスクローアドレスにロックされ、双方の合意なしには動かせまん。つまり、売り手は買い手の同意なしにビットコインを引き出すことはできず、逆に買い手も売り手の協力なしにビットコインを入手することはできません。両者が取引を完了すれば売り手+買い手の2署名でリリースが可能となり、万一トラブルが起きた場合にはHodlHodl運営が仲裁役として（買い手または売り手の一方と協力し）2署名目を提供することで不正を防ぎます。このようにマルチシグ契約によって、詐欺や持ち逃げのリスクを最小限に抑え、安全かつ公平な取引が実現されています。

● 非カストディアル（ユーザー主導の資金管理）: HodlHodlは取引プラットフォームでありながら、ユーザー資金を一切預からないという非カストディアル設計を貫いています。取引中のビットコインは常にマルチシグエスクローにあり、HodlHodl運営が単独で動かすことはできません。これはつまり、中央集権的な取引所とは異なり、HodlHodlがハッキング被害に遭ってもユーザーのビットコインが盗まれる心配がないことを意味します。またプラットフォームが万一ダウンしたりサービス提供を停止した場合でも、当事者間で2つの鍵さえあればエスクローのビットコインを取り戻すことが可能です（※この場合やや技術的な手順が必要になりますが、HodlHodlが完全に消失するケースでも資金はブロックチェーン上に安全に存在し続けます）。HodlHodl運営は3つの鍵のうち1つを保有するのみで、しかもそれは紛争時の仲裁に使うためのものです。通常の取引では運営が介在することなく、ユーザー同士で完結します。以上のように、HodlHodlはカストディアルな第三者を排除し、利用者自身が資金と取引の主導権を握るというビットコイン本来の精神に沿った安全設計となっています。

● 評判システムと取引履歴: HodlHodlでは、各ユーザーに公開の評価（Rating）と取引履歴が紐づいています。取引を完了するごとに互いにレビューを残せるため、他ユーザーの信頼度を事前に知ることができます。初めて取引する相手がどんな評価を受けているか、過去の取引回数や成功率などの情報を確認することで、怪しい相手を避けることが可能です。特に初心者のうちは評価の高い相手を選ぶ、もしくは身近に信頼できるユーザーがいればトラスト機能（他のP2Pプラットフォームでの実績を証明する仕組みや信用できるユーザーをお気に入り登録する機能）を活用すると良いでしょう。

● 二要素認証(2FA)と信頼できる端末: アカウントの不正アクセス対策として、HodlHodlは二段階認証(2FA)のオプションを提供しています。AuthyやGoogle Authenticatorと連携し、一度設定すればログイン時にパスワードに加え6桁のコード入力が求められるようになります。これにより、万一パスワードが漏洩しても本人のデバイスがなければログインできず、アカウントを保護できます。またTrusted Devices（信頼できる端末）機能を有効にすると、新しいデバイスからログインしようとした際にメール確認が必要となり、ユーザーの許可なく不審な端末からアクセスされるのを防ぎます。初心者の方でも、アカウント登録後は設定画面から2FAや信頼できる端末機能を有効化しておくことを強くおすすめします。

● ディスピュート（紛争解決）機能: 万が一取引相手との間でトラブルが発生した場合（例：買い手は支払ったと主張しているが売り手が確認できない等）、HodlHodlのプラットフォーム上でディスピュート（紛争）を開始することができます。ディスピュートが発生すると、HodlHodlのサポートチームが両者から事情を聞き、中立的な立場で問題解決に当たります。必要に応じて前述の運営のマルチシグ鍵を用いて適切な側にビットコインをリリースするなど、公平な裁定が行われます。ディスピュートは最終手段ではありますが、万一の場合の安心材料として覚えておいてください。

以上のように、HodlHodlは技術的・制度的な多層防御によってユーザーの資金と取引の安全を確保しています。他のユーザーの評価を確認する、取引手順を順守する（エスクロー未成立での送禁止等、アカウントのセキュリティ設定を有効にするといったユーザー自身の注意もあわせて心掛ければ、P2P取引でも安心してビットコインを利用できるでしょう。

HodlHodlの特徴：他プラットフォームとの違い

最後に、HodlHodlが他のビットコイン取引サービスと比べて優れている点、特徴的な点を整理します。初めて利用する際の不安解消にもつながるポイントです。

• 🌐 KYC不要の匿名取引: HodlHodl最大の特徴は、本人確認（KYC）なしでビットコイン取引ができる点です。メールアドレスさえあれば世界中誰でも利用開始でき、パスポートや身分証の提出は一切求められません。これはプライバシー保護の面で大きな利点ですし、取引履歴が本人名義に紐付かないため将来的な資産没収や口座凍結のリスクも低減します。規制が厳しい地域のユーザーや銀行口座を持てない人々でも、HodlHodlならビットコイン経済に参加しやすくなっています。

• 🔐 ユーザーが鍵を管理する非中央集権型取引: 前述の通り、HodlHodlはノンカストディアルなP2P取引所であり、ユーザー自身が資産の鍵を管理します。取引ごとにマルチシグのエスクローが生成され、利用者はその一方の鍵を保持します。そのため「取引所にビットコインを預けっぱなしにしていたらハッキングで失った」といった事態が起こりません。常に自身のウォレットから直接取引を行うため、ビットコインの自主管理の原則**が守られています。中央集権的な管理者がいない分、自分で秘密鍵を安全に保管する責任は伴いますが、その分だけ第三者リスクが排除された公平な環境と言えます。

• 💱 世界中の通貨と多様な決済方法に対応: HodlHodlはグローバルなプラットフォームであり、世界中のあらゆる法定通貨 で取引できます。現在100を超える国の通貨と地域が利用されており、取引に使える決済方法も100種類以上と非常に豊富です。銀行振込やオンライン決済サービスはもちろん、現金の対面受け渡しやギフトカード、電子マネー、モバイル送金、さらには商品と交換などユニークな方法までユーザーが自由にオファーを作成できます。これにより、自分の利用しやすい手段で取引相手を見つけられる柔軟性があります。他のプラットフォームだと対応通貨や決済手段が限定されがちですが、HodlHodlでは*「自分の条件でオファーを作成できる」 の強みです。

• 💰 低い手数料と透明な料金体系: HodlHodlの取引手数料は一律0.5%（買い手と売り手で折半で各0.25%ずつ負担）と比較的低コストです。しかも手数料は取引成立時にビットコイン額から自動控除される仕組みで、隠れたコストがありません。さらに紹介プログラムを利用すると0.45%に割引されるなどの優遇もあります。入出金に伴う手数料も基本的に存在せず、各自が使うウォレットの送金手数料以外に余計な負担はありません。他の取引所でありがちな「出金手数料が高額」「スプレッドが不透明」といった心配もなく、明朗会計でユーザーに優しい料金体系です。

• 🤝 初心者に優しいインターフェース: P2P取引というと難しそうな印象を持たれるかもしれませんが、HodlHodlのサイトはシンプルで直感的なインターフェースになっています​。必要な操作は「Buy BTC / Sell BTC」ボタンから進んでフォームに入力していくだけで、画面の指示に沿って進めれば迷うことは少ないでしょう。サイトは現在ウェブブラウザ経由で利用しますが、スマートフォンのブラウザからでも見やすく設計されています。専用アプリはありませんが、その分アップデート時にもすぐ全員が最新機能を利用できます（ダウンロード不要で常に最新版が提供されるメリットです。また、取引画面にはリアルタイムのチャット機能があり、相手ユーザーと直接コミュニケーションを取れるため安心です。困ったときは相手に質問したり状況を確認できるので、言葉の壁がある場合でも定型文や翻訳を活用して意思疎通できます。

• 🛠 API提供による拡張性: HodlHodlは上級ユーザーや開発者向けに**公式APIを提供しています。APIを利用すると、自分のプログラムからHodlHodl上のオファー取得や契約作成、ステータス更新などを自動化することが可能です。例えば、マーケットメーカーとしてレートを自動調整したり、他のサービスと連携して複数のP2P取引所のオファーを比較表示する、といった応用ができます。APIキーはプロフィール設定から発行でき、ドキュメントも公開されているため高度な取引戦略を実装したいユーザーには魅力的な機能です。PaxfulやLocalBitcoinsなど一部他サービスでもAPIは提供されていますが、HodlHodlのAPIはエスクロー操作まで含め包括的にサポートしている点で強力です。

• 💳 ビットコインレンディングサービス: HodlHodlは現物取引だけでなく、ビットコイン担保のレンディング（貸借）プラットフォームも運営しています。サイト上部の「P2P Lending（レンディング）」からアクセスでき、ビットコインを担保にUSDTなど他の暗号資産を借りたり、あるいは逆に他の人に貸し出して利息収入を得ることができます。技術的には取引プラットフォームと同じマルチシグエスクロー方式を用いており、借り手がビットコインを担保としてエスクローにロックし、貸し手が安定通貨を送金することでローン契約が成立します。期間満了時に借り手が返済すればビットコイン担保が戻り、返済不能（延滞や価格変動での清算）の場合は貸し手に担保が渡る仕組みです。驚くべきことに、このレンディングサービスでも一切KYCは要求されません。短期のビットコイン活用や利息収入を得たいニーズに応えるユニークなサービスであり、HodlHodlを使いこなせば「ビットコインを売買するだけでなく、借りたり貸したりする」といった金融活用も可能になります。P2P Lendingについては、今後別のチュートリアルで詳しく説明します。

• 🧪 テストネットで練習可能: 「いきなり本番は不安…」という方向けに、HodlHodlはテストネット版サイトも提供しています。TESTNETでは、本物のビットコインではなくテスト用のビットコイン（signet**ネットワークのBTC）を使って、実際の取引手順を練習できます。架空の資金でHodlHodlの操作感を試せるため、初心者はまずテストネットで売買の流れをシミュレーションしてみると良いでしょう。十分に慣れてから本番取引に移行すれば、落ち着いて対処できます。テストネットBTCは各種ファウンセット（蛇口サイト hhtestnet.com）から無料でもらうことができ、HodlHodlのテスト環境で練習するのに役立ちます。

以上がHodlHodlの主な特徴と利点です。匿名性・安全性・使いやすさを兼ね備えたHodlHodlは、まさに「ビットコインをネイティブにP2P利用する」ための理想的なプラットフォームと言えるでしょう。初めは不安もあるかもしれませんが、本チュートリアルで説明した手順に沿って取引を行えば、きっとその手軽さと利便性に驚くはずです。ぜひHodlHodlでのP2P取引に挑戦してみてください。自分自身でビットコインを扱う経験を通じて、ビットコインの真の価値である「個人が金融の主導権を握ること」を実感できるでしょう🚀

---

もしビットコインのP2P取引やHodlHodlなどについてもっと深く知りたい、あるいは個別に相談してみたいと思えば、どうぞお気軽にご連絡ください。1対1のコンサルも承っています。

サービスには決まった料金はありませんが、ご相談を通じて「役に立った」と思い、お悩みや疑問を解決できたと感じていただけたら、「3つのT」でのご支援（Value for Value）をぜひご検討ください：

• 時間（Time）：この記事をSNSなどでシェアしていただくこと。
• 才能（Talent）：コメントや補足情報などを通じて知識を共有していただくこと。
• 宝（Treasure）：世界で最も健全なお金、ビットコインの最小単位「sats」でのご支援。

もちろん、支援の有無にかかわらず、お力になれればとても嬉しいです。 では、また次回！

参考資料

• Bitcoin Whitepaper - Bitcoin: A Peer-to-Peer Electronic
• HodlHodl公式サイト - Welcome to Hodl ([P2P BITCOIN TRADING platform]
• HodlHodlヘルプセンター - How to buy Bitcoin / How to sell Bitcoin
• HodlHodlヘルプセンター - Why is trading on Hodl Hodl secure
• HodlHodl FAQ - Why should I use HodlHodl、How secure is trading on HodlHodl
• HodlHodl Medium - Hodl Hodl’s API release
• HodlHodl Lend FAQ - What is Lend a ([Earn Highest Returns on Your Crypto Investment - Lend at Hodl Hodl]
• ZoneBitcoin - Hodl Hodl: Tutorial on the anonymous and KYC-free P2P platform
• など

@ b60c3e76:c9d0f46e

KRIS menjamin semua golongan masyarakat mendapatkan perlakuan sama dari rumah sakit, baik pelayanan medis maupun nonmedis.

Demi memberikan peningkatan kualitas layanan kesehatan kepada masyarakat, pemerintah baru saja mengeluarkan Peraturan Presiden (Perpres) nomor 59 tahun 2024 tentang Jaminan Kesehatan. Melalui perpres itu, Presiden Joko Widodo (Jokowi) telah menghapus perbedaan kelas layanan 1, 2, dan 3 dalam Badan Penyelenggara Jaminan Sosial atau BPJS Kesehatan.

Layanan berbasis kelas itu diganti dengan KRIS (Kelas Rawat Inap Standar). Berkaitan dengan lahirnya Perpres 59/2024 tentang Perubahan Ketiga atas Perpres 82/2018 tentang Jaminan Kesehatan, Presiden Joko Widodo telah memerintahkan seluruh rumah sakit yang bekerja sama dengan BPJS Kesehatan melaksanakannya.

Kebijakan baru itu mulai berlaku per 8 Mei 2024 dan paling lambat 30 Juni 2025. Dalam jangka waktu tersebut, rumah sakit dapat menyelenggarakan sebagian atau seluruh pelayanan rawat inap berdasarkan KRIS sesuai dengan kemampuan rumah sakit.

Lantas apa yang menjadi pembeda dari sisi layanan dengan layanan rawat inap sesuai Perpres 59/2024? Dahulu sistem layanan rawat BPJS Kesehatan dibagi berdasarkan kelas yang dibagi masing-masing kelas 1, 2, dan 3. Namun, melalui perpres, layanan kepada masyarakat tidak dibedakan lagi.

Pelayanan rawat inap yang diatur dalam perpres itu--dikenal dengan nama KRIS—menjadi sistem baru yang digunakan dalam pelayanan rawat inap BPJS Kesehatan di rumah sakit-rumah sakit. Dengan KRIS, semua golongan masyarakat akan mendapatkan perlakuan yang sama dari rumah sakit, baik dalam hal pelayanan medis maupun nonmedis.

Dengan lahirnya Perpres 59/2024, tarif iuran BPJS Kesehatan pun juga akan berubah. Hanya saja, dalam Perpres itu belum dicantumkan secara rinci ihwal besar iuran yang baru. Besaran iuran baru BPJS Kesehatan itu sesuai rencana baru ditetapkan pada 1 Juli 2025.

“Penetapan manfaat, tarif, dan iuran sebagaimana dimaksud ditetapkan paling lambat tanggal 1 Juli 2025,” tulis aturan tersebut, dikutip Senin (13/5/2024).

Itu artinya, iuran BPJS Kesehatan saat ini masih sama seperti sebelumnya, yakni sesuai dengan kelas yang dipilih. Namun perpres itu tetap berlaku sembari menanti lahirnya peraturan lanjutan dari perpres tersebut.

Kesiapan Rumah Sakit

Berkaitan dengan lahirnya kebijakan layanan kesehatan tanpa dibedakan kelas lagi, Kementerian Kesehatan (Kemenkes) menegaskan mayoritas rumah sakit di Indonesia siap untuk menjalankan layanan KRIS untuk pasien BPJS Kesehatan.

Kesiapan itu diungkapkan oleh Dirjen Pelayanan Kesehatan Kemenkes Azhar Jaya. “Survei kesiapan RS terkait KRIS sudah dilakukan pada 2.988 rumah sakit dan yang sudah siap menjawab isian 12 kriteria ada sebanyak 2.233 rumah sakit,” ujar Azhar.

Sebagai informasi, KRIS adalah pengganti layanan Kelas 1, 2, dan 3 BPJS Kesehatan yang bertujuan untuk memberikan layanan kesehatan secara merata tanpa melihat besaran iurannya.

Melalui KRIS, rumah sakit perlu menyiapkan sarana dan prasarana sesuai dengan 12 kriteria kelas rawat inap standar secara bertahap. Apa saja ke-12 kriteria KRIS itu?

Sesuai bunyi Pasal 46A Perpres 59/2024, disyaratkan kriteria fasilitas perawatan dan pelayanan rawat inap KRIS meliputi komponen bangunan yang digunakan tidak boleh memiliki tingkat porositas yang tinggi serta terdapat ventilasi udara dan kelengkapan tidur.

Demikian pula soal pencahayaan ruangan. Perpres itu juga mengatur pencahayaan ruangan buatan mengikuti kriteria standar 250 lux untuk penerangan dan 50 lux untuk pencahayaan tidur, temperature ruangan 20--26 derajat celcius.

Tidak hanya itu, layanan rawat inap berdasarkan perpres itu mensyaratkan fasilitas layanan yang membagi ruang rawat berdasarkan jenis kelamin pasien, anak atau dewasa, serta penyakit infeksi atau noninfeksi.

Selain itu, kriteria lainnya adalah keharusan bagi penyedia layanan untuk mempertimbangkan kepadatan ruang rawat dan kualitas tempat tidur, penyediaan tirai atau partisi antartempat tidur, kamar mandi dalam ruangan rawat inap yang memenuhi standar aksesibilitas, dan menyediakan outlet oksigen.

Selain itu, kelengkapan tempat tidur berupa adanya dua kotak kontak dan nurse call pada setiap tempat tidur dan adanya nakas per tempat tidur. Kepadatan ruang rawat inap maksimal empat tempat tidur dengan jarak antara tepi tempat tidur minimal 1,5 meter.

Tirai/partisi dengan rel dibenamkan menempel di plafon atau menggantung. Kamar mandi dalam ruang rawat inap serta kamar mandi sesuai dengan standar aksesibilitas dan outlet oksigen.

Azhar menjamin, Kemenkes akan menjalankan hal tersebut sesuai dengan tupoksi yang ada. “Tentu saja kami akan bekerja sama dengan BPJS Kesehatan dalam implementasi dan pengawasannya di lapangan,” ujar Azhar.

Berkaitan dengan perpres jaminan kesehatan itu, Direktur Utama BPJS Kesehatan Ghufron Mukti menilai, perpres tersebut berorientasi pada penyeragaman kelas rawat inap yang mengacu pada 12 kriteria. "Bahwa perawatan ada kelas rawat inap standar dengan 12 kriteria, untuk peserta BPJS, maka sebagaimana sumpah dokter tidak boleh dibedakan pemberian pelayan medis atas dasar suku, agama, status sosial atau beda iurannya," ujarnya.

Jika ada peserta ingin dirawat pada kelas yang lebih tinggi, kata Ghufron, maka diperbolehkan selama hal itu dipengaruhi situasi nonmedis. Hal itu disebutkan dalam Pasal 51 Perpres Jaminan Kesehatan diatur ketentuan naik kelas perawatan.

Menurut pasal tersebut, naik kelas perawatan dilakukan dengan cara mengikuti asuransi kesehatan tambahan atau membayar selisih antara biaya yang dijamin oleh BPJS Kesehatan dengan biaya yang harus dibayar akibat peningkatan pelayanan.

Selisih antara biaya yang dijamin oleh BPJS Kesehatan dengan biaya pelayanan dapat dibayar oleh peserta bersangkutan, pemberi kerja, atau asuransi kesehatan tambahan.

Ghufron Mukti juga mengimbau pengelola rumah sakit tidak mengurangi jumlah tempat tidur perawatan pasien dalam upaya memenuhi kriteria KRIS. "Pesan saya jangan dikurangi akses dengan mengurangi jumlah tempat tidur. Pertahankan jumlah tempat tidur dan penuhi persyaratannya dengan 12 kriteria tersebut," tegas Ghufron.

Penulis: Firman Hidranto Redaktur: Ratna Nuraini/Elvira Inda Sari Sumber: Indonesia.go.id

@ 20986fb8:cdac21b3

Relay is the soul of the decentralized Nostr network. In previous articles, we discussed who would bear the ongoing operational costs of Relay. To ensure a thriving storage network, Relay needs to be incentivized. In order to achieve better decentralization of media, YakiHonne has launched the Relay's early incentive plan to support the development of 50 Relays for a period of 6 months.

The details of the grant program are as follows:

• Grant amount: A total of $50,000, with each grant ideally being $1000.
• Application period: From May 15, 2024, to December 31, 2024.
• Applicants: Existing Relay node hosts or new hosters, with a funding ratio of 20 existing Relay nodes and 30 new Relay nodes.

Relay operational requirements:

1. The minimum requirements for Relay deployment are according to [1]:

2. 1.1. High performance Intel

3. 1.2. 1 vCPU
4. 1.3. 2048 MB Ram
5. 1.4. 50 GB NVMe SSD

6. 1.5. OS Ubuntu 22.04 LTS

7. There are no restrictions on storage service providers, and you can choose any stable provider.

8. There are no restrictions on the location of Relays, but it is recommended to have geographical diversity to maintain a balanced distribution of Relays.

9. Relays need to operate continuously for the next 6 months with downtime not exceeding 30 minutes.
10. You can choose from the already existed relays implementations: nostr-rs-relay based on Rust, nostr-ts-relay akk nostream using Typescript, or strfry using C++.
11. Relay models can be of any type: thematic Relays relying on keyword filtering for specific topics, invitation-only Relays that restrict publishing permissions through public keys, or paid and free public Relays corresponding to paid publishing and fully open modes, respectively. However, to maintain a balanced incentive, the proportion of paid and invitation-only Relays will not exceed 20%.
12. Monthly reports on Relay stability and availability need to be shared to maintain good operational status.

Application process:

You need to submit a proposal including whether you are already hosting a Relay, the name of the existing Relay, specifications of the Relay hosting service, possible service provider choices, Relay development environment, Relay model, and more details to help you secure funding.

Submission: npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q

Grant Evaluation and Disbursement:

Within one week of receiving the application, we will provide feedback on the grant decision. The grant amount will be disbursed in two installments, with 50% being provided initially and the remaining 50% being disbursed after 3 months.

Rewards:

In the early incentive program, nodes that contribute consistently to improving Relay performance, expanding functionality, and ensuring stability will receive special rewards and have the opportunity to earn more income.

The goal of this incentive program is to further decentralize Nostr, enhance its performance, and promote the development of Relay functionality. Through the early incentive program, we aim to explore sustainable incentive models for Relays and lay the foundation for their sustainable development.

@ 1bc70a01:24f6a411

Thought 1: Content Creation, Discovery & Remixing

Recently I’ve been thinking about ways we could highlight nostr’s unique properties while at the same time attracting creators to the platform.

There’s been a lot of discussion about what might spark nostr’s next wave of growth. I pointed out that people come for either other people, or for content. But, I also failed to realize that people also seek ways to express themselves via new tools that enable easy or unique ways of expressing yourself.

One thing we can say with certainty is that people are not coming to nostr for other people. While generally following influencers is a proven growth strategy - after all, many of us followed Jack, we still have a catch 22 problem of lacking audience and incentives for those creators to come here. Even if we managed to convince some large influencers to try the platform, it is not likely that they would stay. They’d need to be really passionate about nostr’s principles and vision to buckle in for the long term.

Problem: creators and influencers won’t come to nostr unless they can grow their audience, and nostr lacks the audience. We’ve seen this play out with Matt Taibi. He joined nostr but was reluctant to stay because there’s little incentive to share with a small audience when Twitter/X can bring in many more eyeballs.

Possible Solution: Instead of brining creators to the platform, enable some of the current passionate user base to become decent creators themselves. We don’t need influencers with giant audiences, we just need good content that keeps people around. If we apply the 80/20 rule (Pareto’s principle), it turns out we don’t need that many creators to have a great flow of content. Enabling just a handful of people to create great content might just do the trick.

How to get there: focus on creating tools that enable expression of creativity. One such tool is Pinstr, but its value is largely untapped. On its own, pinstr is nothing interesting, it’s practically a clone of Pinterest. But, given the interoperable nature of nostr, it would be interesting to see pinned boards / content surfaced within kind 1 clients. People could then explore the board or that user’s other boards further by making their way to Pinstr.

How do we encourage more people to curate interesting pins? How about a pin extension that makes it easy to do so?

How do we enable people remixing other pins? Allow them to re-pin the content to their own boards. These are all mechanics that made Pinterest interesting, but lack in pinstr (as far as I’m aware).

Other ways that we might encourage content creation:

1. Multi-account support. Can we make it SUPER easy to switch between identities when posting some curated content? Yes we can. (Select a different identity when posting)
2. Surfacing “Other stuff” with a call to action to do that thing. For example, if someone shares a list, a kind 1 client should be able to render that list in a way that’s easy to browse, share and encourages to create your own list. If someone shares a music playlist (hopefully via native nostr kind), a person should be able to see the playlist and be encouraged to create their own. Watch stream? > prompt to start your own
3. Gif / meme discovery with a call to action to create your own. (Plebhy, Memester)
4. Styling tools (more complex) to style media, add soundtracks etc (perhaps via integration with Wavlake or other nost-native music events).

5. Content scheduling - help existing users become power users. Instead of posting everything at once, allow users to schedule it out for even distribution. Tools like Shipyard enable this already, but having this ability in-client might make it more accessible and useful.

6. Content pinning extensions - bring the outside world to Nostr. How can people 1-click pin content to nostr without having to switch tabs constantly?

7. App discovery - I think this is already in the works, but being able to surface other apps within kind 1 clients would be super interesting.

8. Enable surfacing of highlighted content and paid content - with highlights, nudge people to read more of the content if it comes from within one of the nostr clients. With paid content, indicate that it is premium content and encourage creation of premium content “Become a creator” or “Join creator studio”.
9. Encourage people to write long-form opinion content. When reading a long form article, perhaps have a call to action to start your own nostr publication. “Publish on Nostr and earn”
10. Surface and encourage audio creation - we don’t have a nostr podcast client yet, but if there was one, kind 1 clients could surface that content automatically and encourage people to start their own podcasts, audio diaries, audio chats (nostr nests) or audio stories. Kind 1 clients could surface audio clips with waveforms and subtitles built in, or create a framework by which other developers could create this type of interaction with your kind 1 client. Can users create their own clip playlists from audio content fetched from the nostr podcast app? Why not?

The common objection to all of this might be that “you can already do all of this just by copying links”. Yes, and no. Copying links does share content - albeit in a boring preview way. It does not enable interactivity, nor prompt people to create that type of content. I think this is where nostr could shine.

Thought 2: Interoperability

One of the greatest strengths of nostr is the ability to display events across clients. I think of kind 1 clients as the glue that holds together the “other stuff”. The other stuff apps can be used to create the stuff, and kind 1 can enable discovery of said stuff, while encouraging to visit those tools to create their own.

Traditional social media platforms are encourage to put up walls and discourage leaking of users to other places. The more time a user spends on a website or app, the better for that company. But, with nostr, there’s a virtuous positive loop that does not punish leaking of attention, but instead, rewards it. The more content people create, the more interesting your kind 1 discovery client becomes.

How to get there: It’s going to take a lot of work to integrate the other stuff, but it’s already under way. As a client developer, partner up with other stuff clients to figure out how to best support them. Open up nostrapps.com to see what exists, and how your client can accommodate the surfacing of that stuff with minimal effort (since our resources are so scarce). Tap into product designers to help conceptualize and visualize interactions and growth loops. #nostrdesign is ready to help with this.

Type of content kind 1 clients could surface and create loops for:

1. Playlists
2. Pin boards (pinstr)
3. Audio chats (nost nests, corny chat)
4. Highlights (highlighter)
5. Payments
6. Fundraisers (Heya, Geyser)
7. Communities
8. Events (Flockstr)
9. Streams (zapstream)
10. Long form content
11. Job posts / boards
12. Recipes (zap cooking)
13. Lists
14. Torrents (Stan)
15. News feeds
16. Calling functionality
17. DMVs
18. Podcast clips, playlists
19. Audio clips
20. Marketplace items (Shopstr, Creatstr, Plebeian Market)
21. Paid content (highlighter)

Recap

1. Build tools to aid content creation
2. Surface “other stuff” in kind 1 clients
3. Prompt people to create their own stuff

I’m probably missing a ton, or not thinking of unique experiences that are just under the nose. What am I missing? What other cool interactions could be enabled by nostr’s interoperabilit

@ 7dc16771:70ed704f

『マーダーボット・ダイアリー』マーサ・ウェルズ著・中原尚哉訳・東京創元社

「マーダーボット」と呼ばれる主人公“弊機”は保険会社に所属する人型警備ユニット。顧客に貸し出される警備システムの「構成機体」でありながら、自分で統制モジュールをハッキングして、“自由”な存在になっている。でも彼がその“自由”を使って行うのは大好きな連続ドラマ『サンクチュアリムーン』を繰り返し繰り返し見ること。――とにかく“弊機”が可愛い！　一人称を“弊機”と訳した訳者さんがすごい！　人間の作ったドラマにどハマりしながら「人間とは付き合いたくない」と思ってる自意識過剰な引きこもりオタbotによる一人称日記形式のSF小説。安倍吉俊さんの表紙イラストも可愛いので是非！

アーケードゲーム・タイポグラフィ ビットマップ書体の世界 (大曲都市・著/グラフィック社)

パックマンのフォントを覚えているでしょうか？

本書は、70〜90年代のアーケードゲーム黄金期に生まれた様々なゲームのために作られた、個性豊かなフォントを取り上げています。 そこはわずか8✕8ピクセルの小さな文字の世界。その中で工夫を凝らされた数百にも及ぶフォントにはひとつとして同じものはなく、視認性と世界観の演出を追求した試行錯誤と進化の歴史を感じることでしょう。

いわゆる8bit風、ピクセルアートがひとつのジャンルとして市民権を得て久しいですが、キャラクターや背景だけではなく、フォントにもこんな奥深い世界があることを感じてほしいと思います。

ネガティブ・ケイパビリティ 答えの出ない事態に耐える力 (帚木蓬生/朝日選書/朝日新聞出版)

本書は、医師たちが「ネガティブ・ケイパビリティ=答えの無い状況を耐える力」を発見するまでの道程からはじまります。以降、それが「医療」、「創作」、「教育」、および平和の源泉たる「寛容」の点から、実践的にも極めて重要である理由を述べています。

本書は読み物として面白いだけでなく、文献の列挙など参考書としても役に立つ様に書かれています。物語作家であり、現役医師でもある帚木氏ならではです。多くの人に一読をお薦めできます。

面白く読め、困難に直面した際に誰もが持つ根源的な力について、理解を助けてくれます。豊富な解説は、現代的な問題を俯瞰する際に、辞書的に参照することもできる一冊です。

王様のプロポーズ 極彩の魔女 (橘公司/富士見ファンタジア文庫)

この物語の始まりは不意に誘 (いざな) われた異世界、目の前で殺されたのは世界最強の魔女。 彼女に託された最後の魔法を受け取り、その犯人に迫っていく。 一見するとシリアスに感じられるストーリーに色を付けるのは主人公の一途さ。一目惚れから始まった彼女への恋愛感情はどこまでも愚直であり、故に周りから奇異の目で見られ滑稽なやり取りが発生することもある。しかし一途であるために犯人が露見した場面で主人公の決意がより重いものとなり、それまでの伏線の美しさが強く感じられる。

「人生が整うマウント大全」著:マウンティングポリス 技術評論社

登頂者(マウンティングピープル)たちの能力バトル開幕ッッ！お前の“普通”で相手を殴れｰｰｰｰ！

強者は何気無い発言の全てが他者を傷つけていることに向き合え。弱者はマウントの型を取り入れて精神武装を身につけろ。

書籍の半分を占める圧倒的なマウンティング実例で、今日から実践可能な知識をインプット可能。マウンティングする“剛”の技だけではなく、マウンティングを受ける“柔”の技も身につく、全方位に特化した業界トップのハウツー本。

5年間Twitterでマウント警察をし続け、“体系的な学問”としてのマウントフルネスをぶち上げた筆者に涙が止まらない、感動の一冊。

@ ff517fbf:fde1561b

フアン・ラモン・ラッロ氏は、スペイン出身の経済学者・作家であり、自由市場経済とリベラルな思想の提唱者として知られています。彼は、国家による過剰な介入や財政政策の問題点を鋭く分析し、自由主義の基本原則に基づく社会の実現を目指す論考や著作を多数発表しています。数多くのメディアや学会で講演を行い、現代社会における経済政策や公共の役割について、国際的な議論にも影響を与えている人物です。

---

皆様、こんばんは。そして、Andorra Economic Forumの皆様、本日はご招待いただき誠にありがとうございます。
本日の講演では、これまで私が持ち続けてきた見解、すなわち、より自由で、より繁栄するために、スペイン及び世界において自由主義革命がなぜ必要であり、さらには急務であるのかという理由をお伝えしたいと思います。また、現代国家が、ストックホルム症候群のような論理に我々を陥れており、その結果、国家が我々の自由を体系的に制限し、財産を構造的に攻撃している状況を、ほとんどの人々が抗議もせず、またはその非常事態性すら意識していないという現実をどのように理解すべきかについても触れます。

まず初めに、皆様のご反応から察するに、これは既知の内容に感じられるかもしれませんが、自由主義の基本原則、すなわち四つの基本的な考えを確認させていただきます。どのようにして、社会生活と、各個人が自らの人生計画を追求するための自律性とを両立させ、かつ、個々の自律性が打ち消されるような一個または多数の専制に服従することなく生きることができる社会が成立するのでしょうか？　それは、協力と共存が可能な社会の中で、各人が自己の利益を追求し、同時に他者の利益追求を尊重するための基本原則、すなわち以下の四つの原則によって支えられているのです。

第一に、個人の自由、すなわち他者の行動を踏みにじることなく自ら行動するという、いわゆる非攻撃の原則です。自分が望むことは何でもできますが、他者が望むことをするのを妨げてはならず、また、他者があなたの望むことを妨げることも許されないのです。

第二に、私有財産です。平和的に獲得し、平和的に自らのものとしたものはあなたのものであり、それによって自由に行動し、自らの人生計画や行動計画を追求する手段となります。もしも、これらの計画遂行に必要な手段が恣意的に奪われるならば、それはあなたの個人の自由、すなわち自らの人生計画を追求する自由を侵害することになるのです。

第三に、契約の自律性です。あなたは第三者と自由に合意を結ぶことができます。もちろん、第三者を攻撃することは許されませんが、双方が望むことについて自発的に合意することは可能です。合意は、当事者間の私法上の契約であり、両者が履行すべき約束であり、第三者が介入してこれを正当化したり否定したりするものではありません。ただし、合意の内容は、あくまで当事者双方やその所有物にのみ影響を及ぼすものです。

そして最後に、広義の意味での結社の自由です。個人は、契約上、望むことについて合意するだけでなく、共に生活する方法や、ある程度安定した形で組織される方法を合意することも明示的に可能です。これらの原則は、しばしば国家によって保証されると言われます。なぜなら、国家がなければ、法体系も安全保障機関も存在せず、個人の自由、私有財産、契約の履行、そして結社の自由を保障するものが何もないと思われがちだからです。とはいえ、確かにある程度の国家は、警察国家としてこれらの基本的な社会的共存の規範を保証するために必要かもしれませんが、私たちが必要としているのは、単にこれらの自由主義社会の原則と自由な人々の相互作用が尊重されることを確保するための、巨大かつ過剰な国家ではありません。

実際、国家が大きくなるほど、つまり社会における国家の存在感が増すほど、これらの原則は侵害されがちです。なぜなら、国家は恣意的に規制を強化し、税金を引き上げることで、たとえ他者に損害を与えなくとも、個人が望むように行動する自由を阻み、また、私有財産を強制的に奪い、当事者間の取引を妨げ、さらには、結社および脱会の自由さえも制限してしまうからです。たとえば、誰かが既存の国家から離れ、他の国家に参加したり、あるいは新たな国家や政治共同体を形成して自らを組織しようとした場合でさえ、現行の国家はそれを認めないのです。

さて、これらの自由主義の基本原則は、各個人の計画や人生のプロジェクトが社会の中で花開くために必要不可欠なものであり、現代国家によって体系的に侵害されているのです。しかし、現代国家とは、必ずしも常に我々と共にあった国家ではありません。私たちは、今日のようなメガ国家、ハイパーステート、過剰に肥大化した国家をある程度は当たり前のものとして受け入れてしまっていますが、これらは唯一の政治的選択肢ではなく、歴史を通じて存在してきた唯一の政治現実でもないのです。

ここで、主要な西洋諸国における国家の社会に占める重みの変遷について、皆様にご覧いただければと思います。今日、国家の重みは国によって大きな違いはないものの、概ね国内総生産（GDP）の40〜50％を占めています。中には、例えばフランスのようにGDPの60％に達する国もあります。国家が社会的調和や幸福の保証とされることは稀であり、実際、フランスは世界最大の国家を有しながら、またはそのために、今最も分断され混沌とした国の一つとなっています。

しかし、現状、国家はGDPの40〜50％、すなわち社会が毎年生み出す生産の約半分を吸収し、再分配または政治層や官僚階級が決定した形で消費しているのです。これは常にそうであったわけではありません。19世紀、ひいては第一次世界大戦前までは、近代先進国における国家の経済的重みはGDPの5〜10％程度に過ぎなかったのです。

例えば、アメリカ合衆国では第一次世界大戦前、国家のGDPに占める割合は3〜4％でしたし、今日巨大な社会民主主義国家となっているスウェーデンでさえ、かつてはGDPの5％程度でした。すなわち、国家というものが必然的に経済の半分を占めなければならないというわけではなく、これは徐々に積み重ねられてきたプロセス、いわばゆっくりと沸騰させられるカエルのようなものです。第一次世界大戦後、国家の経済に対する重みは大幅かつ確固たる上昇を見せ、さらに第二次世界大戦後には、急激かつ持続的な上昇を経て、1970年代以降、現在の水準にまで達したのです。

ちなみに、ここで我々がしばしば耳にする「国家が後退しているから、我々は新自由主義の時代にいる」というレトリックが、いかに毒性がありずる賢いものであるかにも注目してください。過去40年間で、グラフ上に国家の重みが大幅に後退したと示す兆候は見当たりません。ある時点で国家のGDPに占める割合が1〜2％減少することがあったとしても、200年の間にGDPの5％から50％へと増加し、現在は概ね50％前後に留まっているのです。国家が後退し、民間部門がすべてを占めるようになっている、というのは全く逆の現象です。

実際、多くの人は、国家が拡大し続けるのが当然であり、もし急速な成長が見られなければ、国家は後退していると考えがちです。しかし、国家は既にそれ以上大きく成長する余地がほとんどないのです。もちろん、GDPの60％、70％、80％にまで達すれば、直接的または間接的な社会主義経済になってしまいます。

そして、なぜ国家はこれほどまでに成長したのでしょうか。急激な国家拡大を説明する基本的な要因の一つは、福祉国家の発展です。つまり、かつては国家が提供していた医療、社会保障（年金、事故保険など）や教育といったサービスの国家による提供が、福祉国家として大きく発展したのです。

ご覧の通り、1930年代や第二次世界大戦後までは社会保障費は非常に低い水準にありましたが、特に第二次世界大戦後からは、GDPの20〜30％にまで急上昇しました。これらはかつて、市民社会や市場を通じ、または必ずしも商業的な交換を介して提供されていた、労働組合などが担っていた社会保障の役割を、国家が吸収していったものです。労働組合は国家から独立し、時には国家に対抗しながら、社会保障の機能を果たしていたのですが、その役割が国家に吸収されることで、我々は国家に依存するようになってしまったのです。

なぜなら、社会保障費は支出であり、中には「依存費用」とも呼ばれるものもあります。たとえば、老後に収入がなくなった時や、何らかの障害によって収入が得られなくなった時のために、個人の貯蓄から基金を積み立てる場合、その基金が自分自身で管理されるなら自律的ですが、国家が管理すれば、私たちは国家に全く依存することになってしまうのです。国家が消滅するか、大幅な予算削減が行われれば、我々は何も残らないのです。結果として、国民は容易には消えない国家の爪痕に囚われることになるのです。公共年金制度の問題を考えてみてください。現代の先進国家において、公共年金制度は最も大きな支出項目の一つです。

では、どうすれば公共年金制度を解体できるのでしょうか。どうすれば、必要以上に介入してきた国家、例えばアメリカ合衆国では大恐慌期（1930年代）に、必要がなかったのに介入してきた国家を、その状況から脱却させることができるのでしょうか。設立当初は、ある一定の年齢に達した者には一定額の年金を支給すると約束し、その費用を現在働いている者への税負担によって賄うというシステムでした。

システムの構築は、当時の平均寿命がかなり低く、支給期間が2～3年程度であったため、比較的容易で安価に行われたのですが、システムが一度確立され、世代を超えた労働者の貯蓄能力を事実上奪う形で構築された今、どうやってそれを解体すればよいのでしょうか。もし「年金は支給されなくなるのか」と言えば、かつて生産期に労働者の給与のかなりの部分を国家が吸収し、貯蓄を阻害していた結果、何百万人もの人々が貧困に陥ることになるのです。

じゃあ、もう引退されている皆さんは年金を受け取ることになりますが、現役世代がその年金の費用を負担し、そして自分たちが引退する時には年金を受け取ることができなくなるのです。つまり、この世代からは何の対価もなく、給与のごく大部分が没収されることになるというわけです。これをどうやって解体するつもりですか？　決して容易なことではありません。

また、例えば医療制度についても同様です。若者にとっては医療制度の解体はそれほど難しくないように見えるかもしれませんが、貯蓄がなく、保険にも加入していない高齢者にとって、もし今、公共医療制度が終了し、年齢とともに医療費が指数関数的に上昇するために通常以上の医療費が発生すると告げられたら、彼らはその医療費にどう対処すればよいのでしょうか？　彼らは、公共医療制度が機能するという説明のもとに、その医療費が賄われると予め想定し、税金を支払っていたのです。

これをどう逆転させるか？　もちろん、即座に行えることではありませんが、時間をかけた移行措置として行っていかなければなりません。だからこそ、国家はこの道を通じて成長し続け、社会がますます国家による再分配に依存するようになることで、国民の自律性を奪っていくのです。

ちなみに、現代福祉国家の発明者の一人であるのは、プロイセン出身のドイツの首相オットー・フォン・ビスマルクです。彼の回顧録――つまり、批判的ではない親しい記者によって書かれた回顧録――によれば、ビスマルクは、公共年金制度を創設することで労働者階級を国家に依存させ、労働者が国家に対して反抗しないように仕向けたと説明しています。当時、反抗は、いわば反資本主義的な行為とみなされていたのです。彼は、国家主義を維持するためではなく、「労働者には社会主義的傾向がある。では、どうすれば労働者を手なずけることができるのか？」という視点から、公共年金制度を利用したのです。同様に、労働者は公共年金制度を通じて、または国家に対抗する形で手なずけられるのです。そして、現状はこの通りになっています。

そこで、皆さんは疑問に思うかもしれません。この何世代にもわたって築かれてきた巨大国家は、具体的にどのような機能を果たしているのでしょうか？　その資金はどこに行っているのか？　この巨大国家は何に対して支出をしているのか？　ここに、2022年の欧州連合各国の平均、すなわちGDPの50％という数字があります。スペインの場合も2022年時点で大きな差はなく、GDPの47％を支出しているため、概ね代表的な数値といえます。さて、この50％のうちの20％は社会保障費、主に年金費用（老後だけでなく、遺族、障害、孤児などに関する給付も含む）です。これに加え、比較的低コストな非拠出型給付も存在します。次に、スペインの場合は約7.7％、すなわち7〜8％が医療費、6％が官僚機構の運営費用、そして何よりも重要なのが公債の利子支払い費用です。さらに6％は経済政策に充てられ、例えばインフラ整備や農業支援などが含まれています。教育に関しては、公立教育や協定校を含めて約4.7％、環境保護は0.8％（これは必ずしも気候政策だけでなく、森林の管理なども含む）、住宅や地域サービスが1％、そして余暇、文化、宗教に関しては1.1％となっています。これらは、メディアや文化、宗教団体への補助金などとして支出されています。

かつて、リベラルな最小国家、例えばアメリカではGDPの3％程度であった国家がありました。なぜなら、当時は上記のような広範な機能を持たず、防衛（GDPの1.3％）と治安・司法（GDPの1.7％）に集中していたからです。つまり、19世紀にGDPの3％を占めていた国家が、現在もその核となる部分は同じ3％のままであるということです。国家が高価になったわけではなく、19世紀に存在した国家のコストは大体同じであったにもかかわらず、現代国家は19世紀よりもはるかに多くの機能を担っているため、多くの税金が必要とされているのです。もちろん、すべては税金で賄われています。

では、いったいどれだけの税金が支払われているのでしょうか。ここでは、国民が被っている税負担の実態について十分に認識されていないのではないかと思います。もしその実態が明らかになれば、社会的不服従が起こるでしょう。国家は、税の実感を曖昧にするための手段を多数用いているのです。例えば、さまざまな理由で税金を徴収する仕組みです。「この項目に対して税金を払え」と一律に要求するのではなく、「稼いだ金額、支出、保有資産、さらには支出全体に対して税金を課す」といった形で、複数の種類の税金を同時に適用します。消費全体に対して一律に税金を課すのではなく、付加価値税（IVA）やその他の特別税など、多岐にわたる特別な税金が存在し、相続税に至るまで多岐に渡ります。

さらに、我々はさまざまな側面で税金を支払っているにもかかわらず、その実感すら持っていないこともあります。たとえば、関税はその値上がり分を商品の価格に転嫁されるため、意識されにくいのです。付加価値税が上がっても、スーパーなどが告知しない限り、私たちはその上昇に気づきにくいのです。また、税負担を一度にまとめて徴収するのではなく、分散して給与から差し引くことで、その実感を薄めています。かつては、年間に稼いだ金額に対して一括で所得税（IRPF）を支払うのが普通でしたが、現代では分割して徴収されるため、納税者は自分がどれだけの税金を支払っているのかを実感しにくいのです。ちなみに、IRPFの源泉徴収制度は、第二次世界大戦中にリベラルのミルトン・フリードマンによって考案されたものです。つまり、敵はしばしば自国に潜むものでもあるということです。

ここで示したのは、平均的な支出額です。スペイン国家のすべての財政収入を国民または労働者で割ると、国民一人あたりの国家負担のおおよそのコストが見えてきます。実際には公共赤字、すなわち収入以上に支出している部分もあり、その分は将来の税負担として転嫁されるため、実際のコストはさらに大きくなります。ここでは、現状で国民から徴収されている税金のみを取り上げています。なお、これらの数字はインフレーションを考慮していないため、2001年と2024年の数字を直接比較することはできませんが、ここでは2024年現在の状況に焦点を当てています。現在、平均してスペイン国民一人あたり、約15,000ユーロの税負担がかかっているのです。つまり、一般的には夫婦と子供一人の家庭で約50,000ユーロの税金が支払われている計算になります。労働者という視点に立てば、実際に税金を支払っているのは、平均で30,000ユーロ以上にのぼります。もちろん、高所得者層が多くを負担しているという見方もありますが、これは平均値であり、平均値は必ずしも実態を正確に反映するものではありません。

さて、労働者一人あたりの支払いを、かなり寛大な見積もりで考えてみましょう。スペインにおける現在の中央値の給与は22,400ユーロです。しかし、この22,400ユーロという数字が給与明細に反映される前に、企業側がすでに支払っている社会保険料が約7,000ユーロ存在しています。つまり、実際の中央値の給与は29,000ユーロ、ほぼ30,000ユーロであるべきものですが、この30,000ユーロは労働者自身が実感できるものではありません。そして、たとえ「実際は自分のものである」と伝えても、「それは企業が支払っているものであって、自分が支払っているわけではない」と言われ、自己欺瞞に陥るのです。結局のところ、実際に支払っているのは自分自身なのです。

実際、30,000ユーロの実質報酬を基にすると、そこから7,000ユーロが差し引かれて、給与明細に表示されるのは22,400ユーロです。さらに、労働者側の社会保険料として約1,500ユーロを追加で支払い、所得税（IRPF）が約3,000ユーロ、さらに消費に応じた間接税が最低でも約2,000ユーロ（場合によってはそれ以上）かかります。さらに、ここでは取り上げていない他の国家への支払い、たとえば不動産税（IBI）やサービス料、共済負担金なども存在します。結果として、中央値の労働者は、本来約30,000ユーロあるべき給与のうち、税引き後に手元に残るのは約15,800ユーロに過ぎないのです。つまり、ほぼその半分が国家によって吸収されていることになります。年間で見ると、さまざまな税金、特に社会保険料、所得税、そして間接税として、合計約13,400ユーロが徴収されているのです。

このように、中央値の労働者は、所得分布の中央に位置しており、非常に多くの人々が彼より少なく、また多く稼いでいる人もいます。だからこそ、中央値の労働者が支払っている税負担、すなわち年間約13,400ユーロという数字は、スペイン国民に対して行われている極めて大規模な税負担の実態を物語っています。これにより、国家から提供されるサービスが強制的に受け入れられているのです。

果たして、これは必然なのでしょうか？　歴史的に見れば必ずしもそうではなく、また現代においても地域によって差があります。つまり、労働者が生み出す富の半分以上を国家が吸収するという、巨大な国家が当然であるという考え方は、今後も続くものではありません。ここには、異なる繁栄度を持つ国々が存在し、一般的に発展した国々であっても、欧州やアメリカのような国家に比べ、国家の規模はかなり小さく抑えられている国もあります。しばしば「スペインの国家規模は欧州平均より小さい」と言われますが、欧州平均自体が、プロの略奪者たちのクラブのようなものなのです。従って、欧州平均という水準と比較するのではなく、もっと控えめな国家規模を持つ国々や、税負担の貪欲さが制限された国々と比較すべきです。

例えば、ヨーロッパ内ではスイスがあります。偶然かどうかはさておき、スイスはヨーロッパで最も豊かな国の一つでありながら、国家のGDPに占める割合は33％と、欧州やアメリカに比べて10〜15ポイント低いのです。また、香港や韓国はGDPの28％、チリはこの分類の中では最も貧しいかもしれませんが約26％、台湾は16％、そして世界で最も豊かな国であるシンガポールは15％です。シンガポールや台湾は、国家がGDPの15〜16％という小規模な状態で十分に現代社会の機能を果たしているのです。もちろん、シンガポールの場合は都市国家であるため、経済規模のメリットもあるでしょうが、公共支出の大部分が社会保障に回っている現状を鑑みると、都市規模か大国家かは大した違いがないのです。むしろ、シンガポールや台湾のように、GDPに対して国家の規模が30ポイントも低い国の方が、国家による私有財産の侵害が少ないと言えます。

したがって、もし大規模な国家による大規模な略奪を回避でき、しかも機能的には他の国と同等以上に運営できるのであれば、当然、より少ない税負担で、なおかつより効率的な公共サービスを提供する国家の方が望ましいのです。実際、国家が何でもかんでも行おうとすれば、その多くは非効率にならざるを得ません。一方で、企業がすべてを行おうとしても、専門分野に特化した他の企業に競争で敗れるため、最終的には消費者がより良いサービスを選ぶことになるのです。問題は、国家の場合、国民が国家から自由に離脱し、同じサービスを提供する他の組織と契約する余地がないという点にあります。国民は、非常に非効率かつ高コストな国家サービスに縛られており、選択の余地がないのです。したがって、もし小規模で効率的な国家が存在すれば、それは大規模で税負担の重い国家よりも好まれるはずです。

そして、もし国家が回収するGDPの割合が30ポイントも大きいのであれば、それは明らかに国民の私有財産を暴力的に侵害していると言わざるを得ません。ですから、もし国家による大規模な略奪を回避し、かつ他国と同等以上の機能を果たすことが可能であれば、国家は少なくとも縮小されるべきです。なぜなら、そうした国家は国民にとって好都合であるだけでなく、公共サービスの質も向上し、効率的に運営されるからです。結局のところ、すべては国家ではなく、国家に寄生する巨大な官僚組織の福祉が優先されているのです。

もし、あなたの社会にこれほど大きく根付いた寄生虫が存在するならば、その寄生虫は当然、去ろうとはしません。むしろ、さらに大きな植民地を形成しようとするでしょう。これが、国家が成長し続ける理由であり、そして、血を吸い上げるこの寄生虫と戦う必要性が生じる所以なのです。

別のシナリオを考えてみましょう。つまり、現代社会における国家の規模を実質的に縮小するという仮定を立て、その実現可能性や現実味について見極めるためです。これまでに、ヨーロッパにおける現代国家の重みがGDPの50％に達していること、その内訳を示してきました。さて、かつての状況を想像してみてください。あの時代は、科学フィクションのようなことは必要なく、医療はゼロ、経済政策も実質ゼロで、民間部門が構築できないインフラだけが、もしあれば驚くほど僅か、GDPの1％程度だったのです。教育はゼロ、防衛と公共秩序は維持されるものの、余暇・文化・宗教への補助金はゼロでした。地域サービスや環境保護に関しては、下水道、街路灯、森林の維持管理など必要な分は残され、官僚組織も非常に大幅に縮小され、社会保障も一部のみが残されていました。

さて、しばしば「国家は富裕層からお金を奪い、貧困層へ再分配するために存在する」と言われますが、実際、社会保障はGDPの20％に相当します。ここで、極端な貧困を防止するために本当に必要な支出額を計算してみましょう。そうすれば、皆さんも、このGDPの20％は貧困撲滅のためのものではなく、むしろ国家が横方向の所得再分配システムを通じて国民を捕らえ続けるためのものであると気づくでしょう。すなわち、国家はあなたからお金を取り、そのお金を自らの利益や必要に応じて配分するために、あなたと国家の間に割り込むのです。バストス教授が正しく指摘しているように、その所得の移動は、富裕層から貧困層へ、またはその逆ではなく、すべての人々から国家へ向かっているのです。そして国家は、その所得を自らの利益や必要に従って再分配することを決定します。

では、先ほど示したような形で国家の各機能を大幅に縮小した場合、結果として国家はGDPの9～10％程度の規模となり、現状よりも30～40ポイント、つまり約80％縮小された国家になるでしょう。防衛費、治安費は現状と同等に維持される（ただし、治安費については内部の官僚機構によっても左右されるため、この点はまた別の議論になります。たとえば、スペインはヨーロッパで国民一人あたりの治安部隊職員数が最も多い国ですが、本当にそれだけ必要なのかはまた別問題です）。安全保障費がGDPの1.7％、防衛費が1.3％、官僚組織が1％、地域サービスや環境保護が1％、民間部門ではまかなえないインフラがさらに1％、そして社会保障が3％という具合です。現在、社会保障としてGDPの3％、すなわち450億ユーロが支出されています。これは、450億ユーロの社会保障費を、例えば4.5百万人（スペイン人口のおよそ10％）に対して年間1人あたり1万ユーロずつ支給するか、あるいは300万人に対して1万5千ユーロずつ支給するということになります。繁栄した社会において、極端な無助状態に陥る国民の割合はどれほどか、という問題です。彼らは、生命保険、障害保険、個人貯蓄すら持たず、福祉国家が生まれる前に存在したボランティアや民間の相互扶助ネットワークさえも利用できなかった層です。これらを踏まえた上で、絶対的な無助状態に陥り、国家からの継続的な支援を必要とする国民の割合がたとえば5～10％だとすれば、実際に必要な支出はGDPの3～4％程度で十分にカバーできるはずです。しかし、現実には我々は社会保障にGDPの20％を費やしているのです。

明らかに、このGDPの20％は、富裕層から少しだけ富を奪って、巨大な貧困層を作らないためのものではありません。驚くべきことに、国家がGDPの50％を占めるにもかかわらず、貧困層は依然として存在しているのです。さらに、貧困を解消するための手段として、まず第一に、依存性を生む補助金を設けるべきではありません。しかし、現実には、経済活動が全くできず、自己の貯蓄や家族の支援、民間の相互扶助ネットワーク、そして最終的には国家に依存せざるを得ない層が一定割合存在します。しかし、そのようなケースはGDPの3％程度の支出で十分にカバーされるはずなのです。

さて、国家の規模を縮小した場合、たとえばGDPの50％から10％にまで削減できると仮定しましょう。これは約80％の削減に相当します。先に述べたように、中央値の労働者は現在、年間約13,500ユーロの税金を負担しています。この80％の削減が実現すれば、労働者の可処分所得は、国家が提供する各種サービスに充てるための支出分が年間1人あたり1万～1万1千ユーロ増加することになります。家庭内で中央値の労働者が2人いる場合、2万～2万2千ユーロの追加収入となるでしょう。この追加収入があれば、教育費、医療費、年金のための貯蓄など、国家が現在負担させているコストを自前でまかなうことが可能になるはずです。実際、多くのスペインの労働者は、国家の劣悪なサービスから逃れるため、民間の医療や教育、そして補完的な年金積立を実施しているのです。特に、公共教育は、学生の生産性向上よりも、国家のイデオロギーを植え付けることに重きを置いている場合が多いのです。

また、この話は、GDPの3％相当の再分配、すなわち450億ユーロ分が、現実的に考えても国民の基礎的な生活を支えるには十分であるという観点からも論じられます。現行の過剰な収用体制に対して、もし国家規模が大幅に縮小されるならば、労働者にとって有利な状況が実現するはずです。

さて、ここまでの議論から、もし国家主義のウイルスが社会の頭脳や利権に深く根付っている現状において、現状が最適でないと理解したとしても、移行のコストの高さゆえに多くの人々が現状から変わることを望まないという現実があるのです。たとえば、公共年金制度の解体は非常に困難です。年金受給者は「こんな不公平な体制であっても、自分の年金を受け取りたい。自分自身の貯蓄がなくなるリスクを冒したくはない」と考えるでしょう。

では、この国家――明らかに国家とその官僚機構に有利なこのモデル――から脱却するために、すなわち、表向きは国民のために存在するようでいて、実際には社会を寄生しているこの体制から逃れるためには、どのような手段が考えられるでしょうか。ここで、国家改革またはハイパーステートのパラサイト化に対抗するための、四つの可能なアプローチについて述べます。

第一のアプローチは、トップダウン型の方法です。すなわち、自由主義的な理念を掲げた善意の政治家が権力の座につき、内部からリベラル革命を起こそうとするというものです。しかし、私はこの方法は、次に述べるボトムアップ型の文化戦線と併せなければ、全体として非常に単純で実現不可能だと考えます。なぜなら、社会の大多数が国家改革を望まなければ、その改革は十分な勢いを持って実施されることは決してないからです。多くの改革は長期的な取り組みであり、一夜にして実現できるものではありません。一度実行された改革が元に戻らないようにするには、最低でも二世代を要するのです。もし社会がその方向に向かわなければ、いつかまた別の人物が権力に就いて、国民の大多数が望まない体制を再び打ち壊してしまうでしょう。例えば、チリの年金制度の民営化は、ピノチェト政権下の1981年に始まり、数年前に旧公共年金制度が完全に清算されました。しかし、その後、旧体制に戻そうとする動きが見られるのです。なお、チリは当時、非常に若い労働人口と限られた高齢人口という、改革に適した人口構造を有していたにもかかわらず、改革には約40年もの歳月がかかりました。これが、世界の他の国々で実施されるとなれば、どれほど困難なものになるか想像に難くありません。そして、もし世界中がそのような改革を望まなければ、いかに自由主義者の政治家を内部に潜り込ませ、社会民主主義の装いを与えたとしても、十分な効果は得られないでしょう。さらに、政治そのものが権力に触れると必ず腐敗すると、ロード・アクトンが指摘したように、権力は人を変えてしまいます。つまり、権力に惹かれて権力の座についた者は、その権力を維持・拡大するために、かつて掲げた理念を容易に放棄し、他者を蹂躙し、欺く行動に出るということです。

政治的競争というのは、もしあなたが行動しなければ、行動する者があなたを追い出してしまう、という状況を生み出します。そのため、もし存在するとしても、誠実で、信念を持った政治家は、力に屈する者に押されて公共の場から姿を消してしまうのです。権力闘争では、手が縛られている者と自由な手を持つ者との間で戦いが行われるため、劣悪な選択が働き、最終的には最悪の者が権力の座に就くという現象が生じるのです。（この点については、ハイエクも『隷属への道』で記述しています。）

次に、第二の可能性はボトムアップ、すなわち文化戦線によるアプローチです。これは、アイデアの戦いを、じわじわと、少しずつ社会に浸透させ、心を開かせ、意識を目覚めさせ、より多くの人々がこの変革を要求するようになるという方法です。しかし、これは特に有望な道ではないことは明白です。もし、ここでマルクス主義的な語調に傾くとすれば、客観的な物質的条件があって、そうした思想が大規模に広まる環境が整わない限り、人々は現状に満足して「今のままで十分だ」と感じ、急激な変革に乗り出す理由が見出せません。現状が著しく悪化しない限り、文化戦線による大規模な勝利が起こり、既存の社会制度が覆されるというのは極めて困難な道なのです。例えば、アルゼンチンでは、40年間にわたって底をつき続けた結果、人々が明らかに欠陥だらけのモデルにうんざりし、ハイパーインフレーションに苦しんだことで変革が進んだように見えます。もし、そこに一貫性があり、破壊的かつ斬新なメッセージ―社会主義的なものか、あるいは幸運にもリベラルなもの―があれば、一定の確率でそのアイデアが覇権を握り、新たな現状として定着する可能性が出てくるのです。しかし、スペインの場合、文化戦線による闘いは、相手側のプロパガンダがあふれ、対抗する者がいなければ、現状が一層固定化し、国家権力が加速度的に拡大していくため、非常に厳しい状況にあります。私自身も長い間、文化戦線で戦ってきましたが、スペインという環境におけるその限界を痛感しています。

第三の道は、そもそも国家改革を目指さず、自分の生活を改善するために他の地域へ移住するというものです。もし、競争が可能な複数の法域が存在すれば、現状に非常に不満を抱く者は、物理的に他の地域へ移り住み、そこで自らの生活基盤を築くことができます。そして、こうした法域間の競争は、他の法域による収用や寄生的な政策の力を制限する効果も持ちます。たとえば、ある法域で税率が非常に低く、規制が緩やかであれば、他の法域は資本が流出し、寄生者側から見れば、寄生対象（＝ホスト）が成長しなければ、寄生する意味がなくなるのです。もし、ホストを窒息させて殺してしまえば、またはホストが他の、寄生が少ない地域へ流出してしまえば、寄生者にとっては不利益となります。このような効果は、実際には見かけ以上に大きな影響を持つのです。

たとえば、最も身近な例として、アンドラの場合が挙げられます。多くの場合、静かに、あるいは時に華やかに報じられる移住現象があり、一定の社会的反響を呼んでいます。問題は、これらはすべて財政上の問題であり、移住者を犯罪者扱いする試みがあっても、スペイン国家にとっては重要な問題とならないのです。よく批判されるのは、YouTuberなどがアンドラへ移住することについて、「国が自国民の資源不足を訴えるような状況に直面しない」とされる点です。もしそうなれば、国家は財政の引き締めを迫られるはずですが、現実はそうではありません。むしろ、これは他者に対する懲罰の一形態であり、「移住して税負担を軽減しようとするなら、あなたは悪い人間であり、悪い市民だ。もしあなたが著名人であれば、意識を啓発するために、我々はあなたを徹底的に攻撃し、公の場から追放する」といったメッセージが発せられるのです。しかし、実際にアンドラへの移住が進むこと自体は悪いことではなく、たとえそれがスペイン国家に与えるダメージが短期的にはそれほど大きくなくとも、他のケースでは、目に見えにくいながらも国家に損害を与えている場合があるのです。

たとえば、2か月前に発表されたドラギの報告書では、欧州が「足を引きずっている」との根本的な不満が示されています。すなわち、欧州では生産性が20年間にわたって停滞しており、成長期に新たに設立される企業が、厳しい規制の下で成長できず、資本調達が困難となり、結果としてアメリカに流出してしまうという現象です。これは「足で投票する」という現象であり、企業側の実情を反映したものです。そして、これは国家権力の内部から出た、我々の社会が停滞しているという自らの寡占層からの認識でもあります。彼らは、ここ20年間にわたり市民を内部から圧迫してきた手法を見直す必要があると訴えているのです。そして、ここで議論されているのは、欧州連合とアメリカという二つの経済ブロック間での移住の問題なのです。

もし、かつてヨーロッパに存在していたような、多数の競合する法域が現在も存在していたと想像してみてください。ここで歴史的な議論に深入りするつもりはありませんが、ヨーロッパが16世紀あるいは17世紀から産業革命に至るまで発展し、東洋が（少なくとも最近まで）停滞していた理由の重い仮説の一つは、ヨーロッパが政治的にはるかに細分化され、都市国家や小国、王国、そして公国など、まさにアンドラのようなケースに近い形態であったため、相互の競争が激しかったという点にあります。ひとつの領域内で生まれる思想を制限・抑制・検閲する能力は非常に低く、もし一方で弾圧されれば別の場所へ移動できたため、その結果、後の産業革命を引き起こす知的な開花が促されたのです。これに対して、中国のような中央集権的で統一された国家では、官僚組織が本来より強大な権力を持っていたため、このような発展は見込めませんでした。

「足で投票する」という現象は非常に強力です。したがって、文化戦線から取り組むべきもう一つの課題は、政治的な中央集権化や財政の調和化に反対することです。なぜなら、政治的に中央集権化が進んだり、財政が調和化されるほど、法域間の競争は減少し、その結果、国家が無罰で私有財産を寄生的に吸い上げる余地が広がるからです。これは市場経済ではよく理解される現象ですが、国家の場合は例外扱いされがちです。市場において本当の意味での独占、すなわち単にその分野で唯一の企業という状況ではなく、競合が存在しない真の独占状態になると、その独占者は価格を引き上げ、品質を低下させる傾向にあります。なぜなら、あなたは逃げ出すことができない、まるで人質のような状態に置かれるからです。つまり、国家もまた独占状態にあり、国家が直面する唯一の競争は、他の国家へ移住するという可能性なのです。領域を統一して競争余地を狭めれば狭めるほど、国家は独占的な力を強め、結果としてあなたに提供するサービスの質を低下させ、収用を強める傾向が出てきます。したがって、私はどんな中央集権化のプロセスにも反対し、逆に政治的な分権化を支持すべきだと考えます。

そして最後に、第四の戦略ですが、これはやや曖昧で漠然としているかもしれません。しかし、私が考えるに、実際に多くの人々が採用しており、多くの場合国家の影響力を制限している方法、それは直接的に「国家からの分離」を目指すことです。もちろん、あなたにとって寄生者のような国家が窮屈に圧しかけてくる場合、その寄生者を打倒しようと多大なエネルギーを費やすこともできます。しかし、寄生者が既に存在する以上、その存在を前提として生活基盤を築く、その固定費を受け入れながらも、寄生者のさらなる拡大を防ぐ、あるいは寄生の及ばない領域を確保する新たな方法を模索するということです。これが国家からの「分離」、すなわち、重くのしかかる国家の負担から自らを切り離す試みなのです。例えば、先に述べたように、私立教育、私立医療、私的年金といった選択肢があります。本来であれば、国家が私たちから過剰な資源を吸い上げることなく、その分をこうした目的に振り向けられれば理想的ですが、幸いなことに、現状では国家が私立教育への進学を禁止しているわけではありません（ただしかなりの規制は存在します）。私立教育は完全に自由なものではなく、国家のカリキュラムに沿ったものですが、それでも私立教育、私立医療、そして貯蓄や資産形成の道を開いてくれるのです。もちろん、今後さらに税が引き上げられ、国内外で資産が収用されるリスクが高まるまではの話ですが。

したがって、国家を一つの悪と捉え、その悪に支配される中で自由を追求する、すなわちその影響力からできるだけ逃れる方法を探るべきです。さらに、社会が自ら開発していく様々なツールが、私たちが国家の監視や統制から離れて生活する手助けとなります。たとえば、デジタル経済は、今日のところ、国家が我々をコントロール・規制・収用するのをより困難にする領域をある程度確保できる可能性を秘めています。ビットコインの例は、没収不可能な資産として、適切な管理を行えば、富の保蔵庫あるいは国家の統制や知識から独立した交換手段として機能する可能性を示しています。

これらは、寄生者である国家に吸い付かれないため、自らの活動から国家の影響力を一部でも排除する、新たな生活の仕方を模索する一つの方法です。こうした新しいツールは、今後も次々と登場し、国家が私たちの生活に及ぼす影響を制限するために活用されるべきです。社会全体を変えるのは非常に困難ですが、多くの人々を同じ方向に動かすことが難しい現状において、少なくとも我々が体系的に受けている搾取の度合いを最小限に抑えることは可能です。

以上、複数の道筋があります。第一の道は私個人としてはほぼ排除したいと考えますが、残りの三つは排他的ではなく、互いに補完し合うものです。どの方法も目的地に必ず到達できる保証はありませんが、これらは連携することで、国家が私たちや社会全体に及ぼす権力の影響を徐々に抑制する助けとなるでしょう。そして、我々自身の利益のため、あるいは共に生きる社会を改善するために、可能な限りこれらの道を追求すべきだと考えます。

@ 220522c2:61e18cb4

npub1ygzj9skr9val9yqxkf67yf9jshtyhvvl0x76jp5er09nsc0p3j6qr260k2

@ 714dd0db:9c6f1a4c

やっと春が来ました

ようやく暖かくなってきた。 買い物から帰ってくると、なにやら甘い香り。

あ、もしかして、花の香りか！

探してみると、沈丁花が咲いている。

ああ、甘くていい香り。

近くには蝋梅も咲いている。我が家の近くに蝋梅があったなんて、すっかり忘れていた。

そして、早咲きの桜。桜のどの種類かは分からないのだが、毎年、ソメイヨシノよりも先に咲いている。

花の蜜を吸いに百舌鳥も来ている。いや、鳥の種類には疎いが、おそらく百舌鳥だろう。多分。

モノクロの冬から、ようやくカラフルな春になってきた。

季節を感じるのは、心が豊かになる。 今は今、今度は今度。 俺は今を生きている。

@ 8fb140b4:f948000c

As many of you know, https://nostr.build has recently launched a new compatibility layer for the Blossom protocol blossom.band. You can find all the details about what it supports and its limitations by visiting the URL.

I wanted to cover some of the technical details about how it works here. One key difference you may notice is that the service acts as a linker, redirecting requests for the media hash to the actual source of the media—specifically, the nostr.build URL. This allows us to maintain a unified CDN cache and ensure that your media is served as quickly as possible.

Another difference is that each uploaded media/blob is served under its own subdomain (e.g., npub1[...].blossom.band), ensuring that your association with the blob is controlled by you. If you decide to delete the media for any reason, we ensure that the link is broken, even if someone else has duplicated it using the same hash.

To comply with the Blossom protocol, we also link the same hash under the main (apex) domain (blossom.band) and collect all associations under it. This ensures that Blossom clients can fetch media based on users’ Blossom server settings. If you are the sole owner of the hash and there are no duplicates, deleting the media removes the link from the main domain as well.

Lastly, in line with our mission to protect users’ privacy, we reject any media that contains private metadata (such as GPS coordinates, user comments, or camera serial numbers) or strip it if you use the /media/ endpoint for upload.

As always, your feedback is welcome and appreciated. Thank you!

@ 4bcc0228:299141d7

GeminiのDeep Researchiで今日の昼ご飯に良いレシピを調べてもらった。

プロンプトはこんな感じ。

今日のお昼ご飯に何が適しているか調査してください。

要望として以下のものがあります。

・麺類が良い

・自宅で調理可能なものが良い

・自宅にはパスタの乾麺とそうめんがある

・パスタソース等はない

・自宅近くにコンビニがあるので、最悪そこで調達することは可能だが、できる限り避けたい

---

今日のお昼ご飯、お家にある麺で簡単レシピ

はじめに：悩ましいお昼ご飯を、手軽な麺料理で解決！

毎日のお昼ご飯、何にしようか悩みますよね。特に時間がない時や、わざわざ買い物に行くのが面倒な時、お家にあるものでパッと美味しいものが作れたら最高です。このレポートでは、そんなあなたのために、ご自宅にある乾麺のパスタとそうめんを使った、簡単で美味しいお昼ご飯のアイデアをご紹介します。パスタソースがなくても大丈夫！特別な材料がなくても、身近な調味料で本格的な味わいが楽しめます。パスタもそうめんも、アレンジ次第で様々な表情を見せてくれる万能な食材です。このレポートを読めば、きっと今日のお昼ご飯の悩みが解消され、手軽で満足できる一品が見つかるはずです。

パスタの力：ソースなしでも美味しい、簡単パスタレシピ

パスタといえば、お店で食べるような本格的なソースがないと美味しくないと思っていませんか？実は、ご家庭にある調味料を工夫するだけで、簡単に絶品パスタが作れるんです。ここでは、特別な材料は使わず、あなたのキッチンにあるかもしれないもので作れる、とっておきのパスタレシピをご紹介します。

ごま油香る！和風にんにくパスタ

いつものパスタに、ちょっと意外な和の風味を加えてみませんか？ごま油とにんにくの香りが食欲をそそる、簡単なのに本格的な味わいの和風パスタです。1
作り方

1. にんにく1かけをみじん切りにします。鍋にお湯を沸かし、スパゲティ80gを表示時間より1分短く茹で、水気を切ります。茹で汁を大さじ2ほど取っておきましょう。
2. フライパンにごま油大さじ1を入れ、中火で熱します。にんにくから香りが立ったらスパゲティを加え、取っておいた茹で汁と3倍濃縮めんつゆ大さじ1を加えて混ぜ合わせます。
3. 塩こしょう少々で味を調えたら完成です。

このレシピのポイントは、何と言ってもごま油の香ばしさ。加熱することで風味が引き立ち、食欲をそそります。また、めんつゆのうま味がパスタ全体に広がり、シンプルながらも奥深い味わいに仕上がります。茹で汁を加えることで、麺と調味料がよくなじみ、一体感のある美味しさになります。普段とは違うパスタを試してみたい時におすすめです。
アレンジ：お好みで、ラー油を少し加えてピリ辛にしたり、乾燥パセリや刻みのりを散らして風味をプラスするのもおすすめです。

バター醤油のシンプルパスタ

材料はシンプルなのに、なぜか後を引く美味しさ。バターと醤油の組み合わせは、まさに魔法です。2
作り方

1. 鍋に湯を沸かし、塩（分量外）を少々入れ、スパゲティ100gを半分に折って袋の表示時間通りに茹でます。茹で汁を大さじ2ほど取り分け、スパゲティは水気を切ります。
2. フライパンをさっと洗い、有塩バター10gを入れて中火で熱します。バターが溶けたらスパゲティ、取り分けた茹で汁、醤油小さじ2を加えて炒め合わせます。
3. 器に盛り付け、お好みで刻みのりを散らしたら完成です。

バターのコクと醤油の香ばしさが絶妙にマッチした、シンプルながらも奥深い味わいのパスタです。茹で汁を加えることで、パサつきを防ぎ、しっとりとした仕上がりになります。刻みのりの風味がアクセントになり、食欲をそそります。忙しいけれど美味しいものが食べたい、そんな時におすすめの一品です。お弁当にもぴったりですよ。
アレンジ：仕上げに粗挽き黒胡椒を振ると、味が引き締まります。

電子レンジで簡単！ツナとガーリックのオイルパスタ風

火を使わずに、電子レンジでパパッと作れるお手軽パスタです。3
作り方

1. 耐熱ボウルに早ゆでスパゲッティ（1.6mm）100gを半分に折って入れ、シーチキンマイルド1缶（油を切らずに）、水適量（パスタが浸る程度）、おろしにんにく少々を加えます。ラップをせずに600Wの電子レンジで7分加熱します。
2. 加熱後、めんつゆ大さじ1、オリーブ油小さじ1、バター5gを混ぜ合わせ、醤油少々、こしょう少々で味を調えます。
3. 器に盛り付け、お好みで粉チーズ、黒こしょうをかけたら完成です。

電子レンジで麺を茹でることで、時短になり、洗い物も少なく済むのが嬉しいポイントです。ツナの旨味とニンニクの風味が食欲をそそり、めんつゆとバターのコクが絶妙なハーモニーを生み出します。忙しいけれど手軽に済ませたいランチに最適です。
アレンジ：加熱前に、冷凍のミックスベジタブルなどを加えても彩り豊かになります。

シンプル is ベスト！オイルとニンニクの基本パスタ

材料はシンプルながらも、素材の味が際立つ奥深い味わいのパスタです。4
作り方

1. にんにく1かけを薄切りにします。お好みで赤唐辛子を少量用意します（輪切りでも種を取り除いたものでも）。鍋にお湯を沸かし、スパゲティ80gを表示時間より少し短く茹でます。茹で汁を大さじ2ほど取っておきます。
2. フライパンにオリーブオイル大さじ2を入れ、弱火で熱します。にんにくを加え、焦がさないようにじっくりと炒めます。にんにくが薄く色づき、香りが立ったら、お好みで赤唐辛子を加えます。
3. 茹で上がったスパゲティをフライパンに加え、取っておいた茹で汁を加えてよく混ぜ合わせます。塩、こしょうで味を調えたら完成です。お好みで刻みパセリを散らします。

このパスタの美味しさの秘訣は、じっくりと炒めたにんにくの香りと、良質なオリーブオイルの風味です。シンプルだからこそ、素材の味がダイレクトに伝わります。茹で汁を加えることで、オイルと麺が乳化し、より一体感のある仕上がりになります。
アレンジ：ベーコンやきのこなどを加えても美味しくいただけます。また、仕上げに粉チーズを振ると、コクが増します。

そうめんの魅力：軽やかで爽やかなランチアイデア

暑い日や、あっさりとしたものが食べたい時にぴったりのそうめん。いつものめんつゆで食べるのも美味しいですが、少しアレンジを加えるだけで、全く違う味わいが楽しめます。ここでは、簡単にできるそうめんのアレンジレシピをご紹介します。

定番の美味しさ！シンプルめんつゆでいただくそうめん

まずは基本から。そうめん本来の美味しさを味わう、シンプルながらも飽きのこない食べ方です。10
作り方

1. 鍋にたっぷりの湯を沸かし、そうめん1束（約80～100g）を入れ、表示時間通りに茹でます。
2. 茹で上がったそうめんをザルにあげ、流水でよく洗い、ぬめりを取り除きます。しっかりと水気を切って器に盛り付けます。
3. 市販のめんつゆを用意し、お好みでネギやミョウガ、大葉などの薬味を添えていただきます。

冷たくてつるつるとしたそうめんは、食欲がない時でも食べやすく、暑い季節には特に美味しく感じられます。めんつゆの優しい味わいと、薬味の爽やかな香りが食欲をそそります。
アレンジ：めんつゆに、すりおろし生姜やラー油、ごま油などを加えると、風味豊かな味わいに変わります。15

ちょっとアレンジ！簡単そうめんバリエーション

いつものそうめんに、ちょっとした工夫を加えるだけで、様々な味が楽しめます。

• ごま油香る塩そうめん 10：茹でたそうめんにごま油と塩を和えるだけで、風味豊かな一品に。お好みでネギや白ごまを加えても美味しいです。
• トマトとツナのそうめん 11：茹でて冷やしたそうめんに、ツナ缶とカットしたトマトを乗せ、めんつゆをかけるだけ。大葉や刻みのりを添えると、さらに美味しくなります。
• 釜玉風そうめん 10：熱々の茹でたてのそうめんに、生卵と醤油（またはめんつゆ）を絡めるだけ。お好みでネギやかつお節を添えて。
• 韓国風ピリ辛そうめん 10：茹でて冷やしたそうめんに、きゅうりやキムチを乗せ、コチュジャンやごま油を加えたピリ辛のタレをかけます。
• バター醤油そうめん 12：茹でて水気を切ったそうめんに、バターと醤油を絡めるだけ。シンプルながらも後引く味わいです。

これらのアレンジは、どれも手軽にできるものばかり。冷蔵庫にあるものや、ちょっとした調味料を加えるだけで、普段のそうめんが大変身します。

温かくいただく！あったかそうめんレシピ

そうめんは冷たいイメージがありますが、温かくしても美味しくいただけます。

• かきたまにゅうめん 12：だし汁を温め、茹でたそうめんを入れ、溶き卵を流し入れてさっと煮れば完成。優しい味わいで、寒い日にもぴったりです。
• わかめスープそうめん 12：市販のわかめスープに茹でたそうめんを入れるだけで、手軽な一品に。ごま油を少し加えると風味がアップします。
• 親子にゅうめん 19：だし汁で鶏肉と玉ねぎを煮て、茹でたそうめんを加え、溶き卵でとじます。栄養も満点で、満足感のある一品です。

温かいそうめんは、冷たいそうめんとはまた違った優しい味わいが楽しめます。体調が優れない時や、ほっこり温まりたい時におすすめです。

いざという時のコンビニ頼み：ちょい足し食材でさらに美味しく

できる限り避けたいとのことでしたが、もし少しだけ何かプラスしたいと思った時のために、コンビニで手軽に手に入るおすすめ食材をご紹介します。

• にんにく：チューブタイプでも、カットされたものでも。パスタの風味を格段にアップできます。
• ラー油：ピリ辛好きにはたまらない。そうめんやパスタに少し加えるだけで、味が引き締まります。
• ツナ缶・鮭フレーク：手軽にタンパク質をプラスできます。パスタにもそうめんにも合います。
• 卵：パスタのトッピングにしたり、釜玉風そうめんにしたり。栄養も満点です。
• ネギ：刻みネギが便利。そうめんやパスタの薬味に。
• めんつゆ：もし自宅にない場合は、コンビニで手軽に購入できます。そうめんの基本としてあると便利です。
• バター：パスタやそうめんにコクをプラスできます。
• 醤油：バター醤油パスタや、そうめんの味付けに。

これらの食材は、少量から購入できるので、必要な時に少しだけ買い足すことができます。

結論：今日のお昼ご飯は、お家にある麺で決まり！

このレポートでは、ご自宅にある乾麺のパスタとそうめんを使った、簡単で美味しいお昼ご飯のアイデアをいくつかご紹介しました。特別なソースや材料がなくても、工夫次第で様々な美味しい麺料理が楽しめます。パスタは、ごま油やバター醤油でシンプルに、また電子レンジを使えばさらに手軽に調理できます。そうめんは、定番のめんつゆでいただくのはもちろん、ちょっとしたアレンジを加えるだけで、飽きずに楽しむことができます。温かくしていただくのもおすすめです。
今日のお昼ご飯、何にしようか迷ったら、ぜひこのレポートでご紹介したレシピを参考に、お家にある麺で美味しい一品を作ってみてください。きっと、手軽さと美味しさに満足できるはずです。

| レシピ名 | 主な材料 | アレンジ例 | 調理方法 | 参照元 | | :---- | :---- | :---- | :---- | :---- | | ごま油香る！和風にんにくパスタ | スパゲティ、にんにく、ごま油、めんつゆ | ラー油、刻みのり | 炒め | 1 | | バター醤油のシンプルパスタ | スパゲティ、バター、醤油 | 黒胡椒 | 炒め | 2 | | 電子レンジで簡単！ツナとガーリックのオイルパスタ風 | スパゲティ、ツナ、にんにく、めんつゆ、オリーブ油、バター | 冷凍野菜 | 電子レンジ | 3 | | シンプル is ベスト！オイルとニンニクの基本パスタ | スパゲティ、にんにく、オリーブ油 | 赤唐辛子、ベーコン、きのこ | 炒め | 4 |

| レシピ名 | 主な味付け | 主な材料 | 参照元 | | :---- | :---- | :---- | :---- | | シンプルめんつゆそうめん | めんつゆ | そうめん | 10-13-18 | | ごま油香る塩そうめん | ごま油、塩 | そうめん | 10 | | トマトとツナのそうめん | めんつゆ | そうめん、トマト、ツナ | 11 | | 釜玉風そうめん | 醤油またはめんつゆ | そうめん、卵 | 10 | | 温玉そうめん（にゅうめん） | だし汁、醤油、みりん | そうめん、卵 | 12 | | バター醤油そうめん | バター、醤油 | そうめん | 12 |

引用文献

1. ごま油がポイント！ にんにく風味の和風パスタのレシピ動画 ..., 3月 14, 2025にアクセス、 https://delishkitchen.tv/recipes/167590676693778924
2. 簡単！ 具なしバター醤油パスタのレシピ動画・作り方 | デリッシュ ..., 3月 14, 2025にアクセス、 https://delishkitchen.tv/recipes/525069302701752674
3. 包丁なし簡単 ツナ缶油ごと使って作るやみつきパスタ | セブンプレミアム公式, 3月 14, 2025にアクセス、 https://7premium.jp/recipe/search/detail?id=9949
4. 材料は…たったこれだけ！？超簡単なのに絶品な「シンプルパスタ」レシピ帖 | キナリノ, 3月 14, 2025にアクセス、 https://kinarino.jp/cat4/33954
5. 【作り置き】材料５つだけ！簡単ペペロンチーノソース - macaroni, 3月 14, 2025にアクセス、 https://macaro-ni.jp/53793
6. にんにく香る！簡単に作れる基本のペペロンチーノの作り方 | デ ..., 3月 14, 2025にアクセス、 https://delishkitchen.tv/recipes/171524636704506348
7. 簡単・本格・失敗なし！ペペロンチーノ基本のレシピ - Nadia, 3月 14, 2025にアクセス、 https://oceans-nadia.com/user/253470/recipe/440736
8. 【乳化の極意を解説】にんにく香る本格ペペロンチーノレシピ。プロの技で旨みたっぷり！ | 三越伊勢丹の食メディア | FOODIE（フーディー）, 3月 14, 2025にアクセス、 https://mi-journey.jp/foodie/77708/
9. すぐにできる！ 具なしペペロンチーノのレシピ動画・作り方 | デリッシュキッチン, 3月 14, 2025にアクセス、 https://delishkitchen.tv/recipes/301564582369953005
10. 毎日食べても飽きない【そうめん】レシピ20選！余ったそうめんの ..., 3月 14, 2025にアクセス、 https://www.kurashiru.com/articles/336924d1-3266-4050-bc51-e79a6383400f
11. 【そうめん】アレンジ人気レシピ45選！15分以内で簡単 - Nadia, 3月 14, 2025にアクセス、 https://oceans-nadia.com/user/10022/article/3242
12. 子どもも喜ぶ そうめんを使った人気のレシピ20選の人気レシピ ..., 3月 14, 2025にアクセス、 https://delishkitchen.tv/curations/9367
13. アレンジそうめんの簡単レシピ・人気料理 1位～20位, 3月 14, 2025にアクセス、 https://recipe.rakuten.co.jp/category/16-154-918/simple/
14. もうゆでない！絶品そうめん作り方！火を使わず簡単 つゆもレンジにおまかせ つゆのアレンジも紹介しています - YouTube, 3月 14, 2025にアクセス、 https://m.youtube.com/watch?v=LyChkGwtH4A\&pp=ygUiI-OCsOODqeOCueOCseODvOOCrTEwMOWdh-WFpeOCjOeJqQ%3D%3D
15. そうめんつゆの基本＆アレンジレシピ16選！人気のおすすめちょい足しも - マカロニ, 3月 14, 2025にアクセス、 https://macaro-ni.jp/32748
16. そうめん＆つゆのアレンジレシピ20選を一挙ご紹介！ - デリッシュキッチン, 3月 14, 2025にアクセス、 https://delishkitchen.tv/articles/1048
17. めんつゆレシピをご紹介！料理にめんつゆ｜だし・かつお節のヤマキ, 3月 14, 2025にアクセス、 https://www.yamaki.co.jp/mentsuyu/recipe/
18. めんつゆを使った簡単アレンジレシピ！基本の料理から「かえし」を使ったレシピも紹介, 3月 14, 2025にアクセス、 https://www.sobahonda.co.jp/blog/mentsuyu_arrange/
19. 【そうめん】定番からアレンジまで 激旨な人気レシピランキング (全332品) - デリッシュキッチン, 3月 14, 2025にアクセス、 https://delishkitchen.tv/categories/3058
20. 【アレンジ自在！そうめんレシピ】バラエティ豊かな人気レシピ70選 - デリッシュキッチン, 3月 14, 2025にアクセス、 https://delishkitchen.tv/curations/7216

@ 75869cfa:76819987

GM, Nostriches!

The Nostr Review is a biweekly newsletter focused on Nostr statistics, protocol updates, exciting programs, the long-form content ecosystem, and key events happening in the Nostr-verse. If you’re interested, join me in covering updates from the Nostr ecosystem!

Quick review:

In the past two weeks, Nostr statistics indicate over 228,000 daily trusted pubkey events. The number of new users has seen a notable increase, with profiles with a contact list amounting to 17 times the same period. More than 11 million events have been published, with posts and reposts showing an increase. Total Zap activity stands at approximately 13 million, marking a 22% decrease.

Additionally, 28 pull requests were submitted to the Nostr protocol, with 5 merged. A total of 45 Nostr projects were tracked, with 11 releasing product updates, and over 462 long-form articles were published, 26% focusing on Bitcoin and Nostr. During this period, 2 notable events took place, and 1 significant events is upcoming.

Nostr Statistics

Based on user activity, the total daily trusted pubkeys writing events is about 228,000, representing a slight 8.7% decrease compared to the previous period. Daily activity peaked at 18256 events, with a low of approximately 16087.

The number of new users has increased significantly. Profiles with a contact list are now around 393,637, a 17-fold increase. Pubkeys writing events have declined to approximately 227,635, but have still grown by 14%. Profiles with a bio are now 9 times the previous number.

Regarding event publishing, the total number of note events published is about 11 million. Posts remain the most dominant in terms of volume, totaling approximately 1.7 million, reflecting an increase of 6.8%. Reposts are showing a increase of approximately 12%, while reactions have experienced a 8% decline.

For zap activity, the total zap amount is about 13 million, showing a decrease of over 22% compared to the previous period.

Data source: https://stats.nostr.band/

NIPs

nip99 e-commerce use case extension

nostr:npub1gmmrkec8een5jelrxq5rz260nqzpnj45yzznpaerqv0yma3s86gqpfe2h0 is proposing nip99 e-commerce use case extension. This pull request simply adds a link to the specification we are developing and have consensus on, allowing other developers who want to implement NIP-99 for e-commerce to discover how the major developers are approaching it. In this way, we ensure that NIP-99 remains lightweight and allows for broad use cases while also providing guidance for the e-commerce use case that is currently prevalent.

add "global" relay lists

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 is proposing "global" relay lists that streamlines the b/c process by standardizing it across multiple apps and also by allowing these lists to be shared, so when the relays that were hardcoded (and that were, at the time of the hardcoding, known to be such public squares) get shut down then clients can automatically or manually switch to new ones.

[NIP 53 Addendum] - Add Interactive Rooms, Meetings, and Live Presence.

nostr:npub18pudjhdhhp2v8gxnkttt00um729nv93tuepjda2jrwn3eua5tf5s80a699 is proposing that add Interactive Rooms and Meetings, and Live presence to NIP-53. Kind 30312 (Interactive Rooms), Kind 30313 (Meetings), Kind 10312 (Room Presence). These Kinds would apply to interactive audio/video platforms such as Hivetalk version 2.0 (not public yet) and Nostr Nests.

NIP-5E: Censorship Resistant Live Streams

v0l is proposing a way to distribute live video streams via Nostr. "Live Video" in this context implies segmented video streams like HLS or DASH. Each segment of the stream is a NIP-94 event which describes where the file can be found and its hash.

Add birth field to NIP-24 for birth date representation

nostr:npub12egp0pvh2f0fp6sk5nt6ncehqzkz8zsma8dl8agf8p3f98v6resqku4w26 is proposing a PR that introduces the birth field to NIP-24, allowing users to specify their birth date. The goal is to enable applications to celebrate users' birthdays and allow other users to notice and join in the celebration, enhancing social interactions.Defined the format as [day, month, year (optional)]. The year is optional to accommodate users who prefer not to disclose their age.

NIP-05: add dynamic server recommendation

nostr:npub1q3sle0kvfsehgsuexttt3ugjd8xdklxfwwkh559wxckmzddywnws6cd26p is proposing NIP-05 services who let people sign up for a NIP-05 name are recommended to make the names unique case insensitive.

Add delegation to nip 46

Staab is proposing PR that adds a delegation command to NIP 46, which allows applications that are already authorized to create new sessions with limited permissions. My use case for this is sharing a read-only session with push- or email- notification servers, which can only sign kind 22242 events on behalf of the user, in order to get access to auth-gated relays.

Add notifiers nip

Staab updates NIP: XXX - Push Notifiation with the following differences: It uses parameterized replaceable events, which allows for multiple subscriptions to exist at the same time；It uses NIP 44 encryption rather than NIP 04；It uses filters rather than ad-hoc targets；It uses delegated authentication in order to gain access to gated relays；It uses a different mechanism for pausing notifications and auto-expiring pauses.

NIP-22: Format should follow scope

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z is proposing This adds some flexibility in formatting styles for NIP-22. Since this NIP is always used inside a scope (another NIP), formatting rules SHOULD be defined by that NIP. Examples: If the Comment is replying to a markdown-based NIP, it should allow markdown. If the Comment is replying to an asciidoc-based NIP, it should allow asciidoc.

NIP-34!: use NIP-22 thread style for patch and status events

nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr created this as part of reviewing #1744. For the status event, references to merged patch events are done using the q tag even though the they are not included in content. This is because NIP-22 only supports the use of e reference for the parent event id.

NIP90: Add Ping/Pong to DVMs

believethehype introduces kind 7007 (ping) to send a small request to a dvm to check if it is alive. The DVM replies with a kind 7000 feedback event and status pong, and optional information in content. This allows clients to test if a dvm is alive without sending an actual job request to the dvm.

Notable Projects

Coracle 0.6.5 nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn

New maintenance release of Coracle is out: * Fix memory leak * Fix isEventMuted * Fix toast animation * Fix (and improve) drafts * Fix parser dropping sections of notes

Primal nostr:npub12vkcxr0luzwp8e673v29eqjhrr7p9vqq8asav85swaepclllj09sylpugg

Primal for iOS build 2.1.26 has just been released. Here’s what’s new: * Improved feeds * Deep linking threads, articles, profiles * Bug fixes & stability improvements

Yakihonne nostr:npub1yzvxlwp7wawed5vgefwfmugvumtp8c8t0etk3g8sky4n0ndvyxesnxrf8q

web v4.4.0： * Zap polls can now be added directly from the list or created instantly within notes and comments. * Muting users is now more reliable. * Users can download and export their NWC secret for wallets. * Wallets and account credentials are automatically saved upon signup and logout. * Faster login and signup when interacting with Yakihonne while logged out. * Bug fixes and performance optimizations for improved reliability.

mobile v1.6.6: * Ability to export your NWC wallets and your keys. * Blink wallet is now available as one of the external wallets that can be used. * Private messages drafts are now available. * Notes stats optimised. * Wallet management overall performance has been improved. * Fixing bugs and improving the overall performance

GOSSIP nostr:npub189j8y280mhezlp98ecmdzydn0r8970g4hpqpx3u9tcztynywfczqqr3tg8

Several major bugs have been fixed in the last week. * PRIVACY: gossip was authenticating to relays in many cases even if you turned on "require user approval before AUTHenticating..." * Gossip was rendering nevent links as note1 links in some cases * When clicking the parent link, sometimes it wasn't finding the parent note (even though the note you clicked correctly hinted at which relay the note was at) * New users who adjusted settings during the first run were having their public key wiped, which appeared to have no identity and they had to regenerate on second run

nos.social nostr:npub1pu3vqm4vzqpxsnhuc684dp2qaq6z69sf65yte4p39spcucv5lzmqswtfch

With the Nos 1.2 update, you can use Nos to create, edit, and delete lists of your favorite people and accounts! We're also bringing you fixes for the biggest issues in the previous version: * Fixed: restarting app reverts to Following rather than selected list or relay * Fixed: lists change positions randomly * Fixed: adding and removing relays is not reflected in the feed filter * Fixed: text fields sometimes don't work on onboarding screens * Fixed: main action button is not visible on iPad on "Build Your Network" onboarding screen * Fixed: crash when processing a malformed delete event

Fountain 1.1.17 nostr:npub1v5ufyh4lkeslgxxcclg8f0hzazhaw7rsrhvfquxzm2fk64c72hps45n0v5

• In this update, we completely rebuilt the authentication flows as some users reported issues accessing the app. We're currently building out the redesigned library and content pages along with updates to transcripts.

Plebeian Market nostr:npub1market6g3zl4mxwx5ugw56hfg0f7dy7jnnw8t380788mvdyrnwuqgep7hd

• Social Sharing: New social sharing buttons have been implemented, allowing users to share listings and pages effortlessly across social platforms.
• Open Graph Integration: Enhanced sharing capabilities with the addition of an Open Graph library, making it easier to share listings on social media.
• Pagination on Mobile: Now see up to 20 items before you need to paginate, making browsing smoother and more efficient on your mobile device.
• UX/UI Overhaul: Significant improvements to the UX and UI of the Settings and Dashboard for a more intuitive navigation.
• Dashboard Enhancements: Various fixes to ensure the dashboard is more functional and user-friendly.
• Relays Pop-Out: Improved UI so the Relays pop-out no longer goes underneath the category menu on the homepage and other pages.
• Save Button: A 'Save' button has been added to every page for quick and easy updates to your listings or settings.
• Payment Details Clarity: Examples are now included in the 'Payment Details' field to guide sellers on what information to provide.
• And fixes some bugs.

DEG Mods nostr:npub17jl3ldd6305rnacvwvchx03snauqsg4nz8mruq0emj9thdpglr2sst825x

• The ability to switch between reply and quote-replies
• Preview the recent posts of an author under their profile box when viewing a mod or blog they've published
• Clicking on images in a feed post triggers the gallery system for it
• Adjusted the design of images and videos that appear in the feed page
• Reposting won't trigger a popup
• Textarea in feed page will reset its size after posting, along with preview reset
• Load new posts button now works/appears properly
• Reply depth numbering now works correctly
• User LN address now updates correctly if they change it (was a caching issue)

Zapstore 0.2.5 nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8

• Hopefully fixed the missing apps issue
• No more toast showing Zapstore update available (pinned instead)
• Trigger local version refresh on app detail page

futr nostr nostr:npub18wxf0t5jsmcpy57ylzx595twskx8eyj382lj7wp9rtlhzdg5hnnqvt4xra

• Optimized Subscription Handling
• Implemented proper event pagination with timestamp tracking.
• Added event deduplication across batches.
• Improved debug logging for pagination and subscription events.
• Fixed timestamp handling to prevent future-dated events.
• Reduced events per pubkey from 2000 to 500 for better efficiency.
• Relay Connection & Event Parsing
• Improved relay connection state management.
• Fixed parsing of OK messages from relays.
• Updated follow list and DM relay parsing.
• Added proper nevent links for quoted reposts.
• Increased connection timeout from 3s to 15s to enhance reliability.
• UI & UX Enhancements
• Fixed follow list flickering by improving model caching.
• Improved login experience with better async timing.
• Fixed profile filter issues to improve data consistency.
• And another changes.

ZEUS v0.10.0 nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5

• Receive: add advanced settings toggle
• Remove deprecated backends
• Move sweep on-chain functionality to Tools view
• Update colors according to themes in external link modal
• Improve contrast of warning buttons in Disaster Recovery view
• Bug fix: display of backup status
• Bug fix: ZEUS Pay local notifications
• Renewable channels
• NWC client support
• Embedded LND: v0.18.5-beta
• New share button (share ZEUS QR images)
• Activity: highlight filter icon when filters active
• chantools: sweepremoteclosed
• Tools: Export Activity CSVs, Developer tools
• Activity: filter by max amount, memo + note
• CLNRest: add payment timeout setting

Long-Form Content Eco

In the past two weeks, more than 462 long-form articles have been published, including over 79 articles on Bitcoin and more than 42 related to Nostr, accounting for 26% of the total content.

These articles about Nostr mainly explore its potential as a decentralized, censorship-resistant communication protocol, contrasting it with traditional social media platforms like Facebook and X. They discuss Nostr’s ability to foster free speech, privacy, and security while providing a foundation for new applications, including encrypted messaging (such as the use of the Double Ratchet Algorithm in NIP-117 and NIP-118), decentralized identity management, and anonymous event relaying (as proposed in "Renoters"). Several pieces, including "The Advancement of the Nostr Protocol," highlight recent technical advancements, developer tools like Nostr SDK, and practical use cases for Bitcoin applications. Others, criticize centralized platforms for their control over user data and content moderation policies. Additionally, topics like relay setup, voting systems, and AI alignment with human values are explored, emphasizing Nostr’s broader applications beyond social media.

These Bitcoin articles explore adoption, investment strategies, security, privacy, and their impact on global finance. Many highlight Bitcoin’s role in fostering financial resilience in Zimbabwe, rural economies, and the importance of user adoption over merchant adoption. Investment discussions cover DCA strategies, ETF influence, and ways to maximize returns. Privacy and security topics emphasize decentralization, self-custody, and best practices to protect assets. Bitcoin is framed as an alternative to fiat, with critiques of traditional finance and central banking. Geopolitical discussions examine the IMF’s influence, France’s fiscal crisis, and El Salvador’s Bitcoin policy. Technical innovations, such as EVM integration, Lightning Network advancements, and multi-payment solutions, continue to expand the Bitcoin ecosystem, driving broader adoption and usability.

Thank you, nostr:npub1m0sxqk5uwvtjhtt4yw3j0v3k6402fd35aq8832gp8kmer78atvkq9vgcru nostr:npub13rvvn5g23anm09kwnya8qvzqejxfajfa56rnn47ck5l96ke6cq4sdcd4e0 nostr:npub10m6lrv2kaf08a8um0plhj5dj6yqlw7qxzeag6393z352zrs0e5nsr2tff3 nostr:npub17v7g49shev2lwp0uwrx5v88ad6hj970zfse74wkes9jguhkx7aqsgjwsvj nostr:npub18lav8fkgt8424rxamvk8qq4xuy9n8mltjtgztv2w44hc5tt9vets0hcfsz nostr:npub1nlk894teh248w2heuu0x8z6jjg2hyxkwdc8cxgrjtm9lnamlskcsghjm9c nostr:npub1xzuej94pvqzwy0ynemeq6phct96wjpplaz9urd7y2q8ck0xxu0lqartaqn nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk nostr:npub16dswlmzpcys0axfm8kvysclaqhl5zv20ueurrygpnnm7k9ys0d0s2v653f nostr:npub1x7zk9nfqsjwuuwm5mpdu8eevsnu2kk0ff23fv58p45d50fhuvaeszg44p2 nostr:npub1mwce4c8qa2zn9zw9f372syrc9dsnqmyy3jkcmpqkzaze0slj94dqu6nmwy and others, for your work. Enriching Nostr’s long-form content ecosystem is crucial.

Nostriches Global Meet Ups

Recently, several Nostr events have been hosted in different countries. * The Bitcoin Freedom Festival took place from February 20 to 24, 2025, at the Awakening Center in Uvita, Costa Rica. In collaboration with the Awake Earth Festival, the event blended a music festival with Bitcoin seminars and lectures. From February 20 to 23, it featured music, healing workshops, ceremonies, and educational talks, with internationally renowned artists and captivating discussions. February 24 was a special day dedicated to Bitcoin, with all activities centered around it. nostr:npub14f26g7dddy6dpltc70da3pg4e5w2p4apzzqjuugnsr2ema6e3y6s2xv7lu * The 5th Bitcoin Educators Unconference, organized by Mi Primer Bitcoin, was successfully held on February 27, 2025, at Bitcoin Park in Nashville, USA. The event focused on grassroots projects and Bitcoin education, adopting a decentralized, community-led format. Every participant was a potential speaker, proposing discussion topics at the beginning of the event, which were then grouped into breakout sessions for in-depth discussions. nostr:npub17cyatz6z2dzcw6xehtcm9z45m76lde5smxdmyasvs00r4pqv863qrs4ml3

Here is the upcoming Nostr event that you might want to check out.

• The Bitcoin Educators Unconference will take place on April 10, 2025, at Bitcoin Park in Nashville, USA. The event follows a decentralized, community-led format, with a focus on Bitcoin education and independent Bitcoin educators. It aims to foster collaboration and networking among Bitcoin educators, creating a truly interactive space.

Additionally, We warmly invite event organizers who have held recent activities to reach out to us so we can work together to promote the prosperity and development of the Nostr ecosystem.

Thanks for reading! If there’s anything I missed, feel free to reach out and help improve the completeness and accuracy of my coverage.

@ 6b9da920:7841cc6e

Here is a simple chart for developers to understand when to "Nostr Native" and when to "Nostr Integrated"

Definition:

Nostr Native: Uses relays as the only network layer and storage layer and business logic is 99%+ client side.

Nostr Integrated: Has in-house solutions and only connects partially to Nostr.

Both categories could be open sourced or close sourced.

| Features | Benefit From Network Effect | Don't benefit from Network Effect | | --- | --- | --- | | Contribute To Network Effect | All in Nostr Native | Recommend Writing to Nostr | | Harm Network Effect| Don't Write to Nostr and could read from Nostr | Should be in-house solution and not write to Nostr |

Category 1

If we think we should be all-in Nostr Native no matter what (like 99%+), we are limiting ourselves to only features that both benefit from Nostr and contribute to Nostr. This is a totally valid proposition as long as developers are consciously aware that they are indeed making a product within this category.

Pretty much all public facing social features fall into this category.

But, there are many products that need features that fall into other 3 categories.

Category 2

For features that benefit from Nostr but harms it, you are basically stealing data from Nostr without contributing back. My advice to is not write to Nostr at all and only read from Nostr if you have to do it, but you should minimize this product design in general.

Pretty much any massivly bot/batch job/pipeline generated data fall into this category. Machine generated data do not necessarily mean spam data. In the data engineering & machine learning world, it's very common to generate intermediate data in data pipelines for downstream analytics. This kind of data is huge and can also be purely textual. Don't write to Nostr relays.

Category 3

Is it even possible to have features that don't benefit from the network effect of Nostr and can contribute to it?

I can't think of any. But if it exists, consider writing to Nostr even if you don't use relays as the primary storage.

Category 4

These are features that don't benefit from Nostr and also harm Nostr if writing to it.

Slack style internal organization communication falls into this category. In fact, we want to actively prevent these features from having network effects because having these data in an open network might reduce their security.

Writing them to Nostr also harms the network because these data, encrypted or not, only have semantic meaning within the organization. Posting them to Nostr reduces the overall signal(value) density of the network.

Outtro

It is very common and almost inevitable for a single product to have both lots of category 1 and lots of category 4 and some % of category 2 & 3.

Using this chart, you will know how to make wise engineering decisions that help your product design instead of harming it and help the network at the same time.

@ e70d313e:573808ed

Kevin F. Boehnke, Assistant Professor of Anesthesiology, University of Michigan for The Conversation

The U.S. Drug Enforcement Agency announced in late April 2024 that it plans to ease federal restrictions on cannabis, reclassifying it from a Schedule I drug to the less restricted Schedule III, which includes drugs such as Tylenol with codeine, testosterone and other anabolic steroids. This historic shift signals an acknowledgment of the promising medicinal value of cannabis.

The move comes in tandem with growing interest in the use of psilocybin, the active component in magic mushrooms, for treatment of depression, chronic pain and other conditions. In 2018 and 2019, the U.S. Food and Drug Administration granted a breakthrough therapy designation to psilocybin, meant to expedite drug development given that preliminary studies suggest it may have substantial therapeutic value over currently available therapies for treatment-resistant depression and major depressive disorder.

Both of these developments represent a dramatic change from long-standing federal policy around these substances that has historically criminalized their use and blocked or delayed research efforts into their therapeutic potential.

As an assistant professor of anesthesiology and a pain researcher, I study alternative pain management options, including cannabis and psychedelics.

I also have a personal stake in improving chronic pain treatment: In early 2009 I was diagnosed with fibromyalgia, a condition characterized by widespread pain throughout the body, sleep disturbances and generalized sensory sensitivity.

I see cannabis and psilocybin as promising therapies that can contribute to bridging that need. Given that an estimated 50 million Americans have chronic pain – meaning pain that persists for three months or more – I want to help understand how to effectively use cannabis and psilocybin as potential tools for pain management.

Cannabis versus other pain medications

Cannabis, also known as marijuana, is an ancient medicinal plant. Cannabis-based medicines have been used for at least 5,000 years for applications such as arthritis and pain control during and after surgery.

This use extended through antiquity to modern times, with contemporary cannabis-based medications for treating certain seizure disorders, promoting weight gain for HIV/AIDS-related anorexia and treating nausea during chemotherapy.

As with anything you put in your body, cannabis does have health risks: Driving while high may increase risk of accidents. Some people develop cyclical vomiting, while others develop motivation or dependence problems, especially with heavy use at younger ages.

That said, lethal overdoses from cannabis are almost unheard of. This is remarkable considering that nearly 50 million Americans use it each year.

In contrast, opioids, which are often prescribed for chronic pain, have contributed to hundreds of thousands of overdose deaths over the past few decades. Even common pain medications like nonsteroidal anti-inflammatory drugs, such as ibuprofen, cause tens of thousands of hospitalizations and thousands of deaths each year from gastrointestinal damage.

Furthermore, both opioids and nonopioid pain medications have limited effectiveness for treating chronic pain. Medications used for chronic pain can provide small to moderate pain relief in some people, but many ultimately cause side effects that outweigh any gains.

These safety issues and limited benefit have led many people with chronic pain to try cannabis as a chronic pain treatment alternative. Indeed, in survey studies, my colleagues and I show that people substituted cannabis for pain medications often because cannabis had fewer negative side effects.

However, more rigorous research on cannabis for chronic pain is needed. So far, clinical trials – considered the gold standard – have been short in length and focused on small numbers of people. What’s more, my colleagues and I have shown that these studies employ medications and dosing regimes that are far different from how consumers actually use products from state-licensed cannabis dispensaries. Cannabis also causes recognizable effects such as euphoria, altered perceptions and thinking differently, so it is difficult to conduct double-blind studies.

Despite these challenges, a group of cannabis and pain specialists published a proposed guideline for clinical practice in early 2024 to synthesize existing evidence and help guide clinical practice. This guideline recommended that cannabis products be used when pain is coupled with sleep problems, muscle spasticity and anxiety. These multiple benefits mean that cannabis could potentially help people avoid taking a separate medication for each symptom.

Traditional hurdles to studying cannabis

Since the Controlled Substance Act was passed in 1970, the federal government has designated cannabis as a Schedule I substance, along with other drugs such as heroin and LSD. Possession of these drugs is criminalized, and under the federal definition they have “no currently accepted medical use, with a high potential for abuse.” Because of this designation and the limits placed on drug manufacturing, cannabis is very difficult to study.

State and federal regulatory barriers also delay or prevent studies from being approved and conducted. For example, I can purchase cannabis from state-licensed dispensaries in my hometown of Ann Arbor, Michigan. As a scientist, however, it is very challenging to legally test whether these products help pain.

Reclassifying cannabis as a Schedule III drug has the potential to substantially open up this research landscape and help overcome these barriers.

The emerging role of psychedelics

Psychedelics, such as psilocybin-containing mushrooms, occupy an eerily similar scientific and political landscape as cannabis. Used for thousands of years for ceremonial and healing purposes, psilocybin is also classified as a Schedule I drug. It can cause substantial changes in sensory perception, mood and sense of self that can lead to therapeutic benefits. And, like cannabis, psilocybin has minimal risk of lethal overdose.

Clinical trials combining psilocybin with psychotherapy in the weeks before and after taking the drug report substantial improvements in symptoms of psychiatric conditions such as treatment-resistant depression and alcohol use disorder.

Risks are typically psychological. A small number of people report suicidal thoughts or self-harm behaviors after taking psilocybin. Some also experience heightened openness and vulnerability, which can be exploited by therapists and lead to abuse.

There are few published clinical trials of psilocybin therapy for chronic pain, although many are ongoing, including a pilot study for fibromyalgia conducted by our team at the University of Michigan. This treatment may help people develop a healthier relationship with their pain by eliciting greater acceptance of it and decreasing rumination often related to negative thoughts and feelings around pain.

As with cannabis, some states, such as Colorado and Oregon, have decriminalized psilocybin and are building infrastructure to increase accessibility to psilocybin-assisted therapy. One recent analysis suggests that if psychedelics follow a similar legalization pattern to cannabis, the majority of states will legalize psychedelics between 2034 and 2037.

Challenges ahead

These ancient yet relatively “new” treatments offer a unique glimpse into the messy intersection of drugs, medicine and society. The justifiable excitement about cannabis and psilocybin has led to state policies that have increased access for some people, yet federal criminalization and substantial barriers to scientific investigation remain. In the years ahead, I hope to contribute toward pragmatic studies that work within these difficult parameters.

For example, our team developed a coaching intervention to help veterans use commercially available cannabis products to more effectively treat their pain. Coaches emphasize how judicious use can minimize side effects while maximizing benefits. Should our approach work, health care providers and cannabis dispensaries everywhere could use this treatment to help clients in chronic pain.

Approaches like these can supplement more traditional clinical trials to help researchers determine whether these drug classes offer benefit and whether they have comparable or less harm than current treatments. As our society connects to the rich history of healing using these ancient drugs, these proposed changes may offer safer and substantive options for the 50 million Americans living with chronic pain.

This article is from The Conversation, a nonprofit news organization dedicated to sharing knowledge with the public.

Kevin F. Boehnke receives funding from the National Institutes of Health, the State of Michigan Veteran Marijuana Research Program, and has received grants from Tryp Therapeutics and Journey Biosciences. He is affiliated with Doctors for Drug Policy Reform as an unpaid expert. He also has received honoraria for speaking at conferences as well as for participating in a podcast on fibromyalgia from the European Medical Journal funded by Viatris Inc.

@ 97c70a44:ad98e322

#lastword

A few weeks ago, Mike proposed the addition of a feature to nostr. The content of the proposal itself isn't important, but the resulting conversation illustrated something important about nostr development that I wanted to draw attention to.

If you're interested, you can find the issue here. The idea was basically a tag that disabled comments to a reply, for when you wanted to gracefully exit a conversation that had outlived its usefulness.

While I definitely sympathize with the experience of getting stuck in an unproductive argument and being unable to leave because you have to have the last word, I do think it's better to take responsibility for leaving the conversation, rather than make other people do it for you. You can either outlast your opponent, let them have the last word, or tell them "I don't want to talk about this any more, I'm not going to reply".

This is just my opinion, and it's really not important whether I'm right or not. What was interesting was how Vitor responded:

I am not sure if the NIP review process should consider "what's good for the user" in the discussion. That kind of nanny state thinking is what went wrong with regular social media in the first place.

Permaculture and Ethics

What it sounds like (although I have a hard time believing this is actually his position), is that Vitor is dismissing the relevance of an ethical framework in designing a protocol, preferring to stick to the mechanics of what is being suggested. As Vitor says, "Clients can do whatever they want, of course." This is true, but ignores the question of why a client developer might want to do any particular thing.

In a recent Thank God for Nostr episode, I interviewed Scott Mann of the Permaculture Podcast. When I asked him his opinion on how to manage decentralized protocol design and build effective consensus, here's what he had to say:

[You] don't need to frame it as a software development project, or even a protocol. I would look at it as a distributed community-based and community-supported project, whatever that is. Because permaculture is such a large umbrella, I like to go up to that 50,000 foot view and pull away from what the details are. Because the details are what we're going to build our solutions from.

And that's one of the things I didn't mention earlier — there's kind of a hierarchy within permaculture that goes, at the top are the ethics of permaculture: earth care, people care, fair share. Beneath that are the principles, then usually we have strategies and techniques.

But there's a dividing line between ethics and principles and the strategies and techniques, that we start at that top, and use the ethics to decide whether or not we're even going to launch a project.

He goes on to say:

I'm going to use the principles and see how can I apply those principles to my research and original design. To make sure that whatever I'm creating creates some kind of a surplus, to have a refinement process in place before I even launch, like what is that going to look like, even if I have to change it later, just having some of these building blocks in place.

And then once I've done that and have gone deep into my research into what this might look like, how I might launch it, that's where I would start going into strategies and going ok, how do I want to market this? How do I want to get this out to the people who are going to use it, how do I want to maintain this, how do I want to do distributed decision making, and then as I start to think about distributed decision making, looking at what is the form that I want to use for that?

Scott's thesis is that ethics and principles should be in the front of your mind both as you're considering a project, and as you continue to build it out. This not only makes sense as something to do if you want to succeed, it's categorically true. Action can't happen without agency, and it is your agency that informs what you choose to do, and how you plan to go about it.

The word "ethics" comes from the Greek ēthos, meaning "moral character". In other words, your ethic is who you are. Your values, hopes, preferences, faults all factor in to your actions.

This is not always clear, because in fiat-world, many people suspend their values in order to "get something done". If you want to protect your savings, you invest it in index funds, propping up the stock price of companies that hate you. If you want to make money, you go work at a job where you're berated quarterly for being racist. People think that they can exercise their own values in their private life, while actively undermining those values with the majority of their time and purchasing power.

But this is not how people with integrity act. And I think if you can say one thing about nostr — both its developers and the community at large — is that they have a very high level of integrity. In other words, their actions are clearly informed by their ēthos.

This is a very good thing. What is the point of building an entirely new internet if we're not going to impose our values upon it? What an absolute waste of effort.

A Nostr Manifesto

This is not to say that any one developer has the right to imposing his own vision on the protocol because of his own personal values and reasons for contributing, which is what I think Vitor was being cautious about. But there are lines I think we can draw as a community that can't really be crossed without excluding yourself from what I might call the "nostr group ethic".

So what are those boundaries? What is a nostrich? Here are some values I've observed to be generally shared among nostr developers and users. Not everyone would full agree with these (including myself), but I think they're a fair characterization of the community.

1. Free speech absolutism. No central entity should be able to globally censor any content. This comes with the trade-off of objectively evil content continuing to exist. This trade-off is acceptable, both because of the value of free speech, but also because evil will continue to exist regardless of attempts to suppress it.
2. Empower individuals over institutions. No centralized entity can be trusted to safeguard the interests of the individual. Institutional incentives are asymmetric and easily corrupted. Better to have many subjective views of the world, than a single, centrally managed view of the world.
3. Advertising-based business models should be viewed with great skepticism and caution. Advertising is a system of incentives that is central to the institutional corruption we see around us. Broadly, this includes paid ads, monetization of engagement, public/private partnerships, and "crypto".

There are others that are shared by many within nostr, although not as widely agreed upon. Two I can think of are:

• Economic activity should be voluntary. Software and content should be free, and creators should be amply rewarded via zaps or other value-for-value models.
• Social media should support real life community and relationships, not detract from them. We should all take time to touch grass.

I'm personally skeptical of the first of these, and strongly in support of the second. Much of my energy as a nostr developer has gone into attempting to subvert and reform traditional patterns of social media to not only support, but also resemble relationships that exist in the analog world God made, and placed us in.

This particular principle is the one at play in the conversation I linked to at the top of this post. My comments weren't an accusation that anyone was acting "unethically" in a universal sense, only that the proposed feature was incompatible with my vision for what nostr should be.

But of course, my vision is not shared by everyone, and the principle of "support real life" is clearly subservient to core ethic #2, which admits the value of a diverse set of opinions about the world. I have no right (or ability) to invalidate anyone else's core principles. But by the same token I'm free to express my own, and attempt to convince other people to share them. This is the basic value proposition of freedom of speech itself.

Ethical Cohesion

I would go further, and say that not only is it permissible to talk about ethical reasons for building one thing or another on nostr, it's essential. By having these conversations we fuse our individual ethics into a shared ethic. By calibrating our moral compasses to point in (roughly) the same direction, we also decrease the friction involved in getting something done.

I think this was a significant part of the idea behind Sovereign Engineering — get a bunch of people in a room together sharing meals and going on hikes, and the work will accelerate! This is also the way a church works. By meeting weekly together we strengthen our shared identity and build one another up through our activity. In fact, this is the basic definition of a community as Scott Mann puts it. In his words, a community can provide:

a series of connections, and a knowledge base, and a skillset that we can't fulfill as an individual, while having a social relationship with people in such a way that we can call on them for help.

So maybe, as I've said before, the real protocol is the friends we made along the way. Disagreement and discussion is a healthy thing for a community to have, and we should never stop asking "why?"

@ 266815e0:6cd408a5

Lot of people are starting to talk about building a web-of-trust and how nostr can or is already being used as such

We all know about using the kind:3 following lists as a simple WoT that can be used to filter out spam. but as we all know it does not really signal "trust", its mostly just "I find your content interesting"

But what about real "trust"... well its kind of multi-denominational, I could trust that your a good developer or a good journalist but still not trust you enough to invite you over to my house. There are some interesting and clever solutions proposed for quantifying "trust" in a digital sense but I'm not going to get into that here. I want to talk about something that I have not see anyone discuss yet.

How is the web-of-trust maintained? or more precisely how do you expect users to update the digital representation of the "trust" of other users?

Its all well and good to think of how a user would create that "trust" of another user when discovering them for the first time. They would click the "follow" button, or maybe even rate them on a few topics with a 1/5 star system But how will a user remove that trust? how will they update it if things change and they trust them less?

If our goal is to model "trust" in a digital sense then we NEED a way for the data to stay up-to-date and as accurate as possible. otherwise whats the use? If we don't have a friction-less way to update or remove the digital representation of "trust" then we will end up with a WoT that continuously grows and everyone is rated 10/10

In the case of nostr kind:3 following lists. its pretty easy to see how these would get updated. If someone posts something I dislike or I notice I'm getting board of their content. then I just unfollow them. An important part here is that I'm not thinking "I should update my trust score of this user" but instead "I'm no longer interested, I don't want to see this anymore"

But that is probably the easiest "trust" to update. because most of us on social media spend some time curating our feed and we are used to doing it. But what about the more obscure "trust" scores? whats the regular mechanism by which a user would update the "honestly" score of another user?

In the real world its easy, when I stop trusting someone I simply stop associating with them. there isn't any button or switch I need to update. I simply don't talk to them anymore, its friction-less But in the digital realm I would have to remove or update that trust. in other words its an action I need to take instead of an action I'm not doing. and actions take energy.

So how do we reflect something in the digital world that takes no-energy and is almost subconscious in the real world?

TLDR; webs-of-trust are not just about scoring other users once. you must keep the score up-to-date

@ 97c70a44:ad98e322

I think there's been an inflection point recently in NIPs that are being proposed. Some examples:

• Products with pubkeys: https://github.com/nostr-protocol/nips/pull/1225
• Shared-ownership events: https://github.com/nostr-protocol/nips/pull/1192 and https://github.com/nostr-protocol/nips/pull/1015
• Spreadsheets: https://github.com/nostr-protocol/nips/pull/1189
• Relational databases: https://github.com/nostr-protocol/nips/pull/1168
• Relay-specific notes: https://github.com/nostr-protocol/nips/pull/1146
• Editable notes: https://github.com/nostr-protocol/nips/pull/1090
• Restricted events: https://github.com/nostr-protocol/nips/pull/1083
• Relay-based access control: https://github.com/nostr-protocol/nips/pull/1030
• Protected events: https://github.com/nostr-protocol/nips/pull/1029
• Closed groups: https://github.com/nostr-protocol/nips/pull/875

Some of these I like, some I don't. But most of them go beyond adding new features to nostr (for example audio, video, speedruns, resumes, etc), and begin to change how nostr actually works.

Nostr can be an everything app, but I think that means something very specific. Nostr can represent data types from pretty much any domain, but it can't actually support all the semantics needed to build any arbitrary system.

I would suggest conservatism in what we build on nostr, but of course anyone can build whatever they want. But I do think it's possible to identify things that nostr is good at, and things it's bad at, and play to nostr's strengths.

Nostr's strengths:

• Being able to model any data type orthogonally to the rest
• Single-owner, self-authenticating, atomic data types
• Potential for robust content dispersal and retrieval if we can flesh out NIP 65 etc.

Nostr's weaknesses:

• Mutable state, non-atomic state
• Shared ownership, key delegation/rotation
• Privacy — metadata will always leak, lack of consistency makes key rotation harder
• Consistency — not everyone has the same view of the world
• Transactionality — nostr isn't good for updating multiple pieces of data in lockstep

It happens that the original use case of nostr — public broadcast social media — benefits greatly from nostr's strengths, and isn't bothered by any of nostr's weaknesses. Blob storage like what blossom is building also works well in this paradigm. A lot of the use cases @PABLOF7z​ has identified work beautifully well because of the single-owner public-read nature of nostr, which makes forks easy to model.

But things like access control, relational data, collaborative document creation, heavier datasets, or anything that requires a solution to the double-spend problem become very awkward (or impossible) to model on pure nostr. A simple example of this is lists. Not only is it common for a single user to mess up his follow lists because of a lack of consistency between clients or devices, but commonly requested features like shared ownership lists immediately result in a huge increase of complexity, either on the key management side or on the data structure side. Both of these problems are difficult to solve on nostr due to lack of consistency — keys can't always be reliably or safely shared, and linked data structures spanning multiple events by different authors can be hard to assemble reliably.

I think the danger here is that if we as a developer community fail to realize the limitations of nostr and try to adapt the protocol to fit every possible use case, on an ad-hoc basis, we're going to end up with a tragedy of the commons, where no developer can comprehend what must be done to get his work done, and all kinds of weird artifacts appear for end users that no one can explain.

Here are some suggestions I have for preventing this from happening. I realize no one is going to follow them. But maybe they can be helpful for avoidance of wasted time.

• Don't overload event kinds. Many people (including myself) have tried to extend kind 0 with attributes for forms, products, and groups, but that leads to madness. Instead, create a new metadata event signifying a different kind of agent.
• Don't model things as replaceable events if you can avoid it. This creates the problem of shared mutable state, which nostr doesn't have a good story for resolving. They also have a hard limit on how big they can be.
• Use different keys for different things. For domains where some kind of access control needs to be implemented, not tying everything to your main pubkey makes it possible to create and burn keys as needed. Incidentally, this can help users maintain better privacy. An example of this is private groups, which have a dedicated key separate from the group creator's own key.
• Event ownership should always be (is) single-key. If you need shared ownership, figure out a way to share keys. More work needs to go into key invalidation and rotation for this to really work.
• Explore the fork model — this is "my" version of the same thing, and coexists with rather than supersedes the original. This has potential not just for groups or wiki entries.
• Distinguish between different ways to use relays. Relays may be used as indexers (holding specific event types or supporting different features like search/count), repositories (holding many diverse events, to be used with filters), or curated feeds (to be used without filters, or with only a few filters).

These are just suggestions, and many of them may be wrong. Nostr development is hard, and getting harder. Keep it simple.

@ 6ad3e2a3:c90b7740

I remember reading a while back about how Omega 6 fatty acids found in seed oils (soybean, sunflower, corn, vegetable, etc.) promote inflammation while Omega 3s like the kind found in wild salmon or grass-fed beef reduce it. Of course, both are essential. If you were unable to produce inflammation, then you might bleed to death from a cut, rather than having it clot into a scab.

The problem was the proportion we consume of each has changed drastically over time. Our ancestors apparently had somewhere between 3:1 and 1:1 Omega 6 to Omega 3, while the standard American diet has between 30:1 and 10:1. That’s a lot of excess inflammation.

And it’s no surprise then that most of our modern diseases are inflammatory in nature — diabetes, cancer, auto-immune disease, heart attacks and strokes are all diseases of a body that’s too inflamed, hyper-responsive, over-sugared, clotting internally. Few people die of too little blood sugar anymore, at least in the calorie-abundant West.

. . .

I listened to a Jocko Willink podcast a few years ago wherein he told the story of a soldier who survived years in a Vietnamese prison camp. The takeaway was that while he was ardently optimistic about his ultimate fate, he remained steadfastly agnostic about the particulars. He said the soldiers who were sure they’d be home for Christmas, for example, were always the first to break when Christmas came and went.

The key was to be generally optimistic only. Think of it as the difference between someone who thinks God will help him pick the right lottery numbers vs one who believes whatever happens to him is in his best interests because God only provides exactly what he needs to learn. The latter is probably going to make it, the former not so much. . . .

The phenomenon of hyper-inflammation is not restricted only to the alimentary diet and the physical body. We are overstimulated by information too. In particular, the amount of threatening news we consume from all over the world is far in excess of what we’ve evolved to process. As such, despite being physically more secure than ever before, we’re in a state of chronic mental inflammation. There’s a word for chronic mental inflammation: “anxiety.”

. . .

I used to think I could overcome fears and other negative emotions by imagining the undesirable outcomes in detail and allowing myself to become okay with them. For example, if someone said something negative about me, I thought I could go over the slight repeatedly and in detail and have it not bother me one bit. But I came to realize the thinking of the slight was itself the being bothered by it. I couldn’t both think I had gotten over it and really get over it. I had to choose to think about it and not be over it, or not to think about it and actually get over it. I couldn’t have it both ways.

. . .

Even if you see through the fears endlessly promulgated by legacy institutions: climate change, terrorism, covid, the unvaccinated, Trump, Putin, the insurrectionists!, you are tuned into a new set of anxieties: CBDCs, the WEF, the WHO, GMOs, mRNA mandates, the impending collapse of the financial system. I’ve come to realize lately that even being aware of all the so-called real threats is also mentally inflammatory.

. . .

If being agnostic as to specific positive outcomes was the key to survival in the prison camp, perhaps it follows one should be agnostic as to negative ones too. While it’s easy to see the folly in the poor, tortured soldier clinging to the hope of being home for Christmas, it’s harder to see it in the anxious housewife fretting over the lives for her children in the face of near-certain climate doom. But it’s essentially the same error — being overly certain about the future outcome on which the hope or fear rests.

The alternative is to be on guard generally about threats of ruin, but agnostic about the specifics. It could be a car crash, a heart attack, a nuclear war, financial collapse, virus or dystopian new world order. You can read the signs, but you never really know. What makes the future the future is precisely this quality. You can protect yourself generally by taking care of your health to the best of your ability, putting your finances on solid ground to the greatest extent practicable and, it might turn out, decreasing your exposure to an information diet that leads to chronic inflammation of mind.

. . .

In the information age, there is a fine line between head-in-the-sand denial of real threats and inflammatory paranoia, one the new media (social algorithms) are designed to make ever more difficult to walk. You need the capacity to defend yourself against acute threats, to clot the cut so to speak when they arise, and yet chronic inflammation will kill you if you try to stay on high alert for every potential attack vector.

You have to choose, it seems, between being prepared generally, trusting yourself to face unknowable threats with the best acute response you can muster, and being specifically armed in advance, at the cost of making yourself sick.

There is no guarantee you survive, but that was ever the case, no matter your preparations.

@ 955e5a04:c03b3cc3

"If the things that cause you unease or disturb your peace don't come to you, but you, in a certain way, go to them, remaining unmoved, then judgment must cease warring against them. And thus, you will no longer desire them nor flee from them henceforth." –Marco Aurelio

"In this meditation, Marco Aurelio reflects on how our emotional reactions are influenced by our desires and aversions, rather than external circumstances.

Here's an interpretation for each line, based on all the principles applied in Stoicism and his Meditations, this is in the 11th book:

"If the things that cause you unease or disturb your peace don't come to you": Marco Aurelio points out that the things that cause us emotional distress don't actively pursue us, but it's our own reactions to them that create that distress. "But rather, you, in a certain way, go to them, remaining unmoved": Suggests that it's us who, in some way, seek out those disturbing emotions, even when external circumstances remain unchanged. "Therefore judgment must cease warring against them": Here, Marco Aurelio advocates for ceasing to fight against those disturbing emotions with the power of judgment or reason. Instead of resisting them, he suggests we should accept them as part of our human experience. "And thus, you will no longer desire them nor flee from them henceforth": By freeing ourselves from the struggle against those emotions, we cease to desire or fear them in the future. By accepting them peacefully, we lose interest in them and no longer actively pursue or avoid them."

Embrace inner strength. Master reactions. Find peace. That's the true path to empowerment and serenity.

@ 76c71aae:3e29cafa

Why are there 5.5 million people with Bluesky accounts and about 800k to 1.3M on Nostr?

Some of it boils down to social dynamics and chance. It's akin to how immigrants often cluster in the same neighborhoods. Most people are simply following their communities, and their primary decision is driven by where their community is heading.

Why did the communities choose Bluesky over Nostr, Mastodon, Farcaster, or the several dozen centralized and decentralized alternatives?

That’s a more pertinent question. Firstly, very few people actually make these decisions, and most simply follow them. Secondly, the choices aren't primarily based on the technology or the features of the apps or protocols.

Bluesky had certain advantages and disadvantages. It received a fair amount of press as a Twitter spinoff. However, it was late to launch, only preceded by Threads, which had Meta’s platforms for promotion.

In terms of initial marketing, I’d say Bluesky and Nostr were about equal, both often pitched as a ‘Jack Dorsey thing’, which wasn’t true in either case. The press loves stories about people and drama over networks and systems. Social media is vast and complex, and its technology even more so, which is why it’s often presented through personalized narratives about the creators.

Under the hood, Bluesky’s atproto and Nostr are very similar technologically. Both were inspired by Secure Scuttlebutt. Bluesky has adopted a cathedral model of open source, akin to how Android is open source but controlled by Google. Meanwhile, Nostr developed under the bazaar model of open source, created by a community rather than a company.

This company model gives Bluesky some advantages; for instance, they could launch with an invite list, a classic tactic to make something feel more desirable. Even then, most Bluesky users haven’t posted a single thing, and when they had a million registered users, they had fewer than 1500 Daily Active Users (DAU) see bluesky stats.

Bluesky is a lot easier to try than Nostr. The ways keys and content signing work in Bluesky and Nostr are overwhelmingly similar, except that Nostr doesn’t tell you where to store your keys and in Bluesky, you put them on your PDS server, which Bluesky provided free by default for all new users.

This means for Nostr, you have to figure out what to do with your nsec and npub, then how to get a nip-05 for a Nostr name which makes sense. If you want to log in with a username and password, you need to find and set up a nip-46 service. Not all apps support that, so you’re copying and pasting around an nsec. If you want to use a web app, you need to go find and choose one of several browser extensions and set that up. This is easy and natural for folks with experience in crypto but really foreign for everyone else.

Maybe a million people have figured out how to get started on Nostr; it’s definitely possible. And some apps like Primal and Nos have integrated name services as part of the signup, which makes it cleaner.

Once you’re on Nostr, people often discuss zaps, a functionality that may not work as expected. You’ve got to learn how to set up a wallet, what lightning and Bitcoin are. Some get really into it, we’ve seen folks get into Bitcoin through Nostr, but for many, it’s a confusing hurdle.

Bluesky provides a neat way to get into a single default app and gives you a username. Sure, you can change it—I self-host my DID at rabble.nz—but apparently less than 1% of Bluesky users do that, just like most Nostr users have chosen to use a cloud service for their nip-05 Nostr name.

Why else has Bluesky grown bigger than Nostr? It's their approach to positioning the protocol. They’ve set up default moderation controls and a trust and safety team. Initially, they didn’t have these, and when users demanded action and the company refused, growth stalled and usage dropped last July. The Bluesky team didn’t post for about a month, and there was a real question about whether Bluesky would survive.

The user community wanted pretty heavy-handed moderation. The Bluesky team was committed to building a decentralized protocol that didn’t do that. The compromise was that Bluesky would be slow about opening up open federation over atproto until the Bluesky apps, protocol, and company-hosted services could have a trust and safety team and a moderation bot. Their moderation bot is fancier than @reportinator, but it’s the same idea, but with a bigger team of humans reviewing reports. And if you’re using the Bluesky-provided PDS, there’s no way to block or unfollow their default moderation bot. We don’t make everybody on Nostr follow nostr:npub14h23jzlyvumks4rvrz6ktk36dxfyru8qdf679k7q8uvxv0gm0vnsyqe2sh .

That compromise worked for the community and company, and the user base started growing again. The negative press about Bluesky's content ceased and those upset by the policies left, some migrating to Nostr. Bluesky was able to position itself as the socially responsible social media protocol that was easy to use. Jack deleted his Bluesky account, signaling to the world and press what we already knew: he is much more interested in Nostr’s approach to bottom-up development by community and support for lightning payments.

During this period, Nostr's growth really stalled. There are a few reasons for this. We'd saturated the community of folks who both love Bitcoin and dislike Elon enough to leave Twitter. Additionally, our new user experience pushed people to view a global feed dominated by a single topic of conversation.

Nostr has positioned itself strongly as a protocol for those who are freedom-loving, anti-censorship Bitcoin enthusiasts. The easiest Nostr client for new users, Primal, markets itself as a Bitcoin wallet first, and only secondarily as a social media app. People view Nostr as a Web3 project. We’ve had individuals visit the Nos.social website and decline involvement, saying they dislike Web3 because they perceive it as a planet-harming scam (let's not argue the carbon emissions of mining here). We never mention Web3 or any cryptocurrency elements on the Nos website, yet all decentralization has been associated with dubious schemes.

As Nostr’s growth has stalled, the ecosystem has matured and flourished. Nostr boasts technology and apps that other platforms envy. I often hear Bluesky and Fediverse developers express admiration for the cool things Nostr is doing with technology and apps, but since their communities don’t use it, they don’t either.

Just look at the articles my posts last week about Nostr vs. ActivityPub kicked off: Extending ActivityPub and Nomadic Identity is Coming to ActivityPub

I suspect what’s holding back Nostr is twofold. First, how we talk about Nostr. We discuss it in political and ideological terms—we're against censorship, for free speech, value-for-value, etc.—but not about the types of content and people on Nostr, how to find your friends, or the interesting stuff you followed elsewhere. Nor do we talk about how you can use all these cool apps with the same identity and content. It's a hard concept to grasp, and I find myself constantly having to explain it.

The biggest issue people see with Nostr is its perceived association with Bitcoin enthusiasts plus those who’ve been deplatformed elsewhere, often for contentious reasons. I’m not saying the deplatforming was justified, but the perception among those unfamiliar with arbitrary bans and sanctions on platforms is that those who've been deplatformed had it coming—that they were all conspiracy theorists, bigots, or harassers. Some were, some were not, but it's perceived that way by many.

The way we talk about Nostr and onboard new users doesn’t help. The goal of the creator and journalism projects we just launched was to both diversify the content on Nostr for new users and to demonstrate to those creators and journalists that micropayments and paid content on Nostr are viable alternatives/additions to how they publish on social media elsewhere. It is value-for-value without the label, because our theory is that people want the functionality but aren't so keen on the cultural ideology.

This is all solvable. We can: - Make it easier to set up a nip-05 for new users. - Ensure that nip-05 also functions as an nsec bunker for easy login, if users desire. - Add Webfinger files so your nip-05 name functions as a Fediverse name (it’s pretty easy to do; we're experimenting with it on nos.social). - Show users a variety of content types when they join. - Help users find communities, perhaps encouraging groups/channels the way Farcaster does. - Make it easy to find and choose moderation settings, offering more middleware services like Reportinator but with different content labeling ideas. - Change our marketing to attract these new users, focusing on what they can see and who they can connect with, less on Bitcoin, technology, or evading censorship. - Develop apps that offer new functionalities, drawing people in instead of being mere clones with or without certain features.

It always takes a long time for people to figure out what the native mediums are on a technology platform. Initially people would make a phone call to listen to a concert, the first radio stations had people just reading the newspaper, and the first tv broadcasts were either a camera pointed at radio announcers or a single camera shot of a play. People always do the same things, we're the same humans that evolved a couple hundred thousand years ago, same brains, same bodies. What's changed is the way we do things with technology, so what fundamental human thing can we do new and different now that we've got these social protocols and tech?

Addressing the app design and technology will help, but actual growth will come when people discover us, join, find connections, and genuinely want to invite others to join them. Nostr users are incredibly welcoming to new users. However, we also have a subset of users who engage in sexist, racist, and homophobic harassment. This harassment drives people away from Nostr and deters them from recommending it to others. If we don't provide better tools for users to protect themselves from this harassment, they'll leave and find social spaces where they feel safe. Some might abandon public social media altogether, or just switch to Bluesky, which promises to eventually open up their network and has just announced support for uploading images, coming soon.

We're way ahead of the other protocols in some areas and way behind in others. We've got enough momentum and users to figure this out, but we're not there yet.

@ 6b9da920:7841cc6e

When I was a corporate programmer, I never had the chance to directly work with designers because I was a backend developer and more importantly, individual contributors usually have no sayings on what designers should be. Usually, the project manager discusses with designers and decides what should be done and we as programmers just receive the decisions.

In this context, programmers are not treated as engineers because real engineers have to influence the design.

I have the chance to work on designs and with designers for the first time in my life since I started Nostr last year. It has been a huge learning journey for me.

---

At first, I simply saw UI designers as some kind of painter that drew the shapes I want as the product creator. I have worked with several different designers to come up with UIs or graphics in a side gig, ad-hoc way, either paid or as a community effort.

I need to thank @Karnage and nostr:npub10000003zmk89narqpczy4ff6rnuht2wu05na7kpnh3mak7z2tqzsv8vwqk who have volunteered to help me a bit.

However, the problem unveiled itself shortly. I never finished their design! Roughly 12 months ago, I asked @Karnage to do a redesign of Blowater. He finished it in like a week. But I still have not implemented 30% of what he designed!

Why?

The surface reason is that there are designs that I don't like or visuals that simply goes against the functionality intention. I, as the product creator, did not communicate clearly with the designer what functionalities I want. Therefore, many changes, iterations are needed.

The root reason is, in an exploratory project, designers can't be treated as ad-hoc helpers or outsourced laborers. They have to participate in the core process to shape the product. They can't just do the UIs, they have to actively get involved into the design of the whole product, from functionalities to UIs. This is what I did not understand back then and it took me 12 months to realize. While a designer does not need to spend 40 hours working on a single project. They still need to be considered as a full-time team member instead of an occasional helper.

---

To address the title, moving forward, I either have to become a UI designer myself, or I have to work with a designer who shares similar visions and is willing to work with me as a long term collaborator. I will never outsource ad-hoc design works again.

@ 8f69ac99:4f92f5fd

No discurso moderno em torno do capitalismo, não é incomum encontrar veemente oposição e crítica. Desde acusações de exploração a pedidos da sua queda, o capitalismo muitas vezes encontra-se na mira do debate ideológico. No entanto, sob a superfície desses argumentos, reside uma complexa rede de motivações psicológicas e crenças filosóficas que impulsionam o sentimento anticapitalista.

A Deturpação do Capitalismo

Desde a sua criação, o capitalismo tem enfrentado uma enxurrada de deturpações e distorções por parte dos seus críticos. Seja alimentada por preconceito ideológico ou genuína ignorância, essas deturpações contribuíram para uma percepção negativa generalizada do capitalismo. Por exemplo, os críticos frequentemente retratam o capitalismo como um sistema que leva inerentemente à desigualdade de riqueza, desconsidera o bem-estar social e prioriza o lucro corporativo sobre o bem-estar dos indivíduos. No entanto, evidências crescentes mostram os benefícios do capitalismo, como aumento do crescimento económico, produtividade e inovação. Apesar dessas evidências, a deturpação persiste, tornando o capitalismo um dos conceitos mais mal representados na história cultural.

Capitalismo difere do que vemos hoje, um híbrido distorcido de mercantilismo e estatismo. No capitalismo puro, o governo desempenha um papel mínimo, apenas fornecendo as infraestruturas mínimas necessárias para um mercado livre funcionar de forma eficiente. O que temos hoje é frequentemente um Estado forte que interfere nos mercados, desvirtuando o princípio básico de oferta e procura, levando à inflação e ao desequilíbrio económico.

A confusão entre capitalismo e esta forma distorcida leva muitos a concluir incorretamente que o capitalismo resulta em desigualdade e injustiça social. No entanto, o capitalismo real, baseado em concorrência leal e sem interferência do Estado, não só gera prosperidade geral, mas também garante que o mérito seja recompensado e que cada indivíduo tenha oportunidades iguais de sucesso.

"Quando não há uma ligação entre esforço e recompensa, o que se obtém é menos esforço." - Thomas J. DiLorenzo

A Influência Corrosiva do Sistema Fiat

A moeda fiat desempenha um papel central na distorção do capitalismo, uma vez que o próprio governo tem o poder de criar dinheiro à vontade, inflacionando a moeda e degradando o valor da riqueza, e poupança, real. Isso gera instabilidade económica, permitindo que os ricos e os poderosos manipulem o sistema ao seu favor. Assim, o sistema fiat não é um reflexo verdadeiro do capitalismo, mas sim uma forma de mercantilismo velado, que prejudica os cidadãos comuns e perpetua a ideia de que o capitalismo é culpado por essas falhas.

Ao entender a verdadeira natureza do capitalismo e a influência corrosiva do sistema fiat, podemos começar a desconstruir as ideias preconcebidas sobre o capitalismo e a sua suposta culpa pela desigualdade e injustiça. A fim de garantir uma sociedade verdadeiramente justa e próspera, é crucial que o nosso sistema se afaste do estatismo e do mercantilismo e retorne às raízes do capitalismo verdadeiro.

Raízes Psicológicas do Anticapitalismo

No cerne do sentimento anticapitalista estão factores psicológicos profundos. Medo da independência, medo do fracasso, aversão à perda e suscetibilidade a vieses cognitivos podem desempenhar um papel significativo na formação das atitudes dos indivíduos em relação ao capitalismo.

• Medo da independência refere-se à apreensão em relação à autossuficiência e às responsabilidades que a acompanham.
• Medo do fracasso abrange a ansiedade em torno da possibilidade de cometer erros ou não corresponder às expectativas da sociedade, particularmente no contexto de sucesso económico.
• Aversão à perda significa a tendência de preferir evitar perdas em vez de adquirir ganhos equivalentes, levando a uma preferência pela segurança e estabilidade em detrimento do potencial crescimento e inovação.

Indivíduos que lutam com estes factores muitas vezes procuram a segurança e previsibilidade, tornando-os mais propensos a abraçar ideologias que prometem segurança coletiva. Além disso, a suscetibilidade a vieses cognitivos pode reforçar ainda mais os sentimentos anticapitalistas. Por exemplo, o viés de confirmação pode levar os indivíduos a concentrarem-se selectivamente em informações que confirmem suas crenças preexistentes sobre o capitalismo, enquanto descartam evidências contraditórias. Da mesma forma, a heurística da disponibilidade pode distorcer as percepções de risco, fazendo com que os indivíduos sobrestimem a probabilidade de resultados negativos associados ao capitalismo.

Compreender esses fatores psicológicos e vieses é crucial para fomentar um discurso e políticas informadas. Embora o capitalismo possa apresentar incertezas, também é um sistema que prospera na inovação e fomenta oportunidades económicas significativas. Ao reconhecer essas nuances psicológicas e promover o pensamento crítico, podemos trabalhar para abordar as preocupações subjacentes e cultivar um cenário económico mais equitativo e inclusivo.

A Fuga da Razão e da Realidade

Alguns indivíduos, motivados pelo desejo de escapar das exigências da razão e da realidade, buscam escravizar os produtores de bens e serviços da sociedade. Esses "escapistas" pretendem criar um Estado omnipotente na esperança de riqueza e honras imerecidas. Eles estão dispostos a dar obediência total ao Estado em troca de provisão e proteção contra os desafios da vida independente. Esse profundo medo de enfrentar a vida por conta própria, assumir a responsabilidade por suas acções e fazer julgamentos informados impulsiona seu comportamento irracional.

O único meio de alcançar o imerecido é através da força física, razão pela qual os inimigos do capitalismo são estatistas. Aqueles que buscam escapar da razão e da realidade só podem fazê-lo esperando que os seus objectivos, desejos ou medos possam de alguma forma triunfar sobre a realidade. Eles esperam que, escravizando os produtores de bens, os produtores económicos, criando um Estado omnipotente, de alguma forma cavalguem nos ombros dos membros racionais da sociedade, os membros produtivos, aqueles capazes de lidar com os factos da realidade de forma adequada, não apenas na questão da produção de bens materiais, mas em todas as questões.

A Moralidade do Altruísmo

Uma das ideologias que desafia o capitalismo é o conceito de altruísmo. Aqui, o autossacrifício é visto como a virtude mais elevada, e o interesse próprio é condenado. Isso cria uma tensão moral com o capitalismo, que se baseia na busca do ganho pessoal, em primeiro lugar. Aqueles que subscrevem fortes princípios altruístas podem ver o sucesso alcançado no capitalismo como inerentemente explorador, alimentando o sentimento anticapitalista.

Contexto Histórico: As raízes do altruísmo podem ser rastreadas até filosofias antigas como o estoicismo e o cristianismo primitivo. Essas escolas de pensamento enfatizavam a importância do dever para com os outros e de viver uma vida virtuosa, mesmo que isso significasse sacrifício pessoal. No entanto, o altruísmo desenfreado pode ter consequências indesejadas. Por exemplo, os experimentos utópicos do século 19, inspirados nos ideais socialistas de propriedade comum, muitas vezes lutaram com a ineficiência, escassez e a falta de motivação individual.

Subjectivismo e Estatismo

Paralelamente ao altruísmo estão o subjectivismo e o estatismo, ou estadismo, que oferecem estruturas alternativas para aqueles que consideram as demandas do capitalismo e da tomada de decisão individual intimidadoras. O subjectivismo pressupõe que a verdade e a realidade são subjectivas e podem ser moldadas pela percepção individual. O estatismo, por outro lado, defende um forte controle centralizado pelo Estado, prometendo fornecer segurança colectiva e estabilidade.

Essas ideologias podem ser vistas como um refúgio das incertezas e responsabilidades inerentes a um sistema de livre mercado (capitalismo). No entanto, o subjectivismo desenfreado pode levar ao relativismo e à negação dos factos objectivos, enquanto o estatismo excessivo invariavelmente sufoca a iniciativa individual e a inovação.

Tanto o altruísmo quanto os conceitos de subjectivismo e estatismo levantam questões importantes sobre o papel do indivíduo na sociedade e o equilíbrio entre responsabilidade pessoal e bem-estar social.

A Tentação do Totalitarismo

Para alguns, o atractivo do totalitarismo - uma forma extrema de estatismo - torna-se irresistível perante ameaças existenciais. A história está repleta de exemplos em que sociedades, temendo instabilidade ou invasão externa, abraçaram regimes que prometiam segurança e estabilidade à custa da liberdade e autonomia individuais.

Após a Primeira Guerra Mundial, a frágil República de Weimar na Alemanha debateu-se com depressão económica e turbulência política. Essa vulnerabilidade criou terreno fértil para o surgimento do Partido Nazi (Partido Nacional-Socialista dos Trabalhadores Alemães) totalitário. Hitler prometeu a restauração nacional, recuperação económica e uma Alemanha forte no palco mundial. Muitos alemães, ansiando por ordem e um sentido de orgulho nacional, estavam dispostos a ignorar a supressão nazi dos direitos individuais e das instituições democráticas.

Da mesma forma, a União Soviética sob Joseph Stalin fornece outro exemplo sombrio. Enfrentando a ameaça de invasão durante a Segunda Guerra Mundial, Stalin consolidou seu poder e esmagou impiedosamente a dissidência. Embora a União Soviética tenha finalmente repelido os nazis, isso aconteceu ao custo de milhões de vidas e de um regime totalitário que sufocou as liberdades individuais por décadas.

Estes exemplos históricos ilustram o poder sedutor do totalitarismo em tempos de crise. A promessa de segurança pode ser muito atraente, mas deve ser ponderada em relação ao alto preço da liberdade individual.

Resumindo

Ao mergulhar nas profundezas do debate em torno do capitalismo, torna-se claro que as objecções e críticas frequentemente têm raízes mais profundas do que simplesmente questões económicas ou políticas. O cerne do anticapitalismo reside numa teia complexa de motivações psicológicas e crenças filosóficas que moldam as atitudes individuais em relação ao sistema económico.

Desmistificar Deturpações: É crucial desmistificar as deturpações comuns sobre o capitalismo, destacando a sua verdadeira natureza e os benefícios que pode trazer quando implementado correctamente. Desde a sua concepção, o capitalismo tem sido alvo de distorções que obscurecem a sua capacidade de promover prosperidade e progresso.

Desafios Psicológicos e Ideológicos: O medo da independência, aversão à perda e a influência de ideologias como o altruísmo e o estadismo desempenham papéis significativos na formação das opiniões anti capitalistas. Compreender esses desafios psicológicos e ideológicos é essencial para abrir caminho para um diálogo mais informado e produtivo sobre o papel do capitalismo na sociedade.

Alerta Contra Totalitarismo: Os exemplos históricos do poder sedutor do totalitarismo lembram-nos dos perigos de abraçar sistemas políticos que sacrificam a liberdade individual em nome da segurança coletiva. É um lembrete contundente da necessidade de proteger e valorizar os princípios fundamentais da democracia e dos direitos individuais.

Ao desvendar as raízes psicológicas do anti capitalismo, abrimos espaço para um diálogo mais inclusivo e esclarecedor sobre o papel do capitalismo na construção de uma sociedade justa e próspera. Reconhecer e enfrentar essas raízes é o primeiro passo para promover um entendimento mais profundo e uma abordagem mais equilibrada das questões económicas e sociais que moldam o nosso mundo.

@ f72e682e:c51af867

Spaniards already dedicate more than 75% of their salary to taxes: Indirect taxes, the 69 tax increases this year, and 50% of the salary for social security make Spaniards the people in Europe whose tax pressure has increased the most since 2019. Tax experts already talk about “modern tax slavery”. The video in the link is in Spanish but I believe you may be able to translate the subtitles. A psychologist analyze this new modern version of slavery.

(ES) Los españoles dedican ya más del 75% de su sueldo a impuestos: Los impuestos indirectos, las 69 subidas del fisco, y el 50% del sueldo para cotizaciones y varios hacen de los españoles el pueblo de europa al que más suben la presión fiscal desde 2019. Expertos fiscales hablan ya de “esclavismo fiscal moderno”

https://www.youtube.com/watch?v=63zP9XlLg4k

@ f72e682e:c51af867

Yes, as you read.

There is a controversy on if this was intentional, or just a bug introduced by Satoshi when he programmed Bitcoin. But the bug causes this money supply graph:

As you can see, after a large period of flat supply, it jumps again up with 50 btc per block, and the cicle repeats indefinetly.

Yes, I know, those are a lot of years, and not even our grandchildren will see it happening. But ey, better to have the future well tied!

The core programmer Pieter Wuille solved it in BIP-0042 ten years ago:

https://github.com/bitcoin/bips/blob/master/bip-0042.mediawiki

@ 1bc70a01:24f6a411

We’re all daily users of Nostr, so it can be easy to see things through an advanced user lens while forgetting what it felt like to be a newbie. I thought I would take some time to go over major client from the start in hopes of evaluating what it might feel like for a new user.

The other reason for running this review is to hopefully improve the overall nostr retention rate across clients. As it stands, according to nostr.band, retention of trusted users 30 days after signups trends to 0 for recent cohorts. This seems to be supported by the lack of growth in daily active users, with the average remaining in the 10,000-12,000 range for “trusted” pub keys.

The following report consists of several criteria which I felt were essential to basic first-time social media experience:

1. Ease of signup
2. Ease of logging in
3. Ability to understand what you are looking at (sufficient explanations)
4. Seeing a good initial feed
5. Ability to follow something of interest
6. Minimizing technical /dev lingo
7. A fast scrolling experience
8. Ability to easily upload media
9. A good search experience overall
10. Good keyword searching
11. Hashtag searching
12. Ability to follow hashtags
13. Easily accessing followed hashtags
14. Good experience reacting to notes

In total there are 140 points, 10 for each category. This is by far not the most comprehensive score card, but I felt it did a decent job covering most things you’d want to do in a social client.

Some notes of caution:

1. This report and score card are meant to be a general quick glance at where your client may stand in overall UX. It does not differentiate between the intended target audiences.
2. The criteria that I deem important may not be important to you as the founder / developer, so take it for what it’s worth. Adding your desired criteria may increase your score significantly. For example, I did not evaluate the zap experience, or thoroughly test nested replies.
3. This report is not a substitute for proper user testing. It’s just one person’s observations. While we have done some user testing in the past, I highly recommend doing your own. You can do so by approaching and interviewing new users (if you are able to distinguish if they came from your client), or via other user testing software. Talk to me (@karnage) if you need some help getting set up.
4. People’s reported experience regarding usability may vary greatly depending on their familiarity with cryptographic concepts, their background, and technical experience. What I may deem as a great score of 10, may not be a 10 for others. I have seen user tests where “obvious” things were not obvious to testers.
5. This report only looks at the English language version of the client. The actual user experience for someone on a different language version of the app could be totally different from what is graded here. It’s worth considering geographies of where users are coming from and how they experience your client.
6. I did not test re-activation of new users. Meaning, once they close the app, I did not test if they are pulled back by some notification or other means. This is a crucial aspect of any new app usage that should be considered carefully.

Tested Clients: Damus, Amethyst, Primal iOS, Snort (web), Iris (sort of), Coracle, Nostur.

I also tested Instagram and X/Twitter for comparison.

Results, highest points to lowest: Primal iOS: 136 Twitter: 125 Instagram: 109 Nostur: 108 Coracle: 99 Amethyst: 93 Snort: 90 Damus: 87 Iris: N/A Facebook: could not test.

My main takeaway was that among all apps (including Twitter and Instagram), the traditional apps win simply by having much better content selection. You get to see a variety of interesting things that Nostr simply can’t match. Going forward, this is an area I would probably recommend focusing on - how to engage people to post more interesting content, onboard creators etc… Nostr is lacking in content and I believe this could be the primary reason people are not sticking around after trying it.

Other Nostr Notes:

There seemed to be little of interesting topics to follow or stick around for. The experience of joining nostr doesn't feel special or different in any way opposed to X for example. Twitter has interesting accounts, TikTok has interesting videos, what does Nostr have? The lack of "popular" conent due to the generally low number of users is probably to blame. In a way we suffer from the chicken / egg problem where new users are needed to generate more content, and more content is needed to retain new users. Going forward, I think clients should think about ways to encourage users to share content (whether that be their own, or posted from other platforms). Nostr also does not seem to have any external growth loops. For example, there is no way to invite people to the platform by email with a single click (by accessing the address book). Even if a friend does manage to join and you can find them, they are in no way notified when tagged (as far as I know). People have to have a habit of opening the app to know if something is happening. The habit formation of using a new app is important in the early usage phase and nostr seems to have a weak spot here.

You can find all of the detailed scoring, notes for each client and other thoughts in this spreadsheet: https://docs.google.com/spreadsheets/d/14w8-aQ1sHfGBSuNpqvOA9i7PHNSfhn6lUOV6H293caw/edit?usp=sharing

@ ec965405:63996966

Me gusta cocinar y bailar!

@ 3bf0c63f:aefa459d

Nostr is not decentralized nor censorship-resistant

Peter Todd has been saying this for a long time and all the time I've been thinking he is misunderstanding everything, but I guess a more charitable interpretation is that he is right.

Nostr today is indeed centralized.

Yesterday I published two harmless notes with the exact same content at the same time. In two minutes the notes had a noticeable difference in responses:

The top one was published to wss://nostr.wine, wss://nos.lol, wss://pyramid.fiatjaf.com. The second was published to the relay where I generally publish all my notes to, wss://pyramid.fiatjaf.com, and that is announced on my NIP-05 file and on my NIP-65 relay list.

A few minutes later I published that screenshot again in two identical notes to the same sets of relays, asking if people understood the implications. The difference in quantity of responses can still be seen today:

These results are skewed now by the fact that the two notes got rebroadcasted to multiple relays after some time, but the fundamental point remains.

What happened was that a huge lot more of people saw the first note compared to the second, and if Nostr was really censorship-resistant that shouldn't have happened at all.

Some people implied in the comments, with an air of obviousness, that publishing the note to "more relays" should have predictably resulted in more replies, which, again, shouldn't be the case if Nostr is really censorship-resistant.

What happens is that most people who engaged with the note are following me, in the sense that they have instructed their clients to fetch my notes on their behalf and present them in the UI, and clients are failing to do that despite me making it clear in multiple ways that my notes are to be found on wss://pyramid.fiatjaf.com.

If we were talking not about me, but about some public figure that was being censored by the State and got banned (or shadowbanned) by the 3 biggest public relays, the sad reality would be that the person would immediately get his reach reduced to ~10% of what they had before. This is not at all unlike what happened to dozens of personalities that were banned from the corporate social media platforms and then moved to other platforms -- how many of their original followers switched to these other platforms? Probably some small percentage close to 10%. In that sense Nostr today is similar to what we had before.

Peter Todd is right that if the way Nostr works is that you just subscribe to a small set of relays and expect to get everything from them then it tends to get very centralized very fast, and this is the reality today.

Peter Todd is wrong that Nostr is inherently centralized or that it needs a protocol change to become what it has always purported to be. He is in fact wrong today, because what is written above is not valid for all clients of today, and if we drive in the right direction we can successfully make Peter Todd be more and more wrong as time passes, instead of the contrary.

---

See also:

• Censorship-resistant relay discovery in Nostr
• A vision for content discovery and relay usage for basic social-networking in Nostr

@ ec965405:63996966

The homie and tech mentor, Iris, ispired me to write this with their recent blog about the intersection of politics and technology.We're heeding Tim Berner Lee's call to "demand higher standards and greater accountability for our online experiences"from the powers at be by being creators and collaborators on the Internet in accordance with the 7th principle of the Contract for the Web.If my readers ever need any tech support, be sure to hit up Iris and check out Light Crystal Systemsfor your freedom tech needs.

Mi amigx y mentorx tecnológica, Iris, me inspiró a escribir esto con su reciente blog sobre la intersección de la política y la tecnología.Estamos atendiendo el llamado de Tim Berners-Lee de "exigir mayores estándares y mayor responsabilidad para nuestras experiencias en línea" por parte de los poderes establecidos, siendo creadores y colaboradores en el Internet de acuerdo con el séptimo principio del Contrato para la Web.Si mis lectores alguna vez necesitan soporte técnico, asegúrense de contactar a Iris y revisar Light Crystal Systems para sus necesidades de tecnología para la libertad.

---

"The fight for the web is one of the most important causes of our time." - Tim Berners Lee, 2018 - 30 years on, what’s next #ForTheWeb?

"La pelea por la web es una de las causas mas importantes de nuestro epoca." - Tim Berners Lee, 2018 - 30 años después, qué sigue #ForTheWeb?

Do you remember how liberating it felt to customize your Myspace with HTML, CSS,and embeded playlists? I miss that feeling. I'm blown away by the power of the web browser to facilitate meaningful connections with other humans across long distances over cable. Did you every flash a custom operating system on a device to unlock endless possibilities? Modding a jigkick battery to install custom firmwareon my God of War Edition PlayStation Portable enabled me to emulate Super Mario and customize the layout of the home screen. It added my own seasoning salt to the device and instilled confidence in my ability to mess with a computer's guts without bricking it. I fondly remember these early years of my relationship with technology that provided me with an escape from bullying at school and an abusive household while empowering me to navigate a rapidly digitizing world.

¿Te acuerdas de lo liberador que era personalizar tu Myspace con HTML, CSS y listas de reproducción integradas?Extraño esa sensación. Me sorprende el poder del navegador web para facilitar conexiones significativas con otras personas a largas distancias a través de cable. ¿Alguna vez instalaste un sistema operativo personalizado en un dispositivo para desbloquear infinitas posibilidades? Modificar una batería jigkick para instalar firmware personalizado en mi PlayStation Portable Edición God of War me permitió emular Super Mario y personalizar el diseño de la pantalla de inicio. Le añadí mi propio sazón al dispositivo y fortaleció mi confianza en mi habilidad para manipular las entrañas de un computador sin dañarlo. Recuerdo con cariño esos primeros años de mi relación con la tecnología que me proporcionaron un escape del acoso escolar y un ambiente abusivo en casa, mientras me empoderaban para navegar en un mundo que se digitalizaba rápidamente.

When Facebook and Twitter dethroned Myspace in the early 2010s as the mainstream social media platforms, however, technology started to affect my life in less liberating ways. The monetization of my attention span ruined real life relationships and probably prevented me from getting hired. I was cyberbullied and even doxed in a Facebook group on one occassion. These are humiliating experiences that I imagine some of my Millenial and Gen Z readers can relate to as being the first generations to grow up with the Internet. As much as these corporations market their software as giving people "the power to build community and bring the world closer together",the lack of accountability for their role in aiding and abetting genocide, destroying marriages, or in fueling the youth behavioral and mental health crisis(which I would argue extends to adult users of these platforms as well) are examples of the "unintended consequences of benevolent design" that Tim Berner's Lee and the Web Foundation aim to address in their movement.

Cuando Facebook y Twitter destronaron a Myspace a principios de los años 2010 como las plataformas sociales principales, la tecnología empezó a afectar mi vida de formas menos liberadoras. La monetización de mi atención arruinó relaciones en mi vida real y probablemente me impidió conseguir empleo. Fui acosado cibernéticamente e incluso expuesto públicamente en un grupo de Facebook en una ocasión. Son experiencias humillantes que imagino que algunos de mis lectores Millennials y Gen Z pueden entender, siendo las primeras generaciones criadas con Internet. Aunque estas corporaciones promocionan su software como una manera de dar a las personas "el poder de construir comunidad y acercar el mundo,"la falta de responsabilidad por su rol en ayudar y fomentar genocidios, destruir matrimonioso alimentar la crisis de salud mental y conductual de los jóvenes (lo cual, argüiría, también se extiende a los usuarios adultos de estas plataformas) son ejemplos de las "consecuencias no intencionadas de un diseño benevolente" que Tim Berners-Lee y la Fundación Webbuscan abordar en su movimiento.

A genocidal blockade by washington forces Cubans to jump through hoops to access Internet services that the Global North take for granted.Though amendments have been made to allow for a handful of personal communication services like WhatsApp to be accessed by Cuban IP addresses, the majority of Cuban citizens have to spend their salaries on costly VPNs to surf the web.These economic sanctions shed light on the lack of technical understanding in washington of how the Internet works and run afoul of the second principle of the Contract for the Web; keep all of the Internet available all of the time.

Un bloqueo genocida por parte de washington obliga a los Cubanos a saltar obstáculos para acceder a servicios de Internetque en el Norte se dan por sentados. Aunque se han hecho enmiendas para permitir el acceso a algunos servicios de comunicación personal como WhatsApp desde direcciones IP cubanas, la mayoría de los ciudadanos cubanos deben gastan sus salarios en VPNs costosas para navegar en la web.Estas sanciones económicas evidencian la falta de comprensión técnica en Washington sobre cómo funciona el Internet y contravienen el segundo principio del Contrato para la Web: mantener todo el Internet disponible todo el tiempo.

“It would be interesting to know how it is possible that the us is so interested in a free access internet for Cubans but prevents us from accessing digital platforms such as WeTransfer, OpenSea, Adobe and dozens of others that are accessed by the rest of the world, adding obstacles to our human development.” - Rubén Martínez Rojas, Havana Resident

"Sería interesante saber cómo es posible que los estados unidos esté tan interesado en un acceso libre a internet para los cubanos, pero al mismo tiempo nos impida acceder a plataformas digitales como WeTransfer, OpenSea, Adobe y docenas de otras que están disponibles para el resto del mundo, añadiendo obstáculos a nuestro desarrollo humano." - Rubén Martínez Rojas, Resident de La Habana

When you juxtapose cruel sanctions with the recent pushes to pass the Protecting Americans from Foreign Adversary Controlled Applications Act(PAFACAA) and the Kids Online Safety Act(KOSA), the united states increasingly seems less like the "land of the free" and more like Soviet Russia. The Electronic Fronteir Foundation found that KOSA "empowers state officials to target services and online content they do not like" and will unfairly endanger activists and other groups.If passed in the Senate, the PAFACAA would ban Tik Tok from devices and app stores in the united states if its China-based owner, ByteDance, doesn't sell its stake to a us-based company. Former united states Treasury Secretary steve mnuchin, a close friend of former mossad chief yossi cohen, whom he previously invited to join his investment fund, has already mobilized potential buyers.This is no doubt to squash political dissent on a platform that has mobilized and educated millions on the ongoing genocide in Gaza. The us empire is throwing the weight of its bloated aparatus around to maintain a waning political and cultural hegemony and blatantly violating our our civil liberties in the process.

Cuando juxtapones las sanciones crueles con los intentos recientes de aprobar la Ley de Protección de los Americanos contra Aplicaciones Controladas por Adversarios Extranjeros (Protecting Americans from Foreign Adversary Controlled Applications Act) y la Ley de Seguridad en Línea para Niños (Kids Online Safety Act),los estados unidos cada vez parece menos como la "tierra de los libres" y más como la Unión Soviética. La Fundación de la Frontera Electrónica (Electronic Frontier Foundation) encontró que KOSA "otorga poder a los funcionarios estatales para atacar servicios y contenidos en línea que no les gustan" y pondrá en peligro injustamente a activistas y otros grupos. Si se aprueba en el Senado, PAFACAA prohibirá TikTok en dispositivos y tiendas de aplicaciones en los estados unidos si su propietario Chino, ByteDance, no la vende a una compañía estadounidense. El exsecretario del Tesoro de estados unidos, steve mnuchin, amigo cercano del exjefe del Mossad, yossi cohen, a quien previamente invitó a unirse a su fondo de inversión, ya ha movilizado a posibles compradores. Esto es, sin duda, para suprimir la disidencia política en una plataforma que ha movilizado y educado a millones sobre el genocidio en curso en Gaza. El imperio estadounidense está utilizando el peso de su aparato inflado para mantener una hegemonía política y cultural en declive y, en el proceso, violando descaradamente nuestras libertades civiles.

"Imagine something similar happening in another country, where its former finance minister ended up as the buyer." - Robert Weissman, president of the watchdog group Public Citizen

"Imagina algo similar ocurriendo en otro país, donde su exministro de finanzas termina siendo el comprador."- Robert Weissman, presidente del grupo Public Citizen

Yes, Iris, technology is political AF. Each corporate tech acquisition and authoritative legislation passed is a nontechnical factor in technology-policy decisions as outlined in Kranzberg's 4th Law.The World Wide Web just turned 35 years old and it's power has concentrated in the hands of a few corporations and an authoritarian regimethat are working in tandem to erode our civil liberties and keep us from building the world we want. How do we achieve Tim Berner Lee's original vision for an open, decentralized information sharing network that empowers humanity?

Sí, Iris, la tecnología es política. Cada adquisición corporativa tecnológica y legislación autoritaria que se aprueba es un factor no técnico en las decisiones de política-tecnológica, como se describe en la cuarta ley de Kranzberg.La World Wide Web acaba de cumplir 35 años y su poder se ha concentrado en las manos de unas pocas corporaciones y un régimen autoritario que están trabajando juntos para erosionar nuestras libertades civiles y evitar que construyamos el mundo que queremos. ¿Cómo logramos la visión original de Tim Berners-Lee para una red de intercambio de información abierta y descentralizada que empodere a la humanidad?

"A new paradigm is emerging, one that places individuals’ intention rather than attention at the heart of business models, freeing us from the constraints of the established order and returning control over our data."- Tim Berners Lee, Marking the Web’s 35th Birthday: An Open Letter

"Está emergiendo un nuevo paradigma, uno que sitúa la intención de los individuos en lugar de la atención en el centro de los modelos de negocio, liberándonos de las restricciones del orden establecido y devolviendo el control sobre nuestros datos." - Tim Berners Lee, Con motivo del 35.º aniversario de la Web: Una Carta Abierta

We can siphon power out from the tentacles of the evil tech lords and politicians back into the hands of the people by wielding the power of open source technology. We have to be better consumers of tech and the Internet and think critically about our digital presences if we want to have a chance at disabling the lying machine. Protocols like Nostr create digital spheres that facilitate this power exchange and give us the means to govern our online spaces, free from the influence of corporate greed. That's why I'm following your lead in this fight for digital democracy. Hasta la victoria siempre!!

Podemos sustraer el poder de las tentáculos de los malvados corporaciones tecnológicos y políticos para devolverlo a manos de la gente mediante el uso del poder de la tecnología de código abierto. Tenemos que ser mejores consumidores de tecnología e Internet y pensar críticamente sobre nuestras presencias digitales si queremos tener una oportunidad de deshabilitar la máquina de mentiras. Protocolos como Nostr crean esferas digitales que facilitan este intercambio de poder y nos dan los medios para gobernar nuestros espacios en línea, libres de la influencia de la codicia corporativa. Por eso estoy siguiendo tu ejemplo en esta lucha por la democracia digital. Hasta la victoria, siempre!!!

"The web is for everyone and collectively we hold the power to change it. It won’t be easy. But if we dream a little and work a lot, we can get the web we want." - Tim Berners Lee, Marking the Web’s 35th Birthday: An Open Letter "La web es para todos y colectivamente tenemos el poder de cambiarla. No será fácil. Pero si soñamos un poco y trabajamos mucho, podemos conseguir la web que queremos." - Tim Berners Lee, Con motivo del 35.º aniversario de la Web: Una Carta Abierta

@ 266815e0:6cd408a5

While I was in Mediera with all the other awesome people at the first SEC cohort there where a lot of discussions around data storage on nostr and if it could be made censorship-resistent

I remember lots of discussions about torrents, hypercore, nostr relays, and of course IPFS

There were a few things I learned from all these conversations:

1. All the existing solutions have one thing in common. A universal ID of some kind for files
2. HTTP is still good. we don't have to throw the baby out with the bath water
3. nostr could fix this... somehow

Some of the existing solutions work well for large files, and all of them are decentralization in some way. However none of them seem capable of serving up cat pictures for social media clients. they all have something missing...

An Identity system

An identity system would allow files to be "owned" by users. and once files have owners servers could start grouping files into a single thing instead of a 1000+ loose files

This can also greatly simplify the question of "what is spam" for a server hosting (or seeding) these files. since it could simply have a whitelist of owners (and maybe their friends)

What is blossom?

Blossom is a set of HTTP endpoints that allow nostr users to store and retrieve binary data on public servers using the sha256 hash as a universal id

What are Blobs?

blobs are chunks of binary data. they are similar to files but with one key difference, they don't have names

Instead blobs have a sha256 hash (like b1674191a88ec5cdd733e4240a81803105dc412d6c6708d53ab94fc248f4f553) as an ID

These IDs are universal since they can be computed from the file itself using the sha256 hashing algorithm ( you can a files hashing on linux using: sha256sum bitcoin.pdf )

How do the servers work?

Blossom servers expose four endpoints to let clients and users upload and manage blobs

• GET /<sha256> (optional file .ext)
• PUT /upload
• Authentication: Signed nostr event
• Returns a blob descriptor
• GET /list/<pubkey>
• Returns an array of blob descriptors
• Authentication (optional): Signed nostr event
• DELETE /<sha256>
• Authentication: Signed nostr event

What is Blossom Drive?

Blossom Drive is a nostr app built on top of blossom servers and allows users to create and manage folders of blobs

What are Drives

Drives are just nostr events (kind 30563) that store a map of blobs and what filename they should have along with some extra metadata

An example drive event would be json { "pubkey": "266815e0c9210dfa324c6cba3573b14bee49da4209a9456f9484e5106cd408a5", "created_at": 1710773987, "content": "", "kind": 30563, "tags": [ [ "name", "Emojis" ], [ "description", "nostr emojis" ], [ "d", "emojis" ], [ "r", "https://cdn.hzrd149.com/" ], [ "x", "303f018e613f29e3e43264529903b7c8c84debbd475f89368cb293ec23938981", "/noStrudel.png", "15161", "image/png" ], [ "x", "a0e2b39975c8da1702374b3eed6f4c6c7333e6ae0008dadafe93bd34bfb2ca78", "/satellite.png", "6853", "image/png" ], [ "x", "e8f3fae0f4a43a88eae235a8b79794d72e8f14b0e103a0fed1e073d8fb53d51f", "/amethyst.png", "20487", "image/png" ], [ "x", "70bd5836807b916d79e9c4e67e8b07e3e3b53f4acbb95c7521b11039a3c975c6", "/nos.png", "36521", "image/png" ], [ "x", "0fc304630279e0c5ab2da9c2769e3a3178c47b8609b447a30916244e89abbc52", "/primal.png", "29343", "image/png" ], [ "x", "9a03824a73d4af192d893329bbc04cd3798542ee87af15051aaf9376b74b25d4", "/coracle.png", "18300", "image/png" ], [ "x", "accdc0cdc048f4719bb5e1da4ff4c6ffc1a4dbb7cf3afbd19b86940c01111568", "/iris.png", "24070", "image/png" ], [ "x", "2e740f2514d6188e350d95cf4756bbf455d2f95e6a09bc64e94f5031bc4bba8f", "/damus.png", "32758", "image/png" ], [ "x", "2e019f08da0c75fb9c40d81947e511c8f0554763bffb6d23a7b9b8c9e8c84abb", "/old emojis/astral.png", "29365", "image/png" ], [ "x", "d97f842f2511ce0491fe0de208c6135b762f494a48da59926ce15acfdb6ac17e", "/other/rabbit.png", "19803", "image/png" ], [ "x", "72cb99b689b4cfe1a9fb6937f779f3f9c65094bf0e6ac72a8f8261efa96653f5", "/blossom.png", "4393", "image/png" ] ] }

There is a lot going on but the main thing is the list of "x" tags and the path that describes the folder and filename the blob should live at

If your interested, the full event definition is at github.com/hzrd149/blossom-drive

Getting started

Like every good nostr client it takes a small instruction manual in order to use it properly. so here are the steps for getting started

1. Open the app

Open https://blossom.hzrd149.com

2. Login using extension

You can also login using any of the following methods using the input - NIP-46 with your https://nsec.app or https://flare.pub account - a NIP-46 connection string - an ncryptsec password protected private key - a nsec unprotected private key (please don't) - bunker:// URI from nsecbunker

3. Add a blossom server

Right now https://cdn.satellite.earth is the only public server that is compatible with blossom drive. If you want to host your own I've written a basic implementation in TypeScript github.com/hzrd149/blossom-server

4. Start uploading your files

NOTE: All files upload to blossom drive are public by default. DO NOT upload private files

5. Manage files

Encrypted drives

There is also the option to encrypt drives using NIP-49 password encryption. although its not tested at all so don't trust it, verify

Whats next?

I don't know, but Im excited to see what everyone else on nostr builds with this. I'm only one developer at the end of the day and I can't think of everything

also all the images in this article are stored in one of my blossom drives here

nostr:naddr1qvzqqqrhvvpzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qq8xzun5d93kcefdd9kkzem9wvr46jka

@ 3bf0c63f:aefa459d

Censorship-resistant relay discovery in Nostr

In Nostr is not decentralized nor censorship-resistant I said Nostr is centralized. Peter Todd thinks it is centralized by design, but I disagree.

Nostr wasn't designed to be centralized. The idea was always that clients would follow people in the relays they decided to publish to, even if it was a single-user relay hosted in an island in the middle of the Pacific ocean.

But the Nostr explanations never had any guidance about how to do this, and the protocol itself never had any enforcement mechanisms for any of this (because it would be impossible).

My original idea was that clients would use some undefined combination of relay hints in reply tags and the (now defunct) kind:2 relay-recommendation events plus some form of manual action ("it looks like Bob is publishing on relay X, do you want to follow him there?") to accomplish this. With the expectation that we would have a better idea of how to properly implement all this with more experience, Branle, my first working client didn't have any of that implemented, instead it used a stupid static list of relays with read/write toggle -- although it did publish relay hints and kept track of those internally and supported kind:2 events, these things were not really useful.

Gossip was the first client to implement a truly censorship-resistant relay discovery mechanism that used NIP-05 hints (originally proposed by Mike Dilger) relay hints and kind:3 relay lists, and then with the simple insight of NIP-65 that got much better. After seeing it in more concrete terms, it became simpler to reason about it and the approach got popularized as the "gossip model", then implemented in clients like Coracle and Snort.

Today when people mention the "gossip model" (or "outbox model") they simply think about NIP-65 though. Which I think is ok, but too restrictive. I still think there is a place for the NIP-05 hints, nprofile and nevent relay hints and specially relay hints in event tags. All these mechanisms are used together in ZBD Social, for example, but I believe also in the clients listed above.

I don't think we should stop here, though. I think there are other ways, perhaps drastically different ways, to approach content propagation and relay discovery. I think manual action by users is underrated and could go a long way if presented in a nice UX (not conceived by people that think users are dumb animals), and who knows what. Reliance on third-parties, hardcoded values, social graph, and specially a mix of multiple approaches, is what Nostr needs to be censorship-resistant and what I hope to see in the future.

@ 266815e0:6cd408a5

Not much going on in this release, just a lot of cleanup under the hood and a few new tools

Minor Changes

• Add "open in" modal (NIP-89)
• Add event publisher tool
• Added Event Console tool
• Add option to automatically decrypt DMs

Patch Changes

• Rebuild observable class
• Add UI tab to relays
• Fix custom emoji reactions having multiple colons
• Fix jsonl database export format
• Fix auto-playing blurred videos
• Fix bunker://pubkey connect URIs
• Fix profile form removing unknown metadata fields
• Unblur all images when clicking on a note
• Update emojilib ( thanks nostr:npub168ghgug469n4r2tuyw05dmqhqv5jcwm7nxytn67afmz8qkc4a4zqsu2dlc PR )

Event Console

A handy tool I built to explore that raw nostr events from nostr relays (or the local cache) It supports auto-completion for the REQ fields and @

Event Publisher

Similar to the event console the event publisher tool lets you write any kind of nostr event, sign, and publish it to your relays

Auto Decrypt DMs

While I'm not a fan of nostr apps prompting the user to sign or decrypt things automatically. in this case it dose make the user experience better.

If your tired of clicking "decrypt" on each message you can turn on the "Auto Decrypt DMs" in the "Performance" settings

As always you can run the app locally using docker docker run --rm -p 8080:80 ghcr.io/hzrd149/nostrudel:0.39.0

@ ec965405:63996966

I'm finally getting around to sharing this note after Aaron Bushnell, a 25 year old united states service member streamed a video of his self immolation in front of an israeli embassy on Twitch last weekend in protest of the ongoing Palestinian genocide. He's the second in recent months to do so and the first to lose his life in the process. This note is for the martyrs.

Finalmente estoy compartiendo esta nota después de que Aaron Bushnell, un miembro de 25 años de las fuerzas armadas de Estados Unidos, transmitiera en vivo su autoinmolación frente a una embajada israelí en Twitch el fin de semana pasado en protesta por el genocidio palestino en curso. Es el segundo que lo hace en los últimos meses y el primero en perder la vida en el proceso. Esta nota es para los mártires.

---

I woke up feeling sick to my stomach in the middle of the night during my recent delgation to Cuba; probably a side effect of mixing 3 plates of Ropa Vieja at dinner with cigars and beer at La Fabrica the night before. Chastising myself for hitting my body with 3 things I normally avoid at home (tobacco, alcohol, and meat), I wasn't able to make it downstairs to the cafeteria for breakfast or the day trip with the group. I was allowed to stay and rest at the center in the morning while they checked out El Rincón de los Milagros,where they learned about the impact of the Haitian revolution on Cuban society. Everyone said I would have loved it. After looking through their pictures and videos of the drum sessions,I'm certain I would have. I'm going to prioritize visiting this spot next time I'm in Cuba.

Me desperté sintiéndome mal del estómago en medio de la noche, durante mi reciente delegación a Cuba; probablemente un efecto secundario de mezclar 3 platos de Ropa Vieja en la cena, con cigarros y cerveza en La Fábrica la noche anterior. Regañándome a mí mismo por someter mi cuerpo a 3 cosas que normalmente evito en casa (tabaco, alcohol y carne), no logré bajar a la cafetería para desayunar ni unirme al viaje del día con el grupo. Me permitieron quedarme a descansar en el centro durante la mañana mientras ellos visitaban El Rincón de los Milagros, donde aprendieron sobre el impacto de la revolución haitiana en la sociedad cubana. Todos dijeron que me hubiera encantado. Después de ver sus fotos y videos de las sesiones de tambores, estoy seguro de que así hubiera sido. Voy a hacer de visitar este lugar una prioridad la próxima vez que esté en Cuba.

On the flip side, I was deficient in sleep hours, so catching up on rest put me in a better position to participate in the evening social at El Sauce. El Sauce is a smaller venue that wasn't nearly as packed as La Fabrica the previous evening. I enjoyed down time with my fellow delegates, happy to get to know them in an intimate space and eventualy joining them on the dance floor for an electric slide.

Por otro lado, me faltaban horas de sueño, así que ponerme al día con el descanso me colocó en una mejor posición para participar en el evento social de la noche en El Sauce. El Sauce es un lugar más pequeño que no estaba tan lleno como La Fábrica la noche anterior. Disfruté del tiempo libre con mis compañeros delegados, contento de llegar a conocerlos en un espacio íntimo y finalmente uniéndome a ellos en la pista de baile para un electric slide.

I watched a man dressed in plain shorts and a red shirt dance enthusiastically with at least 5 separate partners of varying ages and genders throughout the night, radiating joy with each graceful spin as if he hadn't a care in the world. His magnetic energy drew everyone around him into his orbit despite coming to El Sauce alone that night. The circumstances of an inhumane blockade on his country did not seem to phase him as he laughed and sang along to the music, his humanity on full display for us to see.

Observé a un hombre vestido con shorts sencillos y una camisa roja bailar entusiasmado con al menos 5 parejas distintas de variadas edades y géneros a lo largo de la noche, irradiando alegría con cada giro elegante como si no tuviera ninguna preocupación en el mundo. Su energía magnética atraía a todos a su alrededor a pesar de haber llegado solo a El Sauce esa noche. Las circunstancias de un bloqueo inhumano sobre su país parecían no afectarle mientras reía y cantaba junto a la música, mostrando su humanidad para que todos la viéramos

Before dinner the next evening, the group gathered in the cafeteria for a reflection activity about our first few days in Cuba where we broke the ice by sharing an African word that we were familiar with and its significance to us. My mind instantly snapped to "Ubuntu", a word that represents the inception of my programming journey and my intentions with what comes from it. From the African Journal of Social Work,

Antes de la cena la siguiente noche, el grupo se reunió en la cafetería para una actividad reflexiva sobre nuestros primeros días en Cuba, donde rompimos el hielo compartiendo una palabra africana con la que estuviéramos familiarizados y su significado para nosotros. Mi mente se dirigió instantáneamente a 'Ubuntu', una palabra que representa el inicio de mi carrera en la programación y mis intenciones con lo que resulte de ello. Según el Journal Africano de Trabajo Social:

Ubuntu refers to a collection of values and practices that Black people of Africa or of African origin view as making people authentic human beings. While the nuances of these values and practices vary across different ethnic groups, they all point to one thing – an authentic individual human being is part of a larger and more significant relational, communal, societal, environmental and spiritual world. Ubuntu se refiere a un conjunto de valores y prácticas que las personas negras de África o de origen africano consideran que hacen a los seres humanos auténticos. Aunque los matices de estos valores y prácticas varían entre los distintos grupos étnicos, todos apuntan a lo mismo: un ser humano auténtico es parte de un mundo más amplio y significativo que incluye lo relacional, lo comunal, la sociedad, el medio ambiente y lo espiritual.

I explained my philosophy around the use of open sourced software and a healthier relationship with the Internet highlighting the need to boycot corporate tech platforms that inflict irreparable harm on the massses. The constant bombardment of corporate advertising guided by antagonizing algorithms fuel a dire behavioral health crisis that's actively destroying the fabric of our society and disconnecting us from our humanity. Open source software is my weapon in this war against the tech corporations that dominate our dystopic digital lives that I will leverage to center humanity and dignity in communications.

Expliqué mi filosofía sobre el uso de software de código abierto y una relación más saludable con internet, resaltando la necesidad de boicotear las plataformas tecnológicas corporativas que infligen un daño irreparable a las masas. El constante bombardeo de publicidad corporativa, guiado por algoritmos antagonistas, alimenta una grave crisis de salud conductual que está destruyendo activamente el tejido de nuestra sociedad y desconectándonos de nuestra humanidad. El software de código abierto es mi arma en esta guerra contra las corporaciones tecnológicas que dominan nuestras vidas digitales distópicas, el cual utilizaré para centrar la humanidad y la dignidad en nuestras comunicaciones.

I shared this with the group, happy to look over at a fellow delegate and see her point to the bracelet on her wrist with the letters U-B-U-N-T-U spelled out. I felt right at home with this crew.

Compartí esto con el grupo, contento de mirar a una compañera delegada y verla señalar hacia la pulsera en su muñeca con las letras U-B-U-N-T-U. Me sentí como en casa con este equipo.

@ fa984bd7:58018f52

I have recently launched Wikifreedia, which is a different take on how Wikipedia-style systems can work.

Yes, it's built on nostr, but that's not the most interesting part.

The fascinating aspect is that there is no "official" entry on any topic. Anyone can create or edit any entry and build their own take about what they care about.

Think the entry about Mao is missing something? Go ahead and edit it, you don't need to ask for permission from anyone.

Stuart Bowman put it best on a #SovEng hike:

The path to truth is in the integration of opposites.

Since launching Wikifreedia, less than a week ago, quite a few people asked me if it would be possible to import ALL of wikipedia into it.

Yes. Yes it would.

I initially started looking into it to make it happen as I am often quick to jump into action.

But, after thinking about it, I am not convinced importing all of Wikipedia is the way to go.

The magical thing about building an encyclopedia with no canonical entry on any topic is that each individual can bring to light the part they are interested the most about a certain topic, it can be dozens or hundreds, or perhaps more, entries that focus on the edges of a topic.

Whereas, Wikipedia, in their Quijotean approach to truth, have focused on the impossible path of seeking neutrality.

Humans can't be neutral, we have biases.

Show me an unbiased human and I'll show you a lifeless human.

Biases are good. Having an opinion is good. Seeking neutrality is seeking to devoid our views and opinions of humanity.

Importing Wikipedia would mean importing a massive amount of colorless trivia, a few interesting tidbits, but, more important than anything, a vast amount of watered-down useless information.

All edges of the truth having been neutered by a democratic process that searches for a single truth via consensus.

"What's the worst that could happen?"

Sure, importing wikipedia would simply be one more entry on each topic.

Yes.

But culture has incredibly strong momentum.

And if the culture that develops in this type of media is that of exclusively watered-down comfortable truths, then some magic could be lost.

If people who are passionate or have a unique perspective about a topic feel like the "right approach" is to use the wikipedia-based article then I would see this as an extremely negative action.

An alternative

An idea we discussed on the #SovEng hike was, what if the wikipedia entry is processed by different "AI agents" with different perspectives.

Perhaps instead of blankly importing the "Napoleon" article, an LLM trained to behave as a 1850s russian peasant could be asked to write a wiki about Napoleon. And then an agent tried to behave like Margaret Thatcher could write one.

Etc, etc.

Embrace the chaos. Embrace the bias.

@ 3f770d65:7a745b24

February 24, 2024 - Nostr Nests, the premier decentralized audio platform powered by the Nostr protocol, announces the launch of its highly anticipated version 2.0 beta release. This major update brings complete integration with Nostr, a redesigned user interface, and a host of powerful features, making it easier than ever to connect, collaborate, and create in an open and censorship-resistant environment.

Originally launched in January 2023 as Nostr Plebs Spaces, Nostr Nests quickly gained traction as a haven for audio-based interactions across the Nostr protocol. The official rebrand to Nostr Nests in February 2023 further solidified its position as the go-to platform for chatting, jamming, micro-conferences, live podcast recordings, and more with the onboarding of users, shows, and content from around the globe.

Version 2.0 marks a significant leap forward:

Seamless Nostr Integration: Nostr Nests 2.0 was built from the ground up to be a full fledged Nostr client, enabling a truly decentralized experience with direct Nostr authentication. No need for separate accounts, logins, or verification posts. Login with your current Nostr keys via nsecBunker or NIP-07 extensions such as Alby, Nostr Connect, or Nostore for iOS.

Discoverability and User Choice: Find your favorite live audio events like never before, not only on NostrNests.com, but also via a variety of Nostr clients that support live events such as Amethyst, Snort, Iris, Flockstr, Nostrudel, Wherostr and more. Install Nostr Nests as a PWA on Android, iOS, or your favorite desktop operating system.

Redesigned Interface: Navigate with ease thanks to a streamlined and intuitive layout. Find scheduled events, discover communities, and manage your interactions effortlessly.

Enhanced Functionality: Host events with flexible permission settings, record and store audio directly from your Nest, be in charge of your data while you chat on your customized relays, leverage advanced moderation tools for a smooth and secure experience, and broadcast it all across the Nostr protocol. Experience value for value with Zap enabled profiles and chat announcements.

Multi-lingual: Access Nostr Nests in your native language. Nostr Nests supports over a dozen languages, making Nostr Nests a truly global platform for our users. Open Source: The platform's code is fully open-source under the MIT license, welcoming community contributions and fostering transparency. Submit issues and pull requests on GitHub to shape the future of Nostr Nests.

Nostr Nests 2.0 empowers individuals and communities to:

Connect: Host and attend audio events with like-minded people based on shared interests, making new friends along the way or reconnecting with old ones.

Collaborate: Jam with musicians, brainstorm with colleagues, or conduct insightful interviews in a live audio setting.

Express Yourself: Share your voice, thoughts, and ideas with the world in an uncensored and secure environment via text chats as well as audio conversations.

Build Communities: Foster vibrant, customizable communities around shared passions, hobbies, or professional pursuits.

Whether you're a musician, podcaster, entrepreneur, or simply someone who enjoys meaningful audio interactions, Nostr Nests 2.0 invites you to join the conversation. Visit NostrNests.com today and experience the future of social audio.

Join and contribute to the Nostr Nests community:

Website: https://NostrNests.com

GitHub: https://github.com/nostrnests/nests

Current Features:

Nostr Integration: * Sign-in * Live events * Scheduled events * Zaps * Public chat * Reactions * Room presence * Relays (default or custom) * Social sharing * Follow/Unfollow * Profile creation * Profile Editing * Lobby filtering

Lobby: * Active rooms * Scheduled rooms * Filter by global or following * Create new room * View profile

Create room: * Create custom room * Customizable banner * Preselected colors * Custom image (static or animated) * Schedule room * Use default relays or custom relays

Rooms: * Stage and audience * Add/Remove people to/from stage * Public chat (ability to hide/view on mobile) * Raise hand * Mute/Unmute own mic * Mute others (Mod or Host) * Zap * Reactions * Edit profile * View profile * Share to Nostr * Stream audio (coming soon) (Mod or Host) * Record audio (Mod or Host) * Access room recordings (Mod or Host)

Sign-in: * Sign-in as guest to listen only * Create new Nostr profile * Use existing Nostr profile

Future Features:

• Chat zaps, chat reactions, mutes, etc.
• Support additional nsecBunkers
• More room customization options
• Monetization options for creators
• And more!

Please note: While Nostr Nests 2.0 marks a significant step forward, this release should be considered beta software. Users may encounter occasional bugs or unforeseen issues as we continue to refine and optimize the platform. We appreciate your understanding and patience as we work towards a fully polished experience.

Known Issues:

• A lot! It's very new and very beta!
• Sign-in user flow for direct links to rooms
• Mobile UI alignment
• Mobile UI chat bar

@ 2d5b6404:d4b500b0

1. アンフィールドでリバプールの試合を観戦する
2. イタリアでピザ食べたりエスプレッソ飲む
3. じゅりよんやラルフ、ewelina、マルティン、jefgとか𓆏に会いにヨーロッパ旅行行く
4. 長崎ぺんぎん水族館に行く
5. 九十九里で貝を食べる
6. 奄美大島でクジラの鳴き声を聞く
7. 蒸気機関車に乗る
8. 台湾旅行に行く
9. 韓国旅行に行く
10. 船で東京か大阪、四国に行く
11. Punkt. MP02を買い替える
12. ベトナムに住んでる友達に会いに行く
13. ホームベースとなる共同体を見つける。もしくは作る
14. 収入の10分の１を寄付する
15. ~~デスストランディングをクリアする~~
16. ブレワイ、ティアキンをクリアする
17. べランピングする
18. 冷蔵庫を伊良コーラでいっぱいにする
19. 友達とこたつでゲームする

@ 7fa56f5d:751ac194

I'm happy to announce a new release of Habla.

Nostr connect

Users can now login via Nostr Connect remote signers. Both bunker:// URLs and NIP-46 compatible nostr addresses (NIP-05) are supported.

Local drafts

nostr:nevent1qqs2jfpse4akde0w2ljq0n8sytp7pmnrqj943ymyw5kets45ftvv5qspzpmhxue69uhkummnw3ezuamfdejsygyhcu9ygdn2v56uz3dnx0uh865xmlwz675emfsccsxxguz6mx8rygq4xs2f

Some users have reported Habla eating their blog posts. To avoid the issue Habla will now automatically save the post you are editing in local storage. The option to store drafts on nostr still exists if you want to continue editing from another client or device.

RTL languages

Habla is now translated to Hebrew. The translator was kind enough to review the RTL compatibility of the site and we have fixed multiple layout and text direction issues for RTL language users.

Extracting Habla core code

The core Habla code has been extracted to a library called ngine and I have ported several apps to it. These apps are currently using it:

nostr:naddr1qqxnzdesxvungvecxsungdpkqgs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qrqsqqql8kqf6n74

nostr:naddr1qqxnzdesxgunqvpexuersvp3qgs8lft0t45k92c78n2zfe6ccvqzhpn977cd3h8wnl579zxhw5dvr9qrqsqqql8k6zxwng

nostr:naddr1qqxnzd3exgmrsveh8yerqdfcqgsrx4k7vxeev3unrn5ty9qt9w4cxlsgzrqw752mh6fduqjgqs9chhgrqsqqql8kaulu0l

The next step is to start using it from Habla and document it so other nostr devs can leverage it for building apps quicker. The library has similar scope as Osty so will probably join forces with nostr:nprofile1qqsru22d9lfnnwck54qr4phrvey50h2q33xc0gqxv5j03ftn4efu4rspr9mhxue69uhhyetvv9ujumn0wdmksetjv5hxxmmd9uq3gamnwvaz7tmjv4kxz7tpvfkx2tn0wfnj7qgewaehxw309aex2mrp0yhxummnw3exzarf9e3k7mf0y2nv4h, expect some news about this soon.

---

Happy curating, reading and writing!

@ b3e43e8c:e3068b5f

ああテストだよテストだよ

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

@ 3bf0c63f:aefa459d

Drivechain

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

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

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

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

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

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

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

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

What does the above procedure mean?

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

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

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

What? 6 months to get my money back?

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

Why bother with this at all?

Drivechains solve many different problems:

It enables experimentation and new use cases for Bitcoin

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

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

It solves conflicts and infighting

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

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

It solves "scaling"

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

Use your imagination.

It solves the blockchain security budget issue

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

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

It keeps Bitcoin decentralized

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

Can miners steal?

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

Will miners steal?

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

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

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

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

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

What do we do if miners steal?

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

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

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

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

Because it is impossible.

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

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

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

What about the Blockstream sidechains whitepaper?

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

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

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

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

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

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

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

See also

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

@ 3bf0c63f:aefa459d

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.

@ 3bf0c63f:aefa459d

A Lightning penalty transaction

It was a cold day and I remembered that this lightningd node I was running on my local desktop to work on poncho actually had mainnet channels in it. Two channels, both private, bought on https://lnbig.com/ a while ago when I was trying to conduct an anonymous griefing attack on big nodes of the network just to prove it was possible (the attempts proved unsuccessful after some hours and I gave up).

It is always painful to close channels because paying fees hurts me psychologically, and then it hurts even more to be left with a new small UTXO that will had to be spent to somewhere but that can barely pay for itself, but it also didn't make sense to just leave the channels there and risk forgetting them and losing them forever, so I had to do something.

One of the channels had 0 satoshis on my side, so that was easy. Mutually closed and I don't have to think anymore about it.

The other one had 10145 satoshis on my side -- out of a total of 100000 satoshis. Why can't I take my part all over over Lightning and leave the full channel UTXO to LNBIG? I wish I could do that, I don't want a small UTXO. I was not sure about it, but if the penalty reserve was 1% maybe I could take out abou 9000 satoshis and then close it with 1000 on my side? But then what would I do with this 1000 sat UTXO that would remain? Can't I donate it to miners or something?

I was in the middle of this thoughts stream when it came to me the idea of causing a penalty transaction to give those abundant 1000 sat to Mr. LNBIG as a donation for his excellent services to the network and the cause of Bitcoin, and for having supported the development of https://sbw.app/ and the hosted channels protocol.

Unfortunately lightningd doesn't have a command triggerpenaltytransaction or trytostealusingoldstate, so what I did was:

First I stopped lightningd then copied the database to elsewhere: cp ~/.lightningd/bitcoin/lightningd.sqlite3 ~/.lightning/bitcoin/lightningd.sqlite3.bak then I restarted lightningd and fighted against the way-too-aggressive MPP splitting algorithm the pay command uses to pay invoices, but finally managed to pull about 9000 satoshis to my Z Bot that lives on the terrible (but still infinitely better than Twitter DMs) "webk" flavor of the Telegram web application and which is linked to my against-bitcoin-ethos-country-censoring ZEBEDEE Wallet. The operation wasn't smooth but it didn't take more than 10 invoices and pay commands.

With the money out and safe elsewhere, I stopped the node again, moved the database back with a reckless mv ~/.lightning/bitcoin/lightningd.sqlite3.bak ~/.lightningd/bitcoin/lightningd.sqlite3 and restarted it, but to prevent my lightningd from being super naïve and telling LNBIG that it had an old state (I don't know if this would happen) which would cause LNBIG to close the channel in a boring way, I used the --offline flag which apparently causes the node to not do any external connections.

Finally I checked my balance using lightning-cli listfunds and there it was, again, the 10145 satoshis I had at the start! A fantastic money creation trick, comparable to the ones central banks execute daily.

I was ready to close the channel now, but the lightning-cli close command had an option for specifying how many seconds I would wait for a mutual close before proceeding to a unilateral close. There is no forceclose command like Éclair hasor anything like that. I was afraid that even if I gave LNBIG one second it would try to do boring things, so I paused to consider how could I just broadcast the commitment transaction manually, looked inside the SQLite database and the channels table with its millions of columns with cryptic names in the unbearable .schema output, imagined that lightningd maybe wouldn't know how to proceed to take the money from the to-local output if I managed to broadcast it manually (and in the unlikely event that LNBIG wouldn't broadcast the penalty transaction), so I decided to just accept the risk and call lightning-cli close 706327x1588x0 1

But it went well. The --offline flag apparently really works, as it just considered LNBIG to be offline and 1 second later I got the desired result.

My happiness was complete when I saw the commitment transaction with my output for 10145 satoshis published on the central database of Bitcoin, blockstream.info.

Then I went to eat something and it seems LNBIG wasn't offline or sleeping, he was certainly looking at all the logs from his 274 nodes in a big room full of monitors, very alert and eating an apple while drinking coffee, ready to take action, for when I came back, minutes later, I could see it, again on the single source of truth for the Bitcoin blockchain, the Blockstream explorer. I've refreshed the page and there it was, a small blue link right inside the little box that showed my to-local output, a notice saying it had been spent -- not by my lightningd since that would have to wait 9000 blocks, but by the same transaction that spent the other output, from which I could be very sure it was it, the glorious, mighty, unforgiving penalty transaction, splitting the earth, showing itself in all its power, and taking my 10145 satoshis to their rightful owner.

@ 3bf0c63f:aefa459d

The unit test bubble

Look at the following piece of Go code:

func NewQuery(query []rune) *Query { q := &Query{ query: &[]rune{}, complete: &[]rune{}, } _ = q.Set(query) return q } func NewQueryWithString(query string) *Query { return NewQuery([]rune(query)) }

It is taken from a GitHub project with over 2000 stars.

Now take a look at these unit tests for the same package:

``` func TestNewQuery(t *testing.T) { var assert = assert.New(t)

v := []rune(".name")
q := NewQuery(v)

assert.Equal(*q.query, []rune(".name"))
assert.Equal(*q.complete, []rune(""))

}

func TestNewQueryWithString(t *testing.T) { var assert = assert.New(t)

q := NewQueryWithString(".name")

assert.Equal(*q.query, []rune(".name"))
assert.Equal(*q.complete, []rune(""))

} ```

Now be honest: what are these for? Is this part of an attack to eat all GitHub storage and head them to bankruptcy?

Also

• my personal approach on using let, const and var in javascript

@ 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

@ 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

bolt12 problems

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

bolt12 limitations

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

bolt12 illusions

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

@ 3bf0c63f:aefa459d

WelcomeBot

The first bot ever created for Trello.

It invited to a public board automatically anyone who commented on a card he was added to.

• https://github.com/fiatjaf/welcomebot
• https://trello.com/welcomebot