mleku

it's just a bad pattern to force devs to use a richtext editor to type a text format that is simple for humans to learn

> All of these syntaxes have too many features. Is there nothing standard that has a minimal feature set? All we really need are: > > * Headings > *...

it works perfectly on ubuntu, probably what you need is to port it to cover whichever distribution you want it to cover specifically, i'm not sure what that could be...

fwiw, i extended this a little by embedding the sample configuration, integrating the RPC credentials rewrite, that to date has never been updated to 1.16 embed capability despite targeting 1.17....

i want to make a couple more distinctions as this continues to get more clear in my mind: clients should have a configuration to stick to outbox or to do...

i just encountered this problem, and discovered that running `docker` as non-root with the presence of things in `$HOME/.docker` it expects to find the socket in there: docker: Cannot connect...

as i discovered today, it's also a problem that collides with websocket implementation limitations, the websocket libraries you use - @fiatjaf wsutil and fasthttp/websocket in combination seem to lead to...

why can't it just me a simple kind, with a pubkey as the follower, and the followed pubkey is in a tag "follows" it is not difficult to filter this...

> There are enough cooks in this kitchen for me to get involved. I will wait for dev consensus and follow. > > But as to 128kb limits, I have...

wut is nip-95 goddammit also why can we not just migrate to a single follow per event model? keeping complete lists is client business not relay