Realist, pragmatist, strong-willed, strong-minded. Sometimes taciturn, sometimes loquacious. FLOSS enthusiast but still using Windows. Alpine Linux advocator.
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.
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.
I used them in https://todo.sr.ht/~sircmpwn/sr.ht/194 but there are no expected line breaks.
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.
#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%3E
That 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
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.)
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.
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.
Atm various subsites have different length of name in navbar (sourcehut something), which makes links to other subsites have different position on different subsites. Having fixed width of name (be it todo, man or whatever is put after sourcehut) will improve UX.
Now that mails are not sent on behalf of user's e-mail account, firstname.lastname@example.org is too generic to be used in From: field.
it would be good to use something more informative, like:
I'd rather these show up in the global event log that will eventually end up on meta.sr.ht
If there will be global log, it could be simply filtered down to the repo in such tab.
There could also be an event log that shows up on git.sr.ht specific to git events, but global, not repo specific.
Sure, that's also an option, but I think subscriptions are more likely to happen based on repository. OTOH subscribing to someone's whole git.sr.ht should be also considered, at least for the sake of completeness.