---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 2657baa..0a84e38 100644
--- a/README.md
+++ b/README.md
@@ -17,21 +17,21 @@ $ mkdir -p ${XDG_CONFIG_HOME:-"$HOME/.config"}/senpai
 $ cat <<EOF >${XDG_CONFIG_HOME:-"$HOME/.config"}/senpai/senpai.scfg
 address chat.sr.ht
 nickname senpai
-password "my password can't be this cute (2010)"
+password "my password can’t be this cute (2010)"
[message trimmed]

---
 README.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/README.md b/README.md
index 2369fdf..2657baa 100644
--- a/README.md
+++ b/README.md
@@ -12,16 +12,16 @@ senpai is an IRC client that works best with bouncers:
 
 ## How do I use this?
 
-```shell
-mkdir -p ~/.config/senpai
[message trimmed]

Sometimes I find myself in a situation where I want something more than the
built-in editor. For instance, if I need to write something longer or need special symbols, I would prefer to load up (Neo)Vim and get access to my spell checking, digraphs, all of the keybonds, etc. that are all much nicer in an actual editor. I can’t comment on the best experience on how to accomplish this, but the single-line editor quite simple.

-- 
toastal ไข่ดาว | https://toast.al
PGP: 7944 74b7 d236 dab9 c9ef  e7f9 5cce 6f14 66d4 7c9e

Let’s say I get some trash markup like

[source,html]
----
<div>
  <span><span class="useless">Hello</span></span>
</div>
----

What is the best way to remove the `.useless` element?

[source,html]
----
<div>

> I don't usually read code in the browser so this is less of a problem for me

I usually do though. When assessing a new library or executable, I’ll prefer to look over it in the browser. I can’t think of a time where I did a git checkout just to read the source or a tag’s commit messages to see the release notes. Language community tooling often points repos to read in this manner as well.

> Would be better if it was 'language' instead of 'srht-language' 

No opinion. GitLab prefixed their implementation so I can only assume there was a strong reason to do this, possibly as it's not standard.

-- 
toastal ไข่ดาว | https://toast.al
PGP: 7944 74b7 d236 dab9 c9ef  e7f9 5cce 6f14 66d4 7c9e

I’ve been wanting to show projects I’ve written off in a smaller progamming
language community. Currently it and its config file langauge are in a syntax
not supported by Pygments (which I believe is the highlighter, yes?). While
syntax highlighting isn’t the most important feature, it does affect the
perception of the platform. Specifically not having comments de-emphasized makes
it hard to read code.

I’ve added support to Highlight and helped adding it to Prism in the past, but
do not have the bandwidth or desire to help with Pygments. However, it seems
a bit restrictive to make all languages open a merge request with that project
to get support on Sourcehut–especially for new/toy languages. In my case being
able to tell Pygments to highlight as Haskell would give me good-enough results.

When I think about this space, I think of files with comments like:

https://news.ycombinator.com/item?id=28812863

If you have an comments or answers to questions, could likely help PR
-- 
toastal ไข่ดาว | https://toast.al
PGP: 7944 74b7 d236 dab9 c9ef  e7f9 5cce 6f14 66d4 7c9e

> open https://github.com/NixOS/nixpkgs/pull/134306[merge request] 

Merged!

Well I *do* have an open https://github.com/NixOS/nixpkgs/pull/134306[merge request] now. If you have any feedback, or want me to put it at Codeberg instead and yell at you if you forgot to push a new tag, I can be a manual tool if that is what you prefer. Currently it is pointing to the GitHub repo.

> I think I'd prefer it to be in the upstream Nix

Roger.

> GitHub

Sucks, but it’s not like I don’t understand. Nixpkgs is all done through GitHub. There’s been some attempts to *try* to get an alternative mailing list route going, but it kinda fizzled. Elm has tied all package management *AND* identity to GitHub. PureScript supports alternatives in theory, but no one seems to have a major package publish outside GitHub (this I hope to change this :fingers-crossed:, but I need to create something people _really_ want and I will sadly probably be responsible for fleshing out any current building issues). 

I feel like the it’s too difficult to do both. Buying in to the non-mailing-list route ends you in a GitHub clone situation like GitLab, Gitea, Codeberg, versus mailing-list-only Sourcehut, default repo. Most people are now accustomed (myself included, in hindsight regrettably, but a GUI *was* easier to learn when I was first picking up Git). I think because most people learned through GitHub back in its independenc and ‘cool’ phase, will default to “issues” and “pull requests”. A lot of projects have had some success on GitLab and a lot of the FOSS (like GPL FOSS) community _has_ moved (to gitlab.com or self-hosted) because of GitHub’s close-source, tracking-on existence and still get contributors used to that style and share philosphical views, but GitLab does certainly have its issues (as noted, beholden to VC investors that may turn when they want). At that point, it’s a political stance that is more personal than likely not affect change unless your project is too big and too important to fail (e.g. Linux kernel). I’m personally moving all of my stuff to GitLab and Sourcehut, but I’m also fond of the Haskell motto: avoid success at all costs ^_^

Commiserating rant aside, I know where your heart and head lie in looking for success and adoption. Cannot say I blame you, *but* you may want to update your website docs if this is the case.

* * *