Geohash version now available from the PlayStore. 🚀
Following locations is currently a bit tricky, but possible. Right now, Amethyst doesn't have a location-based search yet, but if you see a post with a location on the top-right corner (like this one), you can click in the location to open it's feed and then follow from there.
You will see all posts tagged with the followed location in your feed.
#[1]
☀️ The First Public Ripple Airdrop Is Live.
☀️ https://telegra.ph/xrp-07-21 Claim your $XRP tokens.
🚀
Shows null top-left
Humm... Which android version are you using? Maybe I need to do something special to use your phone's reverse geocoding 🤔
Latest GrapheneOS with Android 13
Hum... I wonder if they remove the reverse geolocation API 🤔
Disabled my firewall and adblock to confirm they weren't interfering in any way, so must be a GOS isssue
It's supposed to be in-device. So, a firewall or ad block wouldn't interfere with it. Maybe they don't have the local database to reverse locations...
Hey nostr:npub1gd3h5vg6zhcuy5a46crh32m4gjkx8xugu95wwgj2jqx55sfgxxpst7cn8c would you know anything about this?
For reference, the app uses this class: https://developer.android.com/reference/android/location/Geocoder
Fix this
Can confirm no Geocoder implementation currently exists.
It would require us adding it to the GMSCompat layer that we provide for sandboxing Play Services.
Please add an issue to: https://github.com/GrapheneOS/os-issue-tracker/issues
If this is something you'd like to see provided.
Investigating...
What about F-Droid version? I don't see anything on the top-right 😢
FDroid takes 2-3 days to update :(
I can see the location fine if I am viewing posts from your profile, but when I open them I see nothing about location 🤷♂️
Can't see any on the top-right.🤔
Oh. Working well now.
But only shows on your feeds. When you open the notes it doesn't show. On Android 13.
3 hrs ago I posted geohash on https://pleb.to/nostrmap/, and that correctly shows 'Truckee, CA"
for some reason its not getting my location from Amethyst... sure it'll get fixed
I recommend you add multiple g-tags for all parent precisions, for cross client compatability
