1
0
Fork 0
mirror of https://git.sr.ht/~seirdy/seirdy.one synced 2024-11-10 00:12:09 +00:00

Fix some HTTP urls

This commit is contained in:
Rohan Kumar 2024-04-24 16:02:40 -04:00
parent a2545d9e33
commit b8237d8b52
No known key found for this signature in database
GPG key ID: 1E892DB2A5F84479
4 changed files with 6 additions and 4 deletions

View file

@ -1,6 +1,7 @@
--- ---
title: "Real name policies" title: "Real name policies"
date: 2023-10-31T06:31:21-07:00 date: 2023-10-31T06:31:21-07:00
lastmod: 2023-10-31T18:11:51Z
replyURI: "https://fosstodon.org/@drewdevault/111329549329662520" replyURI: "https://fosstodon.org/@drewdevault/111329549329662520"
replyTitle: "Send me your thoughts on “real name” policies in free software contributions" replyTitle: "Send me your thoughts on “real name” policies in free software contributions"
replyType: "SocialMediaPosting" replyType: "SocialMediaPosting"
@ -19,5 +20,5 @@ The primary, hopefully-unintended function of a "real-name policy" is to exclude
There's plural systems. And trans users who haven't made a full break from their deadname(s) yet. And at-risk users who would be doxed by such a policy. And folks who simply feel more comfortable with online handles than meatspace names, for no special reason in particular. There's plural systems. And trans users who haven't made a full break from their deadname(s) yet. And at-risk users who would be doxed by such a policy. And folks who simply feel more comfortable with online handles than meatspace names, for no special reason in particular.
What incredible benefits could be worth shafting all these people? Assuming you even manage to pull it off; see {{<mention-work itemtype="TechArticle">}}{{<cited-work name="Falsehoods Programmers Believe About Names" url="http://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names" extraName="headline">}} by {{<indieweb-person first-name="Patrick" last-name="McKenzie" url="https://www.kalzumeus.com/" itemprop="author">}}{{</mention-work>}}. What incredible benefits could be worth shafting all these people? Assuming you even manage to pull it off; see {{<mention-work itemtype="TechArticle">}}{{<cited-work name="Falsehoods Programmers Believe About Names" url="https://www.kalzumeus.com/2010/06/17/falsehoods-programmers-believe-about-names/" extraName="headline">}} by {{<indieweb-person first-name="Patrick" last-name="McKenzie" url="https://www.kalzumeus.com/" itemprop="author">}}{{</mention-work>}}.

View file

@ -138,7 +138,7 @@ These considerations are far more subjective, debatable, and deserving of skepti
8. Dont conflate CLIs and TUIs. A CLI should be non-interactive; a TUI should be interactive. Exceptions exist for really simple interfaces (e.g. Magic-Wormhole and others like it) that accept user input; however, as the interface grows more complex, consider splitting the program into two sibling programs, one of which can have a “pure” non-interactive CLI. 8. Dont conflate CLIs and TUIs. A CLI should be non-interactive; a TUI should be interactive. Exceptions exist for really simple interfaces (e.g. Magic-Wormhole and others like it) that accept user input; however, as the interface grows more complex, consider splitting the program into two sibling programs, one of which can have a “pure” non-interactive CLI.
9. Go above and beyond by writing separate integrations for environments like Emacspeak.[9] 9. Go above and beyond by writing separate integrations for environments like Emacspeak.[9]
=> http://emacspeak.sourceforge.net/ Emacspeak homepage => https://github.com/tvraman/emacspeak Emacspeak homepage
## Name conflicts ## Name conflicts

View file

@ -162,7 +162,7 @@ These considerations are far more subjective, debatable, and deserving of skepti
8. Don't conflate CLIs and TUIs. A CLI should be non-interactive; a TUI should be interactive. Exceptions exist for really simple interfaces (e.g. Magic-Wormhole and others like it) that accept user input; however, as the interface grows more complex, consider splitting the program into two sibling programs, one of which can have a "pure" non-interactive CLI. 8. Don't conflate CLIs and TUIs. A CLI should be non-interactive; a TUI should be interactive. Exceptions exist for really simple interfaces (e.g. Magic-Wormhole and others like it) that accept user input; however, as the interface grows more complex, consider splitting the program into two sibling programs, one of which can have a "pure" non-interactive CLI.
9. Go above and beyond by writing separate integrations for environments like [Emacspeak](http://emacspeak.sourceforge.net/).[^9] 9. Go above and beyond by writing separate integrations for environments like [Emacspeak](https://github.com/tvraman/emacspeak).[^9]
Name conflicts Name conflicts
-------------- --------------

View file

@ -2,6 +2,7 @@
title: "Proposal: an HTML element for spoilers" title: "Proposal: an HTML element for spoilers"
description: "An informal proposal for dedicated elements for spoiler tags in HTML: use-cases, syntax, semantics, recommended UA behavior, and comparisons with “details”" description: "An informal proposal for dedicated elements for spoiler tags in HTML: use-cases, syntax, semantics, recommended UA behavior, and comparisons with “details”"
date: 2023-11-12T13:48:00-08:00 date: 2023-11-12T13:48:00-08:00
lastmod: 2023-11-29T13:09:39Z
outputs: outputs:
- html - html
- gemtext - gemtext
@ -11,7 +12,7 @@ syndicatedCopies:
- title: 'Lobsters' - title: 'Lobsters'
url: 'https://lobste.rs/s/v1yooo/proposal_html_element_for_spoilers' url: 'https://lobste.rs/s/v1yooo/proposal_html_element_for_spoilers'
- title: 'WICG Discourse' - title: 'WICG Discourse'
url: 'http://discourse.wicg.io/t/standardized-spoiler-tag/5814/15?u=seirdy' url: 'https://discourse.wicg.io/t/standardized-spoiler-tag/5814/15?u=seirdy'
- title: 'IndieNews' - title: 'IndieNews'
url: 'https://news.indieweb.org/en' url: 'https://news.indieweb.org/en'
- title: 'jstpst' - title: 'jstpst'