1,799 karma · joined January 25, 2011
email: richter@(domain).net
BUT, there's the occasional nugget hidden in that pool of filth that makes it worth digging through :-)
I still learned something "new" from the article, I was only aware of the ceremony issue that "everbody knows" of.
"One of the first things anyone learns about Zcash" is that at least one of the ceremony's participants must be trusted to have securely destroyed his toxic waste.
This article is about the fact that there could be a backdoor, whose absence can only be proven by revealing all participants' toxic waste.
You'll note that these two things are at odds with each other.
We're looking for some help with a smallish ReasonML/ReasonReact app, and later some Python backend stuff.
If you're interested I'd like to talk to you, email info prokapi com, or XMPP hendi prokapi com
Everybody left their desks at 12:45 to stand in the queue, waiting for their coffee worth a few seconds of their time. At 2:15 everybody finished their coffee and went back to their chair.
I can't help but think management paid more in wasted salaries in these 1.5h than if they'd just made caffeine freely available all the time.
"within our means"
Don't you think with a bank account some orders of magnitude larger than mine, Bezos' means are larger than mine?
I've had a junior dev ask me what kind of strange multiplication thing was going on in our C code base. If you don't even know about pointers, maybe you're not "junior" yet and should learn some more.
While I applaud the things above I'm concerned about Cludflare's (growing) size. If it handles so many websites' traffic it's an interesting target for NSA, hackers and other malicious actors. I assume that most of your users use the free SSL certs, meaning Cloudflare possesses their private keys.
The more Cloudflare grows, the faster and the more encrypted "the internet" becoems. But the more Cloudflare grows, the bigger the single point to attack gets (I'm even assuming Cloudflare is and always will be a good actor).
What's your stance on this? Could you comment on this?
Thanks, that'd be great news! I couldn't find any information about that, any chance you could pull out a link like for your other points?
Just the other day I've torrented a PDF that I couldn't buy from O'Reilly.
I discovered Browserling just yesterday looking for a replacement for BrowserStack. I planned to hand over my credit card today but saw this blog post on the commute to the office. Thanks, but no. I'll continue looking and make sure to not make business with this guy.
> The Tor network currently only supports TCP ipv4 traffic
- claims to be "operated by activists and hacktivists"
- uses OpenVPN
- GPLv3 client for many platforms
- accepts Bitcoin (or PayPal, Credit Cards, ...)
- has an APIChanging common settings might in fact even make you stand out _more_.
Check the EFF's Panopticlick [0] to see how your specific configurations leaks identifying information.
The `AudioContext` API exposes several details about the host which may depend on the hardware (sound card, sound chip), software stack (OS, on Linux e.g. PulseAudio vs. ALSA), sound driver and its versions, and connected periphery (speakers? headphones?).
Additionally, the audio API is used to generate a sound (which is muted before being played, but still generated before). Sound is hard, and so the browser vendors don't necessarily generate the "sound bits" themselves but ask the OS to so. Which might in fact ask its sound system to do so. Which might ask its sound driver...
Some of these properties are fairly common or likely to change often. But chances are that combined they give you more bits of information then say the simple user agent string (which is shared by thousands - if not more! - other browsers).
If you'd find some things do change too often to be relied upon you could either take that into account, or simply don't use that specific fingerprinting technique.
> They wouldn't.
But the point of fingerprinting is that practically no two "browsers" are the same:
- browser software and exact version
- installed plugins
- size of browser window
- OS software and exact version (think of patches!)
- language
- time zone
- screen resolution
- ...
- (and all the stuff mentioned in the submitted article!)
See the EFF's Panopticlick to see _how_ unique your browser is. Be sure to click the "Show full results for fingerprinting" after the test to see all things it considers.Have you checked if Postgres works via the py-postgresql driver? It's implemented in only Python 3, with all C optimisations optional.
Edit: GOT IT, thanks!
Links are blue, and turn red on hover.