mrzool

I loved this article since I was one of those who installed fzf, didn't get it, and walked away (at least twice).

> for contrast, a little bit of dust can break an Apple butterfly keyboard

Butterfly switches have been discontinued by Apple in 2019, Macs with Apple Silicon do not have them.

> my infosec early warning bot

What's the handle? Sounds interesting :)

I'm also baffled by that after skimming the page and watching the demo video… seems like a Google Docs wrapper of some sort.

Paywalled, sadly.

> I guess the submitter wants to tell us that the page might have been intentionally removed?

Pretty much. At the very least I wanted to spark some sort of conversation about it.

> So many minor flags already that the problem could be completely accidental.

I hope you're right, but honestly there are also legit reasons to think otherwise. It could be a fuck up due to staff shortage and knowledge loss crisis, but it could also be an impromptu, poorly implemented and communicated decision. Both scenarios would not be surprising at this point.

> I assume the post is suggesting the Twitter api has been "removed" in relation to the reader apps being blocked.

Your assumption is right, that’s what I was hinting at. I might be wrong but I strongly suspect this is all intentional.

> Anyone got more context on what the "missing" page was?

I don’t know exactly, I assume some sort of landing page with links to your aforementioned resources.

EDIT: Here’s the Web Archive link:

https://web.archive.org/web/20221119170753/https://developer...

Honestly... I just don't have time for social media and already spend way too much time in front of a screen anyways.

Bold of you to assume Elon Musk would be able to use ssh.

> Possible method 1: Data attributes. Any time you as an author want to add additional data to an element, you are free to invent any custom attribute names you want, so long as they begin with "data-".

From the linked docs:

> It's worth mentioning that, if you prefer, you can use the data- prefix when using htmx:

    <a data-hx-post="/click">Click Me!</a>

I find it irritating, but I can see your point.

> This.

You're not on Reddit, pal.

That’s a good one.

I didn't pick it, that's how the layout works out of the box. I agree that :a would be probably more convenient.

I do you enable the third layer? I don't have a menu button on my Mac.

I am on macOS as well and the diacritics I mentioned ("a → ä, `a → à) work out of the box with the "US International PC" layout. If I press ⌥a I get å with my layout.

> Though I prefer the X11 compose sequence business where you type <Compose>'a to get á and so on. X11 compose sequences are a lot more intuitive than the Windows U.S. international keyboard because there's no ambiguities, so, for example, a cedille is just <Compose>,c whereas in the Windows U.S. international keyboard layout it's 'c

That sounds pretty good indeed. Any idea how could I go about setting this up under macOS?

> Also, if you program or use a shell, then the Windows U.S. international keyboard layout is just unspeakably unbearable.

I have indeed a couple of little, weird problems when working in the terminal. That's inconvenient but still beats switching between 3 layouts 50 times a day.

You are correct. It works for me.

That would be… inconvenient. That’s not how I use it. I type "a to get ä and 'a to get à. If I want to type actual quotes followed by a vocal I need to “confirm” the quotes with space before typing the vocal.

As multilingual user constantly switching between 3 languages, that's why I fully committed to the US_intl keyboard layout a while ago and ditched the abomination that is QWERTZ. Took a while to get used to, but overall it has been a very noticeable improvement. One layout to cover all languages, no more constant switching.

Edit for clarity: I type "a to get ä and 'a to get à. If I want to type actual quotes followed by a vocal I need to “confirm” the quotes with space before typing the vocal. That’s all there is to it, really.

The perfect response. Thanks for your comment :)

Afraid literally nobody cares anymore. Too late.

We wish too!

For what it's worth, I'm an HN user and hold Drew and his work in very high regard.

The focus on just one platform is the best selling point for me. I love 100% native Mac apps.

From what I understand Jobs was probably fine with using the Apple logo on the physical key, the problem was rather displaying the logo everywhere in the menus, where the shortcuts are displayed. That would have been way too much indeed.

> Also as per the spec the `-` operand requires a whitespace

Thanks, my bad. I fixed the title.

If only. An old phone number of mine is still somehow tied to my Google account. I can’t for the life of me figure out how to remove it. Google sometimes randomly decides to send the access code to my old number, which I no longer have, instead of using the new one. The only solution when that happens is to try the login again from an incognito window, hoping the Google decides to use the right number. Getting locked out someday is a very real possibility for me.

> People who use screen readers would probably be very supportive of plain text Web sites.

I beg to disagree. Plain text doesn't offer any support for embedded metadata, which are vital for screen readers. With just plain text you have no way to tell apart a header, footer or aside from the main content.

> Web devs usually do a lot of work to make a Web site accessible.

Yes, they do a lot of work. Mostly using semantic HTML and embedding text descriptions in data attributes.

This should go without saying: Plain text is less accessible than well written, semantic HTML, not more.