I'm surprised the title was so literal. I think what people really need is guidance on how to migrate away from the Google ecosystem in general before they actually need to go hunting for the "delete account" button.

Yet another extension that could as easily be and indeed already is a userscript.

Without a link to the userscript, your comment is not helpful.

Not quite what you asked for, but this is the bookmarklet I use:

  javascript:(() => { let v = window.location.href.split("/"); window.location = "https://www.youtube.com/watch?v=" + v[v.length - 1]; })();

There's a million ways to get any one thing done... You could modify the browser's source code (possibly more efficient), edit your Youtube settings, use an addon with custom redirect rules, stop using youtube, etc...

If you are maxing retirement funds you are not living paycheck to paycheck.

I know. I’m not saying I am. I’m just saying it feels similar, because I remember making a thousand dollars a month and having to do odd jobs to cover rent and food. I have the same urge now.

Look, I’m not looking for sympathy. I was honest about that. I’m just trying to add some color from my perspective to this article.

Do you reckon polarized glasses would have helped? Even if they're color graded or something, those photos are probably using polarized lenses.

There's no such thing as polarized lenses, only polarization filters. Also, Light from bioluminescence isn't polarized.

I assume the pictures taken for Wikipedia just had very long exposure times.

No - I think the photos just look like that because they use a long exposure time or high sensor sensitivity (high ISO)

I must say I am mildly amused that the author went to the effort to specify six SKUs based on size when the largest is only 10% larger than the smallest. And this approaches 0% as you add content to your wiki. But I always love seeing some blazing-fast web pages!

Slippery slope! If you don’t watch out, that thing could balloon to 74K, 75K in a matter of years. And then where would we all be?

Many birds and twitter :)

I think the creator(s) should just simplify to the one full download. It'll make support and releases easier, and I genuinely can't see any reason why someone would download the other releases: https://feather.wiki/?page=downloads

Here, I'll simplify the options:

- All features, transpiled

- All features, not transpiled

- No Markdown, transpiled

- No Markdown, not transpiled

- No WYSIWYG, transpiled

- No WYSIWYG, not transpiled

And the difference in gzipped size from the largest to the smallest size is... 2KB.

I could simplify it to one file, but then I wouldn't be able to think of fun bird names to go with the relative file sizes! ;)

A great point! :)

I thought so, too, but maybe the author got a bit carried away with the bird analogies and needed a reason to add more bird photos (which is totally understandable).

Exactly this. I wanted to see how small I could get it (Hummingbird) and then got obsessed with the idea of bird names for the build versions and just had fun with it :)

Be(e) Hummingbird!

The goal is making it smaller and smaller at the same time improving usability. It will never be like TiddlyWiki, it sort of complements TiddlyWiki. This project is very new. So I think there will be lot of improvement. Any willing hackers here can check this out and contribute code: https://codeberg.org/Alamantus/FeatherWiki and help make it smaller, faster, better

What does SKU mean in this context? I assume you mean metrics but not sure which acronym for SKU this is

Stock Keeping Unit - if I produce mugs, my SKUs might be MUG-001-BLK and MUG-001-BLU based on the colourway.

This is a metaphoric meaning, as software doesn't really need to be 'stocked', and just refers to the different configurations available.

Wouldn't that just lead to everyone going to the fields for 1 day and coming back for their check?

I already have a `q`, and frankly it's useful to me, so this piece of software will never be called `q` on any of my systems.

I suspect a lot of people have locked up all the single-letter aliases too, and I believe almost all of them would have the same position.

There's other tools for doing DNS diagnostics that are already installed on every system in the world. If I learn this one, I will have to take responsibility for maintaining the fact that I have to give it another name, and distribute that to other systems -- I won't be able to use this tool in a script, because I'll have to make sure the name is configurable for everyone else just like me.

Now I will not even give this software a chance because all of that seems so obvious to me, and the cuteness of the name such a display of fetishism (which usually detracts from quality in my experience) has me starting with an extremely low opinion and I haven't even made it to the github page yet. This software would have to be really good to overcome that. Is it?

I anticipate that being the big problem with choosing such a high-value single-letter name for something with such a narrow use-case. It just seems smarter to learn the tools that are already there. Heck, "c" can do everything and it doesn't even have the gall to do this; I think "cc" is a much better name, and whilst there are still a fair number of two-letter combinations that aren't used, I think I probably compile more C programs than do DNS diagnostics so maybe three or more letters would be better (if you buy the idea that huffman-coding your names is a good idea-- and I do)

Its probably pretty common to use q for one of those commands. It is also easy to accidentally enter an errant q into the shell.

Call it qdns?

IMHO, it should follow `jq`: `dnsq`: adjective noun

The duality of man[0].

https://news.ycombinator.com/item?id=30952583

Haven't AMD and Intel had to share all their patents with each other for the past 20 years anyway? I remember some agreement coming out of the ashes of the amd64 debacle. And the patent text doesn't seem to have anything to do with the images.

Only for x86 up until that point in time.