shittyadmin

If you need a library to do this, check out GeographicLib. It's written by C. F. F. Karney the same guy who developed an algorithm and wrote a scientific paper about improving Vincenty's formulae for performance and fixing issues at nearly antipodal points.

It has good implementations in C++, C# and Javascript.

https://geographiclib.sourceforge.io/html/

Here's the thing though: You could build this in pure Node and call Windows APIs, Qt, etc and it'd be much, much smaller.

But everyone just goes ahead and pulls in Chrome.

It's shameful, and the worst part is that I get it - at this point I'm suggesting we go to Electron for a new application at work because it seems like the best maintained UI frameworks with readily available 3rd party components are all web based.

On B2 that's $10... yeah, might be reconsidering this...

I wonder at what point they'll just solve the safety issue by removing the windshield and adding shit loads of impact absorption and a few steel plates that isn't possible on vehicles where the driver needs to be able to see outside.

Interesting, unlike Glacier this is significantly cheaper than Backblaze B2, meaning I might have to reconsider how I do my backups again. Any good backup tools supporting this type of service?

I rely on Restic at the moment which seems to need fast read access to data, but their incremental snapshotting is great. It'd be ideal if I could find something like that supporting these "cold storage" solutions.

The Shield uses WiFi Direct to connect to controllers, so it'd pretty much kill the point of the device if you were to fully disable WiFi Direct on it.

So your options are then:

- Cry about it and hope they change the policy (they won't)

- Accept using your cell data at school instead of their wifi (works, but is expensive)

- Bypass it using a VM (requires moderate technical knowledge, networking skills and possibly the ability to bypass vm detection)

- Reverse engineer it and crack it to behave the way you want (requires some pretty advanced technical skills)

As such, the vast majority of people will just go ahead and install it. This is the problem with these sorts of applications...

Definitely a good start but in a targeted attack scenario that's pretty trivial to bypass, if someone brags about having the latest Das Keyboard or something that's all it'd take... we need cryptographic authentication in the USB specification or at least a randomized serial that'd be unique per device so an attacker would need physical access to clone your keyboard.

I believe modern Thunderbolt already has this sort of cryptographic device authentication, which means not only physical access but at least a bit of reverse engineering skill, a much higher barrier than knowing their keyboard model.

They don't necessarily need full knowledge of the product or any such thing, they just need to be able to provide a sort of filter, remove anything uselessly abusive or congratulatory without value, open defects for obvious bugs with reproduction instructions and get users to dig in and provide useful details when asking questions.

Those questions can then be answered directly by them or forwarded off to a dev who will have more detail and be able to get answers faster without the drudge of dealing with the rest of it.

Personally while working at a small company and doing both support and development work, I found it helpful to simply tell customers we'd address issues "with the development team" even when that meant I was going to work on it. Drawing that line in the sand between support and development roles compartmentalize those activities and reduces the immediacy of demand from users.

Google should just kill the YouTube app for iOS and see how long this exclusive bullshit lasts.

Seems like a good idea, I wish I had more of a statistical background for this kind of thing. Seems like it'd have proved more useful for most software purposes than the calculus I had to take instead as a prerequisite.

It's basically just my boss making suggestions and me implementing, so the results are probably less than optimal for this kind of thing.

We've switched to box and whisker plots for most of our statistical reports, they give you a good idea for various important percentiles and adding average indicators is fairly simple if desired. Even for things like latency this can be quite useful.

It would, but I'm guessing they have a very cheap, ~$1 lens filter or glass sheet on those things.

Permanently damaging the camera sensor isn't so cheap or easy to replace. And as many lasers operate in the visible light spectrum you can't block it without worsening the image quality substantially.

Maybe this will be viewed as too anti-social, but has anyone considered doing laser based attacks on these? Lasers seem to be able to damage camera sensors fairly easily and permanently and as they operate in the visible light range should be hard to block. Could make a system like this prohibitively expensive to operate.

They're using a mixture of Streamlined NTRU Prime 4591^761 and X25519.

https://ntruprime.cr.yp.to/

Note that this is still considered "experimental" and probably won't be enabled by default.

I'd advise checking out some of the recent DJB and Tanja Lange talks for further detail on how research on these algorithms is progressing:

https://www.youtube.com/watch?v=ZCmnQR3_qWg

There's also the older but still relevant PQCHacks:

https://media.ccc.de/v/32c3-7210-pqchacks

Haven't seen any talk of post quantum signatures in changelogs yet at least, but research is happening rapidly in this field and OpenSSH has really upped their game in recent years.

Keep in mind that many of the preferred key exchange algorithms and ciphers have changed vastly since 2006. OpenSSH has been improving in the cryptography department by leaps and bounds.

OpenSSH 5.2 switched to preferring AES-CTR.

OpenSSH 5.7 added ECDH as a kex and ECDSA as for signing.

OpenSSH 6.2 added encrypt-then-mac and prefers it by default.

OpenSSH 6.5 added Curve25519 as a kex and chacha20-poly1305 as a cipher. As well as Ed25519 for signing.

OpenSSH 8 will add quantum resistant algorithms for key exchange.

I'm completely reliant on syncthing, termux, file browsers and such, it's literally why I prefer Android. I'm hoping most of these will be available for rooted users like myself still, but developers often lose motivation when most of their users evaporate.

I'm in a unionized position, the least competent people on my team are people who were basically dumped on us from other groups who had to get rid of people and of course, sent off the worst... suffice to say I'm not too concerned about keeping a job somewhere around there.

I think what you're more talking about is just sitting at what he considers "advanced beginner" or "competent" phases, rather than calling yourself an expert at something. And that's fine if it's what you're going for - you definitely don't need to try to squeeze every last ounce of knowledge and skill into every department in your life - just don't assume you know everything!

I feel like I may have wound up on this path... I'm working in a government role where I've been put as the lead developer on some major pieces of software despite only being 5 or so years into my career because the people I'm surrounded with seem to have some significant competency issues.

Not sure what I can do but quit and I just don't want to give up on the stuff I'm working on yet and I'm relied upon quite a bit... but I'm almost completely stagnating. Worst part is, I can probably just keep doing it for another 20 years and retire, it's almost too easy to just go that route.

They actually filter out many exchanges for exactly this concern...

But you don't need to write every time, only on occasion, so you can actually use a read write lock and in the nominal case many threads can read just fine.

That said, it's probably still better to avoid this unless it's absolutely necessary to modify the underlying structure sometimes, I recently had to do this for an LRU cache.

This is actually described quite well in the OP.

Interesting, both the Qt and Java ones seem to use chaining, but I guess they're not designed with these sorts of extremely demanding applications in mind.

So - what's the motivation to use "open addressing" vs chaining, which I thought was the more common approach to solving this.

I assume there must be a substantial performance gain for this to be used as it seems significantly more complicated, any information on how much better it is?

They're not illegal, but many sites ban them - I tried to find an unedited copy of the ISIS video with them dropping grenades from a drone a few years back... you often wind up having to go into the same niche news sites, gore sites, or torrent sites which you do to find this video. My options were pretty much 8chan itself or "BestGore" when I looked.

I'll also note that ISIS does a lot more editing and commentary to slant the content in their favor than this guy did. About all this guy did was make meme references... I can see an argument that this is quite different.

It really deeply bothers me, I wish there was something I could do to help protect my rights from this sort of reactionary response. Does the ACLU still put up a fight in cases like this? They used to back in the day, but I'm not sure they would now...

EDIT: To make my view clear here, Facebook and others are free to remove the videos, I'd prefer if they age-gated and put a warning on them instead, but that's their choice. What I don't like is the way that that some police agencies have been suggesting that mere possession of the video is illegal.

The worst part here is that the attacker himself was suggesting that by hitting on ideas like free speech and the right to bear arms he'd be able to "accelerate" the deepening of political divides. I do not want to be put in a place where I'm forced to choose between fundamental rights and respect for entire races of people, but at this rate I fear that decision time may be approaching. Given time I hope cooler heads will prevail.

To add to this a bit, it also provides a motivation for developers to make games that are too hard and will force users to pay if they want to enjoy them, but people who play like I do will get bored quickly.

This is why I loved the old Peggle games from PopCap but hate the new mobile one.

As a customer it may be great, but this isn't great for the developer in my opinion. Perhaps it's just the way I play, but I will already refuse to advance until I've got a level fully beaten, so I'll basically keep at that until I get bored of your game or beat it fully and you'll never see a penny from me.

Well, the FAA here just drew this conclusion based on ADS-B data picked up from a satellite, so I'm not sure how you're getting that idea.

At least, in areas where such sites have good coverage they may actually get closer to the ground data than the satellites are capable of picking up.

I don't mean to dump on doing a quality analysis, just that the quality of data is not as drastically different as you're suggesting.