I agree partially. For indie devs: get the game directly from the dev if possible, never get the codes, because the dev doesn’t really get money for those.
With AAA games, the picture is different. The business model for most has now pivoted to be about extracting money to the point where its absurd. And for them, I have absolutely no qualms with taking advantage of their bad business decisions.
As someone who quite enjoys lengthy video essays about obscure topics, I disagree.
I am split here. I dont expect anyone to know the manages by heart, but at least doing a quick search should be possible. If that obviously wasn’t done I’m fine with referring people to the friendly manual.
RTFM nice(1)
I really don’t see a reason to write more just to summarise what has already been written. Is that toxic though? I don’t think so. If someone then says that they don’t understand what that reference means, I’ll gladly explain how manpages work and how to search for info. Teach a man to fish and stuff.
Since a definition is descriptive, not prescriptive, I think it’s paramount.
I suppose it depends on how exactly you define a blockchain. If you add distributed consensus algorithms and a requirement for BFT resistance, then it clearly isnt. Its the usual issue with definition…
I would beg to differ. It seems to be pretty useful for Software development. After all git repos are Blockchains. That being said: use a solution that fits your problem, don’t try to adapt a problen to your solution. Thats something a lot of the crypto- or AI-bros are apparently misunderstanding
You might want to take a look at cage which has been designed for that.
That still requires some level of graphical session though
Not sure reality agrees here. Unless the project is huge, it will most likely not see any money. With copy-left code they are at least required to share their improvements and contribute that way. (I am aware of the no-gpl policies of many companies)
What’s probably a better Model are Nextcloud’s “SupportaaS”, Sourcehut’s consultancy, or mailcow’s SaaS. (I also see SaaS critically, but if it’s Libre I’m okay with it)
Dear Debian users: please also update your Debian version, not just your packages. Like… once a decade would be an improvement for many poor servers.
Only acoustic guitar covers of Wonderwall
It’s not android, but Google as far as I am aware. At least my battery settings (latest graphene OS) are… limited to say the least
I found adding an always-on device to my syncthing mesh to be an awesome experience. This way even if my battery dies, it can still pull the latest version after I shut down my PC.
I want it to last. At least 5 years.
That is something that would be very hard to legislate. Especially since battery lifetime is dependent on a variety of external factors (charging-style, temperature of the device, luck). Build quality certainly also factors in, but even the best battery won’t survive a 10 year old regularly overheating their phones with games and charges it for the entire night. I would love to see OEMs implement nice things like “capacity settings”, where you can set your device to stop charging at 80% and show it as 100%.
To exorcise parasites from the earth, ram a cross into the ground and
magicgodly waves will drive then out