Nostr Web Client

Esse Brave tem uma questão de enviar telemetria. A algumas críticas a eles a respeito disso

Aí já não sei, mas acho que tem como configurar para não enviar informações.

Replying to

Itamar Campos

Usei por dois meses. Ideal pra quem gosta de customização, mas com o tempo aquele monte de opções em novas abas deixou de me ajudar e começou a me atrapalhar.

Viu como simplicidade é o segredo? Por isso o Jumble sai na frente.

Replying to

Estou usando o Tor. Queria ver outras possibilidades

Tem o Tor browser né ou até mesmo o Brave tem Tor integrado.

Replying to

Aí que está, o cody trabalha melhor que uma equipe inteira, rs. É preciso saber quem está por trás dos projetos e o nivel de dedicação da pessoa.

Óbvio que no caso do Vivaldi eu não conheço, mas posso afirmar com quase 100% de certeza que eles não tem a estrutura econômica e de pessoal de outros navegadores mais populares.

E outra, no caso do Jumble. não existe um cliente comparável. Mas se tivesse um cliente com uma equipe com 10 Cody's, contra o Jumble com um só Cody, óbvio que o Jumble perderia.

Replying to

Mesmo argumento que uso contra o Jumble. Entendi.

Aí que está, o cody trabalha melhor que uma equipe inteira, rs. É preciso saber quem está por trás dos projetos e o nivel de dedicação da pessoa.

Óbvio que no caso do Vivaldi eu não conheço, mas posso afirmar com quase 100% de certeza que eles não tem a estrutura econômica e de pessoal de outros navegadores mais populares.

Replying to

AgenteP

O que seria "aportar"?

Investir em algo, comprar ações, Bitcoin ou qualquer outro ativo.

Replying to

Já mas a lógica é a seguinte. Qualquer app ou software precisa de equipe de desenvolvimento, logo dinheiro e etc. Manter o desenvolvimento de um navegador custa caro e não é para qualquer um, além disso, um navegador é uma ferramenta importante e que deve sempre estar sempre atualizado contra vulnerabilidades. São poucos navegadores que tem esses requisitos e eu acredito que o Vivaldi não seja um deles.

Logo se você não tem ganhos nítidos ao migrar para um navegador, digamos, menos popular, não faz sentido ao meu ver mudar.

Replying to

Já usou?

Já mas a lógica é a seguinte. Qualquer app ou software precisa de equipe de desenvolvimento, logo dinheiro e etc. Manter o desenvolvimento de um navegador custa caro e não é para qualquer um, além disso, um navegador é uma ferramenta importante e que deve sempre estar sempre atualizado contra vulnerabilidades. São poucos navegadores que tem esses requisitos e eu acredito que o Vivaldi não seja um deles.

Replying to

Alguém usa o navegador Vivaldi ?

Esquece. Vá de Brave mesmo e está tudo certo.

nostr:nevent1qvzqqqqqqypzpc208ca5amdzt0qe8d6d6nrvshzfemnky23yr0ev9znpmjp94fneqy08wumn8ghj7en9v4j8xtnwdaehgu3wvfskuep0d3skuee0wp6qqgxyr8a37mavvcqk855veu3ejleqj6m5anqkprtw6kl9w700sq2ehcdlgwaa

Só abrir o Amethyst então.

Replying to

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

this_is_the_way.gif

Was this gif to load nostr:npub1syjmjy0dp62dhccq3g97fr87tngvpvzey08llyt6ul58m2zqpzps9wf6wl ?

Replying to

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

i think it's because it's small so it hasn't got overwhelmed with complexity but maybe you need to have a look at organising it before new features because this last week i've noticed a few bugs creeping in. feeds not loading, some events not publishing (even to only two relays), and a few other quirks.

you would have a good excuse to tell all the feature requesters to shush for a while also :)

I agree of not having new features for a while and focus on bug fixes and usability.

Replying to

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ

what would be better is a queue that just tries, when it succeeds, remove the item from the queue, and retry the others with an increasing delay until it's like 5 minutes then give up

What I don't understand or what I don't want to understand, haha, is:

Why we don't have a way to know if our reply was or not published on a read relay of the person we are replying? Because if we know that it was not, the Jumble UI could show a warning that the user we replied didn't get a notification and maybe show a way to try to notify the user.

Replying to

I just would like something like:

1- The person has for example four write relays, he reply someone, goes to only one relay. The UI show a message like: Reply tent to only one relay of four that you have. Do you want to try to send to the others relays or skip and send to just one?

*reply sent

Replying to

That said, it’s true that Jumble marking a post as successful after just one relay accepts it isn’t ideal. I’ll adjust it so it only shows success once maybe a third or half of the relays have confirmed.

I just would like something like:

1- The person has for example four write relays, he reply someone, goes to only one relay. The UI show a message like: Reply tent to only one relay of four that you have. Do you want to try to send to the others relays or skip and send to just one?

Replying to

Maybe it’s just that the other person set unsuitable relays, or maybe only one or two relays failed — should the user really have to see error messages all the time for that? In most cases, a few relay failures aren’t a big deal. If you need absolute reliability, that’s what centralized platforms are for.

Understood. Thanks for taking time to always explain me things.

Replying to

JOE2o

>I don't know, I think it's a serious problem if someone mention me and I do not receive notifications when I should.

This is just life on Nostr I think. We can either accept it or move to another decentralised network that takes different trade-offs and where this doesn't happen.

I think the UI could have more explains to the user when these things happens.

Replying to

It’s hard to track reliably, and in some cases certain relays are simply unreachable.

If be unreachable, would fail again and the user will know, no?

Replying to

If every client were the same as Jumble, nostr would be way too boring. Please don’t discourage developers from building around their own vision.

I don't. I think he should customize it. What I don't like on other clients it's usually the basic things don't work and this is frustrating. If a client have all basic things working well, I totally agree people should start innovating, making things differently..

Replying to

There are too many possible points of failure. All I can do is try to make sure any mentions of you from your read relays show up, and do my best to pick suitable relays when publishing events — but I can’t guarantee delivery success.

I don't know, I think it's a serious problem if someone mention me and I do not receive notifications when I should. Maybe could have some logic that when this happens, the client ask to the user retry to republish? I mean in the case where the user was using Jumble client too. For example: The user click post and close Jumble without waiting to publish to all relays. So the user open Jumble again, and maybe should ask to republish to all relays that the post should have be published?

Replying to

Sirius

If jumble’s nostr system is better than ndk, one-off fork could make sense. But probably Iris & Jumble philosophy and UI direction are so different that the forks would not be kept in sync.

Yes, but the basics features of Jumble are almost complete developed and working very well. Maybe you could fork and just start customizing according to your desires? But I don't know, I'm not a developer. I'm just suggesting things that make sense for me.

Replying to

nostr:npub1g53mukxnjkcmr94fhryzkqutdz2ukq4ks0gvy5af25rgmwsl4ngq43drvk please fork nostr:npub17n4cuc4d6y6qh89dekvxrenfkt5s0n49xns00uavjaxpr36c55dq87fyh9 code and add the features you like on Iris that doesn't exist on Jumble, like the custom feed and other things. I think make more sense.

Jumble is more stable and with less bugs than Iris, so make sense use Jumble codebase.

Replying to

https://blossom.primal.net/24f443039b4c478557b7fe99dc55972756565653ccc0a622aef8d8d1d378991e.mp4

My feed just don't load.