List deleted by owner


If they are there, then they should be available to other apps, but you have to grant those specific apps permission to access them. Normally, you receive a prompt for this when launching the app for the first time. It's also possible you granted access to Contact Scopes, a unique #GrapheneOS security feature that you can read about below. If it was Scopes, by default the app cannot read your contacts. You can add exceptions, though.

https://grapheneos.org/usage#contact-scopes


I'm using #Amethyst paired with #Amber, but Amber is not invoked when I tap block & hide. Maybe this is an Amber issue?


Block & hide user function is not working. I'm still seeing those npubs in feed even after stopping & restarting #Amethyst. nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z


nostr:nevent1qqsqvuhsz0vqtyukt2cf33f86zcpnsv4ppk809rwnzuu5rym8lnml6szyzkwz0eu52ke4ntru5c9kgrlp8vvs4n0qygeq8ugsl6qlfzl82djzqcyqqqqq2sf3vmce

*From the user's profile mainscreen


Looking for a recommendation: epub reader with highlighting & notes support

#asknostr #epub #android


Can someone explain how to use #fedimint in #mutiny? How do you get an esat balance with a federation? How do you spend from that balance? #asknostr


Imagine you’re a bitcoin company and not on nostr lol


I like the subscription/pay-per-use model, but I also think there is a place for a minimal core of services comprised mainly of the executive and judicial functions. Think protecting territorial sovereignty, diplomatic relations, criminal prosecution, and local police force.  The tax on these basic core services could be a flat head tax, e.g., $200 per person per year. This is much easier to calculate and enforce than an income or consumption tax. Everything else could be subscription/pay-per-use. Want to drive a car on public roadways? Pay an annual roadway subscription tax based on the weight of your vehicle. The weight of a vehicle directly correlates to wear on the roadway and eliminates the revenue discrepancy between electric and petrol vehicles. Want to forego the personal vehicle and use public transit? Buy the subscription or pay as you go. Same model can extend to all other non-core services like healthcare and education. This forces public services to compete directly with private options and gives citizens more choices. Previously, the pay-per-use model was difficult and inefficient for many use cases. Thanks to digital currency like lightning or cashew, this is now irrelevant.

Re. legislative functions, I tend to think legislators should be publicly elected volunteers who receive little-to-no compensation. They should also be term limited.


Do you have a link?


When copying note IDs from Amethyst, I have to clear the "nostr:" prefix for nostr.band. Also, the nostr.band "view relays" function does not appear to work. #nostrband


Same issue in 0.84.3


This is awesome


I open the app every single day for this very reason


I open the app every single day for this vary reason


Reason always says "Channel closed because user manually force-closed the channel" - which has NEVER been true. In the last incident, I was trying to zap a zap goal with splits for #Amethyst devs.


Same here. I've now lost 3 channels to #Mutiny random closes.


Well, just tried to zap you all from #Mutiny, and my channel force closed - again. Lightning sucks. Sorry guys. Keep up the good work!


Even if you implement nip49, I still think you need to include nsec export. Vitor says nip49 is not meant to replace nsec, and nsec should still be stored in a separate place. If you permit a user to generate new keys, then you need to permit nsec export. Otherwise, users might be left with a lock in situation to your bunker - especially now when client support for all these new nips is incomplete and buggy.


Thanks! I will let you know how it goes.


The mute option for this chat does not appear to work.


Can you give more detail? I've used this method without issue


nostr:nevent1qqsrfx3pchd6sn3q0zst9pacu07mqztqfse3ksclnfwswksrcthd60qpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzpj5fevglr36atdnzyf507s7j9z823vkttwd2n9hlnlmsflysfdutqvzqqqqq9g43kyah

Interesting. Thanks for the explanation! So maybe clients should be handling compression before upload to avoid false flags like this.


Help me understand. What does this mean?

https://image.nostr.build/e10370da49e6968c145f9543697d99408c3aa306b55fa0dead9461c2c29bfd0b.jpg


It would be nice if #Amethyst showed as a "share to" option in the native Android share function - e.g., image upload with a new note or DM.


nostr:nevent1qqsts3uye99gp0pgfsavupt7px9pr8a8xlunenk4t28xadacphkvwqgpz3mhxue69uhhyetvv9ujuerpd46hxtnfdupzp64cyur7yg0cau2x88m47xlksvmkdrxn77v80sfapnak4t6adfeyqvzqqqqq9gsw250w

Good idea, but already tried that. Would work great if Amethyst supported the Android "share" menu. Unfortunately, it currently does not.


I get that images might be stored on a different media server other than the relay(s) storing the note, but we are uploading images via #Amethyst client, correct? How does Amethyst handle this EXIF data before passing the image on to the media server?


Does #Amethyst? strip metadata (like geotags) from images before writing to relays?