Marius, et al.,

thanks.  i *definitely* managed to miss.

good luck to Drew and the rest.

cheers, Greg

hi.  i am seeing odd behavior resolving sr.ht.

i.e.,
----
bash: {3165} host sr.ht
sr.ht has address 173.195.146.133
sr.ht mail is handled by 1 mail-b.sr.ht.
bash: {3166} host sr.ht
sr.ht has address 173.195.146.133
sr.ht has IPv6 address 2606:4700:3036::6815:273d
sr.ht has IPv6 address 2606:4700:3033::ac43:a9b5
sr.ht mail is handled by 1 _dc-mx.ff02c5b93c6b.sr.ht.
bash: {3167} host sr.ht
sr.ht has address 172.67.169.181

Matěj Cepl <mcepl@cepl.eu> wrote:

> The true men (and women) use `pass(1)` (from
> https://www.passwordstore.org/) and its plugin `pass-otp` from
> https://github.com/tadfisher/pass-otp.
> 
> And there is an application on F-Droid which works with this data
> https://f-droid.org/packages/dev.msfjarvis.aps/.

and an application on IOS as well:
https://github.com/mssun/passforios

cheers, Greg

in case it's of any use, i have this code (in my case, i use it to
provide passwords to msmtp):
----
https://git.sr.ht/~minshall/credeface
----

can i suggest that this message (when creating a project):
----
Tags must start with alphanumerics or underscores and may additionally
include dots and dashes
----
maybe have something like the following appended?
----
(multiple tags are separated by commas)
----

cheers, Greg
----
on page: https://sr.ht/projects/create, when i enter "foo bar" as the
tags.

Caleb,

> I forgot to mention: when viewing the thread in a mail client, it
> connects the chain just fine. This leads be to believe that it's a bug
> with Sourcehut and not a mistake in how the email is being sent.

some mail clients use different heuristics for "threading" messages when
displaying them.

  maybe the "spec" way involes the use of one or more of "In-reply-to:",
"References:", and "Comments:", but i think some mail clients will
(also?) use, e.g., "Subject:" (and variations thereof).

cheers, Greg

just fyi, this is reported fixed in a *very* recent mistletoe:

https://github.com/miyuchina/mistletoe/issues/138

cheers.

Drew and jman,

thanks.  i filed
----
https://github.com/miyuchina/mistletoe/issues/138
----

the pointer to https://spec.commonmark.org/dingus/ was very useful,
thanks.

cheers, Greg

hi.  i have a markdown README.md document (1) that includes a list like:
----
-   **`manpages:`, `manhtmls:`:** building the ...

-   **`readme:`:** building `README.md` ...

-   **`check:`:** to run the unit tests, requires ...
----

rendered into .html, the "**"'s are retained, rather than forcing "bold"
(because of the embedded back ticks?).

i'm not a markdown expert, but (2) -- if that is a valid source of
"authenticity" -- seems to render these as bold.

Moritz,

> I think it might be hard to do with commit hashes as the todos are not
> directly connected to the repositories. The hub may know of the
> relationship between the repo and the tracker, but that does not apply
> to todo.

ah, thanks.  i can see how such a facility might likely require a
binding between a tracker and a repository.