If you read the verdict it says: maximum privacy combined with optimal obfuscation techniques. This implies that the sole role of the software is money laundering. The striving for privacy itself is not in question.
Sounds to me like you need an upgrade. I tried Jerboa, but it felt like it always lagged behind or was buggy for some reason. Then I switched to Voyager, which gets constant updates. Also, it’s a PWA, so I don’t need an app and it can thus be used on mobile, tablet, desktop, etc. Not to mention the theming is one of the best, in my opinion.
Jerboa parses url correctly. Look at RFC1738. hpath is made of hsegments, which are made from arbitrary amount of uchars and other symbols, uchars include unreserved, which includes safe, which includes dot.
So correct way to end sentence with url would be either by escaping url with some characters like [https://datatracker.ietf.org/doc/html/rfc1738], or using markdown urls like [display text](url).
If you read the verdict it says: maximum privacy combined with optimal obfuscation techniques. This implies that the sole role of the software is money laundering. The striving for privacy itself is not in question.
Free software can be used for what every you want to use it for.
That is the first software freedom
https://en.wikipedia.org/wiki/The_Free_Software_Definition
That dot became part of url
The ending period? Not for me on Voyager.
For me on Jerboa(official lemmy app)
Sounds to me like you need an upgrade. I tried Jerboa, but it felt like it always lagged behind or was buggy for some reason. Then I switched to Voyager, which gets constant updates. Also, it’s a PWA, so I don’t need an app and it can thus be used on mobile, tablet, desktop, etc. Not to mention the theming is one of the best, in my opinion.
Jerboa parses url correctly. Look at RFC1738.
hpathis made ofhsegments, which are made from arbitrary amount ofuchars and other symbols,uchars includeunreserved, which includessafe, which includes dot.So correct way to end sentence with url would be either by escaping url with some characters like [https://datatracker.ietf.org/doc/html/rfc1738], or using markdown urls like
[display text](url).Thanks, fixed. I usually notice to be careful around URLs because the parsing varies
I do not disturb that in any way, just clarified the verdict from Dutch