The printing press was a great invention, but what is really important is the technology behind it.
The printing press itself had its dark side because it lowered the barriers for spreading ideas that were potentially dangerous to society.
However, the "Transmission of ink by pressure" technology allowed innovation in various industries, allowing the optimization of processes that were previously very expensive. For example, engraving symbols or drawings on cloth, producing cards, and reproducing official stamps on a large scale.
☝️ This is how it sounds when they say "No Bitcoin, but Blockchain technology".
The printing press effectively lowered barriers to the free circulation of ideas and knowledge, which generated a true revolution.
Its main innovation was not "Transmission of ink by pressure" but the movable-type, ideal for the (re)production of text. Just as the innovation of Bitcoin is to order records chronologically in a decentralized way, ideal for transfering digital value.
Both technological tools had (and still have) a great impact on humanity, decentralizing power from a few hands and placing it at the service of all, in pursuit of the progress of civilization.
I don't know how each relay implementation works, but I always thought it made sense to only store recent data, except for profile and other more "static" data.
But I would assume for paid services that could be different.
Tampoco confundir "deberías hacer xxxx" con imponer.
Debatir lo que uno cree que debería hacerse no es imponer, esa es la confusión más habitual que yo veo.
Another alternative would be to let the plugin change the account, not the client. Since in Nostr is the plugin that really manages it.
A new API function could be define that allows the client to notify the website that the account changed so the website acts accordingly.
I'm still not decided on which is the best approach.
?cid=6c09b95272f4b43dfcec85d43aaefccdbf4c60e27a296cd5&rid=giphy.gif&ct=g
¡Espectacular episodio el L174 de #[0] ! 👏
Un conjunto de ejemplos y enseñanzas sobre banca, crédito, dinero, mercado, y economía.
Súper didáctico y claro Ááron, y #[0] un lujo como siempre.
Es largo, pero lo vale.
Y ahora en otro cliente que se me había pasado por alto:
The last point about transferability could change in the future if the protocol updates. Eg: a new event kind that represents a "transfer" pointing to the original issuance and etcétera...
In any case, it's true that they are related concepts. I like the permissionlessness of the Nostr way.
Si te referís a si yo estoy involucrado en el desarrollo, la respuesta es sí.
Ese addon lo había empezado Fiatjaf pero la versión de Firefox la dejó sin atender, así que yo tomé la posta y él siguió manteniendo la versión original para Chrome.
Ideas for future features on nos2x-fox:
https://github.com/diegogurpegui/nos2x-fox/discussions
Feel free to participate
Pruebo otra forma de linkear el artículo a ver qué pasa
@naddr1qqyrswtyv5mnjv3sqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsygx3uczxts4hwue9ayfn7ggq62anzstde2qs749pm9tx2csuthhpjvpsgqqqw4rs8pmj38
Trying new method for linking the note
#[7]
#note10sqgdxulup65vrsclaunek2ptgx27ud3as2kwsqgua4dfj38hmhs74rkz6
New version of nos2x-fox for Firefox mobile just released.
Check this note with instructions:
note:note10sqgdxulup65vrsclaunek2ptgx27ud3as2kwsqgua4dfj38hmhs74rkz6
New version v1.11.0 of nos2x-fox with support for Firefox mobile.
At this moment Firefox does not allow to install addons on its mobile version the normal way, only a selected few "recommended" addons. However, there is a way to do it.
In the following article there are instructions which involve installing the Firefox for Android Nightly (I think now this works for Firefox Beta for Android too):
I just tested it briefly and seems to be working. So you can use your favorite web clients without entering the private key in each of them 😉.
Please, give it a try and let me know! You can open issues in https://github.com/diegogurpegui/nos2x-fox/issues
En iris ni siquiera muestra el artículo en mi perfil, ni tampoco hace linkeable el "nostr:" que puse en mi primer post.
El cliente tiene el scope claro y definido, no incluye Kind 30023.
Or perhaps is the "nostr:" link to a not-well-supported format?
Es cierto, al clickear en "Show More" desde esta nota/post rompe. Sin embargo si voy a mi perfil el artículo (long-form) en cuestión aparece y puedo leerlo en la app.
Curioso que Amethyst decida mostrarlas como un post más, ya que es un Kind diferente.
#[4] any idea what could be happening with long-form content?
El cliente que yo usé es https://blogstack.io
Hice una prueba de escribir un artículo (bueno, transcribí un hilo de twitter mio de hace 2 años 🤭) usando el formato de contenido largo de Nostr (NIP-23).
El pequeño artículo en cuestion, una explicación de los fees de Bitcoin (con analogías, claro 😉):
nostr:naddr1qqyrswtyv5mnjv3sqy28wumn8ghj7un9d3shjtnyv9kh2uewd9hsygx3uczxts4hwue9ayfn7ggq62anzstde2qs749pm9tx2csuthhpjvpsgqqqw4rs8pmj38
Me interesa saber qué clientes levantan esto.
Thanks! I've been here for a while though.
But still...
?cid=6c09b9520be6f172595433e8226b78edfb3b559d88bb7d60&rid=giphy.gif&ct=g