10,008 karma · joined September 23, 2014
There hasn't been sufficient reporting on all the lobbying and back-room dealing.
Often times to bank successfully you need large stagnant balances that are semi-frozen, or meaningful collateral.
This becomes problematic through payment provider platforms which other platforms build upon: it's not straightforward to manage these relationships through so many layers of abstractions. It's easier just to ban the industry.
I don't know the specifics of Kickstarter, but I've seen this happen countless times, so it's not difficult to connect the dots.
I guess I don't really care. As soon as it becomes unworkable to view these publications through archivers I'll just stop viewing them altogether. I don't see this helping their bottom line though.
When optimizing code it's not unusual to look at the assembly. It's not unusual to look for opportunities for autovectorization or to verify inlining or loop unrolling.
Compilers are, for the most part, deterministic. This means after people have reviewed the output, it's unlikely to change. It also means if they do change, only a few people are required to notice.
None of this applies to LLMs. They are worse than compilers, in regards to the quality and characteristics of their output, in every possible way.
If no one reviewed compiler output then https://godbolt.org/ wouldn't exist.
If everyone on your team gets Mise and you're starting to feel pain at the periphery then it can definitely make sense to adopt a more elaborate toolchain orchestrator.
At a recent gig we experienced many, many GitHub outages that were not tracked on their status page, and we kept a log (i.e. just search in slack). After our business people argued with our account executives at GitHub we got hundreds of dollars of credits.
Then the business peopled complained because hundreds of dollars of credits is not worth their time. And so GitHub continues to have terrible uptime and nothing is done about it.
A nappy service is very likely to do a much better job than you'd do at home.
Sometimes it makes sense to roll your own and the cost of a dependency isn't worth it. This can be especially true when you need to accommodate many bespoke environments and you end up needing to make little accomodations here and there. Can create a very unpleasant situation when you don't own the code.
I'm not a cryptographer but I've spent a significant portion of my career focusing on the security-side of things and I've rolled my own auth quite a few times on very public projects you can access today and I've never had any significant findings through repeated pentests.
But that's just the thing: I did it the right way, and there is a right way to roll your own stuff, to forge it in a way it comes out suitable. Is it bug free? Probably not, but I feel significantly better about it having thoroughly tested it by myself, my colleagues and paid professional penetration testers.
I couldn't easily find an answer but I'd like to know if this implementation has been validated by a professional or not.
Juggling multiple directories and tarballs is a pastime from a bygone era. It's even more commands if you want to reuse the existing directory!
If zero data-retention was non-negotiable for the customer, it's totally possible that the negotiations ended there.
I'm not sure what you're trying to accomplish or unearth beyond what's already been said, which certainly suffices for me.
If anything it's the opposite: pit bosses actively police croupiers who are spinning too consistently, and croupiers are encouraged to vary their spin throughout their session to avoid bias.
There's no deep strategy in Roulette, really. I play for fun, and the money I put on the table is already spent.
The anecdote was: I wouldn't have seriously believed that you could reliably manipulate the spin outcome, and as an observer, that's true. I didn't believe the dealer could either, but after seeing this dealer pull it off I definitely see the potential for manipulation. It was almost like she was showing off that she could. And besides, she earned a hefty tip.
I think we would've kept going but she rotated off and I cashed out.
Edit: Thorp and Shannon! What a duo. Great articles, thanks for sharing.
You can use a boatload of providers for automated DNS-01.
The most concerning thing here is that you absolutely should not use GitHub fucking Actions as your control plane. Have you ever debugged actions? It's terrible. Old runs magically disappear. The queue sometimes decides to go for a lunch break. Not to mention GitHub's uptime is atrocious.
I'm sorry (not sorry) but I can't take this seriously at all.
https://store.steampowered.com/bundle/70574/Transport_Tycoon...
But the OpenTTD item listed in the bundle is non-existent at the moment.
Finally, the ability to allow you to unlock your phone bootloader or to run custom firmware has nothing to do with the silicon. It's a software choice. The trusted software could most certainly decide to disable these safeguards.