Thank you so much for this, gonna give a try soon.

Thanks, that indeed shouldn't happen, I will investigate.

serving nginx on /dist should be fine.

Hope you ran with npm run build && npm run preview` instead of `npm run dev`.

post preview will be coming, as I am changing the editor upload approach to look like more github, also with image compression. the client should support relay sets feeds, you just have to access them in the menu `Lists`.

There's an indicator if you are trying to post inside a relay feed (not your home feed), but I will allow you to disable it, this indeed needs to be more flexible, the reason I did was because some people wanted.

No yet, it been on backlog for a long time, gonna try to get some time to do it, your emojis indeed take a wider space, gonna fix that, what browser and os you using?

Yes it has outbox implemented, what signer are you using with nosotros? I recommend using a browser extension like nos2x and check all the messages the client is trying to sign in the popup (don't click "authorize kind 10002 forever"), if you are using a mobile client like damus/primal/amethyst and put your nsec on it, you have no control on what the client is signing (and possibly overwriting it), use a remove signer on mobile like amber.

Did your list was overwritten when you trying to change your relay setting or when you just tried to access some client? you will need to hunt down the client doing that.

> Does it make use of all my published relay lists (inbound/outbound/search/DM/etc), or just some?

When you post, I am broadcasting to yours outboxes relays, if you are tagging someone, I will also broadcast their inbox relays. search relay is used when you search something, you can select other search relay in the search settings, now days is mostly nostr.band. the client will look for your inbox relays for your notifications and replies/reactions of your notes, the client doesn't have DMs therefor doesn't use DM relays for anything.

1. The relay lists in the /relays page under "Active Relays" are relays that were found as you navigate the app, in your home feed, the client will look for outbox relays from the people you follow and fetch notes from these relays, if you follow like a thousand people, it will find and connect lots of relays, the client cap the max number of relays per person (you can change in the settings) to make the number of connections more manageable, you might have concerns of too many websocket connections and a privacy implication, and you will be right, but this is the nostr solution relay centralization. The list of your outbox and inbox relays should be under "outbox relays" and "inbox relays" respectively, not under "active relays".

2. Follows or relays lists being nuke is common in nostr and supper annoying, specially for non technical users, please find and report which client nuked your list, I haven't heard of it in my client as I always fetch your list before publishing a new one, if you are logged with a browser extension make sure to check the event in the popup before signin the event, a follow event should have a bunch of p tags.

3. This happens when the client couldn't find the user metadata or still trying to find, it's trying to find the user outbox relays and fetch user metadata, sometimes this information simply can't be found as the user didn't setup their relays properly, changing outbox relays without migration result in things like this, this has nothing to do with search relays or your relay settings, mostly the user issue or a client issue, nothing really you can do.

4. Thanks for reporting that, haven't heard of this issue, , gonna try to reproduce it, yeah, cleaning the db likely won't fix the issue.

Keep reporting.

That's true, I didn't realize it, maybe because I am on mac and horizontal scroll is almost effortlessly, gonna try to move the create note button.

Deck needs some work still, resizing and switching columns order, maybe some autosizer too to squeeze things as you add more columns, I need to keep in mind horizontal scroll is annoying for some users.

Thanks for the feedback, don't hesitate to suggest anything else or create an issue.

No yet, I will try to prioritise it as is a bit embarrassing.

I have been reading about federated learning these days, there's very interesting possibilities.

Vou revisar seu PR esse fds, tava ocupado com a wotathon 🤣

I don't recommend using the markdown extension in nostr-editor, unless it's very explicitly like writing an article. also the markdown extension is very unstable and I never battle tested it that much as I don't use it, I have intentions to remove it and upgrade to tiptap 3 which natively supports markdown.

I tried nostash with success, no issues, but only directly on safari, not in PWA mode, I don't think PWA apps can access safari extensions as they run in a different context.

weird, it doesn't work for me on jumble, it gives me "Login failed", seems like it couldn't connect to the local relay.

Aegis should allow custom relay in the bunker url, I am afraid a pwa app can't access a local websocket connection (127.0.0.1) of other ios app.

I will investigate safari + nostash

What browser and browser extension are you using?

I was already building something related to wot before I knew about wotathon, can I still participate?

Correct, it's on my backlog, gonna take a look at this soon

Thanks a lot Anthony 🫡

Responder nested replies agora vai abrir um dialog no mobile.

Appreciate the feedback, but without the outbox model nostr just simply doesn't work well, I used to have a outbox toggle long time ago but ended up removing as I found it didn't make much sense, the NIP-65 relay lists were meant to "where you publish your notes" and "where people reply to you" as write and read relays, not as "the only relays the client will connect to", it makes no sense to fetch notes from the people you follow in your 4 write relays as they not necessary are writing there.

Also, even If I didn't had the outbox model implemented, people are quoting events everywhere and the client has to follow those quoted events through relay hints, opening more connection we don't control.

Even if you are viewing a single relay feed I am still fetching quotes and user metadata that might live outside the current relay feed, the client is also fetching kind 10012 (relay favorites from the sidebar) from people who write in different relays, I can kinda hardcode that to avoid opening some connections but it won't fix the 100% problem.

I understand your concerns but that's how the protocol encourage things, decentralisation at the expensive of privacy.

But I've been working on a open source multiplex/proxy relay that you can configure in the client and will bring 60 connections to 1 connection at all times, but It's not ready yet.

Also for reference: https://github.com/vitorpamplona/amethyst/issues/1426#issuecomment-3228578798

nostr:nprofile1qy28wumn8ghj7un9d3shjtnyv9kh2uewd9hszyrhwden5te0dehhxarj9ekxzmnyqyg8wumn8ghj7mn0wd68ytnhd9hx2qg4waehxw309a5xjum59ehx7um5wghxcctwvsqzpmnw5yatnljuff5w47d35d87q99xddqpzlzsac4xzn6vm22ekmn569ddzt great work, ftw, the app is also purging `t` tags from the follows list

In this case because you tagged fiatjaf, if posting to a relay feed and tagging other people, should I broadcast to their inbox relays too or only strictly broadcast to the relay feed? I wasn't sure about it when coding it, it's an easy change tho

Just received 1000 sats from you, thank you, did you sent using nosotros? I can't see on my notifications tho, somethings indeed not working

Looks like a use case for nip66 and the g tag

Give a try again in dev, did a bunch of fixes, last version is 1.0.6 (7947c4e6), thanks a lot for reporting

GM! managed to strike 15 hours of sleep again. Yay!

Thanks a lot for reporting, pushing a fix, I changed too much things, the non-dev enviroment should be more stable for now

Where was the last client you updated your relay list? nostr:nprofile1qyxhwumn8ghj7mn0wvhxcmmvqyf8wumn8ghj7am0wsh82arcduhx7mn9qqspw5udc2nzw6wsj3plrrphe0343744h0ucz9e4g248chl3w8kh03qj7z543 some client is publishing relay lists with `relay` tags instead of `r` tags.

I tried for many many years making true native components on react-native (eg: https://github.com/cesardeazevedo/react-native-bottom-sheet-behavior, and https://github.com/cesardeazevedo/react-native-collapsing-toolbar) and it's not worth it.

The vast majority of the community has really low standard about native feel components and whatever works is "good enough".

The entire navigation was a completely mess from the start, I tried for many hours hacking on airbnb-navigation back in 2018 that they abandoned right after the announcement, spend some time too on the wix navigation rabbit hole too, and you don't wanna do that.

The community was fine with react-native JS implementation for many years, but for me that was just simply not shippable and fake (at least on iOS)

I've seen pretty good iOS only component libraries just see the owner rewrite the whole thing in javascript to support android and ended up with a mediocre UI that doesn't feel native in neither platforms.

Apparently things got better and there is a true native navigation now, but I still think it's not worth it.

I tried RN again some months ago and I was already disappointed from the start, the default android bottom tabs navigation was not native and I was already ejecting from expo to use callstackincubator/react-native-bottom-tabs just to realize I was doing that same thing I was doing back in 2016.

Now days I would just do Kotlin and SwiftUI, and maybe be able to share some core code between them in Rust

I want to try this as well but I am afraid of sqlite wasm be slower than indexeddb because of the worker, but let me know the results.

I sort by people you follow