Seirdy
Joined 9 years ago
Joined 9 years ago
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.
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.
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.
Until then, LD_PRELOAD is your friend (assuming you build with semantic interposition).
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.
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]