m1keil

Suspect there is one in any language. Here's python's option:

https://sh.readthedocs.io/en/latest/index.html

Probably one of my favourite episodes so far. I want familiar with Greg Wilson but I'm almost sure I stumbled onto some of his work before.

My only nitpick with the episode is the background keyboard typing that can be heard during the interview.

Hmm, maybe I was too harsh. I got the change log here: https://doc.samsungmobile.com/SM-S916B/XSA/doc.html

Seems like anywhere between one to three weeks. I think the auto update is a bit lazy. Had to force update on mine just now to make it get January update.

I had similar feeling about Samsung in the past but I think it is quite better nowadays. But there definitely is some AOSP/Samsung duality you cannot escape. My current gripes with existing s23+ is usually one of following:

1. Some of their features are being offloaded to unknown 3rd party vendors (e.g call spam detection). 2. They really want you to install some sort of McAfee AV on your phone to get the "secure" tick. 3. They are usually about a month behind when it comes to Android security patches. 4. Phone comes pre-installed with crap.

So just normal job in bigCorp?

Alternatives: zoxide, autojump, fasd, and probably couple other

Nice read, thanks for sharing. And thanks for the book recommendation, never heard about it before.

I think in that case they might want to make it clear they are recommending unsupported model.

While this is crystal clear, what isn't clear is what actual robots are officially supported..

For example, the buying recommendations mentions Roborock S8/S8+, but the supported robots page doesn't mention it.

¯\_(ツ)_/¯

This is most likely just a security "best practice" that goes unquestioned. It is pretty much on the same level as blocking ICMP.

I remember in the past how I lost couple of hours trying to understand why I can't reach a remote instance via RDP, only to finally figure it was the port blocking on the office firewall.

I spent quite a while trying to convince the local sysadmin that this doesn't make any sense. His only explanation was "security" without any actual explanation of what is he securing us from.

Yep, I am following them already. Cheers! :)

I don't have issue with screenshots in docs except for one small caveat: too many screenshots.

Don't screenshot Every. Single. Step. Doing so makes the documents harder to read as every paragraph ends up seperated by one or more screenshots.

Make sure that "the point" of the screenshot is clear. If required, crop or highlight the important bits.

Granted, screenshots will go out of date but so will any other documentation. This is also why having bit less screenshots will help you keeping docs up to date.

If you still think that screenshoting every step is a better idea, consider screen recording instead.

Honestly feels a bit like the end of another great company - Chef (Adam Jacob). Great tooling, built with great engineers but business realities forced it to take some unfortunate turns.

I hope Hashicorp will manage to find its stride and not end up as some bullet point in a long "solutions" portfolio of some software conglomerate.

And thank you Mitchell for all the work. Can't wait to see what is coming next from you.

Honestly, if there is one reason to use this app is because it allows you to share video with timestamp unlike the official Youtube app that is still unable to do that in 2023.

I don't disagree. Just pointing out that "zero knowledge" isn't the cure for every security issue.

His bail was 250M USD, I don't think money is an issue to his family.

Maybe they will also stop sending snail mail and use electronic email as well. Sending a letter across the world to remind me to renew my subscription seems quiet pointless in 2023.

> The attacks wouldn't have happened if the founders of Israel (not all of whom were Jews, looking at you Britain) hadn't decided to interpret an ancient holy book in a genocidal way. > The Palestinians lived there. Israel has been in the process of kicking them out ever since its founding.

You seem to interpret the history in really one way here...

While the encryption might be solid, if you have a security issue in a sensitive area such as the build environment, you cannot have any confidence in the app.

I'm not saying that this is what happened here, just pointing out that there are other risks here which cannot be mitigated by strong encryption.

Also when you self host, you don't need to "compete" with alternatives. Your goal isn't to provide service on the same scale as the commercial alternatives, but to provide a service to solve your local problem.

True, but in this case we are literally dealing with a company that claims they are really good at data security and it is the reason why the users are paying them.

It is one thing to outsource a monitoring solution. But outsourcing your SSO to a third party? They can only guarantee how well 1Password works, they cannot guarantee how well Okta works.

It is called propaganda and it exists on both sides.

+1. One of these apps that makes leaving macOS impossible.

Makes no difference in his setup as he can rotate the CA and the rest of the infrastructure quickly.

also quite interesting to compare with other implementations from the present and the past:

https://github.com/openbsd/src/blob/master/usr.bin/yes/yes.c https://github.com/freebsd/freebsd-src/blob/release/4.0.0/us...

Haha, Hi Cory, I would really like if 5 years after that article and blog posts if you are still in the Elixir ecosystem?

Does anyone has any followup information about the companies and people mentioned? Sadly last blog from Cory O'Daniel is from 2019 and Bleacher Report engineering blog post shows 2019 as the last post. Pinterest has 81 public repos on GitHub but only 3 with Elixir code base.

It's quite understandable that a "o11y protocol" is very valuable to a o11y service provider (especially the smaller ones) since it reduces the cost of vendor swap.

thank you for that xD

> With the goal of ending this current limbo and soothe longstanding tensions in the Nix community

Can someone with more background give a quick explanation about why is this a source of tension in the nix community in the first place? Is this a situation of too many cooks in the kitchen or something else?