madsushi

Caps Lock is a very fast tool for typing capital letters. Yes, toggling Caps Lock on/off for capital letters can be faster than using Shift.

One of the world's fastest typists uses this technique: http://seanwrona.com/typing.php

YouTube link for the most-recent talk: https://www.youtube.com/watch?v=__wn9zXFiy8

I've seen a couple versions of RAS' talk and learn something new every time.

Only losing user-uploaded data seems pretty mild, in this case. Meraki sells cloud-managed network hardware, so you don't interact with it that often. Network configurations, logs, traffic data -- any of those would've been much worse to lose. The custom bits like voicemail greetings and IVR will likely be the hardest to replace.

There are lots of organizations where certificates are "managed" by a recurring Outlook meeting on a 2-year cycle, where you hope that employee is still around. Moving to an automated system like certbot (which I use and love) with proper logging and email alerts is the right way to go! But that can require a lot of communication between the server teams, web teams, IT teams, etc. There are plenty of places where it seems more convenient (true or not) to just deal with $100 every couple of years than spend the time to implement new processes.

It looks like LE will let you do that:

https://community.letsencrypt.org/t/can-i-use-lets-encrypt-i...

Wildcards were one of the two big blockers for Let's Encrypt adoption at a lot of organizations. The second blocker, the operational discipline to automatically refresh the cert and restart services every <90 days, will likely be the only excuse left.

Twitch bought Curse and revamped their app as the Twitch App, it's moving towards Discord-like features already.

Sure, there's no technical issue since a prefix is a prefix is a prefix. It's all just bits. If you can convince your upstream/peers to accept a route, there's nobody to stop you. I haven't run an ISP, so maybe I haven't had to push hard enough, but my transit providers' willingness to accept someone else's PA block has been nil.

You can get provider-aggretable (PA) IP addresses from your ISP, but they can only be used with that ISP. You can also get provider-independent (PI) addresses, which you can use and move between ISPs with BGP. If they're using Zayo and Level 3 at the same time, you would need PI-IPs that you can move to the other ISP when one ISP is down.

Or, another option is that they're doing CGNAT on all of their client traffic.

If he's using Level 3, he would have to have his own PI-IP block. I'd be interested to hear more about IPv4 and IPv6 in the small ISP world. With 50-100 clients, a single /24 block would serve his current client base.

There's a Chromium bug that goes into more details, but the basic idea was that they didn't want the cert details button to be in the Page Info pop up, but didn't have a new place to put it. In Chrome 56, the SSL icon now shows "Secure" or "Not Secure", so more users will be clicking on Page Info, and they didn't like technical details in that pane. There's a new bug to find a better place for certificate details in Chrome 57.

https://bugs.chromium.org/p/chromium/issues/detail?id=646465

https://bugs.chromium.org/p/chromium/issues/detail?id=663971

Part of Brave's adblocking was replacing site ads with their own ads, and then a slice of the ad revenue back to the user. So you'd get a 15% cut of the revenue and only see Brave-provided or Brave-approved ads. You could then choose to reinvest that and give the money back to the sites that you visit.

There's a USB adapter and software that lets you transfer files/scripts to and from the calculator. You can also record data over that port as well.

Very neat. Similar to the iOS game series Galcon, which ate up many hours of my time.

And software has failures.

Public IPs are about $10/each on the market. If you're running a serious service, $10 is a fairly small cost, so you just buy whatever you need. IPv4 exhaustion has mostly affected people that were getting addresses for "free".

r/K selection theory[1] can help explain why some creatures favor longer reproductive timelines.

[1] - https://en.wikipedia.org/wiki/R/K_selection_theory

They wanted to save the 1 character.

Being able to edit something that someone has already retweeted seems ripe for abuse.

The article mentions that it catches wget | bash as well. I imagine it's due to the fact that bash's characteristic network signature is what they're really detecting, not curl/wget.

IPMI cards are always-on, and run outside the rest of the server. They receive power even if the server is shut down. These are used for out-of-band management, power on/off, etc. Imagine if someone were to have control of the firmware running on your IPMI cards... they would have physical access to your server (essentially) from a remote location. You often don't control what's running on the IPMI cards or if they call home, etc. What if HP or Dell had sleeper software in your IPMI cards, and when it wakes up, opens a direct connection to your server?

The invitee in question: https://en.wikipedia.org/wiki/Curtis_Yarvin

Do you mean the problem is technically hard or politically hard? From my understanding, it's not too difficult for an ISP to implement, the problem is convincing ISPs to implement it (when many don't care).

There's a great EconTalk podcast episode about Matching Markets with Alvin Roth (the Stanford economist mentioned in the article):

http://www.econtalk.org/archives/2015/07/alvin_roth_on_m.htm...

1) Databases - if your app servers at the edge need to talk to your database back at your main datacenter, you've just made performance worse. Replicate the data to the edge? Now it's harder to keep consistent.

2) Too many edges - if you regionalize too heavily, you end up restricting your matchmaking pools to smaller groups. Matchmaking theory says that either (a) quality of matches decreases or (b) time to matchmake increases as your pool shrinks. At some point, to have a healthy matchmaking pool in a game with a wide variety of skill levels, you have to consolidate. Riot already had Euro datacenters (with separate accounts, which solves #1).

3) Performance - cloud low-latency UDP performance isn't nearly as good as you can get yourself. Plus, you have more control (and leverage) doing it in-house.

4) Perception - some level of latency becomes imperceptible, 50ms is getting pretty close to that number.

Cisco was also rushed to release the fix, as all of the new builds are tagged 'interim' and warn users that they have bugs and stability problems that will be fixed later. Most notably, several issues with ASA Clustering were found in the new builds. So you're damned if you do, damned if you don't.

I don't know if the XIM works when connected to a PC, but I think in this example the PC is just a middle-man and the XIM lets you cut it out completely.

Very likely, but also typically not exposed to the internet. So there's definitely plenty of risk here, but an adversary would likely have to be within your network to query your DC.

Both relate to flow control and trying to deliver a lossless network medium.

Regarding B2B credits / Fibre Channel and the hop-by-hop windows in X.25, the idea is that each hop has a counter of how many packets it will send to the next hop without receiving an acknowledgement, which are "credits". Once you're out of credits, that hop stops sending traffic. X.25 was superceded/replaced by TCP/IP (which uses end-to-end acknowledgements, instead of hop-by-hop) due to increased performance. But B2B is used with Fibre Channel (storage) networks, which require lossless performance on each hop.

Regarding PAUSE frames and Ctrl-S/Ctrl-Q, the idea is that as a device's receive buffer fills up (it is receiving data faster than it can remove it from the buffer), it will hit its 'pause threshold', and it will send a PAUSE message to the sender to let it know that it can't handle any more data. This is similar to Ctrl-S/Ctrl-Q, which are XOFF/XON control commands in flow control, to stop and start traffic as you ran out of buffer space.

Continued:

"So we're making them, and we're penalizing any dealerships that are still selling black cars."