2,583 karma · joined February 9, 2011
[ my public key: https://keybase.io/preinheimer; my proof: https://keybase.io/preinheimer/sigs/xuqraBrBI-TAX8MtkyTCa-K8RyFslHOHT1dfAddxO1Q ]
preinheimer.at.hn
If you're looking to trace to something far away when doing a demo we've got servers in ~280 cities around the world so <random large city>.wonderproxy.com works. e.g. taipei.wonderproxy.com or santiago.wonderproxy.com, berlin, newyork, etc.
If you want to test your IP blocks, we have servers on both China and Russia, we can try to take a screenshot from there to see what we get (free, no signup) https://testlocal.ly/
I also think you disenfranchise too many people when you do that.
- People who work on oil rigs won't get to vote
- People who do shift work covering the hours the polls are open wont get to vote
- People who are of sound mind, but too unwell to travel to a polling location wont get to vote
- November is Red/blue king crab season in Alaska, guess those people don't get to vote
- Flight attendants & pilots might be away from home that day.
- People in the military might be on exercise that day, we're cutting them off (though I'll assume deployed service members will get to vote wherever they are)
- Long haul truckers are out of luck
- Anyone on vacation is missing their chance
- College students are always a wildcard, do they cast a ballot where they are (ID could be from a different state) or go home for the weekend?
I volunteer with scouts, kids aged 5-8. We ran a cardboard based activity with the makedo stuff. We tried to supplement with scissors, they were not effective.
With the range of different ways captchas are presented today I can see it getting a good % of folks.
One choice won't get you fired, the other might save you a bit of cash.
I ran my worst client demo ever a few months ago. It was like our product simply didn’t work. A lot of pulled hair and frustrating debugging later we discovered that a recent update to the 1Password extension broke ours. They were subscribing to an auth event, but not returning, this timed out so our subscriber was never called. So our extension would tell the browser to change proxy servers, then sit ready to provide credentials, but the request would never come. 1Password’s support team was better than grammerly’s, but it’s hard to convince an unknown PM to prioritize something, especially if you’re speaking to them via a support team.
We’ve since discovered that there’s some Russian extension you need for government websites that has the same issue.
Why is it a national security issue? Because people who could make billions of dollars say so?
Exponential back off is great for a lot of problems, but irregularly updated blogs doesn’t seem like one of them.
So while an attacker could trick your browser to making a request to get the cookie, and trick your browser into submitting arbitrary form data, they couldn’t get the csrf tokens to match.
> Unfortunately, these Chromebooks could not reliably keep track of time within milliseconds of each other, so this method didn't work for us.
It’s been interesting that media where watermarking has been feasible (like photography) have seen creators get access to some compensation, while text based creators get nothing.
I completely understand a desire to shut things down cleanly, rather than risk something you watched over for years become something terrible.
My problem isn’t being shown an ad beside content I’m consuming, it’s being tracked.
Credit cards are a decent tool to stem the tide of people making lots of free accounts.