subway

I'd personally consider the whole concept of a vitality curve to be rather fucked up.

It's been all but abandoned by the biggest names behind it (GE, MS).

> Some of these facilities have thousands of employees. A few hundred firings in a year seems, at a glance, plausible.

The article mentions these numbers are for a specific warehouse, and provides the total number of employees at that warehouse (~2500).

If you're firing over 10% of your workforce annually for performance, you have fucked up expectations.

If you use that word again, we'll have to ask you to leave. They're water pipes.

On the bright side, room based deployments can also happen with open standards like H.323 and SIP.

https://support.zoom.us/hc/en-us/categories/200110033-H-323-...

s/for extra value//

It's very different when the trigger is locally a not-so-great guess followed by shipping the audio to a remote service that can make a slightly more informed guess.

Since the start of 2018 those numbers have gone down quite a bit, mostly due to the shake out of "dollar gate", leading to some of the popular local tournaments no longer reporting results to the IFPA. Despite the local rankings dropping a bit, it feels like the community has grown drastically.

Security cameras often explicitly lack audio because of these laws. The other devices you mentioned all have primary functionality that doesn't depend of recording nearby audio arbitrarily. The possible exception is Siri and Google's assistant, which fall into the category of services/devices being questioned in this instance.

Imagine how long the devices would stay on the market if owners started being held liable for what the device does.

I'm not suggesting the device be made illegal, but I do think a ton of common applications should be... and without those applications, the device loses viability.

The telephone is only relevant in some jurisdictions. For instance in Illlinois (an all-party state), you cannot record a private conversation. There's no mention of a phone or telecoms, and you should expect to get sued if you're in a conference room recording folks without their consent.

> which makes smart speakers basically impossible to exist.

Then perhaps in their current form, they shouldn't exist. It's already illegal to record people without their consent in many states. We shouldn't give up this right to privacy for a bit of convenience.

You can be right about something without bringing it up every chance you get, despite it only having a vague relation to any topic being discussed.

The history of Stern is a little crazy. Sam Stern founded Stern Electronics with the assets from Chicago Coin and Seeburg. Seeburg had previously owned Williams, but spun it off into its own company when Seeburg went bust. Sam Stern had manged the Williams division, but didnt get the assets to it when Seeburg went under.

Stern Electronics went under in the 80s and folks ended up at Data East, then Sega. Eventually Sega got out of pinball and sold the assets to Gary Stern, Sam's son, to form Stern Pinball. This was about the same time Williams got out of pinball, and I think their assets ended up at a German company.

Chicago has nothing on Seattle (OK, except for a manufacturer, and the Sharpe brothers promoting pinball).

Monday Night Pinball in Seattle now has 26 teams with 10 players each, plus a massive pool of substitute players. We've grown to the point of splitting into upper and lower divisions with promotion and relegation.

https://www.mondaynightpinball.com

And that's just one weekly event. There are a ton of events:

http://www.skill-shot.com/calendar

The bigger issue with public wifi is even actually finding your bank's server in the first place. HSTS largely saves the day here, but is far from universal. If any non TLS requests are in the request chain, and you don't have an eagle eye on the address bar, all bets are off.

This paper doesn't mention anything about TPM. It mentions TEE (TrustZone, really) and SGX.

TPM is effectively a smart card hanging off a system bus, usually on a separate package.

SGX and TrustZone are CPU features enabling a "secure" run time environment separate from the main run time env.

Even creating an app, the hoops are non-trivial. Due to the scope required (gmail.send), app verification and approval is required.

I've been toying with writing a credential helper to obtain the oauth bearer token, but Authen::SASL::XOAUTH2 still needs to be written so that git-send-mail knows how to use it.

Huh?

The magic password is the token. The "scoping" options are just a label (I suppose this might have recently changed), mostly targeting folks who are looking at using legacy mail/cal/card clients with only user/pass support, and are unsure what's going on.

edit: Just triple checked -- the 16 character string returned when creating a "Calendar on iPhone" password works perfectly for SMTP via PLAIN over TLS.

I'm betting it'll be x months free with the device along with a mostly-pre-configured profile.

The Google implementation of application specific passwords is horrible. There's nothing application specific about it -- it's valid for at least mail, calendar, and contacts, with no way to limit the scope. It ends up being a password that effectively bypasses all MFA on your Google account. Where do you store such a password? That's a powerful credential to be regularly unlocking.

I should be able to create a credential that's valid for just SMTP, with no IMAP or cal/card access at all.

It's also the family name of the vile people dictating the behavior of the government.

This is disappointing -- Sony has surprisingly been one of the best Android manufacturers with regard to being open: https://developer.sony.com/develop/open-devices/

Most of their devices can run AOSP, and the various blobs are built for a crazy number of android and kernel versions.

Singularity isn't a scheduler. It's generally invoked by traditional hpc schedulers like moab or slurm.

edit: clearly I'm thinking of a different Singularity than you.

I don't like this for today's Twitter, but it is mildly interesting to consider that once upon a time Twitter's main ui was SMS based.

It really isn't up to the KiCad folks to package it up though -- that should come from the Alpine side of the community.

It sounds like you don't understand the tools you use, and have no interest in learning them. NetwokManager (just like any other daemon) cannot "re-enable" itself. It's possible if you were on an Debian derived host that package post-install scripts enable the service (as is the case with all services on Debian derived distros due to packaging policies. The right way forward here is to indeed remove the package if you aren't using NM. Or better yet, get a better grip on the packages you install in the first place, and just don't install NM to begin with.

If you're on a RH or Arch derived distro, policy is just the opposite, and if the service is ever magically enabled (aside from Anaconda enabling it after the package was selected at install time), it's a massive bug (I can't find any such bug report in Arch or Fedora).

LBNL is an incredibly open, yet monitored network (in the spirit of the collaborative research that goes on there.)

You can be certain that most every packet in, out, or through the place gets captured and inspected by Bro (errr, I guess Zeek now. https://www.zeek.org/ )

I should also mention that not every host had a public IP. I worked with the group that managed midrange compute clusters, which were always behind NAT, with bastion login nodes.

Even now, some large traditional sites put static public IPs on workstations. When I was a lbl.gov, you got a (minimally firewalled) public ip via dhcp, and the hostname sent by your workstation was used to create a dns record of foo.dhcp.lbl.gov. You could request a static address for your host, and you'd be assigned an even less firewalled ip along with a foo.lbl.gov record.

A decade later this still seems to be at least partly in place, as I'm able to browse the webserver running on an old colleague's desktop.

Most nameservers disallow zone transers (requesting the full zone file), preventing this. Additionally it's more and more common for IPs to have a fixed generic PTR that just describes the IP instead of the host, and for a lot of hosts to not even have dns records. (My last webapp never bothered with dns for the dozens of ephemeral webserver instances).

Plenty of unethical behaviors can be sold as being in the best interest of the actor.