Nostr Web Client

If you use Go, did you know the embeddable Dgraph variant: https://github.com/hypermodeinc/modusGraph

Replying to

Keychat

Keychat is composed of several components. One-to-one chats are encrypted with the Signal protocol, small group chats are pair-wise groups aggregated from one-to-one chats, and large group chats use the MLS protocol. It also involves ecash stamps.

We haven’t written any NIPs yet; we need to write several.

https://github.com/nostr-protocol/nips/pull/1813

I can’t decide whether to use NIP-117 or your approach for the double ratchet until you publish your own NIP.

Replying to

Current status of Amethyst Outbox:

124 relays, with 14 subscriptions and 1959 filters at an average of 16 filters per relay.

lol.

Are you likely to be able to solve it?

Replying to

reis

wait, Nostur is awesome. deleted Primal.

but its logo sucks

wait, Nostur is awesome. deleted Primal.

Replying to

No, just the coordinator should be one of the signers.

Understood.

Replying to

Signer should be separate. Clients are too insecure to hold keys.

See nostr:nevent1qqsqqq8klshrth20jlzpu9c9t0m3j3qqqudk5s7ndn3ltjyztqaghuqpr9mhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5q35amnwvaz7tmrdpex7mnfvdkx2tnyw3hkummw9e3k7mgzyqalp33lewf5vdq847t6te0wvnags0gs0mu72kz8938tn24wlfze6wm5a5u

Are you saying that the own shard in nshard should be eliminated in this example? Aside from that, does the rest make sense?

Replying to

fiatjaf

That's what Frostr does.

My assumption is that it's worse because it creates this requirement on all clients, while the Promenade bunker works anywhere with a generic interface. It's faster also in theory because signers are already connected directly to the coordinator.

But yes, if everybody agreed and all apps included this coordinator then it would be technically better. We'll need a strong standard for it and bully everybody to support it.

Thank you for the clarification. If it’s not worse in terms of security, I think it’s worth considering as a possible implementation.

nostr:npub1xtscya34g58tk0z605fvr788k263gsu6cy9x0mhnm87echrgufzsevkk5s nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z what do you think?

Replying to

semisol

nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn what defines the “relay pubkey” in NIP-29 groups?

The pubkey in NIP-11 is meant for administrative contacts not for relay-signed events

https://github.com/nostr-protocol/nips/pull/1764

Replying to

Cody

This looks more interesting than follow packs, stealing it!

nostr:nevent1qvzqqqqqqypzqvhpsfmr23gwhv795lgjc8uw0v44z3pe4sg2vlh08k0an3wx3cj9qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qg3waehxw309ahx7um5wgh8w6twv5hsqgq27sjcxdpxrvdy5h0hunl8zmj9wxyw5ppw0en8ldl97yzyy6ru25phjqeq

LFG

Replying to

State of MarkDown Nostr is barely better btw.

No WYSIWYG editor that integrates even one Nostr-native thing.

They all copy, paste andstop there.

Same for short text in fact.

https://textfieldhack.vercel.app/

I just hacked TextField for notes, but AsciiDoc was a too much for me when I was exploring the Curated Publications NIP. I’d definitely use your package for AsciiDoc if you publish it.

Replying to

#nosciidoc seems to be the best fit for most long form text:

:mail: Mail

:note: Notes (as in actual note taking)

:wiki: Wikis

:article: Articles (kind 30040)

:book: Books

Etc...

So I need help in defining it.

→ as I'm working on a WYSIWG editor for it

nostr:npub1uvhwdxy980y0ufdprjz3j5j3wd2wpl3v5lf36r68fq895xs7ptvsscpjgx do you guys have a spec already with the parts of AsciiDoc you ignore and the parts of Nostr you add?

Do you have an AsciiDoc package? It will be huge for everyone.

https://crypto-sec-n.github.io/

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 I have a question. Instead of using Frost "bunker", would it be possible of a bad idea to embed the coordinator in a client to reduce a point of failure. Please see the simplified image. I don't know nothing about Frost technically so I'm just asking.

reis 8mo ago

For client devs and the users:

Replying to

nostr:nevent1qvzqqqqqqypzqt0ql7s2cg6l7306fn9egnxn7vlhnl6ay870jhcplx23dwmtkukvqy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7qpqkc9cgt4zcg78mgcj8kppu530ckyqdrsaq37dxvwm7rtzahcecr2qw2krze

Added MarkDown (or better #NDown) parsing to Zaplab Design and realized I can just have one renderer for both AsciiDoc and MarkDown. AsciiDoc just expands the MarkDown elements types.

Just one renderer file to maintain, hooray :partypopper:

reis 8mo ago

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl Would you mind adding a 'Read More' button? Or just showing the shorter version on the timeline? Long notes like the one I quoted have a UX problem.

Replying to

Happy lib day people!! New tarifs for everyone!

It is not an optimistic situation. It feels like the eve of a world war.

Replying to

→ Voyage

💯

Replying to

Cody

No, I won't. The two-column layout of Jumble isn't suitable for reading long-form content. It's not immersive enough. Also, there are many things in Jumble that need improvement, and it'll take me some time to perfect it. After Jumble becomes good enough, if there still aren't any good long-form clients, I'll consider developing one separately.

Since it’s your decision, it couldn’t be wrong!

Replying to

Cody

I think so, too

I know you will integrate the long form into Jumble.

nostr:nevent1qvzqqqqqqypzpmzzcaj5rzeah8y940ln4z855wa72af4a6aac4zjypql55egcpsqqyf8wumn8ghj7u3wddhk56tjvyhxjme0qqsgz7ep4n3plchuw0ynp9g4lrc3gfpjde287qus3yx50mvqx7m5q8sl4afue

nostr:npub180cvv07tjdrrgpa0j7j7tmnyl2yr6yr7l8j4s3evf6u64th6gkwsyjh6w6 This is why the University of Tokyo didn't choose Nostr over Bluesky. TLDR: No delegations.

Replying to

HoloKat

No. I’m not in the weeds of any development tbh. Just hacking around in spare time

That's fine. It's just that the answers to your question are in there.

Replying to

HoloKat

GM. I think I asked this but what’s the reason Nostr doesn’t like key delegation?

https://github.com/nostr-protocol/nips/pull/1837

Did you check the recent efforts around this?:

Replying to

Melvin Carvalho

I tried it last week. The mobile client is solid but still a bit glitchy — about on par with Nostr mobile, in my experience. I’d expect a public release in June once they’ve ironed out the bugs.

As for Nostr’s censorship-resistance claims — they’re pretty weak. When real Bitcoin-level censorship resistance was on the table, there wasn’t much interest. The focus seems to be on building a Twitter clone, which makes sense given that most of the ecosystem is funded by Twitter’s founder.

You mean that it's as fast as Nostr when you load the home feed?

nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl Seems that Jumble doesn't show fiatjaf's notes in the Following feed because it only selects lockbox.fiatjaf.com as an outbox for fiatjaf. This is not a bug of Jumble. The outbox NIP is broken.

Replying to

Leito

One would think a simple semaphore would be enough for must stuff that we are trying