urineaut
It's a FOSS public transport routing engine. In the options you can select what type and how much time you want to spend on the first and last "mile" (even something like bike/scooter sharing).
It uses open data or data connectors for the routing. And being FOSS, if there is no data connector yet for you region, it may be interesting to contribute one if there is a sane way to query the data from the local transport compan(y|ies).
This is super useful because (at least on Linux) IPv6 sockets per default are dual-stack and bind to both IPv6 and IPv6 (except if you are using the IPV6_V6ONLY sockopt or a sysctl), so you don't need to open and handle IPv4 and IPv6 sockets separately (well, maybe some extra code for logging/checking properly with the actual IPv4 address).
That is also documented in ipv6(7):
IPv4 connections can be handled with the v6 API by using
v4-mapped-on-v6 address type; thus a program needs to support only
this API type to support both protocols. This is handled
transparently by the address handling functions in the C library.
IPv4 and IPv6 share the local port space. When you get an IPv4
connection or packet to an IPv6 socket, its source address will be
mapped to v6.
about:config works on the mobile variants, too. Granted, it is not the best UX, but it works for now.
It still seems strange to me that browsers overrule the OS' and thus the user's global preferences.
Double Shift is also extremely helpful to navigate to a file if the project has a lot of nested subdirectories.
There are some water-resistant phones with a headphone jack and an IP68 rating even. The LG V30 for example is a beast. Semi-regular usage on rainy days works without any issues. Even using it as a flashlight it survived 30min of pouring rain. I had to wait for the USB-C port to dry up to charge it after getting home, but it still survived without any damage whatsoever.
Other phones that are both water-resistant and have a jack [1]:
* Pixel 3a
* Galaxy S10
* Huawei P30
* and a lot more
If I remember correctly, Apple tried to justify its removal due to its size and water-resistance. I wonder when (not if) Apple will remove the power plug due to "water-resistance" and insist on using Qi charging (even though it has worse efficiency[2]) and cloud services instead of transferring data via cable.
[1]: https://www.androidauthority.com/phones-with-headphone-jack-...
[2]: https://www.wirelesspowerconsortium.com/data/downloadables/1...
A little bit context about the Austrian mobile market: Until 2012 we had four different carriers: Orange, T-Mobile, A1 and Drei (Hutchinson). December 2012 the EU commision approved the merger of Orange into Drei under a few conditions so that competition will not be hindered. One of those conditions required Drei to open its network for up to 16 MVNOs [1]. If I remember correctly, prices soared slightly, but after some MVNOs were successfully established, the other carriers opened up their networks too and the additional competition led to plummeting prices. It seems like it's not even that expensive to set up a MVNO. The request for dialling codes is free at the telecom regulatory body [2] and Drei's reference offer seems reasonable, even without negotiating better conditions[3]
[1]: https://ec.europa.eu/commission/presscorner/detail/en/IP_12_... [2]: https://www.rtr.at/de/tk/Rufnummern [3]: https://www.drei.at/de/business/wholesale/mvno-and-reselling...