Cesar Dias

Public Key

npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c

NIP-05 Address

Profile Code

nprofile1qqsvvcpmpuwvlmrztkwq3d6nunmhf6hh688jw6fzxyjmtl2d5u5qr8spp4mhxue69uhkummn9ekx7mqpz3mhxue69uhhyetvv9ujuerpd46hxtnfduu3l6jj

Publishing to

Author Public Key

npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c

Show more details

Last Notes

2026-01-06 02:12:32 UTC

- reply

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`.

2025-12-16 19:18:37 UTC

- reply

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.
https://blossom.nosotros.app/3e7c2d518c3595d903d1c21d226f7f8e7d90eb5db9772ac75a9e4414cc4bb11e.png

2025-12-16 18:50:54 UTC

- reply

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?
https://blossom.nosotros.app/fdd6db9c879517246828d057d4fa25d41938c6cacd14282758d908ab1394851e.png

2025-12-16 18:49:14 UTC

- reply

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.

2025-12-15 15:52:12 UTC

- reply

> 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.

2025-12-13 01:39:20 UTC

- reply

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.

2025-11-16 14:10:59 UTC

- reply

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

2025-11-16 13:51:55 UTC

- reply

What browser and browser extension are you using?

2025-11-15 01:41:13 UTC

- reply

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

2025-11-02 16:04:15 UTC

I have achieved the impossible 🤣
https://blossom.nosotros.app/07a3fb87c1912b245d3ab07bdd8b79df4953178903a09266b1699a46b195d953.png
#nevent1q…cy3t

2025-10-31 02:16:12 UTC

- reply

I agree with you, my opinion is that the outbox model makes everything complicated, like:
* You split 500+ authors from a filter and send to the authors write relays.
* Open 50+ websocket connections 🤮
* Send the filter with their respective authors + limit of 200, but as you pass it to multiple relays for a group of authors, you get waaay more than 200 events.
* Some relays are slow to connect, you started to receive events from everywhere totally out of order, also some events from 2 years ago (if you don't put a since) because some author has a private relay and don't post that much, so you put a timeout to then sort the events by created_at and hope you got everything.
Previous version of nosotros was something like that, having a caching layer kinda helps as you don't to worry the responses from multiple places to render the feed but just dump them in a database and the UI fetch events from there.
But i agree with a private relay / service approach, I been working in a multiplexer relay but haven't tested yet, it should also improves privacy.

2025-10-16 19:11:01 UTC

- reply

Amazing, I was really happy when I found out about Bacon https://dystroy.org/bacon/

2025-10-14 00:08:49 UTC

Just released nosotros 1.7.0
* New "undo" approach after feedback from fiatjaf to delay broadcast (no more annoying count down in the editor before signing), you can also disable the delay broadcast in the settings.
* New note stats UI.
* Parallel routes, now I don't unmount the feed if you navigate to a note or profile, so navigating back should feel almost instantly, the client should feel really snappy now.
New changes currently being tested at dev.nosotros.app
https://blossom.nosotros.app/4c86877a3676cca8b8548cf34d5677924712d27cd9e9a7d0d6182f97534b935c.png
https://blossom.nosotros.app/cef942545554c85da99d4082e627597941e5767d220774a204c0b647c34292fb.png

2025-10-07 15:57:05 UTC

- reply

Interesting

2025-10-04 02:53:09 UTC

- reply

Reminds me Amyr Klink's book Paratii.
https://blossom.nosotros.app/8aa1a69fba186228c9fa5f50436fc1c43a60f7d5db76a114f277eeb0bfe15bff.png

2025-09-29 17:14:36 UTC

nosotros.app has finally been updated from dev, it also works seamless with multiple tabs, one of the limitations of OPFS/sqlite is a single connection to database, I was kinda concern about this, so I implemented a shared worker communication between tabs thanks to navigator.locks api

2025-09-28 16:46:45 UTC

https://blossom.nosotros.app/744155c04cdb99c97789505a2d06d952973bea4471894518d4d7a656a16aab9e.jpg

2025-09-26 15:54:18 UTC

"cesardeazevedo tagged you as a reviewer"
https://blossom.nosotros.app/8f392faa2f75a4ba62248507d61651a68117aa0cf3137a5c4eb034f3310590cf.png

2025-09-25 23:27:38 UTC

- reply

This makes sense, it will be there next version

2025-09-25 12:14:16 UTC

- reply

https://dev.nosotros.app

2025-09-21 18:37:28 UTC

- reply

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

2025-09-21 17:16:20 UTC

- reply

Try my client and let me know what you think https://dev.nosotros.app

2025-09-20 17:58:05 UTC

Feed settings are now persisted, good for those who want to disable reposts on the main feed
https://blossom.nosotros.app/d950da023b032b9df8e397e88c489aff38f5e0c9d41540e956452a7d4d500569.png

2025-09-16 19:09:00 UTC

- reply

That's true, there's missing parameters in the nostrconnect url, it doesn't have anything to do with NIP-05, I just fixed locally and will go in the next version later today, thank you.
https://blossom.nosotros.app/52dab2842d10a48f7431f20be85ecced4dac1a956d244bd2999a6e74dddedce0.png

2025-09-16 18:50:19 UTC

- reply

NIP-05 should work, where exactly it doesn't show?
https://blossom.nosotros.app/3dfde359761f36471f3734b8bf98d480f061f33fd6ea975d3b8ad3f7ed26154e.png

2025-09-16 13:07:32 UTC

- reply

Thank you so much!

2025-09-11 17:47:32 UTC

dev.nosotros.app 1.4.0 will now group images and videos close together in a carrousel (just like is done with kind 20) and also has a proper lightbox component to visualize them, the thread will load on the right side so you can interact with replies while viewing the media.
(I always wanted to implement this 🤣)
https://blossom.nosotros.app/24debe7d84e6139a0a6786d313c28d6de4213e22e37553e1d96272473ebda082.png
https://blossom.nosotros.app/8b1eaad247ece7bc628478648e0102751046e0379af349ce3cac4e2c3c4334ed.png

2025-09-10 23:42:23 UTC

- reply

Golang LOL 😂

2025-09-10 17:45:20 UTC

- reply

@nprofile…ddzt great work, ftw, the app is also purging `t` tags from the follows list

2025-09-09 15:01:27 UTC

- reply

I understand the other relay list issues, but having a flag on NIP-11 is a very easy gain to block users from adding relays like purplepag.es or algo.utxo.one to their relay lists (I have seen multiple times), and also display a warning to the user if they have those relays there and explain to the user the relay type

2025-09-09 14:20:52 UTC

- reply

Can we have a relay type flag on NIP-11 so client devs can block people from putting these relays on their inboxes/outboxes? your issue https://github.com/nostr-protocol/nips/issues/1282 already perfectly describe it

2025-09-09 03:48:09 UTC

- reply

Just implemented NIP-70 in version 1.3.3, now posting from a relay-feed will create a protected event, it will ask for authentication right after submit, and it won't be broadcasted to people you mentioned, also removed the ability to add and remote relays in the broadcaster for protected events.
https://blossom.nosotros.app/306e41203b4e7ff58c17db9d8202d0629bd8b6061f027d13462b061584747bf7.png

2025-09-08 23:58:42 UTC

- reply

No, I don't have this tag implemented, but I will take a look right now

2025-09-08 22:14:57 UTC

@nprofile…x4vu any idea on what is this error "Recipient wallet error. Please contact the recipient."? I have no idea and can't receive zaps, also I can't link my alby account on my albyhub, get a "Linked to another wallet" which I don't understand, nothing seems to work really 😔
https://blossom.nosotros.app/ea1e7ba2a5c4eb5aa6afbe646f5107eb1849afb03172e1a878100533a29605be.png

2025-09-08 16:18:23 UTC

- reply

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

2025-09-08 16:14:00 UTC

- reply

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

2025-09-08 15:50:30 UTC

- reply

Thanks, yeah this has been annoying, trying to figure out here, thanks for the heads up

2025-09-08 15:32:55 UTC

- reply

It's a bit more complicated than that, If you are tagging people (or quoting a note), the note will also be published the theirs inbox relays, so these people can be notified.
Your note will also be rebroadcasted to other relays you don't control as other people start to interact with your note, so there's no way to know where your note will ended up.
The "Seen on" indicator isn't 100% accurate and there's no way to make 100% accurate I think, current nosotros has a default value of 3 relays per person to fetch notes from for performance/bandwidth reasons, you can change that on settings which may impact the value of the tooltip.
Also changing relays settings makes things very confusing, but your relay settings looks good to me

2025-09-06 01:35:16 UTC

- reply

GN Anthony

2025-09-05 23:37:58 UTC

- reply

Just removed full line timestamp 🫡

2025-09-05 23:05:37 UTC

There's more, profile update is finally here with upload support, it's been embarrassing now having that until now.
https://blossom.nosotros.app/b8d374b057242281ff4c129b45222db6c655c3a13af8746e2811c6c300833d0a.png
https://blossom.nosotros.app/5b77b443da9d17d0d41a6b5ac8fedb6cf5666044224341b571626fff5dd05c8d.png
Also new settings page redesigned.
ps: yes, pronouns are supported now.
#nevent1q…gaq0

2025-09-05 22:45:46 UTC

https://dev.nosotros.app 1.3.0 is out, and now you can choose a compact layout for notifications, I personally never found the need for it, but apparently some people like it, so it's all up to you now
https://blossom.nosotros.app/be498f4414a2f252f555ec84abb9f609be02561d288f206714fa8c3ad9ae31c4.png
#nevent1q…hm5q

2025-09-05 04:23:38 UTC

- reply

Thanks for the feedback, are you using on mobile? on mobile I always show the tray before sending a reaction, which I agree can be a little annoying, but on the desktop you can just quick click on the heart button of the post it will send a heart reaction without showing you the options, I will see what I can do.

2025-09-04 22:29:06 UTC

- reply

Fixed and deployed at 1.2.1, thank you for the report

2025-09-04 22:28:04 UTC

- reply

Fixed and deployed at 1.2.1, thank you for the report

2025-09-04 22:22:14 UTC

- reply

Fixed, pushing a hotfix now, rookie mistake of me, really sorry about that

2025-09-04 22:22:05 UTC

- reply

Fixed, pushing a hotfix now, rookie mistake of me, really sorry about that

2025-09-04 22:16:47 UTC

- reply

Indeed something wrong, trying to push a fix asap

2025-09-04 22:16:29 UTC

- reply

Yes indeed, there's something wrong, trying to push a fix asap

2025-09-04 22:12:57 UTC

- reply

thanks, taking a look

2025-09-04 22:12:39 UTC

- reply

Thanks for the screenshot, let me take a look asap

2025-09-04 22:07:45 UTC

- reply

Certainly not, the following feed is for the people you follow, now I included topics if you follow any topics, which by looking at your account you don't follow any topics

2025-09-04 21:25:18 UTC

- reply

Only managed to published a new release now, sorry for the delay.
#nevent1q…h3rp

2025-09-04 21:24:07 UTC

https://dev.nosotros.app 1.2.0 is out.
* You can publish notes to a specific relay from the relay feed page (reactions and reposts will also be published there)
* If you follow hashtag topics you will start seeing them at the main feed.
* Option to auto update the feed when a new note arrives.
* You can bookmark notes.
* A bunch of bugfixes
full changelog: https://github.com/cesardeazevedo/nosotros/releases/tag/v1.2.0
https://blossom.nosotros.app/0663c50a71183933359baa2b5706fe8775e149a326219ff402ea0a426ecf3b2a.png
https://blossom.nosotros.app/bccdf1941a07b96224bd5baaea9a75bc616aad1f680b54ea5dca697000443717.png

2025-09-03 18:04:12 UTC

wtf threads has now a deck

2025-09-03 16:17:09 UTC

- reply

Yeah this makes sense, but at the same time the app doesn't work well with multiple tables due sqlite/opfs tab restrictions as only one tab can hold a reference to the db at the time, you can test yourself opening 2 tabs and will see the second tab will take 5 seconds to load the feed as there is no database there (a page refresh should be almost instantly).
I knew about this limitation when I was migrating to sqlite, and yeah kinda sucks, there's a few tricks to remedy that but not very straight forward, I will play with it tho.
Also, the scroll restoration should when navigating back, I am also working on configurable content width which will show more nested replies without having to navigate

2025-09-01 18:50:16 UTC

- reply

Yes sure, gonna change on the next version, don't know why I did GPL in the first place

2025-08-30 21:46:12 UTC

- reply

I am very bulish on turso, I tried to see if they have some for the web via wasm but couldn't find much

2025-08-30 03:43:56 UTC

- reply

Publishing to a specific relay has been achieved internally

2025-08-29 01:41:03 UTC

- reply

Absolute not worries, found a little issue here in my code but don't think it's related, keep reporting

2025-08-29 01:08:25 UTC

- reply

Yes, the "no elements in sequence" error is something related to the remote signer that I am trying to hunt it down, I don't think is related to relay feeds, I also just fixed locally broadcasting reactions/reposts to the current relay feed.

2025-08-29 00:53:50 UTC

- reply

not sure if I understood, but are you using a remote signer?

2025-08-29 00:35:38 UTC

- reply

Agree, it's a sick number, but also helps find impersonators if done right with a pagerank

2025-08-29 00:28:59 UTC

- reply

The client isn't publishing reactions to the current relay feed, it's only taking into account the author read relays, I am trying to push a fix here right now, as well with publishing to a specific relay (it's already possible, but too cumbersome, you have to manually remove your relays and add the ones you want to publish, needs better UX in the relay feed page).
Feel free to tag me at anytime 🤣

2025-08-28 23:51:34 UTC

Just pushed a bunch of fixes on dev.nosotros.app (v1.1.1)
I'm now fetching the follow list of any user in the profile page, hope in the future it can shows a bunch of useful stats, including followers count.
https://blossom.nosotros.app/85a704701dd0114e9a9af62d62a4bb7ab5a2a3d9badf2db115d94d0972a0d8c4.png
It also can render a follow list kind 3 event directly from a nevent in the url (tags ordered by the what you follows), you can also filter the tag type and follow all.
https://blossom.nosotros.app/5dec56324330acbf9ffff31757c28be52916c2b3a33dc6004da2091b4e5d1426.png

2025-08-28 20:56:49 UTC

- reply

Yes it does, auth on single relay feeds should display like this.
https://blossom.nosotros.app/46ebd601f57870dc5207aca52cf8e72f4a055fc2713713a9b3af4d26602bed33.png
I am trying to expose to the user in nice UX which relays is asking for auth instead of straight asking the user to sign, which is a little intrusive.
For outbox relays on the main following feed I don't auth automatically (at least yet), and I put all the relays asking for auth in the settings, and you can choose to automatically authenticate with them.
https://blossom.nosotros.app/08aac35c31e9f16852445ff11e5483c5cc3b710d2b140be1752052d764f5b897.png

2025-08-28 20:42:25 UTC

- reply

It was actually intentional because if matches the BG it was hard to see, but I tried increasing the opacity and the results was indeed better.
https://blossom.nosotros.app/113c24b86263533be8bd6e47f80fb6b444b35d42443d6233a003e753054d9d79.png

2025-08-28 17:17:56 UTC

- reply

Thanks, taking a look.

2025-08-28 16:16:12 UTC

- reply

Thanks, I agree lists should be collapsed instead of a pane, I will explore the notifications on the right too

2025-08-28 15:43:35 UTC

- reply

Try increasing the number of relays per user on settings and let me know how it goes, I put 3 as default and not sure if I should increase.
https://blossom.nosotros.app/98ed801a9416556b22fdbabfa78e255281b246daff463220e91d044cc883419a.png

2025-08-28 15:34:56 UTC

- reply

Thanks Vitor, that means a lot to me 🫡

2025-08-28 15:33:34 UTC

😱
#nevent1q…hn37

2025-08-27 16:40:53 UTC

- reply

thank you, let me know how to improve it, dev.nosotros.app has the latest version and is way much faster

2025-08-25 21:39:17 UTC

- reply

Planning that 🫡

2025-08-25 21:36:53 UTC

- reply

Yeah, configurable content max-width has been on my backlog for a while, I haven't I haven't experience much issues on refetching stuff when back on the page in the dev version, but will pay more attention, thanks a lot for the feedback, helps me a lot, don't hesitate to write me more of these, even if it's small ones

2025-08-25 21:31:55 UTC

- reply

Thank you, let me know if there if anything to improve it, I am planning to add new kinds soon

2025-08-23 17:11:59 UTC

- reply

Looks like a use case for nip66 and the g tag

2025-08-22 17:32:03 UTC

- reply

Thanks Gustavo, let me know how to improve in any way

2025-08-22 17:30:42 UTC

- reply

Thanks a lot Anthony for your support, I know you run a local instance, have you tried the dev version? lots has been rewritten, support for more nip/kinds will be added soon

2025-08-22 17:25:11 UTC

Give https://dev.nosotros.app a try again, it's weirdly fast, also working way much better on mobile as a pwa
#nevent1q…8aeq

2025-08-22 17:18:31 UTC

- reply

The core of the client has been rewritten to replace IndexedDB with sqlite-wasm, I intend to merge the main domain very soon as I keep finding small bugs.
#nevent1q…6mwu

2025-08-21 18:17:35 UTC

- reply

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

2025-08-21 06:34:38 UTC

- reply

put back nos.lol, relay.nostr.band and relay.damus.io as you were writing there before, clients might have issues founding your old notes

2025-08-21 06:30:13 UTC

- reply

Indeed don't use inbox.azzamo.net
https://image.nostr.build/95cde2d7c047d44c5db125ad2d5fa9d4cb55d671d34e630ee42701242b1416fa.png

2025-08-21 06:29:20 UTC

- reply

Thanks a lot for reporting, I fixed the image issue earlier today, gonna push a bunch of fixes soon after I wake up, I would not recommend you using a single relay for outbox and inbox, your list before was way better, I recommend you revert it.

2025-08-20 16:30:59 UTC

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

2025-08-20 16:27:00 UTC

- reply

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

2025-08-20 16:23:01 UTC

- reply

Where was the last client you updated your relay list? @nprofile…z543 some client is publishing relay lists with `relay` tags instead of `r` tags.
https://blossom.nosotros.app/fb2dce9b1628b8352c9f51803fe05c4cce1f79b811b5b2bfdd2bd71d7a2be140.png

2025-08-20 16:16:25 UTC

- reply

This might happen on the initial feed load, you should see the posts coming through like this.
https://blossom.nosotros.app/464b244acd35bebfffad6341c39b4fe6aef85fe2cffabfa5422808af0916dc93.png
but there might be a different issue, I can't find your relay list telling where you write your notes? then I can't find your follows list, have you setup the outbox and inbox relays?
https://blossom.nosotros.app/0451855967141dfb5e303821d7b839623091bcd570a09d0fa5b9cdf30f8378d2.png

2025-08-19 20:06:18 UTC

Spent the last 2 weeks replacing IndexedDB with sqlite-wasm on https://dev.nosotros.app (v1.0.4 c4364b29), most of the core ended up being rewritten, it's almost an entire new client, and I think it was worth it, everything feels way better and faster, I personally feel more lightweight with this release.
* New threads feed.
* New section in the sidebar to explore relay feeds (from kind 10012).
* Negentropy support for compatible relays.
* A bunch of other fixes.
https://blossom.nosotros.app/f92f796df6561068baf6a1b9c659c9bf8291d96fd171b3a97f3979675172cac3.png

2025-08-18 23:27:44 UTC

- reply

Thanks Anthony, I still don't know if this is the best approach but I had to come up with something to improve relay selection for outbox model, it's just way too much crap in people's relay list

2025-08-16 04:10:41 UTC

Can you access https://dev.nosotros.app (version: v1.0.1 b3853c53)? are images loading correctly?

2025-08-11 21:16:15 UTC

Trying to come up with the best threads experience for nostr, a feed of replies that load the parent and root note, and some information in between
https://blossom.nosotros.app/323b39bff127810ea97da11d5a11ba653bfa949c3b29c2ffec3bcfb03b8abf15.png

2025-08-08 16:17:37 UTC

- reply

I also open jumble from time to time haha, keep it up 🫡

2025-08-08 16:01:48 UTC

- reply

Thank you

2025-08-06 20:53:59 UTC

dear wss://nos.lol, enable negentropy or remove 77 from the supported_nips

2025-08-06 19:21:57 UTC

- reply

https://github.com/law-chain-hot/websocket-devtools

2025-08-06 19:21:37 UTC

How I didn't know about this chrome extension before? feels way better than the default network tab to debug websockets, wondering about the possibilities to improve it for specific nostr stuff
https://blossom.nosotros.app/fe3e68dbdc86f9a0151632ac00943046ea424c0d7c20424ae493264df734e06c.png

2025-08-05 02:21:43 UTC

- reply

About the material/hig conventions, I personally thing they are really important and I would strictly follow them to the book, but I think what is more important the navigation and gesture system, which is almost a way of life, normal and not so savy users can tell when something is off, UI style and colors can be customizable but you don't want to customize the gesture system.

2025-08-05 02:14:41 UTC

- reply

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