I think it's a column. There was a thing a while ago where the counts were out of sync and they took the site down for maintenance to recount everyone's points. Any karma affecting action just adds to the points atomically.

AWS is free below a certain resource level isn't it? Should be enough for a simple site.

@jak645 was actually doing ML when it crashed. I did briefly mine a bit with it, though I don't really support crypto for environmental reasons, but surprisingly it was stable. Tensorflow just kicked its ass though.

@AtuM it had actually crashed and is displaying garbage values. I had made a custom BIOS for it that raises the power limit but it can't handle it for long. Was actually fine after flashing the stock BIOS. This was one of the few cases where garbage values were mildy believable though(its on liquid cooling so 0RPM is actually right)

Ok the GPU is now bending light around itself and emitting EM pulses corresponding to the next Ethereum block hash. Idk I think I should turn it off

I think he might have been expecting you to return one of the movable STL containers which would be the C++ way to do it honestly, but he could have at least bothered to think through the code you gave him. He seems like he's just looking for ways to trip people up and gets excited when he thinks he sees a mistake.

Its in the normal app manager but in the container. On the base ROM Play services is of course not possible to disable but inside the container it just... is. Probably for high security customers who actually use Knox for important stuffs. I mean Google can still probably track the base ROM as much as they want so not much gained but its kinda cool to have a Google free zone at least.

@Jilano Well source is that I have one and I could :)

AFAIK the typical is that player vehicles are always client side simulated but the server does sanity checks on the changes in player coordinates or even runs the simulation on both sides and compares results. I imagine the game can become very inaccessible to most if its entirely server side.

How about this one for size:
LFDS711_MISC_MAKE_VALID_ON_CURRENT_LOGICAL_CORE_INITS_COMPLETED_BEFORE_NOW_ON_ANY_OTHER_LOGICAL_CORE

Its a macro in liblfds (lockfree data structures lib)

*desperately tries to delete high performance AI library that I've been working on for the last 6 months from Github*
If I ever pluck up the courage to actually make that repo public I am so going to link this rant lol.

@RememberMe Fair call on auto-vectorization being kinda crappy. Just figured I'd get a mention in for SIMD instructions because in my experience re-implementing the library is literally what some people wanting to learn this stuff want to do. High performance programming is indeed a rabbit hole but its a good rabbit hole to know your way around when youre interested in the deeper mechanics of AI, even if you're just going to let a library handle it. Even those libraries can make mistakes sometimes. Some people aren't interested. Thats fine, they can use Python.

Python if you just want to plug things together (not a bad thing), otherwise any language that compiles to machine code with a good compiler backend like GCC or LLVM(like C or Rust) because it can usually auto vectorize to AVX/NEON instructions which you will use a lot in AI.

One of the reasons I had found for actually naming structs is that you can't forward declare an anonymous struct(which is kind of obvious now I think about it) if for example you want to hide implementation details, even if you typedef it. Most of the time I just name things like
typedef struct name_s {} name_t;
Honestly there's not much reason not to name a struct.

Do you maybe have the "Private DNS" option on? AFAIK it overrides what it got from DHCP. Useful for public wifi, not so much at home.

Hacker meanwhile:
$ hack "http://site.com" --with-list male.txt && hack "http://site.com" --with-list female.txt

Evil gnome is a linux virus. He's referring to "Gnome"(DE) and evil gnome as 2 separate things, just making a play in the names.
(Edit: Darn algo bringing up old rants!)

rEFInd's site also has instructions for reinstalling the windows bootloader, because apparently that happens often
http://rodsbooks.com/refind/...
(Probably too late but I thought I'd mention)

*could* be memory corruption. I saw the linaro toolchains legit segfault a couple times though so I don't know anymore lol. Usually you can trust the compiler.

@tahnik

@irene Maybe I'm just salty after having pulled one too many CPUs out their sockets by the cooler lol. Straightening CPU pins isnt fun. Also does anybody know what the word "gently" means? I see it everywhere...

Also I hate AMDs thermal paste they put in their coolers. My suggestion is get something else and clean it off. I don't know if it's necessarily bad, just never got the point of the "sticky" kind.

I went to my mobo support page and sorted the supported ram list by speed and hit buy. Surprisingly it passed many a memtest on 3466 already with a first gen Ryzen?(Summit ridge apparently? Never kept up with Ryzen development). Component pairing is a big deal sometimes.

I quite like the Sennheiser CX 300-IIs. The best earbuds I've ever had are the HTC Usonics, but seeing as those only work with their phones the Sennheisers are a close second

To be honest, we should probably stop cryptomining at every opportunity...
On a serious note: Write software as efficient as humanly possible. If everyone does it you'd probably be surprised how much power we'd save. This is one of the primary reasons I hate software which is obviously consuming way more resources than necessary (*cough* Electron *cough*)

        ↘️
        ⬆️↘️
➡️➡️➡️⬆️➡️↘️
➡️➡️➡️➡️➡️➡️➡️
➡️➡️➡️⬇️➡️↗️
        ⬇️↗️
        ↗️

Looks like you got some faulty RAM there.

The only other one I know for Windows which seems worth a damn is VeraCrypt, though I can't vouch for it as I've never used it.

Yeah UWP apps are not allowed to use the loopback. There's a command to exclude certain apps from the restrictions though. CheckNetIsolation or something like that.

@c3ypt1c Some OEMs enforce a waiting period when requesting a BL unlock token, supposedly to discourage resellers from installing third party firmware which could affect the end user's experience.