rauba_code

Sony Xperia 5 II

Turned off Google Play Services and Google Play Store since the purchase of a new smartphone & set up F-Droid. Everything just works with much less storage space used (for some reason most proprietary apps from Play store usually come together with ~200 MB of bloatware). I tried to flash a custom ROM, as Sony provides instructions for that, but the build is failing, and I don't want to sacrifice the proprietary Sony image-enhancing algorithms. So I'm just sticking with the Google Android but no Play Services option.

IMO, what is good for open-source web solutions, is that, if someone doesn't like the vanilla frontend, one can write a new community-based frontend as a web, desktop or mobile solution, like Whalebird. It greatly expands user's choice and it is a good selling point but goes unnoticed.

Regarding new features, it is a matter of the communitations' protocols (ActivityPub, etc.) New features should comply with the specification and not introduce platform-specific 'spin-offs' as they would threaten the maintainability of the protocol and interoperability between platforms and in the long way ruin the whole fediverse. However, I have not read the specification of ActivityPub and what it can do. Maybe I have to try it first because it looks very promising.

Interesting. DDG has been my primary preference since I boycott Google (search, Gmail, Play & Play Services) in 2020. I know SearX, I use it sometimes for research, but I want to get sure how metasearch works. I struggle to find information whether it 'crawls' and caches all the information from search engines, such as Google, Bing, DDG, Qwant, etc., on its server, or does it just pass your search query to these search engines and sums it up, like StartPage. But if DDG is just another nonfree metasearch, as you say, then it does not matter.

There is const char* that should be added to list.

As far as I remember, Win32 API (C-compatible C++) used to add more complexity: wchar_t*, LPSTR, LPCSTR, LPWSTR, LPCWSTR, LPTSTR, LPCTSTR as they preferred 16-bit strings over UTF-8. These were supposed to be independent safe ANSI/Unicode string wrappers. Sick.