cheeseprocedure
Joined 15 years ago
Karma
367
Submissions
154
Member since
Oct 5
Recent submissions
Comment · 6 months ago
Comment · 9 months ago
Yeah, the Canadian telco was Rogers. Total recovery took multiple days. From the Wikipedia writeup:
> In a letter to the CRTC, Rogers stated that the deletion of a routing filter on its distribution routers caused all possible routes to the internet to pass through the routers, exceeding the capacity of the routers on its core network.
https://en.wikipedia.org/wiki/2022_Rogers_Communications_out...
Comment · 3 years ago
Datapacket has a number of dedicated server configurations in various locations and offers unmetered connections:
Comment · 3 years ago
Yes, I registered as an individual (but was reimbursed through my employer's training budget), and did so a few months in advance as the previous session seemed to fill up pretty quickly. It was USD$1500 for the week. I'm keeping an eye on his course listing too - I'd love to take more.
Comment · 3 years ago
I was lucky enough to take David Beazley's "Rafting Trip," a five-day training course that guides each student through building their own Raft implementation from scratch:
https://www.dabeaz.com/raft.html
I'd recommend the course to anyone with development experience working with or near distributed systems. David is a fantastic instructor and facilitator, and the blend of student backgrounds led to some great learning and discussion.
(I have no financial or personal interest here; I just loved the course.)
Comment · 3 years ago
A prior employer shipped a lot of systems based on Lanner and Portwell equipment:
Comment · 3 years ago
Consul’s autopilot feature makes life a little easier by automatically reaping failed instances:
https://developer.hashicorp.com/consul/tutorials/datacenter-...
Paired with cloud discovery, it makes for a tolerable operational experience when instances are expected to occasionally disappear.
Comment · 6 years ago
You can do this below ground level, but it loses some other useful properties (catching more sunlight, improved drainage, ergonomics). Depending on where you live, one approach may work better than the other.
Comment · 6 years ago
The permaculture community emphasizes the concept of “appropriate technology,” which depends on context but generally means “seek simple/low-impact approaches.”
If you’re building large low-input beds that could last for a decade or more, a tractor might be an appropriate tool given your local constraints vs. a crew of horses/humans and a great deal of time/energy.
Comment · 6 years ago
packagecloud's in-depth writeups on the Linux networking stack are a great read:
https://blog.packagecloud.io/eng/2016/06/22/monitoring-tunin...
https://blog.packagecloud.io/eng/2017/02/06/monitoring-tunin...
The illustrated guide to receiving data is also solid:
https://blog.packagecloud.io/eng/2016/10/11/monitoring-tunin...
Comment · 7 years ago
A recent Canadian example:
> The data being broadcast includes the patients name, age, gender marker, diagnosis, their attending doctor and room number. Other broadcasts regarding medical tests such as x-rays are often associated with a patients last name or medical number, exposing their progression through hospital departments.
https://openprivacy.ca/blog/2019/09/09/open-privacy-discover...
Comment · 7 years ago
It’s possible to raise chickens as part of a broader regenerative system where much of the feed is an output from elsewhere in that system. This has been done profitably by folks like Joel Salatin, but it has its own constraints (for example, availability of pasture land).
Comment · 7 years ago
A surge from a lightning strike near my home travelled over the cable line to kill a network switch and the WAN port on a firewall. (Strangely, the cable modem was spared.)
Everything was on a decent UPS... but I’d completely forgotten the cable line.
Comment · 8 years ago
Another vote for the HiFiBerry. I’ve used their Digi+ board (which includes optical-out) with a Pi3B running Volumio for a couple years and it’s been fantastic.
Comment · 8 years ago
Nope - silly assumption on my part.
> Each electoral list legitimately released by Elections Alberta includes a certain number of fictitious — or "seeded" — names. These unique entries on each electoral list allow investigators to trace each dataset back to their source in the event of a breach.
https://www.cbc.ca/news/canada/edmonton/elections-alberta-vo...