If i live and spend 99% of my time where I'm not in Bluetooth range of anyone else, do i have any use for this app?

Zackly.

With you on this 100%. coffee that tastes like coffee is coffee. Fruit punch should stay fruit punch.

nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z thank you for the recent guidelines for setting up relays; that was very helpful. I did a bunch of cleanup on my configured list of relays in gossip, and pared them down quite a bit. Then I advertised my current relay config from gossip. But when I open Amethyst on my phone, I still have a lot of relays configured in there that I don't have in the set I advertised from gossip. It seems like amethyst is either not picking up or (partly or fully) ignoring the kind 10002 event I'm advertising from gossip.

cc: nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c

Dark.

Thanks for your assistance.

We can close at least one of those issues.

more chorus logging

success!

Ja. I have done, but there are always little corner case pains in the ass with devices. It's not the hardware I'd miss, it's macOS.

God Dammit. I still have my desktop on Sonoma because I'm afraid that Sequoia has too much of that crap in there. But my laptop (which i hardly use and has nothing i consider sensitive on it -- it's mostly hosting ollama for me) is on Sequoia. I've been putting off the latest update and now this makes me want to put it off forever.

so pissed at apple for all the invasive shit and updates defaulting me to opt in to new stuff that sends my bits to them behind the scenes. I've been using apple hardware for my workstation since literally 1984. I manage linux servers for $ and I've run linux desktops before but macOS is just so much better. But all this AI bullshit and unkillable background processes scanning my photos is making me seriously think about getting rid of all the apple hardware and starting over again with a linux desktop.

Fuck you Tim Apple.

test with no image

Testing attaching an image.

No file and line number. The error I quoted was the entirety of the error message and it was from gossip. I will open a ticket in the gossip repo with a screenshot.

Testing blossom with gossip and chorus. Hoping to attach an image and have it just work.

i get this error in gossip: "SerdeJson Error: EOF while parsing a value at line 1 column 0"

Running latest master of both chorus and gossip.

What do i need to configure to make it work?

nostr:npub1acg6thl5psv62405rljzkj8spesceyfz2c32udakc2ak0dmvfeyse9p35c

I was able to create a semi-kludgy work-around.

1. I created a new, non-private list in gossip.

2. i put one non-private npub in the list.

3. i put a bunch of other npubs into the list and toggled them each to private individually.

When i published this list from gossip, it was quickly available in Amethyst and the feed in amethyst does include all the private (encrypted) npubs from the original gossip list. I pulled down the kind 30000 event from my relay and confirmed that all the private npubs are in fact only existing in the content tag in an encrypted blob. The only clear-text ('p') npub is the one non-private contact i added in step 2.

This works but is a PITA.

cc nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z

PRIVATE FOLLOWS LISTS ON AMETHYST!

I request the next development be making Amethyst again be able to parse my private follows lists so I can start using it again.

Why nostr matters in ALL CAPS.

TYPING IN ALL CAPS IS SELF-AUTHENTICATING.

Amethyst used to see private lists created by gossip. I just recently alerted nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z that this is no longer working. But it did definitely work a few weeks ago. Unfortunately, I can't say what version it stopped working with.