Merged. It's now bug-hunting time.

https://github.com/vitorpamplona/amethyst/pull/1388

Reply to this note

Please Login to reply.

Discussion

Waiting for bitchat to be merged in Amethyst :-) .. a Bluetooth client if no network .. nostr client if there is network ..

πŸ‘€

I don't want know what I'm looking at but thanks for making Amethyst for us

Yes. That's the new normal

Is that automatic, a default or did you actually add that many?

Automatic

I like that idea. Is there an APK test build somewhere?

Not yet, but it will be ready soon

Actually I found it. Since you call it outbox I assume this very message will go far and wide.

That failed, they go trough tor which is a good idea but I need to allow an app to do that. I allowed it now lets see how far this reaches.

Wouldnt this have significant performance and data consumption issues?

We will see. True decentralization is not cheap.

It can be, if the feature is optional client side someone could do this same trick as an automatic nostr proxy which then can be added as a relay. That way if opted out and with the proxy the data shifts to the datacenter. That will help users where bandwith is critical.

Yeah, we have a new proxy section on the relay list screen

I dont think so because it seems to be outbox only. I dont know how much background traffic it does just to have them on standby though.

The major problem would be the spam, if you don't choose them carefully. I have only wot and premium relays to avoid it

I think its outbox only which would be a good idea. You post everywhere but incoming you only receive from what you trust. But if all amethyst users begin posting to all relays they domt need an inbox relay in common as long as they have it in their outbox.

LOL

πŸ˜Άβ€πŸŒ«οΈ

Dang that’s a big red number

How can I test it? I need to compile it myself at the moment?

Unfortunately yes. But it will be ready soon

Its on the github action builds, no self compile needed.

It's about time. Thanks for your service Vitor ;).

I think i made a PR in January that got merged but then Vitor's huge refactor started before it got released πŸ˜‚

We're finally close to new Amethyst updates as it seems πŸš€

nostr:nevent1qqsqccl5st4w9jaf2q3w5u39j2gxpt2mwkq7238x2n5cwykl6ppst2spz9mhxue69uhkummnw3ezuamfdejj7q3qgcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqxpqqqqqqzefpy56

long time in the making!

That's a big PR! Thanks for the great product!

compiling!!! πŸŽ‰πŸ˜Ž

How are you constructing the right filters for the right relays to fetch new posts for the "follows" feed?

Are you sending filters with all the user's follows listed as authors to all relays, or you do some smart selection ?

Do you have it in your lists other than search?

It was in my search relay.. But also added automatically to the bottom ones.

Hum... If it was just on search, it should not have triggered this. But it if was somewhere else, then yes.

It was added automatically to the large amount of relays at bottom. I have added it to blocked relays so let's see if the warning goes away...

Also check if just deleting from the amount of relays solves it. I wouldn't want people having to block relays just because of this.

Ohh I see. Those are all the connected ones. You cannot control them anymore. Maybe we should put a button to add them to the block list?

I will do some testing on this as well.

Yes, adding a one click block button would be awesome. Also might need a light filter for names and paid/unpaid.