So many datasets I'm interested in looking at, but they all require me to send data to google to look at.
146 karma · joined July 7, 2018
So many datasets I'm interested in looking at, but they all require me to send data to google to look at.
> I've also read that the forward tilt many houses exhibit was intentional- to make it easier to hoist goods to the upper floors.
I always thought that was just Dutch people being Dutch and getting more floorspace without buying more land. Any of the skyhooks I've seen just extend out above the top floor. I suppose there's more risk of breaking windows if the load swings around as it goes straight up though.
Would be pretty hard on a human timeline though.
Now we know. It's better to know.
If you can actually submit a support ticket, get them to agree that a phone number is not required (like it says on their website), and to reply when that's done, you'll get your account unlocked after a few days. (usually)
I get the account unlocked after a few days if I pester support about it. (which is not easy either)
Turtles, all the way down!
The site/extension basically has to do that each time it scrapes locally (or use generic parametrised scraper) If you wanted to use it in an API, my impression is that you can run it in chrome as an extension you need to get from the chrome store or tunnel your data through a third party server. Is that wrong?
Can you scrape data locally without running chrome/the extension? I can't tell from reading the site, sorry. (if it's actually there, please link an anchor tag to it or something please)
This just seems to add another dependency to whatever I'm developing. Plus, it sends data through a server I don't control. (I assume)
Or install onto a jailbroken device.
Because that exact kind of supply-chain attack thing happened to the original version. (ublock)
Probably a good thing this was caught early, as the typically large number of node.js dependencies required for a package could have led to some sort of combinatorial explosion of ads on install.
Even assuming that any one ad package checked to make sure it only displayed ads once per session, very many people would want to put an ad into some library somewhere, especially if they have existing users/dependants for their pre-ad version. Careful maintenance would be needed to avoid putting other people's ad code in yours, but also keep it up to date to fix exploits.
I use nginx + basic http auth, since I'm using it for https anyway.
Hill wanted to stop working on it, handed it off, and then it got bought by evil Germans. Then, he released and maintained an unfucked/original version: µblock origin
Does anyone else think it's weird that it requires access to your camera roll to view images, access to your camera to use the web version, and access to your contacts to start group chats? (on android anyway)
Aside from the webapp QR-code thing, none of that is technically necessary.
You get it back when you return the trolley though.
Guessing they currently don't have a hardware LED because it might freak people out how much the camera is actually on. Likely no onscreen indicator for the same reason. If they were going to make this change, they'd have to weigh the benefits of making this change against spooking users who have no idea why their bank app is using their front facing camera.
It's probably something really minor they disagree about, or they just haven't gotten around to it.
Is that 512 the lowest you can get it with command line options?
Rather than making all of those applications vulnerable at the same time, they slowly become vulnerable as the release binaries are linked against bugged code. If it's not linked at runtime, or recompiled, it'll be vulnerable forever.
In computing, it actually matters.
This won't really hit people doing self-serve or custom ads much, but it'll cover the vast majority of the web.