Well, I got to dream for a bit…
Disclaimer: I don’t represent KDE in any interaction with this account. I am just freeloading off of the kde.social server.
Well, I got to dream for a bit…
Or it could just be laziness.
In case you don’t want to put the effort into making a system into your organisation, to update code in a public-facing versioning system hosted setup, just tell someone to zip whatever you compiled and package it along with the rest of the stuff.
simply zip up their code and send it to the AGPL’ed software owner
That seems good enough to me. No?
Sure, it would be nice to have the whole versioning system history, but even having the current version of the code makes it possible to do a code review. And modification too.
Self-Building and deployment might turn out to be harder, but that would just be about which side is having to put the effort of making something comprehensive.
So the OSS projects that have been closed due to Cease and Desist notices are actually still viewable !?
Well, guess who’s not buying next gen Ryzen?
They are doing similar stuff with deliberately delaying Linux driver capabilities for Radeon 7xxx series, to make more GPUs die out faster, by overheating (zero RPM fan until 60°+).
Now we just need a friendly neighbourhood nanoscale fab.
In short, if you’re pwned once, you are pwn3d f0r3v#rrrrreeeheehaahaahaa*cough**cough*
These are the kinds of exploits you use to create APT (Advanced Persistent Threats).
Because they look like large outlets of coloured air.
Coloured air coming out of an something is the default way of depicting air pollution.
Even if it is just water vapour, it has a big enough shock factor.
Alternatively, you can just use the `` enclosure, used for single line code.
That is a “grave accent” or a “backtick”, the key you will find on the left of the ‘1’ key and under the ‘Esc’ key on a standard (ISO, maybe) 104/105 key qwerty keyboard.
¯\_(ツ)_/¯
Talking about bootstrap here?
You’re right, but at the same time.
Let’s say a website has an issue and was one time faulty. Clients lost money. Then the site owner is notified of the fault by multiple clients. The site owner uses some words to placate them and goes on with their day.
The site owner then makes some changes to the site, meaning they did have the time and money to pay a developer to update the site, but decides to keep the previous bug in, as a feature, implemented in a different way, this time better at stealing their money.
Sure, the obvious solution is to use another site (the laundromat down the road).
I am a desktop person.
My main reasons for using a smartphone instead of a phone, are:
Until these requirements are met, I will associate Linux mobile with words like, “next” and “tomorrow”.
Welcome to Linux for Mobile.
The next generation OS for keeping your smartphone private and your conversations (kinda) secure.
It’s “next generation”, because we probably won’t have a good enough solution in the lifetime of the current generation’s people.
But if you have both: enough money to buy an extra fairphone for testing and the time and ability to program drivers, please consider it.
Yeah, it doesn’t really make any sense for them to have it anywhere other than the backend.
Guess this particular exec is not getting this month’s bonus.
Sounds like something an apple exec might say… For their products.
commands to install dependencies n shit
That only happens if you are fixated on installing the software without connecting to the internet.
Otherwise, the package manager does it for you (that’s what its job is)
something extremely niche
Desktop Linux is already pretty niche.
Maybe this is the first time their bot score was low enough to get through with just a tick.