Dribbble Wants Its Cut – Pixel Envy

I forgot about my Dribbble account. Just dunked it.

See also:

The Internet’s business model is betrayal.

— Michael W. Lucas

Reply via email

• ⚡️ took apart our nespresso frother and found a dead thermal fuse on one of the mains. paid ~$12 for a new fuse which is annoying. oh well
• 💚 loved keenan’s people and blogs interview. I hope they get the domain they want eventually
• 🎮 obsessed with Minecraft lately as I’ve been playing on a friend’s realm. bedrock edition best edition. I was surprised to find out MCBE supports mods (albeit not serverside) and they’re double-click to install. nice
• 🎮 tried to get back into Diablo IV for the XP bonus after a few week’s break, but my Paragon 144 Sorcerer is too squishy in Torment II and I’m not having fun. next season I’ll probably roll Spiritborn (again) or Necro
• 🎮 been playing through Bioshock Remastered and thoroughly enjoying it. I think my last playthrough was eleven years ago. would you kindly
• 📚 still studying for the CCST and reading the appropriate boring books. I hope the exam won’t require me to calculate network prefixes in my head because that currently takes me way too long. I feel myself getting better though
• 📚 started reading The Two-Hour Job Search because it confirmed my existing bias that applying for jobs without having a guy on the inside is futile. putting together a spreadsheet of companies I’d like to work for was super motivating by itself. we’ll see

Reply via email

Happened to check my Cloudflare firewall events today and realized I thoughtlessly turned on “Bot Fight Mode” again, which completely ignores the rules I added to allow feed readers through. That’s off again now, sorry about that.

I also took the time to comb through and update my feed reader firewall rule. This shouldn’t affect most readers, but if it does and you happen to notice a few weeks later, I’m sharing hints of what gets you through the firewall. I think anyone breathing who might be looking for ways around the firewall is going to figure it out anyway; the rule is in place to stop those who are less inclined to find a workaround for one of the millions of sites they’re scraping.

If your feed reader is:

• sending requests from your home network, or
• in the Feed Fetcher category on the Cloudflare verified bots list, or
• one of the popular self-hosted ones, and
• only accessing URIs ending in index.xml

You’re good. Come on in.

If your feed reader:

• has no user agent, or
• has a user agent which does not describe what it is (e.g. python-requests or pretending to be a web browser), and
• is hosted on a VPS provider with the super combo of low prices and low moderation (e.g. Hetzner)

Update your user agent field. I am getting too many requests from nameless services running on random private servers, and most of them appear to be scraping my website or trying to find WordPress vulnerabilities. If you’re still having trouble after updating your passion project’s UA, feel free to contact me. I don’t want to accidentally exclude anyone.

If you’re legitimately trying to browse my website over a VPN hosted on one of the VPS providers I put on my bad list, you’re going to get a Cloudflare challenge and I’m sorry. There’s no feasible way for me to discern between your web browser and the bots pretending to be a web browser who share your VPS provider.

Sidenote: it made me smile to see jamesg’s Artemis feed reader in the Cloudflare verified bots list.

Reply via email