Well they publish attestations from third-parties, but no full audits, so sure they could be much more transparent.
But the claim about USDT ever claiming that its supply wouldn't increase is pure fantasy. It literally makes no sense if you understand how the peg is maintained (technically by minting and burning tokens).
No, the fact checkers exist to pick their sponsors' preferred sides when there are multiple sources. They have little or no actual expertise of their own but the mere terminology leads the uninitiated observer to directly believe that the "fact-checked" view is objectively true. Everyone else is forced to do the constant rhetorical work of re-explaining why fact-checkers are not what they purport to be.
>A number of journalists have gotten caught inventing stories, plagiarizing stories, and other rather basic issues.
Ultimately, fact-checkers are just journalists who attempt to claim a monopoly on truth. Censorship does not work, and can only be tolerated in a free society in VERY limited circumstances, usually after due process. The censorship we've seen during covid and since "fact-checkers" entered public dialog in general is absolutely not acceptable in any way. I don't have a problem with the existence of so-called fact-checkers per se. The real problem is that it's false advertising and a blatant attempt to rally for censorship of wrongthink. If you want censorship, move to North Korea or China, and leave the rest of us alone.
I love these kinds of sites, since they're indistinguishable from honeypots. Sure, have my license plate and the information that I'm worried about being watched.
I think the VST author knew that fine, but they figured that:
1) Protecting the installer will take care of most casual piracy
2) Protecting the VST might lead to unpredictable performance and issues on something that needs to run in real-time
So they chose to only protect the installer, which seems like a very user-friendly choice. I both enjoyed the writeup and want to second supporting the developer by buying a license.
What's bizarre about it? There's lots of legislation that requires companies to report on various data or to provide access to auditors. It's legally valid.
I think there's a compelling case to be made for requiring large social media platforms to provide data access to researchers, considering the platform's incredibly ability to influence elections and society at-large.
This is definitely just me, but the diagram with "motivation to buy" was amusing to me. I (try to) refuse to be manipulated by these tactics - if I think the software is worth buying, I will purchase and use it, otherwise I will look elsewhere! Nothing sets my "motivation to buy" to zero quicker than aggressive, "uncrackable" DRM. In fact, it usually skyrockets my "motivation to reverse", whether or not I actually need the thing (though usually this is overruled by having better things to do with my time).
What’s the point of this distinction, what does it mean that it’s not chemically addictive? It causes withdrawals, dependence, it definitely acts on brain chemistry.
I didn't read it as them having any attitude. They targeted an obviously low-effort VST plugin and found exactly the implementation failure they suspected.
If the Bass Bully developer didn't want the spotlight, maybe they should have programmed their $200 (!!!) program better.
The blue check symbolised (symbolises) being verified, i.e. this account belongs to who it says it does. But it doesn't carry out any/sufficient checks to actually verify that.
You could easily argue that the IBM of old did die and that what is now IBM is something completely new. But, if you’re a company that is going to be as big and last as long as IBM or Nokia (as another example), you need to have a few good pivots to stick around.
We might be seeing Intel’s pivot taking place in real time. Hopefully it works…
Your best bet is to plan a year or so ahead and get sponsorship in the queue so the spouse can enter with a green card. Timelines are about 8-14 months.
But as PRoberts said, a non-citizen spouse can't enter on a tourist visa with the intention to change status. A spouse can visit, but then change their mind while in the US.
But CBP is well aware of people trying to shortcut the process this way, so it can be very challenging convincing CBP your non-citizen spouse intends to leave. But it can be done showing a job, property or other elements that would require someone to go back.
The line imo is the amount of DRAM OpenAI actually needs/can use. If they end up piling some of it in a warehouse just so nobody else can use it, lock em up.
For enjoyers of classic simpsons, I highly recommend /r/simpsonsshitposting, a delightful blend classic simpsons, absurdist/surrealist/dadaist art, multilayered inside jokes and often NSFW content. It could not exist without The Frinkiac.
I think the "if something bad happens throw an exception" thing does have some value, namely that you can make it very explicit in the code that this is a use case that you can't handle, and not that you merely forgot something or wrote a bug.
static function unreachable() {
throw new Exception('Unreachable');
}
Now, we don't actually need the default match arm. If we just leave it off entirely, and someone passes in something we can't match, it'll throw a PHP error about unmatched cases.
But what I've found is that if I do that, then other programmers go in later and just add in the case to the match statement so it runs. Which, of course, breaks other stuff down stream, because it's not a valid value we can actually use. Or worse: they add a default match arm that doesn't work! Just so the PHP interpreter doesn't complain.
But with this, now the reader knows "the person who wrote this considered what happens when something bad is passed in, and decided we cant handle it. There's probably a good reason for that". So they don't touch it.
Now, PHP has unique challenges because it's so dynamic. If someone passes in the wrong thing we might end up coercing null to zero and messing up calculations, or we might end up truncating a float or something. Ideally we prevent this with enums, but enums are a pain in the ass to write because of autoloading semantics (I don't want to write a whole new file for just a few cases)
