No problem; thanks for trying to help!
vas
Do you know if it works with Signal? (Doesn't seem to be.. Dunno why. Static build of the app? Non-http-based transport technology used by Signal?)
UPDATE: BTW, I've found some experimental support in CoMaps - supposedly, haven't tried it https://codeberg.org/comaps/comaps/src/branch/main/docs/EXPERIMENTAL_PUBLIC_TRANSPORT_SUPPORT.md May be broken easily due to the experimental status of course..
UPDATE2: Tried Moovit, it still works without google services, whoray! .. And still asks money or fills me up with ads to the brim, also as before...
UPDATE3: and it doesn't allow putting GPS coordinates in the search field, unfortunately. This adds some churn if you're switching between CoMaps and back..
UPDATE4: actually in Melbourne, Moovit didn't find anything. Google Maps does. Not sure why this happens. Google Maps in a browser tab is also an option if things get dire..
Oh wow, that's a lot of useful information, huge thank you! Since as you're indicating it's the GTFS data underneath, I'll try Moovit, which last time I checked worked even on my de-googlified phone (GrapheneOS without google services). Thanks again! 💚
Based on the comments so far, maybe something like this makes sense:
Warning: Private messages in Lemmy are not End-to-End encrypted, so the respective instance owners are technically able to read them. Please use a platform with E2E encryption for private messaging. Lemmy recommends Element.io and XMPP.
I agree. That's why I propose to clarify the wording.
Yes. And I think saying "messages in Lemmy are not End-to-End encrypted" is clearer communication than "messages in Lemmy are not secure".
Congratulations to the team and to everyone who supports the project!
Thanks for the response! I think I'd personally try something like that, but I have no idea whether it'll stick.
Overall, the idea of a significantly simpler (than HTML) protocol sounds intriguing, especially to break the google chrome near-monopoly.
Thanks for the response!
It's not only the efficiency boost. What about safe concurrency? Or about the tooling - does sbt really compare favorably to cargo? (I'd say "no", having used both over multiple years)