Warsaw, Poland
Realist, pragmatist, strong-willed, strong-minded. Sometimes taciturn, sometimes loquacious. FLOSS enthusiast but still using Windows. Alpine Linux advocator.
Comment by ~przemoc on ~sircmpwn/scdoc
I missed the
++
in the last code block, of course.
Ticket created by ~przemoc on ~sircmpwn/scdoc
Right now:
- Item 1++ Where am I rendered?
is rendered as:
- Item 1 Where am I rendered?
To achieve proper rendering, one has to write it as:
- Item 1 Where am I rendered?
which is counter-intuitive.
Comment by ~przemoc on ~sircmpwn/scdoc
That would be nice to have indeed.
Ticket created by ~przemoc on ~sircmpwn/paste.sr.ht
Pastes can be created with optional filenames, so it would be convenient to be able to easily download such files with name preserved, instead of having to go to raw, saving it as, etc.
In case of multiple files, also tar archive could be provided to easily download whole paste.
Ticket created by ~przemoc on ~sircmpwn/git.sr.ht
It seems that browsing log page of git.sr.ht page is a one-way ticket.
There is no Back button when you visit non-first page. Is it expected that user has to use browser's built-in history?
It would be also nice to have First (or Newest) and Last (or Oldest) buttons, to easily navigate to the most recent and the least recent history respectively.
Ticket created by ~przemoc on ~sircmpwn/sr.ht
I used them in https://todo.sr.ht/~sircmpwn/sr.ht/194 but there are no expected line breaks.
Ticket created by ~przemoc on ~sircmpwn/sr.ht
It's nice to have project/topic-specific short links that are also editable (fixable) if target URL needs to be changed. Usually that kind of services keep also hit count, so you can see how often particular links are used.
Value of such links is that their name can be meaningful, thus easier to memorize, use, and thanks to their non-permanent nature, future proof.
Such project gotos should be importable and exportable. They could be internally stored in some easy to parse text file in git, so it would be easy to track changes in it and update in some more automatic way via git push for instance.
#Usage examples
#Threads in mailing lists can have very long URLs
"What's cooking on Sourcehut? April 2019" can be found in:
https://lists.sr.ht/~sircmpwn/sr.ht-announce/%3C20190415195704.GA21443%40homura.localdomain%3EThat kind of messages could be reachable via links like:
https://goto.sr.ht/~sircmpwn/sr.ht/201904#External resources that could be moved in future
Ticket created by ~przemoc on ~sircmpwn/paste.sr.ht
Please also consider harder URLs than gist.github.com uses for such secret entries. They use some 128-bit id/hash that is represented as hex string (32 chars). I think it's better to has longer id/hash and at the same time represented less wastefully. For instance 160-bit id/hash represented as base64url will take only 27 chars. (Personally I wouldn't go below 256-bit in this day and age.)
Ticket created by ~przemoc on ~sircmpwn/meta.sr.ht
I logged into sourcehut using two different browsers, yet I see only one entry in Audit Log. Browser's User-Agent should be also shown there.
Ticket created by ~przemoc on ~sircmpwn/lists.sr.ht
Patches in mailing lists can make non-patch mails buried down in thread list (depending on ratio between them). And vice versa (at least theoretically). Therefore it can be useful to be able to have a list of mail threads without patches. Or with patches only.