**New Nostros Release [v0.3.2.6-alpha]**
## What's Changed
* Add relay by @kroese in https://github.com/KoalaSat/nostros/pull/517
* Small performacne improvement by @KoalaSat in https://github.com/KoalaSat/nostros/pull/519
* Upgrade and fix by @KoalaSat in https://github.com/KoalaSat/nostros/pull/525
## New Contributors
* @kroese made their first contribution in https://github.com/KoalaSat/nostros/pull/517
**Full Changelog**: https://github.com/KoalaSat/nostros/compare/v0.3.2.5-alpha...v0.3.2.6-alpha
**Download**
🫂 thank you guys you just made my day. As the message says, I'm totally overwhelmed with reality but I'm always willing to get back to duty 🫡 In the mid time, stay safe and stack sats.
Happy pizza day!
Everyone is talking about spam, but no one mentions the poor design decision most of BTC services took by hiding from the user the option of setting your own fees and therefore contributing to a vicious cycle.
Hey #[0] is your service open source? I can't find any repo link on your webpage and I assumed it's not but I just want to confirm
Jodida está la cosa si tú fuente de ingresos viene de una empresa privada que tenga que ceñirse a lo que el estado estipula. Igual la gente que recién empieza pueda tener una opción pero muchos tendremos una carrera profesional y unos deberes que no podremos tirar a la basura.
I know it's my broken brain, but I always read "Puta vida"
I'm curious now 🙂 do you have any example on the code?
I'm also surprised Nostros also requires maximum 5-6, what's the quantity of subscriptions you were thinking on?
This is now implemented in the latest version 😄
Yeah that was the only solution I could figure out, I just didn't implement it hoping for nip33 to get updated and define groups. Probably I'll end up doing this.
Yes sorry, I meant to say event id. The point is, is there a way to know what's the kind of it prior to send a request to a relay?
Maybe NIP-19 got updated but I can't remember a way to specify a pubkey belongs to a group or to a Note. This is something I still didn't solved for Nostros. Is there any solution for that?
Maybe I'm a nostalgic and I miss when the protocol was really simple 😛 you can basically run with only NIP-1, I'm just wondering if there is a point where it's just too much for relays to deal with everything at the same time, everywhere
Nothing you can't do with a regular API call. It sounds to me like using nostr for the sake of using nostr.
I don't believe this kind of messages should be part of the protocol, adding every single edge case to the protocol over complicates it, overcrows network and relays:ñ; and slowly makes our private keys a single point of failure.
I just implemented a wallet in Nostros by using lndhub API calls and I never had the need of using nostr.
What happens in Nostros stays in Nostros, lightning payments included 😛
Sorry I don't understand, what you meant with your feed? I see nothing wrong are you talking of the view of the note in Amethyst or about the note raw data?
New Nostros Release v0.3.1.9-alpha
What's Changed
• FAQ
We are trying to create an in-app help for newcomers. If you know Nostros and want to contribute contact us!
• Libraries updates and reported bugs fixes
Download
Unethical sending fake zaps? I believe it's a really good exercise. What can be broken, should be broken.