Home relay is the relay that has your notes for everybody else to get from.

General is where your Amethyst will use to get posts from your follows.


Bem vindo!


First look at the iPhone 17 Fold Max. https://image.nostr.build/01bc28c7f2cc20853d8c2aed9e9de407b8b7c9b344c57dae3dc65b0b5a91327c.jpg


What is this?


If it's not open source, it's not private.

If you can't choose to use your own server, it's not private.

If you can't use it when the company is gone, it's not private.

If you can't create anonymous accounts, it's not private.

Stop trusting the marketing. Start verifying.


Does he/she know Kotlin? :)


How do they make those cool videos in the webpage? It's so good.


They are available in the discovery section via DVMs, so we don't centralize on our own server :)


Do they have good libs for Android apps?


Yeah I never ended up finishing the zap verification implementation. Maybe one day .


Super interesting


Is pglite wasm faster than the browsers native DB (SQL lite?) ?


Yep, Connections / Add Connection on your hub.


Hum... what's the number of nuts that will force me to code a Nut wallet into Amethyst. 🤔 😎
nostr:nevent1qqs878hcc4qrjkzgm3cv0uslg4rhv89pqr8ghxjrtf72pnea92nu8ncpzpmhxue69uhkummnw3ezumt0d5hsygzsm98u9kzcp35zkpc62shck8335gqtq5yt4w26xwl0pp2a72qavvpsgqqqqqqsqc9fde


Or just simpler things like content discovery DVMs that must follow certain filters and must prove that they run the filter without any changes to it before sending the feed back to me.


Yeah, but in order to assemble the massive filter, you have to download all contact lists, which I already don't like doing. It compounds with the massive filter.

I am building custom feeds for Amethyst and I was wondering if we could build a feed event and then make a REQ by the feed event id that the relay already has. That would be nice. We could then do a follows of follows of follows of follows filter.


Just sent you (I think) 150 sats via the demo


Just downloading them and processing on memory is already a pain.


I know, but Smart Contracts don't necessarily need a token.


Nostr smart contracts are coming.

Then we add verifiable computations.

And boom. Trustless machines for everyone.
nostr:nevent1qqswm26c4s4h56zwkk47w40mhsqqn66jk6lfas8r07w67h69474kkfgpzpmhxue69uhkummnw3ezumt0d5hsyg8zenmu7gzq8ulj5jj4kv50ph3muwz43f747vmr9ld2alrjdswgavpsgqqqqqqsdwaqz2


If the wallet supports NWC, it should give you a url to paste in the zap setup screen. Most wallets don't support it.

If you want to pay by openning the app every time, just delete 3 fields for the NWC connection.

You can always go back to Alby by pressing the little alby button close to those fields.


We need to change this interface. It's just hard to figure out. Maybe there is a floating + button on that profile tab, which opens a new screen that has a feed for all posts with images on it. Or maybe it is through Search. Or just upload the image again. 🤔


Are you also starting and stopping Tor on onResume and onPause? I thougtht it would create some issues, but it seems to be working just fine.


Sure thing! Let me know what works for you.


That's the goal


Image and video servers can see your IP.


What's the best one? I have only used nutsack. 🤔


It's likely going to be using both at the same time for the vast amount of users.


Yeah sorry. We will get there as well. These relay lists are kinda changing everything :(


Then he can just turn Orbot off.


Yeah, the new settings kinda fucked things up for global. I was trying to code the custom feeds that nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs had but I wasn't able to finish. The idea was to create multiple options in the top bar for distinct relay set options on global and for each hashtag/geotag..


Sorry, no time for centralized stacks.


It's actually super quick boot for reasons.


It might be too much info for new users. Gotta figure out a way to boil this down to grandma.


No network? What do you mean?


Maybe. I don't like turning amethyst into a wallet, but maybe this can change...


Humm.. good point. Is Orbot really that good? I had cases of leaking IP with Orbot. If the dev is not carefu with connection setup (mostly issues with dependencies doing the connection), it can leak indeed.


Correct. It just transfers through Tor instead of the regular web. Everybody else can see it as soon as it reaches any open web relay.


nah.. I avoid centralized stacks.


It's funny that the PR wasn't really that difficult, but to get there.. boy...

All credit goes to the Tor lib that got this far.


Merged. Now other devs can help me test this out. https://github.com/vitorpamplona/amethyst/commit/8841aa9a10605187336703ecc5e85eae095cb00f


Ok, it seems that the option of activating Tor for .onion relays is the bare minimum we should do.

The question is now, as a project, do we want to offer more privacy straight out of the box or not.

I am leaning towards also using Tor for:
1. Relays gathered from the Outbox model that are not in the user's relay list.
2. All relays that require Auth (no IP-Pubkey link)
3. All DM relays

By default.

More ideas are welcome.


I don't think relay connections are that slow via Tor. Images and videos, yes.


It seems to work well with RethinkDNS's VPN, but I will keep testing.


We can also scramble some relay connections and randomize them: some via tor, others clearnet.

Or maybe only Auth via Tor.

Or maybe only Auth and send events via Tor.

So many options... 🤔


everything


Yeah, the "new" package they are offering seems to have worked quite well for the past few hours. I didn't notice any crash from the lib itself, which was fairly common in the past.


I guess there is a

4th: Tor enabled for onion relay only, clearnet for other relays, images and videos.


What should be the default of a fresh Amethyst install?

1. Tor enabled for relays, but clearnet for all videos, images etc (since they are slow)

2. Tor enabled for everything, user can disable

3. Tor disabled for everything, user can enable


If you can see this, Tor is now inside of Amethyst.

No more Orbot.


Right now for instance, I am only getting them from nostr.band


Now that the reply guy is using random profiles, it's all dependent on relays to block it.


I don't know why they did what they did, but that is I report I would like to see even though I disagree with your general take that Nostr is fundametally centralized. Keep pushing.


Did they see the CSAM in the likes in Coracle or in another client?

See.. I take the fact that they didn't know as working well. These reactions are out there. And reports are the things that gather the most amount of heated debate between users that are reporting each other. Reports generally escalate rather quickly. So, if this was a real problem, this thing would not only be known but it would be all over Nostr. It would be our anti-spam filters debacle all over again.

If my actions are leading to other clients breaking and it's my fault, I am happy to fix it. But otherwise, there should be space to play around with different implementations for things and this is one of them. This type of difference is what makes different clients different.

I think what we do is postive to the network. Other clients might disagree and not send the reaction. Receiving clients can filter it out or use it in any way they see fit. And users can pick the client with the approach they like (or that they don't bother about). It's all good.


We also add the note author to their multiple mute lists on the same report button. We also update outdated relays on the fly, we also authenticate in relays without asking the user. The app does A LOT of things that we don't yet have individual little interfaces and explainers for. These combination of actions is what defines Amethyst's user experince from others. It has always been like that. And the code is open. It's not like we are trying to hide what each button does. We package everything into a few simple actions that do a lot, so the interface is not polluted with all the nitty gritty of Nostr.

Also, Amber users get 3 approvals everytime they report. So, people can always reject what the app is trying to do if they want to without us having to code anything.


Yes, in that case I am making the decision for the other client and I think that is the correct decision. As one of the few clients that allows people to report and uses that report information activelly in our user base, the least I can do is to let users that are being reported know that it is happening. Even if their client doesn't want them to know.


Can you please give me an example on how Coracle users are affected? I need something that is real, that is breaking right now and that is not because the other client didn't implement or just ignored what the spec says.

What I don't like in this whole debate is people advocating for other folks. Amethyst has been doing this for 1.8 years at the scale of 200,000+ installs and NONE, literally NONE, of our users ever mentioned this as a problem, even though most of the reports in Nostr come from us. I am not kidding. This is a really bizarre discussion. Even after you and others tried to gather Amethyst users to be angry about this, only a few people engaged. So, forgive me if I don't want to make changes based on hypotheticals. I can't just base my decisions on 5 of 200,000+ users. Otherwise, I would just go crazy with the amount of stuff that I would need to do.


But your client is not affected. How is this affecting Coracle users?


The real Apple Intelligence 😅
https://image.nostr.build/45be6ac9a578202cfb784043b3500707c7847a86deec231365e317ac6ceb70f1.jpg


So, you forcing me how to operate is fine. But when I do it I am hijacking stuff? Come on man...

Plus, I am not hijacking anything. Your client still works because you follow the spec. Other clients don't work because they decided to do not follow it. Which is their decision. I am not here claiming that they are hijacking anything. It's their choice and until now I never asked them to fix, even though it has been breaking Amethyst for over a year. In the end it's their choice. They are free to do it in any way they want it.


Yep.


Aren't they NIP96 compliant? I thought they were and you could just add the server to your media list on Amethyst. If they are not, they can easily become one.


Ok, if that is not enough. Let me give you more (yes, there is more).

If you are in a client that doesn't support reports and you make post people don't like and they start reporting on Amethyst, your post will disappear from everywhere and you won't even know.

If we send the warning reaction, you will know that some people are reporting you and your post and in some cases whole profile is now tainted.

I always side with letting people know, even when their client doesn't want them to know.


I don't know... I have seen so many heated debates about bolt12 being great and terrible that, at this point, I don't even know what to think about it.


"Most of the network" is not even coding reactions correctly, so apologies if I don't give them any credit...


Well, let's hope people keep these ideas coming.


Got your test correctly marked with the warning and the report. https://nostrcheck.me/media/460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c/06a32ffc3a1857760f186f83cbc524bd323ae2dbc949f37f1a4717e893664d34.webp


Clients should never advertise content based on reactions. There are plenty of reactions that are negative. Reaction is not a boost. If you want to advertise reactions, at least filter to only show the positive ones or break the UI it down by reaction type.


To help clients that don't yet implement reports, to help content indexers figure out how good a post is and to help clients that do not want to implement reports because they see as too harsh and/or form of censorship. The reaction tagging is a softer way of doing it.


That's the wrong phrasing. Reactions are not likes.  🤪 is not a like.  Clients should not call them likes. That's the other client's problem.


These days almost anything in Nostr is 3-4 reqs away...


Not really. I would do a service that creates 1985 tags with the language code using the same created_at the tagged post has.

Then a client can just do a REQ for the latest 1985 tags and load all the event ids individually. A webpage could easily do that and I think it would work on Coracle right now, without any changes.


I am just trying to get a test out and the only way to test it is to have sufficient tags in all posts with all clients. One client doing this won't work because the user will miss a lot of posts that are not tagged.

A service can test the idea ery quickly without modifying any client. If no one is willing to run the service, then I trully question if this feature is actually needed or if it is just a hollow feature that nobody actually cares.


No, not by the client, but by a third party service. Then you don't need any client to do this, which will take forever to test.


Why not just tagging all posts with a NIP-32 language tag and then filtering by it? Then the solution is not dependent on other clients.


Nothing that requires the writing client and writing user to change works in nostr. You might as well just run a content tagger using NIP32 and make a client that filters by language code from the tagger.


Has any client tried it? People have been talking about this language tag for more than a year now. I'd love to get some data to see if it actually works or if it's going to be more messy than a local relay.

I don't think it will work because nothing that requires the writing client to change works in Nostr. But I am open to the idea.


That would be nice, maybe a DVM?


I cannot access your server from here. That's why it's invalid. But Tor addresses work on Nip 05.


You can do one Tor domain with 200,000 pre-generates keys or split them into a few hundred domains. Or just use IP directly.


Então vc quer se autocensurar do resto do mundo? Nunca achei que ouviria uma coisa assim no Nostr :)


Spammers can just create a GitHub project, put the nip05 verification there as a GitHub Page and be valid for free. So, I don't really thing this does much.

All they need is a free hosting service. They can even use their own personal computer at home behind a Tor connection to serve as the NIP05 address.

They can even use Orbot and get their phones to reply to the nip05 verification.


Holy crab!


Ou continuar avançando as traduções automáticas de forma que vc consiga entender o que acontece em qualquer língua. Temos o básico hoje, mas pode ser muito melhor.


Posts don't have a language code in them so we need to download everything, process all of them to identify the language (which fails in 10% of the time) and then delete everything that doesn't match the user's language. It's a lot of data usage.

But the main issue is that it creates local bubbles. If you use Twitter, for instance, you rarely see Arabic or Mandarin posts, even though there is as many of them as in portuguese. The app just hides all external viewpoints from you. Making users a slave of their own linguistic cultures.


Posts don't have a language code in them so we need to download everything, process all of them of language code (which fails in 10% of the time) and then delete everything that doesn't match the user language. It's a lot of data usage.

But the main issue is that it creates local bubbles. If you use Twitter for instance, you rarely see Arabic or Mandarin posts, even though there is as many of them as in portuguese. The client just hides all external viewpoints from you. Making users a slave of their own linguistic cultures.


In theory yes, in practice you will need more memory to keep the list of keys while processing. :)

Definatly less possible on a phone :)


If everyone runs a mint, isn't it just lightning? :)


Nice! Can you go 5 levels of follow's follow? That's where I think most of the real game will be played. But it's a massive graph.


I did see it and I do agree its a massive problem and small relays are the solution. But small relays is just decentralized moderation. The moderation is still there, just run by thousands of relay runners instead of an organized central point. Which is better, but the infra to moderate in a decentralized way needs to be there.

That's why to me relay ops interfaces are so crucial to the future of nostr.


I did see it and I do agree its a massive problem and small relays are the solution. But small relays is just decentralized moderation. The moderation is still there, just run by thousands of relay runners instead of an organized central point. Which is better, but the infra to moderate in a decentralized way needs to be there.

That's why you me relay ops interfaces are so crucial to the future of nostr.


When any particular action or position?


I agree with you. I just don't think this particular instance is representative of an actual attack. Whatever we code for it can be circumvented by a smarter player. Not that we shouldn't code it, but let's be mindful of what we are solving for.

Real bots with WoT (because people will gladly sell their nsec to a bot maker and restart their accounts) will be much more demanding than this simple attack. They are going to look, act and work as a real human.

Every message in Nostr with immediately get 200 replies with products and opinions from people that are paying for it by nsecs of previous real users with WoT and so on. Any serious defense on this will need to include a complete understanding of the entire network or it will be something selected by the user, like just people that I follow.


Has he done it or not.

There is no perfect solution. In theory nothing works. But in practice, we only have to reply to what actually exists.


Yep


It worked as the thing it was. If the reply guy gets smarter, we can also get smarter. But it definitely worked against all the 50 or so replies that I got.


This is dumb. You should almost never ask the notes I have reacted to. And if you do, you should be ready to receive LOTS of negative stuff. You should also check for reports and act accordingly.

Reactions of a person are not always positive and will always include posts they didn't like.


It would transfer the payment through your relays.


Some folks just want to burn terrible specifications down and I am here for it.

Static payment codes to replace LNURL-P 🚀

https://github.com/nostr-protocol/nips/pull/1460


Relays já deletam muita coisa hoje em dia. Mas sempre tem um jeito novo de contornar o que eles fizeram.


Sim, Web of Trust é uma opção, mas essa proposta mais raza de olhar só seguidor de seguidor e não seguidor de seguidor de seguidor de seguidor de seguidor é altamente centralizadora. Ela favorece contas maiores e faz com que elas cresceram ainda mais e bloqueia os usuários sem muitos seguidores ainda.


But most clients don't code it.


NIP-39 defines external Identifiers


Using amber right?


In device AI model. We download the model from Google and run it in the app.


Double click the zap button


But they did stop it. At least in the user's own space. Mute words just make sense to a whole lot of people. Sure, there are way better options, but the simplest that gets the job done to that specific user always wins.


Add an English keyboard. Amethyst uses the installed keyboards as the languages you speak and thus don't need translations


Hum... If the user is on the blocked users it should already be hidden. 🤔 Can you check if the user is there? You can always mute the person again to re add it.

It could be that you reported his person but the subsequent hide list never got updated or got deleted 🫤


Relay list to store private content from this author


Just a prescription https://image.nostr.build/e5f2e984b5c139f01538e50d4791dad9e2d1ce1629d4aee223b5def65ef1786b.jpg


It's fine, but def nowhere near Alby hubs experience.


Alby Hub (either paying them to host or hosting yourself) is by far the best one to use on nostr. Nothing else comes close, even custodial ones.


You can add the NIP05 in the new version's hidden words. You can also filter by name or profile picture url. :)


Provavelmente é o seu teclado. Vc usa uma versão modificada do Android, tipo graphene?


No, it's just broadcasting everywhere. We need something smarter with the multiple relay lists into account.


Use the Play version instead of the Fdroid one


We need to code a sync button that connects to all 3000 relays to download everything by and for an account and then send authored by the account to the public and private home/outbox, p tagged posts to the public inbox and DM inbox, depending on the type, and everything to the local relay.


We need to code a sync button that connects to all 3000 relays, sends posts authored by the account to the public and private home/outbox, p tagged posts to the public inbox and DM inbox, depending on the type, and everything to the local relay.


You can use listr.lol to build lists of people and then use Amethyst's top bar to filter between them.


Bizarre. Do you see many videos on your feed?


Humm.. you need the Play version of amethyst, not the FDroid version. If zap.store doesn't show, try Obtainium. You can get it straight from the GitHub releases.


Any feed? Chats as well?


Mastodon people saying GM on Nostr. https://video.nostr.build/38adaa56b1a4f6fbf2dc39238365a13db6d6e16d14dddece3807e54e724d9b1c.mp4


Correct. If that is the only relay there, then people must use Tor.


Inbox must allow other people to access it to send you notes or DMs. If Citrine is only running on your phone, no one will be able to access it. Tor opens it up to the world. If you are not using something it open it up, you will never receive a DM.


Only use Citrine as public inbox/outbox if through Tor.
nostr:nevent1qqs0dkrlqa9z9ad96n7d55df7s59gmpcxtrllv80cjaq5txfgl2zx9spzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtczyrkmgup8z2t6cknp7fml8ng5me2vvl44enfqauxemu5muxrgtwcqgqcyqqqqqqg9cs43c


Myth:
- #Nostr will kill your cell phone batery 🪫

Truth:
- My cell phone battery reached the end of the day with 20%, running #Amber and #Citrine in the background. And I was messing around in my work time in #Amethyst a lot today 😜

Fact:
- #Nostr is battery friendly 🔋💜


There is no way to block anyone on anything in Nostr. You can only hide them.


Them: Don't come back here with your bullshit

Me: coming back with my bullshit
https://video.nostr.build/948ab0dbf071a449fb09c667c0f808cbf1f7c4231b81e9f1bf393401206326ad.mp4


His name for instance or xDBupZ which is what he uses as profile pictures.


You have to add a few words to the hidden words filter in the Security Filters


What do you mean by "nothing to protect themselves with"? Many relays are blocking the spam just fine. It's definitely doable.


Why? I don't think so.


I now have three relays you can use depending on your use case:

Private relay for yourself or a team: GitHub.com/bitvora/team-relay

Relay for everyone you follow:
GitHub.com/bitvora/fren-relay

Relay for everyone in your WoT:
GitHub.com/bitvora/wot-relay

PRs are very welcomed


Add him to the hidden words :)


Play is up to speed. Obtainium is also ready.


what are you using to download?


So, is the spam completely gone? 😎


yep, you can add their name to the hidden words in the security filter and it goes away


keep an eye to see if it is just youtube or any url.


Nobody can read it. It's fully encrypted with your keys. Only your keys can decrypt it.


They do in 0.91.0


No, but we changed the default view to simplified, which removes the second line. You can change it back on the app's settings.


Yeah, one is a fluke. Two is more concerning.


Will keep an eye on it. We haven't change the preview code for quite a while. I am not sure why it would be failing now... 🤔


Clear net or behind VPN/Tor?


We show flare videos on our Stories :)


https://flare.pub  ?


Our trick to get people to stop sharing freaking YouTube links.


All of the links or just some? https://image.nostr.build/dadc4199f80579c8a92654c70c1ddd5d88143cb35f4eb66bbfa2f10a1782d149.jpg


BTC Sessions is starting his decentralized onlyfans.
nostr:nevent1qqs9sxn7gle8c3l6358r55ct3jylvsky3qy2w7u76law5xfjznw6h9gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygqe3yp5u44c7crvwf85tgfvap9prpqkyx40wxp2rajkgwqtn3p8dvpsgqqqqqqs6ldl23


The new version released today (0.91.0) does it.


Slowly becoming a real app. A few more rewrites and we can start thinking about v1.0 :)
nostr:nevent1qqs98szdz7z6tgeq750r3q9qtzmpjqcqcfhy9nrsyurwgsxw0pp52rcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygplwuxkt5a8vj5utj6s8tsj8e3wcavc45p4mqmw92qs7wrh5azmyspsgqqqqqqsq56jvr


Connectivity issues? Are you behind Tor/VPN?


In the new version, you can also block by the profile image url the bot is using, which includes xDBupZD :)


New threads or conversations.

If new threads it's a issue in the don't show too many reposts algo. The reposts appear in the past, it hides some of them. I am not sure how to solve that one yet.


Want to send Nostr DMs on the desktop?

Try Coop.
https://github.com/lumehq/coop


Best client.

It just so happens to be on Android ;)


That's coming. I just need to re-do the current click and hold quick actions


Remember that hidden words are per account. If you have multiple accounts logged in, you need to add the filter for all of them.


There is no way to limit new keys.


There is not way to limit new keys.


You can add it by yourself. This is not coded in the app. Users can always block what they don't want to see.


Not really. Amber uses NIP-46 to sign and decrypt payloads from your phone. Desktops never see the nsec, only people's phones do. Everytime an approval is required, Amber brings up a popup on the phone.

That can come from your team members or from yourself on a separate device.


Then we will use something else


I typed the Reply Guys profile picture code in it :)


I blocked my own post!


Still processing


Let's start with block by picture: "xDBupZD"
nostr:nevent1qqs0hgysl6pq6n9y9skcppqqy697dqufxdlyetz49ed24pmwj2dqatcpzamhxue69uhhv6t5daezumn0wd68yvfwvdhk6tczyz4fq3ej2cpa4n20s9pqjdt8ju6kdh3mrcs2392hku5v80jvd2zykqcyqqqqqqgvzu97j


There is always an anchor string that can block it. I am now using "xDBupZD" because that's his picture.


Challenge accepted Reply Guy.


1. It must be mandatory and coded by all relays and all clients. Otherwise, users will see broken experiences everywhere (things appear here as official accounts of a brand but not there, etc).

2. Encryption and decryption is impossible with subkeys. For instance, we can encrypt DMs for all subkeys, but once you do it, you cannot revoke that anymore.

3. Replaceable events and all the indexing around it now must consider delegated keys whose authority can change over time on a simple re-broadcast. The entire indexing now needs to use the DB as a source for the index itself. It gets extremely complicated.

4. Now compound that complexity with the fact that we don't have a time chain on Nostr and things can appear in the past, future and different relays can and do have different versions of what's authorized at the same time.

It's mess, on top of mess, on top of mess.

All because we use raw pubkeys as the main address and not a time-resolvable DID for instance.


I started, but we do too many decryptions (1000s) in a second. I need to create a separate mode for NIP-46.


Key delegation: the ability to allow subkeys to speak on behalf of the main key with flexible revocation controls to protect the main key when subkeys leak.


Key delegation on Nostr will never work. It's either NIP-46 or GTFO.


It's the only way to query as relays don't offer startsWith queries.


No clear net connections at all.


Zaps can be faked. :(


It's ok. If they are here just for the feed, it's natural that they are going to think everything else is just a waste of time. We are not here just for the feed, though. The goal is to build everything cohesively in one app.


Nao conheco nenhum projeto parecido com o Google keep no nostr, mas seria muito facil faze-lo


Yep, standard cloud flare stuff. They do have an option somewhere to enable Tor. I just don't know where it is.


Amethyst doesn't operate a wallet/node.

Primal's wallet is from Strike, fully custodial and KYCed.


I didn't check lately, but yes the idea of setting a different route per account or per subscription is key for a more private browsing using Amethyst.

Otherwise, the server can just bundle a bunch of filters together and start tracking users even without a stableish IP behind it


Yeah, that's a problem. The phone is getting the same check, but can't answer it.


I think Cloudflare is blocking their Tor connection


Do you know if the server replies inside Tor?


After a while or all the time? Try force closing it from the Settings/Apps/Amethyst


Are you using Tor or VPNs? I think the app is having difficulties accessing that server.


Private Home? It's a bug that has been fixed but not released yet


Yep, let's hope somebody comes up with something better. 🙏


We implement it, but I don't think the way it was done is that good. Web clients cannot decrypt it because the NIP-07 extension and NIP-46 signers don't offer custom methods for it. Right now only Amethyst and Damus support it. And if somebody creates a version that can get more clients to use, I would be happy to support on Amethyst as well.


On the list, but we never found a stable Tor library to use inside Amethyst. Much less one that we can control the routes to avoid routing everything through the same nodes.


You can be a dev.


Self-custodial Alby Hub (either running it yourself or paying them to host the node) is by far the best option to use on Nostr in general.


Looking forward to the Kotlin wrappers for Android developers.


Have you never seen the Broke, Woke, Bespoke meme before?


I see a verified icon, not a red icon. 🤔

Maybe the website was still updating its records?


Basta adicionar a sentenca no Security filters no menu da esquerda.

nostr:nevent1qqsvjlngzvpmzrmf5fvnlvtur5epgvnqh6dk53xcfhze4l38v5vjrygpz9mhxue69uhkummnw3ezuamfdejj7q3qutx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4sxpqqqqqqzvvev4z


Broke: Build things so complicated you are the only one that can fix it

Woke: Build an AI to fix things

Bespoke: Build things anyone can rebuild in a weekend


My phone -> Tor -> His phone


Did you mute on Amethyst?


I will disable saving it, but meanwhile.... Slightly better, with a copy stack button https://image.nostr.build/5764d822e9236bf10b6d3edba9676674076e8bc3c4274a823da5be71917134b9.jpg


On the losing relay on Private Home specifically... It´s a cache bug that has been fixed and will be available in the next update. The relay is save, but not being used right now


Just hit the Default button on Amethyst. There are only 3 options available anyway


I think I will just hide the button when its a m3u8 file


We have HLS support. Uno was trying to save it, which I don´t think it´s possible. Is it?


I have defeated the reply guy bot

https://i.nostr.build/zVkuRcbgr7r779zy.jpg


Like do you want 2 feeds at the same time? Like New Threads and Conversations can be displayed side by side on the big screen


Send me good app designs that you are using on the big screen. Right now Amethyst on Fold is just a scaled up version of the app. We can do better, but I don't know what's good in that form factor.


Testing on foldables is always like "how the hell did this got there?"... "oh.. yeah, It makes sense".


The #DVM replies to the relay In the phone.

👀


Too much work.


Only if they are ecash zaps.


Isso


I assume you have received several good explanations by now, but in case you haven’t I wrote this almost 2 years ago:

How do we check “follower count” on nostr?

1. Your client sends a request to all your connected relays asking for contact lists that follow you
2. Relays answer back with the events requested
3. The client aggregates the event total, de-duplicates, and displays the count

Each relay has a set limit on how many stored events it will return per request. For some relays it’s 500, others 1000, some as high as 5000. Let’s say for simplicity that all your public relays you query use 500 as their limit. If you ask 10 relays for your followers the max possible answer you can get is 5000. In reality you won’t ever get 5000 unique responses, you’ll likely get something closer to the same 500 from each relays you query. That won’t change if you have 20,000 followers or 100,000 or if you query 100 relays instead of 10. You may get back a “different” 500-5000 each time, but you’ll still cap out at 5000 (non-unique) because that is the most events your client will receive.

Primal, nostr.band, and other aggregators that store counts in their own DB will always show different numbers than clients reading directly from relays. Generally speaking, neither number is correct! nostr:note1rg39c6hwy29eucrztq7hupd7gtvqjtfeansgsqresh9dx9jqt8gsklyq75


Also, make sure your public inbox relays can receive zaps from any service out there.


If the lightning transaction happened, the issue is on the zapper service of the receiver. That service creates the zap event and sends it to nostr. If the receiver doesn't have it or has disabled it, or it's offline for some reason, no zap will ever show up.


That's what I meant by evaluating the operator.


All of them.

+ How fast can he run a REQ call :)


A reliable service that doesn't randomly delete your posts or your zaps, etc.

Yeah, most people just put a bunch of relays and it works for a while until everything starts disappearing and they realize their posts were never there in the first place and half of their relay are not even accepting the types of events they are sending...

Not paying attention to reliable relay lists is a terrible idea.


Users. They are reviewing the best ones for users.


Let's say there is a company whose sole purpose is to evaluate relay operators and offer relay list recommendations to the best ones.

How much would you pay for that service?


Fdroid is the same as the Google Play. They centralize everything in the decisions of the few at the top of the group. If they don't like what the app dev is saying, the app doesn't get listed.


It's a cache bug. We fixed it yesterday. New version coming. :)


# Citrine setup

Go to the settings tab.
https://i.nostr.build/ex9B7IdQK1q0AerO.jpg

Fill things in as appropriate. Leave the network related settings default.

# Orbot setup

In orbot got to more/hosted onion services.

Add a new service.

Citrine uses port 4869, so set that for both ports. Name it anything. "Nostr" will do.

You will need to restart orbot after you save. Then you can go back and copy your onion service address.

# Amethyst Setup

Add ws://ONIONADDRESS:4869 as an outbox and DM address in Amethyst. Also add ws://127.0.0.1:4869 as a local relay

https://i.nostr.build/vnvHQEEHAn4e3Kl5.jpg

https://i.nostr.build/UhKC9mEknjHF7BJ2.jpg

This requires running Tor at all times!

😎👌


That's so strange. Do you use any other client? I wonder if clients are saving to different relays and not syncing up. So, you follow 14 people in one, but the other doesn't update and you follow over there. Now the first gets an update event with 14 less follows.


No, just choose the relays that you truly trust.


Your outbox and inbox relay list are also way too big. It should be 2-3 relays in each. Your general section can and should have more.


Today's P2P Nostr using phone-running Relays through Tor in production apps (works with no hacks) will be remembered as a key milestone in Nostr's history.


No, that is how it should work. Did you lose everyone or just a few?


That's strange. Did you uninstall and/or cleared the storage or just updated without logging off as usual?


Was satoshi Brazilian as well? 👀


Faz sim. Eu uso um pessoal da relays.tools


Which version? This was supposed to be fixed in the latest v90.6, but maybe there is another bug somewhere


Which version?


The invoice is for 58000 sats


The best app that just so happens to be on Android :)


Hum... It will try to use npub.cash as a lightning wallet to receive. Maybe there is an issue in there. 🤔


Of course. You have to stay online.


Graphene OS. Super good.


Relay as an android app https://github.com/greenart7c3/Citrine


Wow. Southern Kin. 😅


Well... living here.


Yep


Pro Tip: if you are in Boston and see a Southern-style restaurant... Don't go.


You can edit the post if you use Amethyst.


secp256k1 added to the secure enclave of all phones.


this

is

gentlemen

amber amethyst citrine orbot (#AACO)

nostr:nevent1qqsqqqqq6sz978h0nnf79y6mx036gs987tumeqd8yycm298m87cd5hspzfmhxue69uhkummnw3eryvfwvdhk6tczyp7vx29q3hdj4l0elxl800hlfjp538le09epsf7k9zj59ue2y37quqcyqqqqqqgwae7hv


nostr:nprofile1qqswmdrsyuff0tz6v8e80u7dzn09f3n7khxdyrhsm80jn0scdpdmqpqpf9mhxw309akrx6tevf4xjmt50f6r26rcx3unyamtxcery6r8we6ngc34vd6xs7ttd4jx7e3jdymx5vmhx4kxyurwvf5rwaen09jzummwd9hkuw358qmrjtcmlnu7y people want to know!!!


Lol. Few.
nostr:nevent1qqst3n0fd9rg8cajfzxhqmsxzmg42e6rt6ncsy4sxr6cw8emruxqkpcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygzsm98u9kzcp35zkpc62shck8335gqtq5yt4w26xwl0pp2a72qavvpsgqqqqqqssmjjyt


That's a story for nostr:nprofile1qqswmdrsyuff0tz6v8e80u7dzn09f3n7khxdyrhsm80jn0scdpdmqpqpf9mhxw309akrx6tevf4xjmt50f6r26rcx3unyamtxcery6r8we6ngc34vd6xs7ttd4jx7e3jdymx5vmhx4kxyurwvf5rwaen09jzummwd9hkuw358qmrjtcpg3mhxw309ahhsarjv3jhvctkxc685d35093rw7pkwf4xwdrww3a8z6ngv4jx6dtzx4ax5ut4d36kw6mwdpa8ydpkdeunyutzv9jzummwd9hkutcmkq3ed to tell.


I don't know if it works. It requires iOS to open connections to the phone via Tor.


Come to Android Guy. Stop using old tech.


Today's P2P Nostr using phone-running Relays trough Tor in production apps (works with no hacks) will be remembered as a key milestone in Nostr's history.


In this way, the DM goes from my phone to his phone without anyone seeing it. But if people get access to his private key AND the DM event,  they can decrypt it.

And that is the same design of Signal and others: You have to have both the seed/key and the local database to decrypt.


No, right now both need to be online.


Need to be sure no one controls the fund, otherwise it creates a taxable event on those who do.


It could be. Lots of research needed on this.


There is still a 1 second ping to access somebody else's relay running on their phone...

So don't get too excited. Just mildly pumped.


Nice idea. I guess the app can always try the local proxy even if it is not active.


Last year, I coded many hole punch designs to test P2P DMs on Amethyst. Many somewhat worked but with centralized constraints and huge maintenance costs.

Now Orbot and Citrine just come in, show a few buttons and boom. Done. 😎


It does if you open the connection to the outside world via Orbot.


I name this for the post of the year.
nostr:nevent1qqsg373k7l3c0hets4xykud6xp2anzgrcgwl6fdnk0x50luumk8rylcpz3mhxw309akx7cmpd35x7um58g6rsd3e9upzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqvzqqqqqqykk4xux


People using Amethyst over Tor, do you perceive any slowdown when loading things?

Tor is technically a lot slower, but I can't see any difference when browsing on Amethyst.

If no one notices, maybe we should enable this by default.


Citrine is a relay on the phone by nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck


Only if it is a Giftwrapped DM.


Humm.. I will check. I thought I had covered this already but there might be a bug somewhere.


My phone -> Tor -> His phone

No public relays.


Humm.. that should already be there. Which relay are you getting this issue from?


DMing nostr:nprofile1qqs9pk20ctv9srrg9vr354p03v0rrgsqkpggh2u45va77zz4mu5p6ccpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz9thwden5te0wfjkccte9ejxzmt4wvhxjme0907cz8 from my phone directly to his Citrine relay via Tor. https://image.nostr.build/1ad95bd258670354a25a031e9dcd1ed710794078ba1a06466fdd1dad05303b12.jpg


Working https://image.nostr.build/1ad95bd258670354a25a031e9dcd1ed710794078ba1a06466fdd1dad05303b12.jpg


When you think about how the Internet is just networks allowing trusted computers into their network, it's pretty shocking to see how far we have scaled this. It's the ultimate pyramid scheme.
nostr:nevent1qqs955x7jvukgu7mc9a46jx7uu89rgxk0qzxleuvf3pq0p9hcakregqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpjuxp8vd29p6ancknaztql3eajk52y8xkppfn7au7elkw9c68zg5psgqqqqqqslah5ly


When you think about how the Internet is just networks allowing trusted computers into their network, it's petty shocking to see how far we have scaled this. It's the ultimate pyramid scheme.
nostr:nevent1qqs955x7jvukgu7mc9a46jx7uu89rgxk0qzxleuvf3pq0p9hcakregqpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygpjuxp8vd29p6ancknaztql3eajk52y8xkppfn7au7elkw9c68zg5psgqqqqqqslah5ly


Your ISP will need an ISP.


Lots of people share a lot of trash. The gallery is like a select portfolio of your posts.


Satellite e Coracle tem uma variante implementada (não sei se são compatíveis)


Amethyst


Yep.


You have to turn on Orbot and add the recommended relays to your General list to see this though.

Amethyst doesn't automatically connect to unknown relays.


The robot icon close to NB is somebody else's phone!! Connecting directly from mine. nostr:nprofile1qqswmdrsyuff0tz6v8e80u7dzn09f3n7khxdyrhsm80jn0scdpdmqpqpf9mhxw309akrx6tevf4xjmt50f6r26rcx3unyamtxcery6r8we6ngc34vd6xs7ttd4jx7e3jdymx5vmhx4kxyurwvf5rwaen09jzummwd9hkuw358qmrjtcmlnu7y https://image.nostr.build/87e304ed7da71f7a7f18add772dfdd09e152dc287633b3b96ae0a6db1662872f.jpg


Gotta find a way to do escrow so that users can zap into escrow that gets released later.


How to run Citrine's relay and allow other people to connect into it to download your posts directly from your phone via Tor 🤯🤯
nostr:nevent1qqs2eqnj7xtae25qr252px0jm8mr2xfly30tsp0rvtdwryrkaua0c7gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8dk3czwy5h43dxrunh70x3fhj5celttnxjpmcdnhefhcvxskasqspsgqqqqqqsk7vtrx


How to run Citrine's relay on your phone and allow other people to connect into it to download your posts directly from your phone via Tor 🤯🤯
nostr:nevent1qqs2eqnj7xtae25qr252px0jm8mr2xfly30tsp0rvtdwryrkaua0c7gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8dk3czwy5h43dxrunh70x3fhj5celttnxjpmcdnhefhcvxskasqspsgqqqqqqsk7vtrx


Wait, can other people connect to it via onion?


Yeah, that would be awesome. List a list of things people could vote for by zapping.


Decentralized Identifiers.

Or Dissociative Identity Disorder

Kinda the same thing..


Thank you for being upfront!


I would still be trying to make DIDs work. Fuck that.
nostr:nevent1qqsgaywmrgtk27qyq330ywzm80des03yeqw84ecnk54zc8wl9k5qj0spz9mhxue69uhkummnw3ezuamfdejj7q3qlelkh3hhxw9hdwlcpk6q9t0xt9f7yze0y0nxazvzqjmre3p98x3sxpqqqqqqz9sj0pz


Yes! Let's go!


Click to open them in full screen and then hit the share button to select add to galery


It doesn't work. There are so many ideas on what we should do (every user has a few) that it is impossible to even gather them all. I try my best, but I don't see most of the Amethyst-related discussion out there.


Everytime I hear Brian Armstrong, I feel like he is trapped in 2018. He still talks about blockchaining everything (land, votes, tickets, etc) as if none of these things have been tried and failed miserably.


Does it accept deletions or will it archive everything in spite of the user's desire?


I don't know what you mean by meritocracy. Those involved in the project will already do what they want to do. So, any merit is already been accounted for and by themselves. The only other merit is to those that donate to the project and deserve to be at least listened to.


I don't know what you mean by meritocracy. Those involved in the project will already what they want to do. So, any merit is already been accounted for and by themselves. The only other merit is to those that donate to the project and deserve to be at least listened to.


Sure. It doesn't guarantee that we will follow it, but we will definitely take a look.


This is not a democracy.


Linking comments, DMs, and GitHub issues back with the total zap amount they donated requires some work.


#Amethyst v0.90.6: Profile Zap Amount fix

- Fixes the sat amount when zapping users directly in the profile by nostr:nprofile1qqsv4zwtz8cuwh2mvc3zdrl5853g365t9j6mn25edlul7uz0eyzt0zcpz4mhxue69uhhyetvv9ujumn0wd68ytnzvuhsfy7nnn
- Adds long press to copy relay url in the relay icons and relay row by nostr:nprofile1qqs827g8dkd07zjvlhh60csytujgd3l9mz7x807xk3fewge7rwlukxgpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszrnhwden5te0dehhxtnvdakz7qgswaehxw309ahx7um5wghx6mmd9usjfpck

Updated translations:
- Thai by nostr:nprofile1qqsxdhmq2cke8xk6scfyxeyfj3dyancavg6xk0v50r023gec7vsrceqpzemhxue69uhkvun9deejumn0wd68yvfwvdhk6qg6waehxw309aex2mrp0yezumn0wd68yctnd9sjumn9wsq3yamnwvaz7tm0venxx6rpd9hzuur4vghen3hm
- Dutch by nostr:nprofile1qqs82l74z7g3x8j3avpn2wrjrwn855nyvmpxa4v5pftfvtv5lrvrc5cpz9mhxue69uhkummnw3ezuamfdejj7tk0drp
- Hungarian by nostr:nprofile1qqs88rmfrp9wmfn4qq4kslly0j8futmmrgn86mu3gkc3jvcjl97p3mcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcqngjsj

Download via [Obtainium](http://amethyst.social) or [Zap.Store](https://zap.store/)


We are always working on several things at the same time..


I have to find a way to prioritize issues raised by those who Zapped the Devs. 🤔


You can publish to as many relays you want, but ideally you should tell your followers to look for your events in one or two a reliable datasets so they don't need to search within your 100 relays for your posts. 1-2 relays are more than enough for a follower.

Searching in 10s of relays for each follower is a huge battery and data plan drain.


Just adding to the list. The app will make sure your data is there. Not so much for the others.


Find your 2 favorite relays and make sure they are not going to delete your data.


Tried it, but people don't change default settings. We have to add more interesting measures to get people to take control over their data.


Yep


But I do think choosing a Home relay is key for any new user. If you don't know where your notes are, then what's the point?


In time, all clients will adopt it. We are just early to the game.


Amethyst does a lot. And it will always use a lot of data and connections. And we will push for using more for sure.

That doesn't mean it is "unnecessary".  That is exactly what our users want.

We want to do it all, and if we do, we are loading ALL of it, all the time.

As a relay, you have the option to block what requests you serve and which events you store.  With the outbox model that we now implement, we only hit relays that might have the info. And that's how small relays win. We are the largest userbase app that is at this level.

In fact, we are even pushing for dynamic limits which allow relays to have more power to limit the client on demand.
 https://github.com/nostr-protocol/nips/pull/1434


They have to wonder. Most relays will be screwing them over. So, it's not an optional part. Let's hope people write more articles and analyze the policies and resilience of relays out there. As an app dev, I definitely cannot do that myself. It's too much.


Do you think people can't choose one or two relays?

The onboarding is automated, but they MUST choose a relay to host their notes. Otherwise, we are not anything better than Twitter.


What do you mean? We have supported lots of small relays. In fact, I am talking to small operators almost every day to help them out.


If you had to choose a single relay to host all of your notes, which one will be?

That should be the only item on your inbox/outbox

Your client can check other relays, but your followers will only check your main one.


Sure, but users must know where their notes are by choosing 1-2 relays they want. If they can't do that, Nostr is not much better than centralized Twitter.


Have you chosen 1 or 2 home relays that MUST have all your posts? That's the first step.


It should do that if you add it to the local relay section.


They shouldn't need to do that. Why would they download a larger event just to get the first three? It's just extra data for each follow you have. If they have 500 follows, the extra relays per follow really add up.

Plus, if you have a long list, I can guarantee many of those relays don't have all of your events. So, the follower can miss your posts if it doesn't choose your best performing relays.


Yeah, I didn't even know there was a difference between "open a channel" button and the "increase capacity" button.


Correct. Clients that autocompute would like to see smaller lists to simplify their life.


Need more devs.. send help


I am trying to open a channel with Kappa and ACINQ, but Alby Hub requests a deposit of 860,000 SATs to open.

Something is off.


Your inbox and outbox relays are for your followers, not for you.

I know, 🤯

The list tells your followers where to get your posts. Not where your app should send/receive yours.

So, the smaller the list the better.

Your app should have an additional setting, separate from the Inbox/outbox setup, where you can add extra relays to save your posts, in addition to the inbox and outbox relays.

So, if you want to send/receive to 30 relays... fine. But don't ask your followers to download/send from 30 relays for each person they follow.

That's not cool.


No, you should get only DMs and Zaps. The other stuff is too heavy.


Did it work?


Main issue is the 800,000 sat (500 USD) requirement to open a channel with some (all?) LSPs.


I think it worked now. But keep an eye on it. I am watching for the timeout behavior from the NTFY server


We are not a company. If I receive the full amount and then pay the devs, it creates 2 taxable events, one to me (30% off) and another one for each dev (another 30% off). So, it is better if we split at the source and you pay them directly.


Amethyst


Go to the phone's Settings/Apps/Amethyst and hit force close.


Can you force close the app and reopen it? I want to see if there is a caching issue


Do you see from anything else?


It depends on the server implementation. With NTFY, you don't need to create a topic.


You have a selector on the top bar. You can choose Global, All Follows and/or create your own lists of people on listr.lol


In theory, all you need to do is to have the notification app running on your phone, connected with your server.

Then go to Amethyst's Fdroid version, go to Settings in the left drawer and select the app as a distributor. That will create a topic in the Notification app and you should be able to see our server sending notifications.


Me mande o seu e-mail via DM que posso te mandar um invite.


Do you already have an address? If so, you can just insert it in your profile.

The best integration we have is with Alby Hub, which offers the 3 services Nostr needs:
- The self-custodial lightning node
- The zapper service (to send zap receipts in Nostr)
- The Nostr wallet connect: to automatically pay zaps with single click on Amethyst.


Yep, they might be blocking everyone that uses the free version due to the amount of messages out.


Do you guys run your own servers? I think the ntfy.sh is blocking channels after the initial free-pricing limits.


You can click on them to open the webpage and you should see the notifications there if they went through


Can you see the notifications when you open the ntfy page in the browser?


Cria uma bounty para ver se conseguimos um dev para ajudar nesse novo flavor. Mais ajuda é sempre bem vinda.


Sim, essa é a ideia. Mas seria apenas silenciado, o grupo ainda estaria ativo.


O Amethyst é muito pesado exatamente por causa do volume de features. Sempre estamos trabalhando na performance, mas aparelhos mais antigos ou sem muito poder de processamento não conseguem fazer todo o que o amethyst precisa fazer. Clients mais leves, com menos features, são melhores para aparelhos mais antigos.


Técnica. É como email mesmo. Se o pessoal manda, vc recebe. Não tem como vc sair pq não tem um grupo com moderador. É só uma lista de emails que as contas estão enviando mensagens para todos individualmente.


Vc tem o post em algum lugar acessível que eu possa ver?


Infelizmente não existe outra opção hoje.


Basta bloquear a contas que estão enviando mensagem por ali.

Chats funcionam como email, se a pessoa escreve o seu email e manda não tem como vc sair. Só bloquear mesmo.


Humm nunca tentei nada tão grande. Mas so pelo tamanho deve demorar bastante.


I will try again. On Android, the in-app camera is always worse than the Google/Samsung variants. So, even if I add, it's likely no one will use anyway.


Hum.. yeah, they should work. I will run a few test as soon as I get home


So, make sure they don't require auth.


Yes, the system will use your inbox relays to pull notifications from.


Also, which version are you two using?


Can you try ntfy? I was able to test and it seems to be working. Were you able to select the notification provider on Amethyst?


It's the AI model to translate in device. You should see a new download for each language pair that shows on screen.


We load about 400 posts.


You can disable the anti spam filter in the left drawer.

But yes, we will always block spammers by default.


Ohhh nos.lol is not an image server. That's why it didn't work.

These servers are all different and each has their own plans to host your data. Chose what fits best to you.


You can also see a list of servers in the Media Servers options in the left drawer.


Yeah, that is not what NIP-65 is for. You should only put there the relays that OTHERS should use to find your posts and to send notifications to you. It's about everybody else.

The General List is more like for yourself and Amethyst will send your posts to those as well.


Very interesting. Can you choose another server, try to upload and then return to nostr.build to see what happens?


Version 0.90.3 or 0.90.4?


Seems normal here. Which service are you using?


Yeah, don't do that. You just fucked your followers (now they need to connect to all of those to figure out where your posts are).


That's strange. Your inbox, outbox should be for your posts. The General Section is about your follow's posts. There should be more relays in general than just the 3 on inbox/outbox.


Soon


Notifications will only load from other outbox clients (Damus and Primal have not migrated yet).

Nip04 uses general :)

Chats and communities might not load as well.


Keep the general relays for now, we are still migrating over. Many things on Amethyst need them :(


My repeated #hellthread notifications on #henhouse are reminding me how much I love #amethyst.
Thank you, nostr:nprofile1qqsyvrp9u6p0mfur9dfdru3d853tx9mdjuhkphxuxgfwmryja7zsvhqpz9mhxue69uhkummnw3ezuamfdejj7huv75n


Keep the general relays for now, we are still migrating over. Many thing on Amethyst need them :(


Click on the message to see the incognito icon. If it Is there, it's NIP17, if not it's nip04


That's the best way. You can add your home relay to your Outbox/Inbox section and everyone will get events from it.


That's the best way. You can at your home relay to your Outbox/Inbox section and everyone will get events from it.


What scares me in Brazil's X ban is how overly broad the wording in the judge's decision is:

"Internet providers, on behalf of their presidents (makes it personal legal liability), must add technological obstacles (literally anything) capable of making the use of X unfeasible."

It's not about blocking IPs or domains. It doesn't prescribe any specifics. It names companies that must comply, but only as examples. And it seems to strip corporate protections and goes straight into personal liability. All in just a few sentences.

Too broad. No one should have this much power.


Nice find! It looks like it uses https://github.com/deepmedia/Transcoder. I might be able to switch to this directly from our current compressor.


If you don't have a home, Amethyst will scatter your posts to the General Relays. It doesn't guarantee your followers will see your posts, but it is better than nothing.

Defaults are very centralizing. Everyone should investigate and choose their own home relays.


It's a lesson to not be idiots.


But they don't. None of my friends are on Twitter in Brazil. They never even went to the website. They just don't have any reason to.


Yep. But people buying new phones will quickly degrade the amount of activity from those apps.


And centralization in big players (relays and app stores)


Make sure you run a relay or have a full backup of your events written in Nostr.

Relay.tools ca help you make your own relays.

For the app, use Obtainium to download and install directly from source. In the future, Zap.store will be more available for folks to install Amethyst straight from nostr events.


Check 0.90.4, I think it fixed it.

The issue were the relative urls in your json metadata.


They can ban by IP as well


And yes, governments can't ban Nostr, but they can ban individual relays and remove apps from app stores.

Not your relay, not your data.

Not your app store, not your app.


Try nostr:nprofile1qqs9ajjs5p904ml92evlkayppdpx2n3zdrq6ejnw2wqphxrzmd62swspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qg5waehxw309aex2mrp0yhxgctdw4eju6t0vwuavy :)


For now


Brazil's Supreme Court judge.


Banning X only affects influencers. That's why I think it's really cool. Regular people don't use X. They don't lose anything.

WhatsApp on the other hand... 😱

Yes, he just needs an excuse to ban WhatsApp as well.


Very easy. ISPs can see connections into Tor if you don't use a VPN from your device.


Super cool that Brazil has banned X.

These are the types of actions that truly wake people up on how extremely weak their social media presence is.


Yes, it is. It uses the same private chat we do on Amethyst


No, we download the ai model to the phone and run all translations locally.


What do you mean by switch away? Everytime you send the app to the background?


Wishful thinking.


If the relay is free, you are the product. You don't really control your data. You can be censored at any time. Not that different from Twitter.


Looking forward!


Universidade Federal do Rio Grande do Sul, Instituto de Informática

Brazilian National Council for Science and Tech Development

Brazilian Agency for Industrial Development

Displays to compensate for visual impairment

Photorealistic models for pupil light reflex and iridal pattern def.

Apps gone rogue: Maintaining personal privacy in an epidemic

Tailored displays to compensate for visual aberrations

NETRA: I/A display for estimating refractive errors and focal range

CATRA: interactive measuring and modeling of cataracts

Computer-assisted methods to evaluate retinal vascular caliber

Dual of Shack-Hartmann optometry using mobile phones

High-order and Low-order lensmeter using a smartphone add-on

Somerville's Pedestrian and Transit Advisory Board

A mobile game engine using Java's Mobile 3D Graphics API

Animating relief impostors using radial basis functions

A decentralized approach to covid-19 vaccination coordination

Real-time system for rendering LEGO representations of boundary models

I am the lead developer for Amethyst, a Nostr client for Android


In amethyst, we do compress video and images using two different libraries.


Custom widgets coming to Nostr by nostr:nprofile1qqs2l8tsgp6xgfrar87jg083hm5pum03ucujzlwxvdnt7da2gtg96dgpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgpr3mhxue69uhkummnw3ez6vpj9eukz6mfdphkumn99e3k7mgpremhxue69uhkummnw3ez6vpn9ejx7unpveskxar0wfujummjvu2l76yt's team
https://image.nostr.build/ddec5b5fb3ec282d32df7e303e77a5ca3fd18404a83cd288431a13b4b5e08d7f.jpg

https://github.com/nostr-protocol/nips/pull/1454


More importantly, free relays will never be decentralizing.


Yeah, outbox/inbox is the default now. But people need to choose their own relays. Otherwise no model will work.


Ohh yeah, but no. The idea was to get everyone their own node.


Don't choose random relays. That's not good. There are lots of relays tracking and selling people's data for profit. That's a terrible strategy.

Small relays work on amethyst and other outbox model clients, but many clients haven't updated yet, so the large relay helps with reach.

Most importantly, you want to use the relays your friends and follows use. That's doesn't need to be a large relay. It just do happens that today, users haven chosen to centralize in large relays.


Not your relays, not your data  https://image.nostr.build/09b00a7b43ad04e84c0b285614a4e85c102440a5c4aa5a9856575725c6981413.jpg


It's a full node run by you. They just host it and provide a web app to manage it.


It's a full node run by you. They just host it and provide a we app to manage it.


Does it work all the time. Our current compressor is also ffmpeg, but I don't think it compresses really well most of the time. ☹


On Messages, click + and public


It would be nice to have this baked into the app somehow.


No, they can only close the channel.


How the hell you read all that (which includes personal paid relays) and conclude it's centralizing? The international relay is used for reach in case people's client won't follow the outbox model. It's a fall back.


Mint operators can run away with people's money. ☹


How long in the future is in the future? :)


Dumb me, it's already adjusted.


I am strongly considering deleting it and the follower list from profiles. No one goes there anyway.


People just create new accounts and keep switching them. But If you a looking for a specific impl, I am all ears :)


What's the right price on your mind?


Users don't even want to chose a relay... I am not sure if I will ever be comfortable with ecash mints.


At some point Primal will start charging a similar amount as well, there is no way around it. These types services can only be free for a short amount of time.


Quite expensive for new users though. 🤔


Primal-style wallet integration, but through single-click creation of a self-custodial, non-kyc nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgnwaehxw309aex2mrp09skymr99ehhyecusqvd6 Hub instance with in-app channel management directly on Amethyst through Nostr Wallet Connect? 🤔

Would you use it at the current Alby hosting prices?


nostr:nprofile1qqsyv47lazt9h6ycp2fsw270khje5egjgsrdkrupjg27u796g7f5k0spzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgjwaehxw309ac82unsd3jhqct89ejhxqgnwaehxw309aex2mrp09skymr99ehhyecusqvd6 how can we simplify the onboarding process for people like Terry?


Just to get your posts. Now repeat all the duplicates for each follow.


Data use. You are asking your followers to download duplicated content from each relay in the list.


Do they support blog posts already?


Which client shows the "loading"?


Hopefully analysts and educators out there can turn this quick and dirty post into a real guide with deeper analysis of what each relay operator is bringing to the table, their promises and policies. There are over 2000 relays out there. Lots of options. There is something for everyone.
nostr:naddr1qq9hyetvv9uj6um9w36hqq3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqp65wjvcq4q


Hopefully an educator will turn this shitty post into a real guide with ways to evaluate relays out there.


Full bleed is better for images but a lot worse for texts to the point that users spend less time reading text and more scrolling through images. The current design is optimized for text notes.


Nice! I hope this dynamic relay command can help you change those limits on demand and let Clients adjust their queries.
https://github.com/nostr-protocol/nips/pull/1434


Shortish db (only last 3 months), but for small and large notes.

Be the hub that connects every human post in realtime. Neither Tor, nor archival stuff.


Remember, min 2 and max 3 relays in each of the sections on Amethyst. Only the General Section can have more.


If you don't know where your posts are, you might as well just stay in the centralized Twitter. You either take control of your relay lists, or they will control you. Amethyst offers several lists of relays for our users. We are going to go one by one to help clarify what they are and which options are best for each one.

## Public Home/Outbox Relays

Home relays store all YOUR content: all your posts, likes, replies, lists, etc. It's your home. Amethyst will send your posts here first. Your followers will use these relays to get new posts from you. So, if you don't have anything there, **they will not receive your updates**.

Home relays must allow queries from anyone, ideally without the need to authenticate. They can limit writes to paid users without affecting anyone's experience.

This list should have a maximum of 3 relays. More than that will only make your followers waste their mobile data getting your posts. Keep it simple. Out of the 3 relays, I recommend:
- 1 large public, international relay: nos.lol, nostr.mom, relay.damus.io, etc.
- 1 personal relay to store a copy of all your content in a place no one can delete. Go to [relay.tools](https://relay.tools/) and never be censored again.
- 1 really fast relay located in your country: paid options like http://nostr.wine are great

Do not include relays that block users from seeing posts in this list. If you do, no one will see your posts.

## Public Inbox Relays

This relay type receives all replies, comments, likes, and zaps to your posts. If you are not getting notifications or you don't see replies from your friends, it is likely because you don't have the right setup here. If you are getting too much spam in your replies, it's probably because your inbox relays are not protecting you enough. Paid relays can filter inbox spam out.

Inbox relays must allow anyone to write into them. It's the opposite of the outbox relay. They can limit who can download the posts to their paid subscribers without affecting anyone's experience.

This list should have a maximum of 3 relays as well. Again, keep it small. More than that will just make you spend more of your data plan downloading the same notifications from all these different servers. Out of the 3 relays, I recommend:
- 1 large public, international relay: nos.lol, nostr.mom, relay.damus.io, etc.
- 1 personal relay to store a copy of your notifications, invites, cashu tokens and zaps.
- 1 really fast relay located in your country: go to [nostr.watch](https://nostr.watch/relays/find) and find relays in your country

Terrible options include:
- nostr.wine should not be here.
- filter.nostr.wine should not be here.
- inbox.nostr.wine should not be here.

## DM Inbox Relays

These are the relays used to receive DMs and private content. Others will use these relays to send DMs to you. **If you don't have it setup, you will miss DMs**. DM Inbox relays should accept any message from anyone, but only allow you to download them.

Generally speaking, you only need 3 for reliability. One of them should be a personal relay to make sure you have a copy of all your messages. The others can be open if you want push notifications or closed if you want full privacy.

Good options are:
- inbox.nostr.wine and auth.nostr1.com: anyone can send messages and only you can download. Not even our push notification server has access to them to notify you.
- a personal relay to make sure no one can censor you. Advanced settings on personal relays can also store your DMs privately. Talk to your relay operator for more details.
- a hidden, but public relay if you want DM notifications from our servers.

Make sure to add at least one public relay if you want to see DM notifications.

## Private Home Relays

Private Relays are for things no one should see, like your drafts, lists, app settings, bookmarks etc. Ideally, these relays are either local or require authentication before posting AND downloading each user\'s content. There are no dedicated relays for this category yet, so I would use a local relay like Citrine on Android and a personal relay on relay.tools.

Keep in mind that if you choose a local relay only, a client on the desktop might not be able to see the drafts from clients on mobile and vice versa.

## Search relays:

This is the list of relays to use on Amethyst's search and user tagging with @. **Tagging and searching will not work if there is nothing here.**. This option requires NIP-50 compliance from each relay. Hit the Default button to use all available options on existence today:
- nostr.wine
- relay.nostr.band
- relay.noswhere.com

## Local Relays:

This is your local storage. Everything will load faster if it comes from this relay. You should install Citrine on Android and write ws://localhost:4869 in this option.

## General Relays:

This section contains the default relays used to download content from your follows. Notice how you can activate and deactivate the Home, Messages (old-style DMs), Chat (public chats), and Global options in each.

Keep 5-6 large relays on this list and activate them for as many categories (Home, Messages (old-style DMs), Chat, and Global) as possible.

Amethyst will provide additional recommendations to this list from your follows with information on which of your follows might need the additional relay in your list. Add them if you feel like you are missing their posts or if it is just taking too long to load them.

## My setup

Here's what I use:
1. Go to [relay.tools](https://relay.tools/) and create a relay for yourself.
2. Go to [nostr.wine](https://nostr.wine/) and pay for their subscription.
3. Go to [inbox.nostr.wine](https://inbox.nostr.wine/) and pay for their subscription.
4. Go to [nostr.watch](https://nostr.watch/relays/find) and find a good relay in your country.
5. Download Citrine to your phone.

Then, on your relay lists, put:

Public Home/Outbox Relays:
- nostr.wine
- nos.lol or an in-country relay.
- <your.relay>.nostr1.com

Public Inbox Relays
- nos.lol or an in-country relay
- <your.relay>.nostr1.com

DM Inbox Relays
- inbox.nostr.wine
- <your.relay>.nostr1.com

Private Home Relays
- ws://localhost:4869 (Citrine)
- <your.relay>.nostr1.com (if you want)

Search Relays
- nostr.wine
- relay.nostr.band
- relay.noswhere.com

Local Relays
- ws://localhost:4869 (Citrine)

General Relays
- nos.lol
- relay.damus.io
- relay.primal.net
- nostr.mom

And a few of the recommended relays from Amethyst.

## Final Considerations

Remember, relays can see what your Nostr client is requesting and downloading at all times. They can track what you see and see what you like. They can sell that information to the highest bidder, they can delete your content or content that a sponsor asked them to delete (like a negative review for instance) and they can censor you in any way they see fit. Before using any random free relay out there, make sure you trust its operator and you know its terms of service and privacy policies.

You can either take control of your relay lists, or they will control you.

This is a long form article, you can read it in https://habla.news/a/naddr1qvzqqqr4gupzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqq9hyetvv9uj6um9w36hq9mgjg8


Take control of your verifiable life.
nostr:naddr1qq9hyetvv9uj6um9w36hqq3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqp65wjvcq4q


Devs, this new comment structure is getting ready to merge. Please take a look on the new ways to reference root and parent posts in reply threads. It won't replace kind1 replies, but it will work for everything else.
https://github.com/nostr-protocol/nips/pull/1233


Devs this new comment structure is getting ready to merge. Please take a look on the new ways to reference root and parent posts in reply threads. It won't replace kind1 replies, but it will work for everything else.
https://github.com/nostr-protocol/nips/pull/1233


There is no point of ever making 5 posts that are exactly the same. At that point you are just spamming everyone.


You can always disable the filter. But 5+ equal posts work really well. It gets rid of almost all the spam that is on nostr


It's not automated. You have to open a picture in full screen first, click share and add to gallery.


Yes https://github.com/vitorpamplona/amethyst


5 equal posts in close proximity (last 1000 posts + comments)


We really need to buy the .nostr top level domain.
nostr:nevent1qqsgtqdfeq8jnud7fuca3g6gzcfnwy4k3gjrg6vqzpl7rgek0xqk30cpzpmhxue69uhkummnw3ezumt0d5hsygxhqr7pp4zha6hy7qhtqnt3tgz5sdlx3ghz6qgfwyuzchsszmwfncpsgqqqqqqsrsu0vz


I believe they are Global by default 🤔


Last one was 9 days ago. So I don't expect anyone to see them in the feed.

but here it nostr:nevent1qqsdsg6x7uujekac4ga7k7qa9q9sx8gqj7xzjf5w9us0dm0ghvf4ugsntg3xc


It just displays a torrent when it shows up in the feed and if you click it it will open in your torrent app :)


Are you using Amber by any chance? Amethyst will request Amber to decrypt every time the event comes from any relay


yep. That's what I do on https://crafters.amethyst.social/


"<thing> doesn't scale" is one of the dumbest things you can say to any new idea. Everything scales. If there are users using it, humans will find ways to scale it.

Scaling issues are always the best problems to have.

Now, if no one uses your thing though.. then it really won't scale. But not because it can't.


Keep in mind, there is no need to do everything.

There are largely 3 separate ways to do e-commerce:
- Shopify (my store, my things)
- Ebay (somebody's store, my things)
- Facebook Marketplace (no store, my things)

These are 3 separate product categories. Mixing these requirementrs in one project won't be good. Just pick what you are solving for and go for it.


Don't forget to setup your npub.pro site :)


Mas eles tem via extensao sim.


For all the new users, don't forget to setup your own webpage at npub.pro 😎

You can list your notes and/or your blogposts and separate them by hashtag.


nice!


What do we have here... Is it my own shop page with blogs, store and checkouts? hah... 😎
https://npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z.cypher.space/


You should make a collection of these posts in a new account and build a npub.pro site that just lists them as a guide to new users.


Will users be able to change the design like Shopify does? Can they also run their own servers?


let's go!


Personal domain is key, though. People want to develop their own brands. Otherwise, it's just ebay.


Do you know which relays they were saved?

Ideally you just need to move them to your Outbox/Home relays.


So, who is developing the Nostr-native Shopify?

Not shopstr, but a way to develop one's own store as a separate website as a service.

GM.


Try setting up your relays. Amethyst doesn't know where to get your posts.


It should work for DMs and zaps


Easier format nostr:nevent1qqsdagje94f42zqr0c8vn2rtzqmvtltsp09mdjzkkk7j4phg0u7u5fqpz3mhxw309akx7cmpd35x7um58g6rsd3e9upzq3svyhng9ld8sv44950j957j9vchdktj7cxumsep9mvvjthc2pjuqvzqqqqqqye4gr94


Push only happens on DMs and Zaps :)


Use Obtainium https://blob.satellite.earth/2bd7e308c1797d64fca09b1d61e9bde24c68dd45e501c7383eff1e85392df11f


Ohh you need to install the Fdroid version of amethyst. The one you are using uses the Playstore to send notifications


You don't have inbox relays setup. Amethyst doesnt know where to get the Zap event and the sender doesnt know where to send it to.


Settings, on the left drawer. Make sure to make a UnifiedPush service installed, like NTFY


edit  ( and drafts... and edit proposals ) are super awesome features of #Amethyst..   once you get hooked ..it is impossible to go anywhere..

only one downside .. many other clients still don't show edits ..  hope they will catch up soon ..


What are you missing? FYI, we just fixed a few bugs on version 0.90.3.


Folks using Amethyst with UnifiedPush: see if the version 0.90.3 that just went out has working push notifications.

We fixed a few bugs on the use of Unified Push.


Test 0.90.3 that just went out


Ntfy is borked in the current version. Sending a new one right now.


click on them and mark to not ask anymore


see if it still happens. I just restarted our server


when do you see them? everytime you re-open amethyst?


Fdroid version?


hello everyone!


I was thinking on building a marketplace, that helps relays offer services for each type and users can just explore options.

From a list of all available options, we can then filter by WoT and offer some preferences trogether with the limitations of each pitch.


Hard to measure fast and stable. All relays get slow from time to time, and they all go offline for minutes/hours at a time.


fixed on 0.90.2


That will just centralize in the same large relays we have today as well.

Also, the Outbox and Inbox relays should not be based on what your follows like. We can present a list to make it easier to type, but it's not about them.

It's about where you do you want to store your own notes.

In the extreme, each user should have their own personal relay in both Outbox and Inbox options.


It's really hard to recommend anything. It's like recommending a house. It's really up to the user to develop a relationship with the relay operator and build the trust that is needed to add the relay to their list.

Amethyst recommends a few, but it's a very centralizing action... everyone will just accept our recommendations... which is BAD.

I don't really know how to solve this.


Not personally, but close colleagues did a few of those. 4-5 months to get a response.


of course I had to fuck something up :)


Let's get that IANA request done as soon as possible. It's simple paperwork, but it takes time to go through (months).


#Amethyst v0.90.0: Torrents and Outbox restructuring

https://image.nostr.build/9ffdec74046ed059f8b58f1bce140b1780850a123e948a7f7510ef81af7654f5.jpg

This version adds support for NIP-35 Torrent files (dtan.xyz), adds significant memory pruning for encrypted payloads and large events (DMs, Notifications, Zaps, etc), and completely restructures the way most of our caching works to facilitate immediate subscription updates using the outbox model on custom feeds by NIP-51 lists. This version also offers new defaults for NIP-65 and DM relay lists for new users and fixes several bugs and inconsistencies.

Features:
- Adds support for NIP-35 torrents and their comments
- Adds a simplified sync Signer to the Quartz library
- Adds Default lists for NIP-65 inbox and outbox relays
- Adds Default lists for Search relays
- Adds local backup for UserMetadata objects
- Adds local backup for Mute lists
- Adds local backup for NIP-65 relays
- Adds local backup for DM Relays
- Adds local backup for private home relays
- Improves caching of encrypted DMs
- Updates Twitter verification to X
- Improves the rendering of QR Codes
- Adds support to Delete All Drafts

Code Quality Improvements:
- Separates Account actions from Account state in two objects
- Changes Startup procedures to start with Account state and not the full account object
- Moves scope for flows in Account from an Application-wide scope to ViewModel scope
- Removes all LiveData objects from Account in favor of flows from the state object
- Migrates settings saving logic to flows
- Migrates PushNotification services to work without Account and only Account Settings.
- Migrates the spam filter from LiveData to Flows
- Rewrites state flows initializers to avoid inconsistent startups
- Finishes the migration of the service manager to the Application class
- Moves to hold the all feeds in stateflows
- Updates benchmark, composeBOM and firebaseBOM to the latest versions
- Moves the default zap type to a state flow and avoids passing on to the screen when using the default value
- Removing unecessary livedata objects for translation services
- Moves lastread routes to mutableStateFlow
- Migrating livedata to flow for contact list updates of the user.
- Adds a destroy method to FollowList state for consistency
- Moves follow list states to the AccountViewModel
- Migrates Notification Summary to the new state model
- Moves the notification screen to the new state model instead of viewModels
- Refactoring Moving feed status from ViewModel to State objects

Interface Improvements:
- Show only 3 users in the recommended relays section
- Creates links to njump when events can't be found on Amethyst
- Adds support for MOD reports
- Displays commitment PoW if present
- Changes relay set kind to be NIP-51 consistent.
- Adds more information to when error messages are not available in the relay stats.
- Adds context to highlight events
- Adds previews to test markdown rendering
- Improves the look of inlinde code in markdown
- Improves badge display

Performance Improvements:
- Adds pruning for giftwrapped messages
- Fixes clearing of flows and live data object pools before removing notes from the local cache
- Improves stability of composables
- Migrates caching of decrypted value outside of the Event class
- Removes encrypted parts of NIP-17 from the cache
- Removes old NIP-04 messages from the cache
- Avoids deleting new NIP-17 plain text chats from memory
- Avoids bottom nav recompositions
- Simplifies nav bar selected calculations
- Avoids remembering edit lists that will never exist.
- Improves speed of chatlist rendering

Bug Fixes:
- Fixes lingering cache and threads still active after killing the app
- Fixes crash when opening the Relay screen with empty urls as relays.
- Fixes horizontal padding of the chat messages
- Fixes the download of 1000s of NIP-65 relay lists because some relays consider empty lists as null and return everything.
- Fixes fdroid push registration to re-register even if the saved distributor was already selected.
- Fixes crash when the relay url of a user is duplicated.
- Fixes padding of short quotes
- Fixes slow down when the last message on chat is a base64 image.
- Fixes the centralization of the "and more" part of relay recommendations
- Fixes miscaching flows of the relay lists from follows.
- Fixes miscache of hashtag following button
- Fixes heading sizes on markdown
- Changes Delete all events to use maximum chunks of 200 elements to avoid the 65KB stringified JSON limit of many relays.

Updated translations:
- Czech, German, Swedish and Portuguese by nostr:nprofile1qqsv4zwtz8cuwh2mvc3zdrl5853g365t9j6mn25edlul7uz0eyzt0zcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsshgmkj
- Polish by nostr:nprofile1qqsdyfz0ewdhmgp3a4r3pxvezx5r8yalrgvjn38v2ml5qrusnv7yywgppamhxue69uhhqunv9ecxcatn9ugu22zc
- French by nostr:nprofile1qqs8av5uzf4nv2q80chrmp3mj9a9dd6zjw4fmz56hsn2gzar72rxhtcpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qg3waen5te0w4kkyun9dsargwp58qhsnxcg72
- Arabic, Bengali by nostr:nprofile1qqsgs9hgjw87vz36jf2r83m5zree2q87zvs8s7kty9jljdz7wprytysppemhxue69uhkummn9ekx7mp07uqq9t
- Thai by nostr:nprofile1qqsxdhmq2cke8xk6scfyxeyfj3dyancavg6xk0v50r023gec7vsrceqpzemhxue69uhkvun9deejumn0wd68yvfwvdhk6qg6waehxw309aex2mrp0yezumn0wd68yctnd9sjumn9wsq3yamnwvaz7tm0venxx6rpd9hzuur4vghen3hm and nostr:nprofile1qqs93adzxqyt5k58xzjrta50rrdqkyxw2wxxu2495xmczgrkxpx4nacpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgpr3mhxue69uhkummnw3ez6vpj9eukz6mfdphkumn99e3k7mgpremhxue69uhkummnw3ez6vpj9ejx7unpveskxar0wfujummjvum84tx8
- Hindi by nostr:nprofile1qqs88dt78wgnzvaph6fcstfvsd98xc2qs8eg8tllwv2zlutu8ehec2cppamhxue69uhkummnw3ezumt0d5qs6amnwvaz7tmwdaejumr0dsq32amnwvaz7tmjv4kxz7fwd4hhxarj9ec82cs0t5vfr
- Spanish by nostr:nprofile1qqs07tjpyvvlq9ugdpax8h3jfrpwn7kr72k3tc7ky83tggn4et9eangpr9mhxue69uhhqatzd35kxtnjv4kxz7tfdenju6t09uq3vamnwvaz7tmjv4kxz7fwd4hhxarj9ec82c30qy2hwumn8ghj7mn0wd68ytn00p68ytnyv4mz76xu9qg
- Dutch by nostr:nprofile1qqs82l74z7g3x8j3avpn2wrjrwn855nyvmpxa4v5pftfvtv5lrvrc5cpz9mhxue69uhkummnw3ezuamfdejj7tk0drp
- Chinese by nostr:nprofile1qqsyxnuhnymz0u0xru2watmqe25vlh8vzzje9jhlsfgvsff9942gc9gpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxthwden5te0wfjkccte9ekk7mt0wd68ytnsd9hxktcpzfmhxue69uhkymmnw3ezucmc9ekhxtc24vk7q and nostr:nprofile1qqsp7cq7dw5zmyu8zep83323dzcs8dsv6grdfxmm7xt8p2pzr3jyp9spzfmhxue69uhhqatjwpkx2urpvuhx2ucpr3mhxue69uhkymmnw3ezucnfw33k76tww3ux76m09e3k7mgpzpmhxue69uhkummnw3ezuamfdejsl63s8x
- Hungarian by nostr:nprofile1qqs88rmfrp9wmfn4qq4kslly0j8futmmrgn86mu3gkc3jvcjl97p3mcpzamhxue69uhhyetvv9ujumn0wd68ytnzv9hxgtcpz4mhxue69uhkummnw3ezummcw3ezuer9wchsz8nhwden5te0dehhxarj94c82c3wwajkcmr0wfjx2u3wdejhgtcqngjsj

Download via [Obtainium](http://amethyst.social) or [Zap.Store](https://zap.store/)


We render it, but we are not creating those yet.


No that hard. They just don't need to publish their drivers + code.


Congrats!


Let's give the pope a nostr key and see if god can break it.


Somebody mentioned the idea of putting the bible on Nostr with a list of events, one for each verse. Maybe nostr:nprofile1qqsf03c2gsmx5ef4c9zmxvlew04gdh7u94afnknp33qvv3c94kvwxgspr3mhxue69uhksmmyd33x7epwvdhhyctrd3jjuar0dak8xtcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhszxnhwden5te0wpuhyctdd9jzuenfv96x5ctx9e3k7mf0ss9zgs?


Both worked in their most up-to-date versions.


I just tested primal with many black QR Codes. It read them all correctly. So, I don't know what the problem is.


The zone must be the same color of the background of the QR code. Since the background is black, the zone is black as well.

I think the issue is that some QR readers did not implement reading with inverted colors (which is in the starndard)


If it is closed source, it's not end-to-end encrypted.

Don't trust. Verify.


No relay hints. The app must find where posts from the key can be found. nProfiles include relay hints on them.


get a better machine


Samsung doesn't want it.


Need Kotlin libs for it. Right now all they have is in JavaScript


Yep, no exit.


Default for orbot is one entering node and one exit node. So, all your accounts are seen together.


Yep, batching like I do creates much more complicated queries for their indexes to deal with. It doesnt make any sense.


If the limits we see today are real (I doubt... operators are just using the defaults), they will collapse regardless.

I am just anticipating the issue.


No, but I am testing them all again. Let's hope stability has improved.

Also, before I was looking mostly at the privacy gains. For this, we could just run Tor in parallel with the regular connection. If it works, it goes there, if not, just uses the regular stuff.

Also, I need to be able to control several sessions with different exit nodes without much latency. Let's see how that goes.


There is no other plan though. I don't think I have an option at this point. Relay software is still in the dark ages.

Plus, they would never know anyway.


Now do Amber via nip46 and get your keys out of  desktops.


Comms is a super set of money, thus Nostr will always be bigger than Bitcoin.


Lol. My lane is all lanes.


Nostr > BTC.


nprofiles > npubs

The added relay info avoids the scramble to find the users main home relay.


Yes, up to 10 separate connections coming from the same IP


The hard part is convincing every relay to do a 10x on their sub limits.

Many are still forcing Max 10-12 subs.

Still doesn't solve the auth problem. So, it might not be worth doing it and going straight into Tor.


Bring them to Nostr! We were made for them.


I have 100s of what should have been separate subs packed into 10 subs right now.

Max number of filters, max number of kinds in each filter, max number of follows (usually 2k), max number of etags, etc. I am hitting several limits at the same time now.

I also need AUTH for separate accounts in the same connection, which doesn't seem feasible without a massive change on how Nostr filters work.


Considering adding native Tor into Amethyst just to go around relay per-connection limitations.

Then we could keep all accounts connected and downloading their events at all times, while using a separate exit IP for each nostr filter.

There wouldn't need to be a global account switcher. Users could have 100s of accounts working together.

Plus, huge privacy gains.


* profiles.

npubs are insufficient from a sharing standpoint.


Support is not officially available yet.


Only until you realize every manufacturer locks you in. It's not about a avoiding Google specifically, it's about avoiding the manufacturers control over you and your data.


One day Tor libraries will actually work. Until then, it is what it is.


Just a week in and GrapheneOS already supports the Pixel 9, Pixel 9 Pro and Pixel 9 Pro XL.

Gotta love open source.


I wanna join relays that block NIP-04 DMs.


Relays are just temporary storage to make sure notes get to the destination even if people are offline. They are not here to protect you or your data. Especially free ones. That's not their goal in the system.


Yep. That's how the protocol works.


Maybe one day... There are too many posts for the server to keep track on :(


I'd say it's hard to get anything over 70 :)


Probably just regular variance?


Let's hope this is true. https://image.nostr.build/26099af4deeb297737c8a5ea0fd85ba995a3c24b9133c8dcbb892196c8f2343d.jpg


A friend has the equipment to make it. It smelled the entire house 😀


After I got freshly made garlic powder a few months ago, I have given up on the quality of pre-ground spices :(


Every dinner time when we need to get out of the basement.


Go where no Nostr dev has gone before.


Test worked.


Looks like no Nostr dev will be able to fly to Europe very soon :(


Looks like you have an empty item in your relay list. You can change it here: https://metadata.nostr.com/


I tend to think forks are good, even when they don't work or don't implement the things people want. I think this is the case here. Maybe what we need to find is another dev that can join both projects and keep things up to date without much fuzz.


Click and hold the zap button and press the paste button on the dialog


Something like https://pyramid.fiatjaf.com/  but for DMs?


Feel free to write a tutorial. We need it indeed.


Humm.. I know mine has been slow for sure. I will run some tests on this.


That might be the receiver not sending zap event into the requested relay 🤔


One-click zapping from ecash works!
nostr:nevent1qqsr8729cvf5jscma339ef796el9w0z48hhghudkp6kga376svs308gpz9mhxue69uhkummnw3ezuamfdejj7q3q2rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sxpqqqqqqz2t3tmz


It's the same I have been using :)


What do you mean be done with the pay to dev work? Implementing Monero doesn't solve income for devs. 🤔


Hopefully somebody will build a DVM for that


Yeah, it helps marketing, but I hate those watermarks so much. Let people share. There is no need to put our brand everywhere.


Too heavy to track all new follow notifications from all relays. Primal does that through a centralized service that we will never build.


nostr:nprofile1qqsfhc97pejd8z3f488vnfwgaawcw0ptlffk9f94trd9la5mc09ms8spzpmhxue69uhkummnw3ezuamfdejszrthwden5te0dehhxtnvdakqz9mhwden5te0vesky6tpdchxummnw3erztnrdakslwh58f is a legend. Nostr Nests working in Nostur is a dream. It works perfectly. https://i.nostr.build/gp77UTPU3Y57zjsX.jpg https://i.nostr.build/olg4yozDiFBq6Rue.jpg


High motivation and average skills > high skills and average motivation.


Amethyst doesn't verify anyone. It's truly free. You can look for NIP05 services out there to add to your profile.


Nostr > BTC

GM.


You can now directly connect #Amethyst to your phone's #minibits wallet, and it WORKS!

nostr:nevent1qqsg9z22zhs5czd8rll39pj7a7npvzuxl8nasjvryn8cakrhxwmt5vcpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsygql7xtpcplpf9xsa4rzvsmxq9przjus0qn2wqf3vvrkqmjtnllzrspsgqqqqqqs6czzrz


You have to manually add them. Just open the image in full screen, click on the share button and add to gallery.


Just hit the default button and save :)


In theory, yes.


yep... this whole thing is quite alpha yet. :(


Somebody needs to help me out converting the Kotlin code to Kotlin Multiplatform :)


Make sure you are using search relays. Our search is directly dependent on their availability.


Import content from Ghost to Nostr, anyone?

Here is a work-in-progress tool for that: https://npub.pro/import-ghost

You can bring articles from your Ghost site to Nostr and make them accessible for people here to zap/react/comment.

Eventually the tool will let you copy all website settings from Ghost to an npub.pro site. For now - content only.

Ghost is great, but nothing beats adding your cryptographic signature to your article and broadcasting it to an open interoperable network, right?!

P.S. A reminder about a similar tool for Twitter: https://exit.pub


Me: meme fun.
Them: let's get crazy rich. https://video.nostr.build/bc2e45de93ab42c722509198e14b6c2ea9f7ee8db9df93a2ff76ea1210af58fd.mp4


Thank you!


The Amethyst of iOS is getting ahead. I gotta pick up my pace. 🚀
nostr:nevent1qqs0en32xfnraqw83w4y35c625z9lk5vzsd3ykn29dq4tej47j3239qpzemhxue69uhhyetvv9ujumn0wd68ytnwv46z7q3qn0stur7q092gyverzc2wfc00e8egkrdnnqq3alhv7p072u89m5esxpqqqqqqzq3u8uw


ok, got a new channel. I think we are back :)


Vitor Pamplona

Nostr's Chief Android Officer - #Amethyst


Hum.. alby did close my channel this morning.. let me check. I do have another one with 2M inboud but maybe it's not picking that one up.


Word can be added to the hidden words.

The hard part of this is that you end up downloading everything to just see the few that are real. Data usage goes through the roof.

You can also filter the relays to use for Global on the general section of amethyst.


4m dollars in fees alone in the past hour? 👀


They are. Only crazy people like me would go for the opposite.


Warning for all the new devs... https://image.nostr.build/a6d507ec2fe963c4994546b1ad7b13af4f4833a30eef44c1e1d8c01207c0edff.jpg


Nice!

But FYI, every new client is blazingly fast. They all get super slow over time.


New version has a fix for the Ntfy registration. Hope that solves it.


Just use Obtainum. F-droid is super slow (weeks) to update new versions.  https://blob.satellite.earth/2bd7e308c1797d64fca09b1d61e9bde24c68dd45e501c7383eff1e85392df11f


No good way to do this. Best we could do was to use automatic translations using in-device translation models from Google.


habla.news ?


Just like GitHub

https://image.nostr.build/34ad62979aa5cd07e1e57e6849dfcc66051f7f84da777db906ada9686d769c87.jpg https://image.nostr.build/585b400c14851206ea5badadc0d679a8cbb759b41c75a05318097f7cb49654ab.jpg
https://image.nostr.build/9d760a73c5b9daa33317598b46d78d503b33429770ddc6f2b327a01022df78f1.jpg


Which part? We already have DVMs on Amethyst :)


Story of my life https://image.nostr.build/850102fa53524f319ea37f6434becff6e89ea0a4f8a68c99bcc3af1d49c0a279.jpg


👀 https://github.com/vitorpamplona/amethyst/commit/a05ad6e68697b9d0607c34f791023e973c272eb3


nice!


https://m.primal.net/KGmY.mov

Fountain 1.1 with #nostr is now live on iOS and Android!

Why Nostr?

We regularly hear from both listeners and podcasters that the social features in Fountain are a great way to discover content that's worth listening to.

When you support a podcast, or comment on an episode, your message is surfaced to your followers in the Fountain home feed and anyone that sees these can add the content to their library.

But this came with a few problems. When you first start using Fountain you wouldn't have any followers so your posts wouldn't get seen. If you wanted to share something you were listening to, you had to choose between leaving a comment on Fountain, or sharing on another social platform.

Today we are excited to announce a massive update to Fountain that solves these problems with Nostr:

- You can bring your existing profile and followers to Fountain
- Your boosts and comments will be surfaced in other Nostr clients
- Posts shared from other Nostr clients relating to audio will appear in your feed
- Conversation and interactions now flow freely across multiple apps

Read more about the new Fountain nostr features here: https://blog.fountain.fm/p/1-1


You might be filtering it. Check if the top bar list in Notifications is marked as Global


Then you can remove the key from amethyst and just use Amber as a signer for all apps.


Thats what the DM inbox relays do :)


It already works. Just use Amber sign on Android via NIP46 bunkers.


Nice! Congrats!


no, but freedom is never free.


you can. But this is the easiest way to do it right now.


Se vc transmitir monero via lightning, vc perde a privacidade do monero e usa a do lightning. Nao sei se faz muito sentido.


yep, albyhub is not about privacy, but self-custody. You are still trusting Alby + LSP provider with your transaction data/zaps.


getalby.com 10K sats/month
nostr.build 5.7K sats/month
relay.tools 12K sats/month
nostr.wine 2.5K sats/month
inbox.nostr.wine 2.5K sats/month


wow, i didn't even know users could disable that permission 🤔


no, but they are phasing the custodial wallet out by decreasing the limits over time. So, at some point, everybody will migrate over.


Why are you saying that?


Nostr Freedom Pro setup:
- AlbyHub for self-custodial lightning wallet and Nostr Wallet Connect for one-click zaps
- nostr.build pro account for unlimited hosting of image and video files
- nostr.wine account for all your posts
- relay.tools account to collect all your posts and all notifications to you
- inbox.nostr.wine account for all your DMs


If the DVM doesn't reply in a few seconds, maybe the DVM is offline


nice!


It's not. It fails frequently, it doesn't offer Nostr Wallet connect for one-click zaps and it's custodial.


What's a better lightning wallet with zap services and nostr wallet connect?


Interesting. But yes, the top bar filter is different per screen.


What's the lie?


Best way to use Nostr is via AlbyHub. You can pay for their hosting or install it on your own server. Either way, it's self custodial. It's your keys.
nostr:nevent1qqsgcpkcl8da0jy99jl4s6uyddh9wts04gqjva5vzwetkwp2pfg8fzgppemhxue69uhkummn9ekx7mp0qgsg8lg8m6dhvve5ejw5dunctsj43ekza2l705xxass5ve7t4mzs63crqsqqqqqpgv26k9


Change it to Global to see all replies.

Also, keep in mind the author might have removed you from the notification list of the note


See if the top bar of the Notification page says Global or if it is filtering by a list of users.


Thanks! Looking for your feedback to this: https://github.com/nostr-protocol/nips/pull/1434


notification as in push notifications or on the 5th tab at the bottom?


Connection limits also help relays create multiple plans that users can subscribe to. For instance, relays can offer a basic plan for kind 1 notes and a pro plan to store all drafts privately.

Or a basic plan where clients can only make 1 request per second and a pro plan with 50 reqs per second.

They just need to let the Client know when different plans are active by sending the limits payload.
https://github.com/nostr-protocol/nips/pull/1434


Yeah, go to the relay settings. First section is public outbox, second is public inbox. It's the same list, but broken in two.


Weird but free :)