You need to use chown if you want to own the libs
You need to use chown if you want to own the libs
But you actually don’t know what monero is being used for when it’s used in transactions, no one does. You just have a bias that if people want to keep their transactions secret, it must be illegal.
You could make the same argument for cash.
This is called the “Door in the face method” of bargaining. Start with a request so high and absurd that you “slam the door in their face” because it’s so absurd.
The next time they try, they’ll come back with an offer that sounds far more reasonable than the original request. Since you’re still primed with the previous context, your brain makes it sound less bad than it probably is ("At least it’s not the first offer!). You’re more likely to accept after this.
The opposite technique is called “foot in the door”, start with a small request (get your foot in the door) and then increase the ask after the small request goes over.
This will probably use some well-defined api endpoint to do their telemetry check-in, so this could probably be effectively circumvented if users were willing and able to do host level overrides to specifically prevent the unity engine from phoning home
You need a budget, but it’s not free.
But with Intuit, you are the product, so it’s only free in the sense that they get your info and you get mint in return.
Not a single shot of the front of the phone 🤔
I don’t really use it for this, but here are some things I do use it for:
I mostly just use it for metrics scraping though
Air Canada: we’re not happy until you’re not happy
Some of these “businesses” are in fact chia farming and whatnot, though. I know the marketing language is always what gets people ruffled up in datahoarder, but this isn’t exactly something I would consider as a legitimate business use and a single plot uses 100GB of space which can’t even begin to be deduplicated. If your entire business resolves around making money as a result of storing unreasonably large amounts of data then the cloud ain’t it and realistic data costs need to be factored into your data models. I’m actually a bit surprised that Dropbox responded so quickly to the influx of gdrive abusers.
For the average user, it would be substantially more cost effective and sustainable for you to invest in hard drives rather than paying Dropbox $100/mo to rent storage. Cloud providers will decide at any time to change the term of your agreement. The hard drive is yours until it dies.
DVDs are 480p, 720p wasn’t introduced until the Blu-ray/HD DVD wars
I’ve managed to get in the habit of pointing the screen away from my eye sockets in bed when it’s dark. 60% of the time, it works every time
It was only that price if you managed to buy it immediately after going live. The pricing was adjusted a short while later.
Sync has been a one man show for over a decade. Just how fast did you have in mind?
You could do a data request, that should be everything they have on you
it doesn’t cost money and you can use it for anything you like.
This is misrepresenting FOSS quite a bit. A lot of open source software is indeed this permissive, but not all of it. It’s important to refer to the license of each individual project because various licenses have different terms.
Some open source software may be free for personal use, but that license may not extend to other companies seeking to profit off their open source and good will. ZeroTier comes to mind as an example of this.
Further, other licenses like GPL only requires that you make your sources available upon request but you can require that your customers pay you to receive the product: i.e. RHEL. At the end of the day, FOSS means free as in speech, not free as in beer
Because he prioritized his time in getting the application usable rather than implementing various tiers of payments instead.
One of the messages to the discord this morning seems to indicate he’s planning on adding the one time ad-free unlock today.
Because this strategy worked so well for determining individuals’ assigned sex at birth. What could possibly go wrong?
Updated amd64-microcode for EPYC processors appears available for several distributions which has mitigations available. I went ahead and proactively grabbed the microcode update from Debian unstable (not the best practice) and applied it without issue to my Bullseye/EPYC.
This isn’t exactly condoned as it’s not officially a backport, but I’ll take my chances as this is pretty critical.
Date of the updated microcode should be July 19th.
I happily use Fedora for workstation purposes but hate to admit I use it, so it’s an accurate critique. It’s a great operating system though, naming aside.