> ... but those of any complexity presumably ought to be in a library — that is, a set of magnetic tapes in which previously coded problems of permanent value are stored.
Oddly, I never thought of the term library as originating from a physical labelled and organized shelf of tapes, until now.
At https://youtu.be/DjhRRj6WYcs?t=338 you can see EDSAC's original linker, Margaret Hartrey, taking a library subroutine from the drawer of paper tapes. (But you should really watch the whole thing, of course!)
It's not _that_ they are called libraries, but _why_ they are called libraries. I had assumed, like many others that it was purely by analogy (ie, a desktop), and not that the term originated with a physical library of tapes.
I don't see .lib being all that common, but it might just be what I'm used to. `.so` or `.dll` or such sure (though to be fair, the latter does include the word library.)
.lib is the traditional extension for static libraries and import libraries on Windows. Every .dll has an accompanying .lib. (Msys2 uses their own extensions, namely .a for static libraries and .dll.a for import libraries.)
The issue is that the executive branch still has prosecutorial power with impeachment as one of the only remaining checks against that (if I’m understanding correctly).
A market correction is definitely taking place and jobs like the one in the post that are fully remote are highly coveted so it’s not so surprising. There’s still lots of places for tech to make a meaningful impact but acceptable risk tolerance is much stricter due to tax law shifts and VC funding strictness due to higher interest rates.
I would say that the job market has been tough for the last 6~9 months at least, you had the major tech layoffs occurring about a year ago and auto manufacturing was being impacted in October.
This is part of the reason people were upset with the message that the economy was doing fine during the election.
> Key Advantages: [...] Can provide supportive evidence for VPN/proxy usage, when the latency is too high for all server locations
I'm reading through the description, but I'm having trouble understanding the difference between a client having a higher overall latency due to bandwidth/connectivity concerns (e.g. a 3G phone) versus using a VPN. Both would have increased timings and the clock skew would be similar. Would both would be considered too high for proof of location?
For slow connections you can still make use Geo IP data (such as maxmind.com) to infer location, which should be quite reliable in most cases. You just cannot meet the stricter hardware location proof criteria based on latency. You may still submit a poll answer but it may not be included in the analyses, which require a higher degree of confidence for the location.
For the objective of obtaining a hard-to-manipulate sample of popular opinion, this would only be an issue if people with slow connections give systematically different responses for a given poll. But this should then also become apparent when analysing the data and can be considered for any decisions derived from the poll.
Why is clock skew being used here at all? I'm confused why the client's clock is being trusted or consulted in any way for a measurement like this. I should probably click through and read the details.
ETA Ok, reading the code turned up not a lot of comments. But it did produce the following line. I hope that's for testing and not the actual nonce generation process:
> Why is clock skew being used here at all?
You're right, it's not actually necessary to use the client clock at all. It was easier to implement it that way initially and I kept it in the description and didn't think about it again.. Thanks for pointing that out.
Since all timestamps are measured, the calculations can actually also be made afterwards without using the client clock timestamps at all. However this may add a bit more noise.
> not the actual nonce
The nonce can only be used once so it's ok to share it afterwards.
> No, wouldn't connecting to a slow 3g tower affect ping times to all global servers proportionately?
Yep. Per the article (last point under "How it works"):
> Users with a high latency to all servers can be excluded from polls, as this is a strong indicator of a VPN/proxy usage
Something seems off about how they're measuring latency (which seems to be "fetch various AWS Lambda endpoints"), since their system seems to think that I have hundreds of milliseconds of latency even to the nearest AWS region (even though in practice it should be an order of magnitude lower), and multiple seconds to the other side of the world.
edit: well, if the slowness is just on last-mile delivery, then it should be a fixed amount of overhead added to each connection (rather than a multiplier). For instance, I have about 8ms of latency added by my ISP just by the first hop into their network. But it's that same 8ms overhead whether I'm connecting to a server on the other side of town, or on the other side of the world.
If eliminating signal from malicious, remote actors is more valuable than preserving signal from rural areas, which may very well be the case depending on the application, then adopting this might solve a real problem for you.
I don't see anything terribly idiotic in that.
edit: to be clear I think this is likely one of those solutions that creates more problems than it solves. There's a gulf of sympathy separating that from "idiocy," however.
Pyramid tiling is the general technique used by Google Maps and similar systems to track images as different zoom levels; also similar techniques are used for progressive rendering for example in JPEG 2000.
> So what should you say? Simply remind them that your results, availability, and team spirit make you a reliable actor in the success of the company. Emphasise your future commitment more than your past success. In short, show them that by increasing your salary, they’re investing in a long-term project.
They didn’t put it in a separate section but they do have a bit about what to do at the end.
I read that as "expanding protections to reduce (privacy and security) risks ..." but I guess you're reading it as "expanding protections to reduce (privacy) and (security risks) ..."
I noticed this too but I think it was really smart to post robots in those movement roles because it makes these motion limitations “robotic” and mechanical like you said. It felt really attributable to the robot itself being programmed to operate that way.
Oddly, I never thought of the term library as originating from a physical labelled and organized shelf of tapes, until now.