
Haha, weāre all drowning in imposter syndrome here. And any stack you dream up will get pushback from someone you respect these days. š
š This profile hasn't been claimed yet. If this is your Nostr profile, you can claim it.
EditHaha, weāre all drowning in imposter syndrome here. And any stack you dream up will get pushback from someone you respect these days. š
Well. If you donāt insist and donāt know what fronted does in the background to produce responsive pages, it will derail quickly. There will be miles of co fixes for self-inflicted problems, when all that was needed was to adjust a too-tight constraint on some element that broke the flow. All pages are responsive until you add CSS. LLM wants to force it.
PSA. Donāt reuse private keys across multiple curves. And if you do, for godās sake, donāt announce it publicly. Youāre giving away triangulation points and once guessed you lose control of all connected services.
Iām thinking more along the lines that we have a lot of very opinionated software and a lot of users who just donāt want to deal with the details. This makes protocol hopping possible so users can choose the best software for a given use by some other metric.
This is just a way to provide a link in one place, without having to go through various hoops to prove ownership of said users claimed in the tags. Tags are easy to fake, especially when itās referencing raw private keys.
Depending on the client and the use case, you could be leaning into one or the other. One might want individualy signed notes in the social network context and boards in the project management context. Not saying I have all the answers. Itās just possible to have them coexist.
Exactly. Just reference the satoshi everywhere as a pointer.
We could make it curve-agnostic, using something like PKCP as a bridge. https://github.com/pubkeychain/pkc-protocol If you have an identity chain with pubky and nostr keys in PKCP you get a two-for-one deal, linking of id across protocols and nostr key rotation.
Yep. None of it is set in stone. I have a lite version in mind also, for a single magazine. While Newsroom is meant to become a newsstand eventually. The db is really thin. And if youād be using it for a single magazine-like website, you donāt need redis at all.
Sure. https://github.com/decent-newsroom/newsroom
Frontend dev