gopass has an audit feature.

  Detected a shared secret for:

  Password is empty or all whitespace:

  Password is mangled, but too common / from a dictionary:

  Password is too short:

  Password is too systematic:

Not sure, as I’ve never used Pass. However, if it has an export feature, you could do that and pivot the data in something like Excel.

Oh, that’s a good point, I hadn’t considered that people would interpret the title as a Bitwarden code review. You’re absolutely right, it is misleading so I’ve updated the title, thank you for the feedback.

Little more manual, but not by much and still the same result. Nice work and thanks for sharing as a I know A LOT of people use KeePass, myself included (for work).

I don’t even understand why there was article written for this…It’s so obvious to anyone with any basic HTML understanding.

Apoarently “#top” or just “#” not only works (I remember #top from… The early days. Netscape 4.x?) - but it’s in the standard:

“Note: You can use href=”#top” or the empty fragment (href=”#”) to link to the top of the current page, as defined in the HTML specification.”

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a

Where the spec is… I’d say more than a little obtuse: https://html.spec.whatwg.org/multipage/browsing-the-web.html#scroll-to-the-fragment-identifier

Ed2: not sure why the author felt a need to define a html4 style named anchor for #top..

Ed: Also TIL: in HTML5 linking directly to an ID is preferred over an explicit named anchor.

According to whatwg and MDN this is the preferred method

Problem with that is it would take you to the title of the page, which isn’t necessarily the top of the page.

Interesting. I tested it with Brave (also based on Chromium) and it worked.

This is literally plain HTML. If something is magical here, it is the usage of javascript to emulate a behavior that has been standard in the web since the nineties.

I gave up on the back button roughly a decade ago.

I wanted to ask you what kind of browser would do such a silly thing, but apparently that’s (also?) what Firefox does: fragments do get added to history, and all the “back” button does is dropping the fragment.

I still find it peculiar that there’s even a need for such button (on PC I have a Home button, and on mobile providing one should be the browser’s job imo), but seems like there is a good reason why people use JS for this after all.

Hmmm that’s a good point, and not something I had considered. Thanks for the feedback.

Do you know if 20.04 removed the tear free option?

https://wiki.archlinux.org/index.php/intel_graphics#Tearing

I’m using this in Xubuntu 19.10 without any issues but I have not upgraded yet.

I can’t say I’ve noticed any screen tearing on my machine.

Ah, nice to see that I’m not alone with my distaste for the Ubuntu font. :-)

Yes, and the big userbase means that it is supported by third parties like nvidia for cuda!

For things like email, I cannot accept anything other than 99.999999…% up time.

E-mail was specifically designed to function in environments with like a 0.01% uptime. That’s why smtp has batching, relaying, and retrying in the specification - it was designed in the days of dial-up only connecting every now and then. Sometimes they come a couple hours late if you have an outrage, but they still come.

Imagine missing a critical email related to your bank account because this vendor restarted the mail servers during maintenance. “Sorry for the inconvenience” doesn’t cut it in this case.

The protocol was designed to be resilient to these kinds of faults. A compliant sending server will retry.

99.999999%

Are you sure even gmail commit to 8-nines service availability? Even to paying customers?

Here’s some interesting reading to soothe your mail anxiety:

RFC 5321: SMTP

…and specifically the part on retry strategies starting at page 66.

Email is, or used to be, defined by a relatively straight-forward set of RFC’s which sketched a fault-tolerant asynchronous store-and-forward system for moving textual content from one mailbox to another. The ‘straight-forwardness’ has been muddled by the addition of several access-control related facilities to deal with unsolicited mail, the ‘textual content’ has been replaced by HMTL and mime but the core protocols still stand.

Imagine missing a critical email related to your bank account because this vendor restarted the mail servers during maintenance. “Sorry for the inconvenience” doesn’t cut it in this case.

If a mail server isn’t available it should retry, or the sender will get a bounce back informing them delivery failed. It won’t just disappear into the ether.

For a dev it might be. I tried to find a solution that is simpler to setup and optionally useful for friends of mine

It’s good to minify html as well

Unless the ratio of markup to content is wildly skewed to the former, this doesn’t buy you much but does come with a pile of disadvantages.

I assume because the optimisations I have in Wordpress include minification.

Thanks, I’ll take a look at that.

I find that surprising given the usually privacy-conscious HN crowd. Maybe they are a small, but relatively vocal minority.

Yup, I thought so too.

Appreciate the validity check, will be very handy.

ad 2) I’m not sure if it’s my feed readers, but I have the impression I am not missing posts, so I don’t think that’s necessarily a good idea to limit it.

You can, but like anything dynamic, you’d either need to implement the comments section in client-side JavaScript or else have some way of triggering your site to rebuild and redeploy whenever a new Webmention is posted.

I’m doing that. My site is SSG that is built on my desktop and uploaded via good old rsync.

I use this webmentions SaaS to collect my mentions and a client-side JS to fetch and display them. My design skills are limited, so you can have it looking much better than I did. This post has a lot of mentions at the end. The JS used is not minified and is at the end of the post, near line 152 if you want to check.

Another cool service is bridgy which will send and collect mentions from silos and forward to your web site. I have it configured with my twitter and mastodon account. This way, I can have it send automatic tweets or toots when I post and also deliver replies and comments back to the original post.

Yes, it’s possible with a dynamic webmention endpoint that somehow saves webmentions. I have such a dynamic endpoint that creates a file in a git repo, commits and pushes it. That triggers a pipeline to rebuild my blog with Hugo and then a link is displayed below the page which received the webmention.

I have done it on my static website using webmention.io. I just pull on my personal computer regularly the updates from webmention.io and then I generates the comment section using some Hugo features. Shameless plug to my blog post explaining this

There’s https://webmention.io/ or you can have a self-hosted service somewhere.

I believe so. I know a couple of people who are running Hugo and have this. However, I would assume that that the comments are updated only when the site is regenerates, rather than on-the-fly like WP.

Thanks! :-)

Pretty much, yeah. I cache my site and use a CDN. That’s what makes its performance comparable to an SSG.

I suppose the advantages are that an SSG wouldn’t have to set that up in the first place, but once done, the writing process is much easier (I think) with WP.

That’s very true actually. I don’t play around in the CMS that much, but it can be a distraction.

Based on previous discussions here about SSGs, around 70% of the time is spend developing and tweaking the software, and the rest is for content.

(BTW this mirrored my own experiences back when I bothered to tweak my blog).