I’ve never seen any reason to believe Google has any say in the direction of Firefox. Google pays to be the default search engine, not more, not less.
This same argument could be brought up about Safari. All other browsers are based on Chromium anyway, so they are directly developed by Google themselves.
Transcoding and transcoded downloads does not seem to be merged yet, altough there’s a working PR.
Almost all oft their breaking changes over the last few months were about their docker-compose setup and the simplification of the same. They’ve startend out with multiple purpose-specific (micro) containers, which turned out as a Bad design decision. These changes require manual intervention but seem to be mostly finished, so I don’t expect these to be many breaking changes in the forsseeable future.
The better you plan ahead, the fewer breaking changes you have to impose on your users.
I agree. From what I’ve read, they now have (published) plans for what’s ahead.
Yeah that’s right. Having to post sources rules out usage of LLMs for the most part, since most of them do a terrible job at providing them - even if the information is correct for once.
I noticed those language models don’t work well for articles with dense information and complex sentence structure. Sometimes they forget the most important point.
They are useful as a TLDR but shouldn’t be taken as fact, at least not yet and for the foreseeable future.
A bit off topic, but I’ve read a comment in another community where someone asked chatgpt something and confidently posted the answer. Problem: the answer is wrong. That’s why it’s so important to mark AI LLM generated texts (which the TLDR bots do).
Yes, they’re using several abbreviations, without explaining them properly, which isn’t ideal. It’s likely to keep the article short, which comes at the expense of people unfamiliar with the topic)l/organizations.
Another news site I regularly visit has a small information button besides abbreviations with a popup to explain a term, which also links to Wikipedia. This makes understanding articles about unfamiliar topics way easier.
Is it because oft the author using multiple clauses and multiple layers of context in the first two paragraphs?
If yes, then I understand why. I find myself making the same mistake quite often because my first language is German, which often uses clauses (at least it’s more common than in english).
desec.io can be used with any domain registrar and has an API with support for various ddns clients (ddclient, lego).
deSEC is a free DNS hosting service, designed with security in mind.
Running on open-source software and supported by SSE, deSEC is free for everyone to use.
Edit: To clarify, desec.io does not sell/rent domains. Desec has to be set as the authoritative nameserver on the registrar, then desec can manage domain records instead of the registrar (which usually also provides their own domain hosting for “free” by default).
YouTube changed something about their API to break 3rd party apps again. youtube-dl is also broken, but they’ve found the issue already, so it’ll likely be fixed after a while.
GrayJay and YouTube ReVanced still work in meantime.
It might depend on the particular bridges, but all mautrix- bridges work great for me with conduit. In a way adding bridges to conduit is easier since it’s all done through the admin room on conduit.
This post was posted two times, so you might want to delete one of them.
Bookmarks and GPX export is a great addition. OrganicMaps continues to improve and I find myself using OsmAnd less and less (unless I need specific features).
Great to see Unified Push on the list. As well as improved Wayland input method support, whatever that exactly means.
Immich recently changed license from MIT to AGPL. As far as I understand they can’t sinply relicense to a non-free license unless they redo a good chunk of code from the last half a year.
If they still used the MIT license I’d be worried too.
I personally would be hesitant to host Immich publicly until they’ve done a security audit. The risk of accidentally exposing my photos publicly is too big for me.
That’s why I recommend using Tailscale or Wireguard directly. Personally I’m using Wireguard for me and Tailscale for other people I want to easily access my services.
I don’t see how the ability of users to actually know which repository an app comes from and change the repository makes it more likely for devs to not remove anti-features.
I’ve had this exact issue a month ago where an app was available in official F-Droid repos and Izzy’s and I didn’t know which repo F-Droid selected by default.
If they chose an open source license, a fork under a different name would be possible (else it’s not open source).
Their wording is ambiguous, so maybe they only talk about keeping the name/trademark to themselves, which is definitely a good choice.
It’s also not clear if they accept contributions, but they’ll likely keep deciding what features should get added or not.
At least that’s how I understand it.
It still works for private instances. The moment a public instance makes enough requests to reddit, they block it.
I’m running libreddit on my home server and access it through wireguard. Never been rate-limited. It’s the only thing I still use Libredirect, since most platforms ban third-larry frontends.
I understand what you mean. With Redis and many other database/cloud companies switching to source-available licenses, maybe the term source-available doesn’t have to have such negative connotations. Open-source is also divided in permissive and copyleft licenses (e.g. BSD and GPL), both have big implications on how it can be used.
Redis and others see themselves forced to switch to a more restrictive license because of the big cloud providers, who sell services for others software, without contributing back. This change is not good, but it might be necessary. Just like GPL is more restrictive than MIT, but it’s necessary to force some company to actually give back instead of only taking.
I personally don’t really dislike licenses which allow for the necessary freedoms of open-source after one or two years. It’s a compromise but secures the longevity of software beyond a companies success. It’s way better than proprietary code.
Yeah, I’m not sure whether Bitwarden always had support for exporting the vault on mobile, but it’s an awesome feature.