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.
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.
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".
I am just trying to say that we should begin our conversations giving each other the benefit of the doubt, and then build mutual understanding through compassion and empathy. That is all.
That mod is likely an ill-intentioned guy and in violation of the Discord ToS, but starting every conversation by accusing others of being ill-intentioned is how we end achieving nothing as a society.
Punishment and an escalation of intolerance are not the goal, tolerance is. We are not going to heal the world one accusation or insult at a time.
When you are not a prejudiced person, a good starting point is to consider yourself fortunate in that respect, and then acknowledging others might not have been as fortunate as you.
Is there no self reflection in these communities? Everywhere they go is toxic and hateful. We're giving so much rope to protected groups that they will eventually hang everyone with it.
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.
So you have to pick your lock-in for a Markdown processor? Once you step outside of CommonMark, nothing is compatible. Compare that to AsciiDoc, reStructuredText, Org mode… these support metadata as a first-class feature (as you would expect from almost every other creative format: *.ogg, *.webm, *.odf, *.png, *.svg, *.html, etc.). Choosing such tools makes it a) harder to migrate to another tool & b) difficult/impossible for other tools to render it properly. You can skip that nonsense by just choosing a better format.
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.
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.
I love your blog. It's clear that you care as much about thinking and writing clearly as you do about your tech stack and readers' experience. I hop you continue to publish your ideas on the web. I always learn a lot from your posts.
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.
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.
True in theory, not true in practice. It might work if all the random people on the internet used cURL to visit my websites but they tend to use browsers that are Chrome based. And Chrome's QUIC (or the underlying quiche library) differs how Chrome's H1 and H2 implement TLS. It will not accept a self-signed cert during a HTTP3 QUIC connection. Even going localhost (defeats the point, but to check) and trying --disable_certificate_verification --allow-insecure-localhost will not work.
Like I said, the megacorps that designed QUIC designed it for their use cases and that does not include allowing human people to host websites by themselves. Not if it potentially impacts e-commerce security. Their implementations reflect this.
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.
Under-represented...where exactly? I'm interested in hearing which groups that you think are under-represented based on their percentage of the population.
The cold and disappointing truth is that the only institutions with the power to actually do something about human rights are all captured and steered to acquire wealth & power under the auspices of human rights & 'saving the earth'.
And yes, if you ask me, making whole swaths of populations more poor and less powerful is the same as increasing the power and wealth of this group of usurpers.
This is all possible because most people are good and support human rights because (to me, and us commenting) to do otherwise is ghoulish. So through social manipulation & constant reinforcement of what is good for human rights and telling the public who is doing all this good for humans is critical to grift I described above in the abstract.
So clearly, even though twitter human rights dept has little to no actual power to improve human rights, this department is critical to shaping the narrative to the public that the institutions who DO have power to help 'human rights' are actually doing so.
Look at the world today and you know in your heart things are getting worse but watch with a keen eye at how viciouly the levers of propaganda are fought for.
They did have quite a bit of power in situations where Twitter was being used for coordinated inauthentic behavior in regions where ethnic cleansing and genocide were under way.
Or it will be the end of the insane "approved visible minorities" privileges and the beginning of a system where no one is a special snowflake and everyone is treated equal.
Or even better:
More poor trailer-park-raised peomle in positions of power ! Economic class is the new race (spoiler: is always has been)
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?
That's definitely on the roadmap. I'd love it to also work in the terminal, but AFAIK terminal screen readers will just scrape the terminal. What we need is an API to interactive with.
