242 karma · joined August 25, 2016
CBC tried to head this problem off by disabling comments on all their Facebook posts so people would comment on CBC.ca.
You know how “nobody reads the article” before commenting? That phenomenon is massive on Facebook. News organizations are tired of providing fodder for Facebook comment sections and not getting eyeballs on their own websites. CBC News turned off comments on their Facebook articles to drive more people to their website.
I check yes because I have a half eaten chocolate bar in my backpack.
They ask what I have and I tell them, and immediately send me on my way, it’s great.
If the TLS ciphers the client proposes for negotiation doesn’t align with the client’s User-Agent they get a CAPTCHA.
I would suspect that whoever is doing this proxy-mirroring isn’t smart enough to ensure the TLS ciphers align with the User-Agent they’re passing through.
Get angry, and hurt them.
We did rollouts by age groups, and generally the appointments in urban areas would be two weeks out, but once you had a vaccination booking you could reschedule it. So everyone would book the first thing they found on the site, then could start looking for appointments made available due to other people rescheduling.
I wrote a scraper for vaccine appointment availability and shared it
The depth of BMW diagnosis tools is impressive.
Even more impressive has been the work of scapy around the debug and diagnosis protocols BMW uses.
Check it out: https://github.com/secdev/scapy/blob/master/scapy/contrib/au...
It depends, like everything.
Connection 1
LISTEN 'job-updates';
Connection 2 BEGIN;
INSERT INTO jobs ('a-uuid', …);
SELECT PG_NOTIFY('job-update', 'json blob containing uuid and state change info');
COMMIT;
Connection 3 (used when Connection 1 is notified) BEGIN;
SELECT id, … FROM jobs WHERE id = 'a-uuid' FOR UPDATE SKIP LOCKED;
UPDATE 'jobs' SET state = 'step1_completed' WHERE is = 'a-uuid';
SELECT PG_NOTIFY('job-update', 'json blob containing uuid and state change info');
-- do the thing here: computation, calling external API, etc. If it fails then rollback.
COMMIT;
Because notify has transactional semantics, the notify only goes out at transaction commit time. You want to use a dedicated connection for the notify.The only downsides I immediately think of are you will have every worker contending to lock that row, and you’ll need to write periodic jobs to cleanup/retry failures.
Sure about the long running connection issue being solved? :-)
At that point I realized it didn't matter how many options I had, I was going to get screwed should there be an exit, and made my own.