@ariadne Your blog is advertising `h3` support but is refusing 443/udp connections?
```
$ curl --http3-only https://ariadne.space/feed.xml
curl: (7) QUIC: connection to 2600:3c00:1::68c8:16d6 port 443 refused
```
MacKenzie
@kenzeh
- 12 Followers
- 7 Following
- 21 Posts
Techie, on-social-media-but-not-very-social-media. he/him. Based in Nova Scotia, Canada.
@lachlancooper You're very welcome - my most popular blog post ever (which is to say, it received more than zero replies/thanks messages haha!)
@benjojo Loved the blog! I like that you had some data. I picked a 10.random.random.0/24 LAN a while ago, to avoid collisions, but then thought "Is this a tracking vector somehow?" (My local IP would be unique if it leaked) so I renumbered back to 192.168.1.0/24 to blend in with the normies!
Also I blogged about my internal subnet experience from 10 years of corporate life (pre-cloud!)
https://blog.amen6.com/blog/2024/04/internal-network-numbering-the-good-the-bad-and-the-ugly/
Internal Network Numbering: the Good the Bad and the Ugly
Introduction The Good The (Mundane) Bad The (Creative) Bad - IP Squatting The Ugly - Being Too Clever Postscript - What About IPv6? Introduction This is kind of a #storytime post, but also not. It’s a retrospective of the Good, the Bad, and the Ugly choices I’ve seen over my twenty years of work, in regards to how companies choose to use and abuse their internal network numbering. It should be fairly simple, but it’s one of those choices that can come back to bite you if you choose wrong (even if you do follow RFC 1918).
New Post: Fetching RSS Feeds Respectfully With curl
https://blog.amen6.com/blog/2024/11/fetching-rss-feeds-respectfully-with-curl/
Fetching RSS Feeds Respectfully With curl
Introduction Conditional Requests? Generate and Use a curl config Last-Modified / If-Modified-Since eTag / If-None-Match Grab The Latest curl Version with HTTP/3 Support Don’t Call It From cron Conclusion Introduction I am a member of the Church of RSS, though I’m quite a late convert (I missed the whole Google Reader thing). I use my own self-written Golang tools to parse the RSS/Atom feed files and send myself the entries in an email.
New Post: Self Hosting Email in 2024
It seems to be commonly held wisdom these days that self-hosting is great... but you'd be crazy to use it for *email*...
https://blog.amen6.com/blog/2024/09/self-hosting-email-in-2024/
Self Hosting Email in 2024
My Email History circa 1996 - Present 1996 to 1999 - The Dial-Up Era 1999 - 2003 - @unn.ac.uk / @ntlworld.com 2004 - 2011 - @gmail.com + Spamgourmet tagged Why Did I Decide To Ditch Gmail? 2012 - Present - Self-hosted at my own domain Hardest Thing About Ditching Gmail? Challenge 1 - A Good Webmail Client Challenge 2 - Isn’t It Impossible To Email Google/Yahoo/Microsoft Though? Challenge 3 - Calendar/Contact/File Sync Easiest Things Mail Software Anti-Spam Hosting Locations Conclusion Introduction It seems to be commonly held wisdom these days that self-hosting is great… but you’d be crazy to use it for email.
New Post: Story Time: Job #5: Part 5: Managed Security Provider - Dying Days
This is the final part.. it's taken me 3 months to get this series done and out of my brain, glad it's done!
https://blog.amen6.com/blog/2024/08/story-time-job-05-p5-managed-security-provider/
Story Time: Job #5: Part 5: Managed Security Provider - Dying Days
This is the final part of a long series, click here to see all the parts. Handing In Your Notice To Get Your Expenses Paid Doing My Bit For IPv4 Exhaustion When A Planned Upgrade Leads To A Unplanned Trip To Hell Can You Pinpoint The Moment You Knew We Were Doomed? Suddenly I’m The Only Engineer Left 💁♀️ Using My Leverage Cisco Certified The End The Brief Afterlife Conclusion Handing In Your Notice To Get Your Expenses Paid One day I was in the office when Jay got into an argument with the MD over a train ticket expenses claim.
New Post: Story Time: Job #5: Part 4: Managed Security Provider - Downsizing
https://blog.amen6.com/blog/2024/07/story-time-job-05-p4-managed-security-provider/
https://blog.amen6.com/blog/2024/07/story-time-job-05-p4-managed-security-provider/
Story Time: Job #5: Part 4: Managed Security Provider - Downsizing
This is Part 4 of a long series, click here to see all the parts. Moving Our London DC When A Site Visit Takes You Offline Post-Outage The New DC Moving Offices New Office Tour (Failing To) Sell A Room Full Of Old Solaris Hardware on eBay Sorting Out The Ticketing Database Renaming A Company Conclusion We had three of the biggest projects, concurrently running, you could do to your infrastructure:
New Post: Story Time: Job #5: Part 3: Managed Security Provider - Monitoring
https://blog.amen6.com/blog/2024/06/story-time-job-05-p3-managed-security-provider/
https://blog.amen6.com/blog/2024/06/story-time-job-05-p3-managed-security-provider/
Story Time: Job #5: Part 3: Managed Security Provider - Monitoring
Introduction Monitoring.. I had not had much exposure to monitoring so far in my career at this point. Either because I was on the Helpdesk and so our monitoring consisted of a user phoning us up to complain that "$THING IS DOWN!!".. or because there was already a mature monitoring set-up (or monitoring was siloed off into their own team). This story is similar to the last part about Email in that there was a Monitoring set-up.
New Post: Story Time: Job #5: Part 2: Managed Security Provider - Email Is On Fire
https://blog.amen6.com/blog/2024/06/story-time-job-05-p2-managed-security-provider/
https://blog.amen6.com/blog/2024/06/story-time-job-05-p2-managed-security-provider/
Story Time: Job #5: Part 2: Managed Security Provider - Email Is On Fire
March 2008 – Oct 2009 Introduction As I said in the last part: It appeared to have been frozen in time. Almost all the Unix servers were running ancient versions of Solaris (versions 8 or 9 - 2000 or 2002 vintage - and this was 2008) on anemic SPARC hardware. I don’t think anybody dared touch it, as nobody understood how it worked. Our email set-up was the biggest fire we had to put out.