Is it equal to a regular android? Will the usual banking apps work on it, for example?
Kaldo
I can still see the value in owning it in this shitty climate however - maybe I want to keep the patent just so I can distribute it freely instead of someone else staking their claim on it and then charging people for the same thing?
Someone else is imprinting their definition
I mean yeah, that's how words work? AA has the meaning because a bunch of people imprinted their meaning on it.
Open source has a meaning because a bunch of people imprinted their meaning on it too, it has no relevance to actual words "open" or "source". The issue is that other people are now imprinting their own meaning on it and muddling it instead of following the existing meaning or coming up with their own terminology.
I think the only thing we're missing is the official OSI definition for open-source-for-reading-but-not-modifying so we don't use the same name as for the open-source-for-reading-and-modifying code? The issue seems that we don't have OSI-defined names for both, just for one, so people started misusing it unknowingly while the businesses misused it maliciously.
Am I understanding correctly and this is truly FOSS and fully offline, there's no remote server or model we have to connect to? What was the model trained on? I'm really curious but I also don't want to support proprietary unethical data sourcing.
Muddying the waters is the oldest trick in the books, big corporations have even started doing it with "indie" games - Dave the Diver is stylized and marketed as an indie game despite being developed by a division of a multi-billion company Nexon.
I definitely have an issue with it as well, it's really hard to say whether something is actually FOSS nowadays or not, and whether it can be taken away or acquired by someone else down the line. That could be my fault as well since I never bothered to learn about the licenses beyond what MIT / Apache2 are, and even those I understand superficially.
There should absolutely be more pushback for things like these though.
It has picked up again, ernest is posting regular updates
This is obsolete info, it has been changed since.
And that Kira hut episode
I'm not sure what Ansible does that a simple Docker Compose doesn't yet but I will look into it more!
My real backup test run will be soon I think - for now I'm moving from windows to docker, but eventually I want to get an older laptop, put linux on it and just move everything to the docker on it instead and pretend it's a server. The less "critical" stuff I have on my main PC, the less I'm going to cry when I inevitably have to reinstall the OS or replace the drives.
Ahh, so the best docker practice is to always just use outside data volumes and backup those separately, seems kinda obvious in retrospect. What about mounting them directly to the NAS (or even running docker from NAS?), for local networks the performance is probably good enough? That way I wouldn't have to schedule regular syncs and transfers between "local" device storage and NAS? Dunno if it would have a negative effect on drive longevity compared to just running a daily backup.
These bridges are usually self-hosted so I'm assuming this is not due to infrastructure costs but rather the bridge code maintenance issues? Do they require so much work to stay functional, are other bridges at risk of abandonment too?