Seirdy

Joined 9 years ago

Karma
1,512
Submissions
539
Member since
Oct 13
Website and blog: https://seirdy.one

I've reduced my use of HN. I mostly interact with HN to collect and respond to feedback, correct misinfo, and ask questions.

[Verifying my OpenPGP key: openpgp4fpr:AC6AF1F838DF3DCC2E47A6CF1E892DB2A5F84479]

View on Hacker News

Recent submissions

Comment · 2 years ago
Said people are trusting the intel from the AI. Those who provide that intel possible should shoulder responsibility for its effects, or at least its efficacy.
Comment · 2 years ago
Shortly after you posted this, it looks like their TLS certs expired. Checking my TLS-RPT bundles reveals 5 failures in the last couple days from Google.
Comment · 3 years ago
Correction: this was not a case of accidental misgendering. The post refers to someone abusing mod privileges to edit someone's pronouns to "who/cares".
Comment · 3 years ago
It's a very common Markdown extension supported by PHP-Markdown-Extra, Goldmark, Pandoc, Kramdown, and dozens of others. Several of these have supported it for almost ten years now, with the same syntax.

PHP-Markdown-Extra is the closest thing to a standard with more than GitHub-Flavored-Markdown; several other Markdown engines use its featureset as a baseline for compatibility for anything not present in GFM, even blocking the shipping of new features until after PME agrees on a syntax. So you can think of CommonMark as the lowest common denominator, GFM for an intermediate version, and PHP-Markdown-Extra as something suitable for building more advanced websites.

Comment · 3 years ago
Goldmark (Hugo) and many Markdown extensions do support description lists. Hugo also supports render hooks which make adding support for attributes, picture elements, etc trivial. And the vast majority of advanced markdown engines support a front matter, typically YAML although Hugo supports TOML and JSON as well.
Comment · 3 years ago
https://seirdy.one/

I'm trying to adopt as much IndieWeb as I can while still remaining a static JS-free site (except for the crappy search results page). Comments are Webmentions.

I test compatibility with a lot more than just mainstream browsers: the Tor Browser's safest mode, various article extractors, NetSurf, Ladybird, w3m, and a dozen other user-agents work well. Accessibility-wise, I'm close to WCAG 2.2 AAA compliance, and have already passed AA; I consider WCAG a starting rather than a stopping point. More on its design is in the "Meta" section.

It has long-form blog articles and short-form notes (microblogs).

My best posts are on the homepage, followed by a bunch of webrings.

Comment · 3 years ago
Gleason is an influential member of the fediverse because of Soapbox. Soapbox adoption generally makes him more relevant and more popular. This clout amplifies his transmisiac message.

It's similar to JK Rowling getting famous off the Harry Potter franchise and using that clout in a way that causes harm, prompting others to stop promoting her works and thus stop feeding her positive attention. Having read one of those books or having watched one of her movies doesn't make you a transophobe, but promoting her works gives her the means to do harm.

Moreover, the majority of soapbox instances tend to be freeze peach servers that either contain or amplify other harassers. Good soapbox instances tend to be the exception rather than the norm.

Comment · 3 years ago
The devs are especially interested in a distribution of musl with hardened_malloc integrated for easy static linking.

Until then, LD_PRELOAD is your friend (assuming you build with semantic interposition).

Comment · 4 years ago
QUIC does not require a CA. Self-signed or DANE-backed TLS certificates work fine. Try using cURL built with HTTP/3 support to see for yourself.

Requiring CAs and not implementing support for other anchors of trust is an implementation decision, and is not mandated by the spec. The spec mandates TLS 1.3, not "the version of TLS 1.3 used by these three web browsers". QUIC was designed with non-browser use in mind too; it's for any situation where you want to maintain connection integrity in an unreliable network.

Comment · 4 years ago
Many worried about what Twitter's changes would mean for under-represented groups. Given this news and Twitter also cutting its accessibility department, I think we can see their new attitude towards minorities isn't particularly friendly.
Comment · 4 years ago
How's the accessibility of these interfaces? I believe you mentioned an intent to target the Web some time ago, implying that Web interfaces could expose semantics to assistive technologies. Is this still on the roadmap?
Comment · 4 years ago
Nor can I. That's why progressive enhancement is common sense: it's way less effort, less complexity, and easier to make accessible.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton