807
Street-Complete, like Pokemon Go but for good.
(lemmy.world)
I first learned of Street-Complete here and I really like it.
It's satisfying to walk around, complete little tasks, and get prizes, scratching a similar itch to Pokemon Go.
Stuck waiting for someone? Add opening hours for a few local businesses.
Have a long walk ahead of you? See if you can add/check house addresses as fast as you can walk.
Want to walk off a few beers before heading home? Complete some tasks in the bar street.
Its a very constructive way to "be right" on the internet.
@smb @openstreetmap
In my browser that can't be expanded and clicking on it just takes you to their definition of "Non-Free Network Services" https://f-droid.org/en/docs/Anti-Features/#NonFreeNet
So they're complaining that an OpenStreetMap app is tied to OpenStreetMap related services and hiding this in a way that makes it look worse than it is.
This dramatically lowers my opinion of F-Droid.
maybe the browser version isn't fully complete, or there might be a thing with css, bad browser specialities, just a bug in the webpage (did you check if it does show up in page source plaintext maybe?)
i would see the warning "bound to a specific non-changeable service as a good thing, as it would promote completely-free apps like (i think) fluffy chat, which does neither depend on a specific matrix service nor on a specific push service (i.e. it uses ntfy for push when installed, and if i choosed to use my own instance it would - i think - use that instead of the default ntfy.sh) in theory everyone could run something like osm and in practice this could come in very handy in the future one day, but currently IMHO only one osm exists, so maybe its not that bad for an app to be bound to it, but its always good to know if an app is bound or free to choice, same i would like to know if its maybe multi-account (which fluffy-chat is), but single-account-apps are so very common and thus this is not seen as an anti-feature which is completely ok for me.
but also in this case here the app is not only bound to osm, but to two other non-changeable services too, thus the warning is due even if label-app-bound-to-label-service would NOT be considered an anti-feature.
@smb @openstreetmap
If I view source I get "phrase not found" on a search for "Jawg" . It also doesn't show up in Firefox's Inspector, which I _think_ includes dynamically loaded stuff.
Just checked Chrome and Microsoft Edge and they don't show it either. What are you using to actually get the detail?
I wouldn't mind F-Droid's warning if they gave me the details, but for some reason they don't seems to be accessible to me.
1/2
@smb @openstreetmap
I don't know how you'd get round the dev using his own site to pre-process (already published) data or host a list of "banned versions" with bugs that could corrupt data. You can't really choose to have a different developer on the fly.
Maybe you could let people chose a different host for a published photo, but I think if there were privacy respecting ones that easily allowed that the dev probably would have use those instead?
https://streetcomplete.app/privacy
2/2
i am using the F-Droid "app" (currently 1.20.0), not a browser now. But i asumed css or such could be a cause as sometimes nonvisible content is behind some bad (ad?) layer. i thought i had seen such infos also on their website, but that is then too long ago and i might just be wrong with that.
maybe you can only get that info from the app which would feel a bit like an anti feature *haha
@smb @openstreetmap
Apparently they're using a more detailed index for the app that isn't supported in the web.
(And yeah, I did call that an F-Droid Anti-Feature when I found out that you have to have to install something for this to be displayed in an intuitive way.)
https://github.com/streetcomplete/StreetComplete/discussions/5756#discussioncomment-10108447
good to know.
well, for me already using the fdroid app obviously that issue still beeing open is not a big concern.
however they could build the app with little extra code so that it would output that information for every app and push it to their website in a readable format, but pls don't comment on why exactly thats a bad idea *hehe