Your idea of ‘containment’ in this sense means you’re defending the equivalent of a gang of serial rapists and murderers entering innocent people’s homes, taking their families hostage, and saying the home is now theirs.
1,240 karma · joined April 4, 2019
Your idea of ‘containment’ in this sense means you’re defending the equivalent of a gang of serial rapists and murderers entering innocent people’s homes, taking their families hostage, and saying the home is now theirs.
They never mentioned whether it’d actually be beneficial for the government.
Can’t wait for all of our federal agency buildings to be named after different members of the Trump family once they’ve changed hands! /s
The simplicity of the approach seemed pretty awesome
I think "new" would make sense and I accidentally conflated them also writing about the EPA rolling back *existing* standards for other appliances in this article.
The only part of the article that explained what was done states: "Today’s actions postpone the efficiency standards for the following home appliance rules:"
Would a title of "US energy department indefinitely postpones efficiency standards for home appliances" sound less deceptive to you?
This is a very odd take. The title is based on the only part of the article that isn't PR fluff and describes what was done:
> Today’s actions postpone the efficiency standards for the following home appliance rules:
Central Air Conditioners
Clothes Washers and Dryers
General Service Lamps
Walk-In Coolers and Freezers
Gas Instantaneous Water Heaters
Commercial Refrigeration Equipment
Air CompressorsI’ve been working with AWS for about 8 years now and have worked on supporting dozens of projects across 5 different orgs ranging from small 5-person shops to 1000+ people. I have only seen a handful of cases where serverless makes sense.
> Taking a legacy application that runs on a single server and is struggling to scale with spaghetti of config files all over the box and security issues that have gone unpatched because no one wants to touch the box as it’s too dangerous to change anything, as everything is intertwined. No backups or unverified backups. No redundancy. No reproducible environments so things work on local but not on remote. Takes devs days to pin the issues.
All of these issues are easily possible with many serverless options. What it really sounds like is your org went from a legacy architecture that built up a ton of tech debt over the course of years and had no one owning the basics (ie backups) to a new one with less tech debt since it was built specifically around current issues you were facing. In 3-5 years I wouldn’t be surprised to hear the pendulum swinging back in the other direction as staffing and resources change hands and new requirements emerge.
It’s often the opposite, but most people don’t see that until after they’ve built their infrastructure around that, get locked in, and then start seeing the surprise bills, difficult to diagnose system failures, and hard-limitations start rolling in.
A bit of early skepticism, and alternative solutions with a long-term perspective in mind, often go a long way.
This is likely why the only other ‘competitors’ you see are peering based or based on a subscription model. Neither of which can really compete with YouTube which really doesn’t need to *directly* make any money
Maybe I’m just jaded from years doing this, but two things have never failed me for bringing me peace of mind in the infrastructure/ops world:
1. Use whatever your company has already committed to. Compare options and bring up tradeoffs when committing to a cloud-specific service(ie. AWS Lambdas) versus more generic solutions around cost, security and maintenance.
2. Use whatever feels right to you for anything else.
Preventing the NSA from cracking into your system is a fun thought exercise, but life is too short to make that the focus of all your hosting concerns
All I can say is: There are a lot of red flags here.
For context, getting out of the sandbox at every org I worked at was essentially a single ticket with the word please and had almost immediate approval.
For my own account for a low volume form notification tool I wrote AWS’s response was ‘We will not approve your request and we will not revisit this decision’.
It’d go to a random company that never did anything related to trash pick up, but one of the board members would be loosely related to the mayor.
The mayor will then do a victory lap in front of journalists talking about this revolutionary project.
The winner would then sub-contract a series of shell companies to handle ‘planning the design and implementation’ of the vehicle used to pick up the debris.
3 months will pass and the first community board meeting about the pilot in the neighborhood will happen, where the project will hit vicious opposition from people citing gentrification, how this pilot will rip apart the fabric of the neighborhood, cause gridlock, be dangerous for kids (What if a kid runs infront of the magnet bike??), etc…
6 months and $5M later, the pilot gets extended and another $50M worth of funding having never picked up an ounce of trash.
Hello from NYC
But I do recognize that really is a legitimate question and it feels like Yubi would benefit from running more outreach / promotion programs with schools and companies. I never felt like I could justify spending $50 just to try it out(especially when it doesn’t have support in a lot of sites), but then they partnered with Cloudflare to sell up to 5 per person at $10 each. It was a no-brainer to try it at that price and I haven’t looked back
Someone would need to physically take your laptop, unlock it, and get your account passwords before they could use your yubikey to login to accounts.
I recently worked on a similar side project but took a very different approach. It pretty much was just:
1. A bash script in a Raspberry Pi W that ran `bluetoothctl` once per minute and wrote the raw output for that minute to a file.
2. A systemd process that would ensure the script would get re-run if the process crashed or machine rebooted
3. A separate script that parsed the logs and pushed them to a local sqlite DB that tracked the minute the bluetooth id was found.
4. A daily push to my backup server that stored the sqlite DB
I decided to use systemd and a simple(10loc) bash script since I faced a similar issue to the OP where my pi would crash(although it was purely my fault for messing with a bunch of cables) and I wanted a way to get it running again with the lowest overhead. I also wanted as few dependencies as possible.
I went with SQLite because it made querying for trends and building dashboards simpler and more interesting(and because the real project was the sqlite interface I was building :) )
One thing I learned from running this which also may answer a couple of OPs questions: Apple devices like hiding themselves. The only way I could get my Apple laptops and phones to show up was to keep the bluetooth settings menu open on them. Otherwise, they wouldn't appear to the bluetooth scanner. I can't speak much to whether android devices are 'noisier', but the lack of bluetooth feeds for Apple devices alone cuts out a significant part of the value of bluetooth scanning for crowd sensing, given the market share for Apple devices.
> Anyone can sign up at this website as a potential reshipping mule, although doing so requires applicants to share a great deal of personal and financial information, as well as copies of an ID or passport matching the supplied name.
I only meant that it would have been the best commuting tool for me.
It seemed like vernon99 was talking about nosediving from a complete stop(trying to go from motor off -> motor engaged but the motor doesn’t engage), whereas in the post you linked to, I was talking about starting from having the motor engaged already at a low speed (ie <5mph slowly moving back and forth waiting for a light) and then the power would just drop out.
Same result, but likely different causes.
I also stand by this: The Onewheel was the most versatile commuter option I’ve ever used in NYC.
If failsafes were added that didn’t rely on ‘maintain balance while skidding on your nose or tail at 15+mph in traffic if the power decides to randomly cut off’, I’d likely buy it again.