Cesar Dias

Building https://nosotros.app

Public Key

npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c

NIP-05 Address

_@nosotros.app

NIP-57 Address

cesardias@getalby.com

Profile Code

nprofile1qqsvvcpmpuwvlmrztkwq3d6nunmhf6hh688jw6fzxyjmtl2d5u5qr8spz3mhxue69uhhyetvv9ujuerpd46hxtnfduq3samnwvaz7tmjv4kxz7fwdehhxmm5wfhhxtnpwpcq2c0lsd

Publishing to

relay.damus.io

relay.nosotros.app

nostr.mom

Author Public Key

npub1cesrkrcuelkxyhvupzm48e8hwn4005w0ya5jyvf9kh75mfegqx0q4kt37c

Show more details

Last Notes

2025-05-03 16:23:46

- reply

Dr pepper is underrated

2025-04-26 16:24:16

- reply

When I was working on nostr-editor I have found this a huge mess and I eventually gave up. I was actually trying to link directly in the "dependencies" instead of overrides, then I tried with the pnpm link command, both kinda worked but then broke for some reason, there was also issues with tiptap versions which i didn't bother to try to understand, I think I would avoid this and try some other approach.

2025-04-18 19:21:10

I am currently being held hostage by a service worker who is refusing to update my app.
It works if I refresh the app with command+shift+r, but then If I refresh with just command+r it goes back to the old version.
I don't know what to do anymore.
And it's not like I can push a fix as the fix won't be updated nonetheless, I thought I had fix this problem some time ago by calling `self.skipWaiting()` which forces the service worker to activate, but still doesn't work, I don't want to manually update the service worker on the browser settings as it will only work for me.
It's a nightmare

2025-04-18 18:46:31

I think i'm gonna take some vacation to code some ocaml

2025-04-18 01:31:29

- reply

Fascinante

2025-04-18 01:04:01

WTF!!! brazilian pizza is out of control
https://blossom.nosotros.app/e91301cc8e8a1126ec9eae3b802318cd2a44e8b24c5a54f24827bc1d808e639b.png

2025-04-18 00:47:43

- reply

This label is incorrect, the outbox relays are actually the ones you writing into, I just fixed and will go on the next version, it's just the label tho

2025-04-05 20:58:39

- reply

Está tudo correto nos relays, devem ser o clients mostrando informação antiga, vai atualizar eventualmente
https://blossom.nosotros.app/c283a55d7457cf7991dc2952d3c52724aa51eac08d2dff13b1114778175ada5b.png

2025-04-05 20:33:26

Maybe the outbox model won't be enough and clients should indeed be setting additional relays, maybe not.
#nevent1q…kfq2

2025-04-05 17:46:05

- reply

Tentei avisar, mas provavelmente não viu
#nevent1q…ul4m

2025-04-04 21:56:28

- reply

Next version of nosotros will work, now I can't see your inbox events as read-only because your single inbox-relay is asking for auth
https://blossom.nosotros.app/fa57c94695f4a526a8915787c58105f5794fe338f58fe2bed514048d21c8bb52.png

2025-04-03 17:50:33

- reply

Boa tarde, remova algo.utxo.one da sua lista de relays, alguns clients não vão funcionar direito e não vão achar seus posts, e coloque wss://relay.damus.io, wss://nos.lol e wss://nostr.mom
https://blossom.nosotros.app/ef29fad1c01b8d46a3f7b78f65cea9bff1b3e065a5e96b368e1fa5534ab2b85b.png

2025-03-31 17:06:20

- reply

Oh, I thought it was a fake Alex, i'm checking now, a fake Ross Ulbricht messaged me the other day you know 🤣

2025-03-28 02:01:03

- reply

Totally agree

2025-03-27 19:09:17

- reply

Got it, then it makes sense for live subscriptions

2025-03-27 17:58:44

- reply

This gif is also really nice.
https://video.nostr.build/e2536a24789e20584e6d49cce9c078a99a75ec0a58e3b0c638931584a8117bbb.mp4

2025-03-27 17:57:46

- reply

RxJs is a mental journey, so embrace it haha, I know you do a bunch of functional programming throughout all coracle code, rxjs will just fit if you embrace it's declarative approach, like your `await tryCatch` function is kinda rxjs `catchError`.
If you have any other question or want to schedule a call just let me know

2025-03-27 17:54:17

- reply

wow, this is looking really good, just found weird req returns "EOSE" | NostrEvent, If I want to listen for "EOSE" I would listen on subscribe({complete: () => {}}) or `finalize` operator, but might going to steal you waitForAuth, I am think I am gonna need it 🤣

2025-03-27 17:39:09

- reply

I am don't have yet, gonna try to push something later today, I'm currently underwater with a unrelated refactor 😭

2025-03-27 17:36:08

- reply

Thanks for the code, just doing some quick code review here.
I think the first issue I spotted is the assigning a stream send$ to itself `socket.send$ = send$.pipe` try to think some other way to do that, it's very easy to compose multiple observables that derives from the same source in a functional style.
I would do something like on socket.ts
```ts
this.socket = webSocketSubject('...')
this.events$ = socket.pipe(filter(msg => msg[0] === 'event'))
this.auths$ = socket.pipe(filter(msg => msg[0] === 'AUTH'))
this.authsJoin$ = auths$.pipe(filter(msg => msg[1].kind === 28934))
this.oks$ = socket.pipe(filter(msg => msg[0] === 'OK'))
```
I would also remove the `authState.subscribe` for something like `return authState.pipe(tap(() => {}))`, but AuthState is a subject with a bunch of subscriptions inside there... hmmm, that's a bit bad, by looking at the commit history you basically kinda ported a event emitter system to rxjs right? you gonna have to embrace some heavy changes to see the gains of rxjs.
Try to think this way, let's say you have a single nostr subscription to a single relay, this subscription has all sorts of complex policies attached to the main stream, the main stream is also connected with other subscription stream like getting each user for each note in the main stream with also their own set of policies, then you decided to call unsubscribe() from the main stream, then the entire pipeline is unsubscribed and garbage collected, nothing left, with your current approach I am not seeing this happening, you might ended up with some parts of stream still listening for changes, unless you complete/unsubscribe the streams manually in multiple places which is a lot of work, which is something you have to do with event emitters.
I also did these exact mistakes a year ago, so I really don't judge you 😅
this angular tutorial describes really well the issue.
https://www.youtube.com/watch?v=bxslNFZvOvQ

2025-03-26 20:53:32

- reply

Yes, relayFilters stream approach was something that I came up with the outbox in mind, it's been very useful and easy to split filters of a single subscription, I also designed in a way to work batching multiple unrelated subscriptions together, everything becomes a queue at the end consumed by the start() operators, this approach has been working really well for me and haven't touch much in a while.
rx-nostr is indeed too tightly coupled and when I started my mind was mainly focus on the batcher.
The way I been designing things is the core the be completely stateless and lazy, you can create a subscription and the core will never initiate any subscription for you, just like rxjs itself wouldn't, it just gives you the building blocks.

2025-03-26 20:52:45

- reply

Working with websocketSubjects has been very easy and flexible, I can even push messages before the websocket was connected and the subject will buffer after connected.
webSocketSubjects just like the other subjects are multicasted.
this will only open 1 connection no matter how many subscriptions you have
```ts
const relay = webSocketSubject('wss://relay1.com')
relay.subscribe()
relay.subscribe()
```
now creating multiple webSocketSubjects it will open multiple connections.
webSocketSubjects multiplex will make a unicast subscription, this will make multiple nostr subscriptions in the same connection.
```ts
const relay = webSocketSubject('wss://relay1.com')
const sub = relay.multiplex(() => ["REQ", <id>, <filter>], () => ['CLOSE', <id>], (msg) => msg msg[1] === <id>)
sub.subscribe()
sub.subscribe()
```
You can pass the webSocketSubject as you wish as it's also a observable, I store relays as webSocketSubjects in a Map<string, Relay> in the Pool which doesn't do anything special, just blacklist relays with errors so it doesn't try to connect again.
Current my core/pool is doing the relay subscription which is incorrect, the consumer should be responsible to initiate the relay connection because he could put any policy mechanism for a particular relay, something like a rxjs retry to reconnect or some auth policy, currently my pool exposes a open callback and we could do something like this (pseudo code)
https://blossom.nosotros.app/083aa9e2210b20a732c61b0a2a8ec194be3386b3414db73c88068632fa8f188b.png
I am still working on auth and trying to think about some flexible way to do it, I'm a little bit hesitant to replay old messages after a a successful auth as I need to store these messages somewhere, but here's a small authenticator (which I think I should rename to createAuthPolicy or something) what takes a pool, a signer a options like whitelist which is an observable as the user can whitelist a observable after the auth was received.
https://blossom.nosotros.app/7def525444a780d4f31c001003146b54b774009d7129dd4339e4700bd0e93af5.png
Still half backed as I am still testing locally

2025-03-26 18:28:21

- reply

Highly recommend rxjs, it's been an incredible journey for me and I had to learn some things the hard way.
After a heavy year on rxjs, I manage to build very complex pipelines with have very little state (variables) and close to no imperative code, I kinda got to a point of no way back.
Your approach of takeUntil is totally correct, which is the rxjs way of doing things, a powerful advice to rxjs is to avoid Subjects at all costs, they deviate the concepts of reactive programming and forces you in the imperative approach, people using rxjs with only Subjects aren't really using rxjs at all, just a fancy event emitter (the meme), there's a reason why xstream (a alternative library to rxjs) called their `next` function `shamefullySendNext` (yes, there's use cases for Subjects)
I have no issues with typescript in rxjs, it works pretty well and point-free operators would work just fine, I have issues naming things properly.
You have to be careful as well where you subscribe to the observables, it should be the final stage and usually close to the UI, and unsubscribe when the ui is "unmounted".
I was writing this document for @nprofile…aql4 the other day but never had a change to finish, which is my client approach for nostr subscription in rxjs https://github.com/cesardeazevedo/nostr-observable, the idea was to have a 100% stateless library for nostr.
This file is how I handle subscription and everything else is built on top of it https://github.com/cesardeazevedo/nosotros/blob/main/src/core/operators/subscribe.ts
If you have any questions don't hesitate to ask, I would love to help anything rxjs related.

2025-03-23 20:39:35

I think I am getting owned by relays urls ending with a slash

2025-03-19 21:47:52

- reply

Está funcionando muito bem com TS e com todas as features de LSP, goto definition, renaming e afins.

2025-03-18 18:44:46

- reply

That's why I use react-strict-dom

2025-03-16 17:48:08

- reply

Eu também uso vim a muito tempo, acabei largando por outras ides depois meu sistema de configuração simplesmente ficou impossível de configurar pra LSPs e outras coisas, eu não aguentava mais vimscript, voltei pro vim faz um ano (agora com neovim), e estou usando o LazyVim, sempre tem alguns probleminhas mas tem me atendido bem, a configuração do folke é um pouco chatinha.
Atualmente estou portando ao poucos as coisas que eu realmente uso pro kickstart.nvim, que é bem mais limpo e assim consigo ter controle 100% do código

2025-03-16 05:50:34

- reply

Obrigado Anthony, testes está meio que salvando o projeto aqui com algumas mudanças que estou fazendo, nova versão vai ser beeem melhor e um pouco diferente em termos de navegação, vou tentar lançar uma versão capenga em breve, preciso lançar as coisas mais rápido, keep building 🫡

2025-03-14 19:57:52

- reply

Appreciate Anthony, really kind words, there's a few things that I am getting close, I did a lot of improvements in the relay selection that fiatjaf had complained, which reduced a lot the number of websocket connections, just need more unit tests and publish.
I am also coming up with a new rich sidebar with dynamic menus for relay feeds and other stuffs, among many other things.
Thanks for the words of encouragement, it really helps moving forward

2025-03-14 17:53:24

- reply

Appreciate your support and recognition, but I think nosotros isn't ready yet, or at least right now, if nosotros will be added to njump or others, it will happen naturally and without asking

2025-03-14 16:33:32

- reply

I'm using docker, guess I just learned something new today, just restarted the container with the restart policy, muito obrigado e bom final de semana aí também

2025-03-14 16:05:38

- reply

It's back, no sure what happed, the container simply exited with code 255 🤷‍♂️
I am doing well btw, hope you doing too, thanks for reporting

2025-03-14 15:58:56

- reply

my imgproxy likely exploded or something, checking right now

2025-03-13 18:32:31

- reply

This is amazing! Nostr devs should organize a game jam for a weekend and develop a game on top of nostr

2025-03-13 18:29:52

- reply

With observables you have a lot more flexibility to do really cool stuff (specially with all the useful rxjs operators), I managed to avoid a lot of state and imperative code on my code base, here's a simple nostrify wrapper example
https://blossom.nosotros.app/011296f3bf1e02ac0ace853460e3cb244c1b5da1f6d2fac429cd432531eb71ac.png

2025-03-13 16:47:01

- reply

I miss the smell of char siu everywhere in the streets

2025-03-13 16:43:31

- reply

Looking really good, what are you using? I really like the avatar as a replacement for "@", might use this idea haha

2025-03-13 02:09:08

- reply

Thanks for the feedback, makes sense

2025-03-09 19:18:30

Sometimes I want to abandon everything, get back to gamedev and work on the game I did in college, The Four Horsemen of the Apocalypse
https://blossom.nosotros.app/032a376c05787625015eee7262256e8404843a8c76f6c3416938b866c60ea5f7.jpg

2025-03-09 07:00:31

- reply

vibe coding let's go!

2025-03-05 23:07:17

- reply

gm!

2025-03-01 22:17:52

- reply

Appreciate the feedback, will investigate, I have some better direction now

2025-03-01 18:17:52

- reply

O plebster resetou meus dados no delete, reconfigurei agora, espero que esteja funcionando

2025-03-01 18:16:32

- reply

Agradeço demais o feedback, de coração, vou implementar links pra outros apps em breve (NIP-89)

2025-03-01 18:14:05

- reply

If the column is a note column (instead of a feed column), clicking in a reply link (the date of the reply), it will replace the current column with that reply, which will basically flat the reply tree into a single thread, I did this because I wanna leave the feed intact otherwise I will have to deal with scroll restoration, you already can expand comments in the main feed without opening a new column for that note.
Also back buttons for a desktop/web app is very annoying in my opinion.
I am currently not muting hashtags, just authors, but will get it done in the next release.
Really appreciate your feedback 👊

2025-03-01 18:03:05

- reply

Eu entendo seu comentário e a situação dos clients hoje, a única forma de resolver isso é manter os clients menores com features mais específicas ao invés de fazer tudo, eu quero focar o nosotros em algumas features mais focadas pra outbox e outras coisas relacionadas a relays, estou criando um feed pra home só com relays da lista de pessoas que segue e não faz parte do relays delas, que talvez possa achar notas que você não tenha visto, em fim, não estou lá ainda. No final os clients sempre terão alguma feature ou outra que overlap entre eles.

2025-03-01 17:51:49

- reply

Em breve vou colocar o numero de contatos em algum lugar, assim te ajuda a saber se a lista está ok, outra coisa é que estou explorando a ideia de finalmente adotar uma sidebar de verdade, meio que tenho evitado a ideia

2025-03-01 17:48:13

- reply

Nossa, era pra ter respondido em português, foi mal.

2025-03-01 17:37:50

- reply

A data do comentário é um link, isso ira transformar o formato de árvore para uma única thread, isso ajuda quando a arvora tem muitos níveis de profundidade, espero que isso seja fácil de entender

2025-03-01 17:34:50

- reply

Yeah I know the issue, has been annoying indeed, gonna fix that soon.

2025-03-01 17:33:46

- reply

That's indeed incorrect, gonna fix that asap

2025-03-01 17:32:00

- reply

I don't think I want to implement DMs as I want the keep the client small as possible (I already feel is getting big with kind20 and deck mode), notification badge is partially implemented already but not very real time, live feeds with income counting are coming next and things will feel more realtime, need to dissect NWC spec, maybe it's not that complicated as I thing it is
https://blossom.nosotros.app/7e19899c3f2de52caba23f0a3e9685dac99dd8688c640ed884273f856c854155.png

2025-03-01 17:26:01

- reply

Can you remove the pwa app and recreate again? previously on click was just expanding the post replies, now I am doing a proper navigation, back button should work now

2025-03-01 17:23:25

- reply

I am actually loading parent notes of replies from people you follow so it adds more context of that reply, but I am considering not loading parent notes at all as your feed might be too intrusive. relay feeds columns is supported now (v0.1.2 last update: 27/02/2025)
https://blossom.nosotros.app/9e4a26c76a8bd593ef726565630a8266c29736ba1df00187fc472a7783c4aa20.png

2025-03-01 17:16:29

- reply

Estava quase começando a implementar isso esses dias, acabei me distraindo com outras coisas.

2025-03-01 16:49:37

How to make nosotros.app better? what you would like see there? what do you hate about it?

2025-02-28 21:01:40

- reply

I just figure it out
#nevent1q…ha53

2025-02-28 21:01:22

- reply

Thanks I just figure it out
#nevent1q…ha53

2025-02-28 21:00:43

- reply

I have figure out, my bad, it was a `deleted:true` property in the kind 0 content that was merged, I manually removed in the json and manually broadcasted, all good now

2025-02-28 20:19:50

- reply

Yes, but still can't login on primal on ios, can't find any kind 62 from me anywhere, the alert makes no sense to me.

2025-02-28 17:50:10

- reply

De praxe

2025-02-28 16:57:47

Did I accidentally deleted my nostr account? Primal says so.
I found out my account was logged in a app called Plebstr (now openvibe) in a old android emulator, something I did right when I joined nostr in 2023 for testing, I couldn't find a simple stupid logout button so I ended up clicking on delete account, which I thought it would acted as logout and it did.
But Plebstr actually replaced my kind 0 metadata with a name "deleted account" which I quickly reverted, now, what else it Plebstr signed and broadcasted? a right to vanish kind 62? I can't find it on any major relay, so I don't know, and can't login into Primal on ios.
I thought the delete account button wouldn't have major impact as I have my nsec and run my own personal relay, so @nprofile…q4ys where this information is coming from? any help?
https://blossom.nosotros.app/0b63f55c670300472612385bcd946e24692a6ce3b78125e75c46ee396adc21c0.jpg

2025-02-28 14:58:34

- reply

Thanks Derek 🫡

2025-02-28 14:42:33

GM.
nosotros.app (v0.1.2) has been updated from dev with new stuff.
- kind 20 feeds with multiple uploads
- blossom uploads
- signin with nostrconnect qrcode
- search of users and notes
- relay feeds
- new deck columns (search, kind 20 images, hashtags, relay feeds)
- lots of other improvements and fixes

2025-02-27 17:19:51

Giving expo a try again

2025-02-24 16:34:42

I miss kaneelbroodje

2025-02-24 16:24:20

- reply

nosotros supports at https://nosotros.app/?relay=wss://algo.utxo.one

2025-02-22 21:24:38

- reply

thank you

2025-02-22 21:24:01

Native observables are coming
https://x.com/benlesh/status/1893053275995357608?s=46&t=Gcnc8IvM2RrI7sbuEtFg6g

2025-02-22 17:55:37

- reply

nostr:@nprofile…qejw

2025-02-22 15:45:02

- reply

GM Terry

2025-02-22 15:43:11

- reply

GM derek

2025-02-19 17:40:52

- reply

Really sorry about that but this was already fixed, it was a bug in the editor when pasting images

2025-02-18 23:16:28

Just freed around 650GB of my very old Hackintosh
https://blossom.nosotros.app/3ff0e2b1dc3a27692ce7c791dbf5924d78c6039ce9b4139f1c8cdb4c56eb0559.png

2025-02-18 00:18:49

- reply

I miss NYC

2025-02-17 21:40:07

- reply

There's any changes on welshman/content that I should know? (I got rid of nostr-editor parser on my client for welshman 🤣)

2025-02-15 17:56:43

- reply

https://github.com/fiatjaf/khatru

2025-02-15 16:21:41

- reply

The nostr-editor already handled blossom uploads, just had to add UI and settings, but had fun spinning a blossom server

2025-02-15 03:02:17

Got a little bit distracted playing with khatru lately, it's so good

2025-02-15 02:34:20

- reply

Testing
https://blossom.nosotros.app/bbbbe3ba78f263c38b803048a12b75a7ae19873d4dd8c0624eab0e6fa5daf858.png

2025-02-15 01:03:19

Works!

2025-02-14 18:20:38

- reply

Hmm, you're welcome, but what happened? 😅

2025-02-12 23:56:30

- reply

Very soon, I am need too.

2025-02-11 02:41:34

- reply

Fixes are coming, what method are you using?

2025-02-09 19:33:11

- reply

That's great, I am on GMT-3 (BRT), let's try this Wednesday so I can prepare some documents/code with insights

2025-02-09 18:31:49

- reply

I will try to write something about my thoughts on rx-nostr and applesauce and my approach for subscriptions, but basically my approach is more outbox oriented, and relays are observables which helps discover relays on the fly as the subscription goes, I think I did something really flexible with very little lines of code.
I didn't went deep on applesauce, from my understanding its a lot more than a subscription handler.
I would love to jump on a audio space and share my rxjs journey I been through the past 12 months

2025-02-08 14:37:45

- reply

I am not sure if I understood you comment actually

2025-02-08 14:27:33

- reply

My pagination range is 4 hours, works well for most accounts, but won't work well for accounts with low activity, profile feeds are much higher ranges, I am still looking for a better solution limited base, but I struggled to get the until value.
I use RxJS extensively throughout the codebase, and I have very little use of promises, my subscription approach is all on top of webSocketSubject + multiplex which makes everything easy and almost no imperative code, also very easy to write unit tests, would be happy to talk about it.

2025-02-08 04:49:03

- reply

Ooooh got it, then makes sense, it's just basically my own following list, which is certainly not ideal, I want some sort of algo relay feed but a generic one for everyone, without AUTH

2025-02-08 04:18:42

- reply

Interesting comment 🤣, but the client doesn't have any algorithm for the feed nor backend cache service, all the feed data comes from the relays or IndexedDB (in case it was already cached)

2025-02-08 04:13:11

- reply

Obrigado demais Anthony, quando a DMs eu não tenho muito interesse no momento, vou esperar um pouco até o client estiver mais estável, também tem a proposta de DMs via MLS (NIP-104), não sei como vai ser, quanto a blossom eu já meio que estou precisando no momento para postar algumas fotografias com meu servidor próprio.
Se tiver mais mais alguma feature ou mudança é só me avisar.

2025-02-08 03:19:34

- reply

The main feed isn't fully sorted, I don't think the main feed needs to be fully sorted by date, most people are very used to heavily algorithm feeds to care about a strict chronologic feed, notification feed makes more sense to be fully sorted.
There's a RxJS bufferTime operator on the feed event stream to update the feed in batches of 500ms (which also helps avoids unnecessary re-renders), so let's say we have a batch of 30 notes, I sort these 30 notes by created_at, and insert them at the end of the feed, the next batch the same, if a slow relay returns new events, it will be just added at the end of the feed, without impacting what the user is reading.
The approach works best with timed range pagination (until + since) instead of limit based pagination (limit, then look for a until date), I tried to implement a limit based pagination way too many times but always run into really annoying issues like huge pagination gaps, also the limit approach doesn't work well with the outbox model as you will split a filter of 1000 authors with a limit of 50 events, you ended up with way more than 50 events.

2025-02-08 01:52:07

- reply

Thank you so much for the zap, really 🫡

2025-02-07 21:29:53

What an incredible day to me on nostr, and to finalize, I have a date 😱

2025-02-07 19:32:34

- reply

Yes, it's NIP-66, unfortunately the video didn't loaded a good relay monitor (i am just selecting the first monitor to appear), but the idea is to show you the people you follow what relays they are part of sorted by the number of people.
https://image.nostr.build/1a2180db1c1cfa00eb79fd77850d3ecc75f5a66af7299edc0ea9ef27b3850ce5.png

2025-02-07 19:25:06

- reply

Love the video, yeah, I think 90% of the issues on the video were already fixed in dev, I left the editor functional for non logged accounts because I wanted to implement post anonymously and people could easily test the nostr-editor, feeds are a lot faster too, really appreciate that.

2025-02-07 19:15:27

- reply

try on https://dev.nosotros.app instead

2025-02-07 19:15:03

- reply

ps: anyone willing to try nosotros try on https://dev.nosotros.app instead of the main domain, it's has a lot of fixes and it's way faster and lightweight

2025-02-07 19:13:54

- reply

Thanks a lot man, I really appreciate it, I certainly inspired on Coracle on some things, although it's not there yet when compared to coracle as a whole, still needs some adjustments specially on the outbox model, but here we are 🫡

2025-02-07 18:53:44

- reply

Thanks a lot Carlo