I write code.
For sourcehut support, see the wiki.
REPORTED RESOLVED IMPLEMENTED
We could write the blob to stdin, perhaps.
Hm, I thought I already explained something similar and closed this ticket. Apparently not. Thanks ~nabijaczleweli!
REPORTED RESOLVED INVALID
REPORTED RESOLVED FIXED
Came across this thread and thought I would do another round of addressing feedback from it after more months of ongoing sr.ht improvements.
"SH is still an alpha" is not a particularly good argument for using it in the first place, to be honest. Things tend to break, even Github has outages.
SourceHut has dramatically better uptime in 2020 than GitHub does.
There's no preview or edit on issue/todo comments
There are now.
A "project" isn't really a project, it's a loose collection of informally affiliated webpages
The project hub now exists and addresses the interlinking problems brought up throughout this thread. Deeper hub integration is ongoing, such as CI for the lists, links back to the project hub from each resource (repo, tracker, etc), and so on.
Right now subscribing to tickets doesn't work without an account, but that's a bug and will be addressed during the alpha.
This works now.
the Go documentation website pkg.go.dev doesn't know about sourcehut
It does now, but only for the main sourcehut instance (i.e. this one, sr.ht).
This thread has been a great source of feedback, thanks :)
I don't like this for a number of reasons.
- "The SMTP service will only accept mail that goes to a sr.ht service; It won't even allow CC or BCC outside sr.ht." kind of defeats the purpose of decentralization that sr.ht pushes for.
- If we ditch that, then we are operating a general purpose mail server, which is ripe for abuse and is a bigger question than this feature demands.
- Git is open source and a highly reputable project and can be trusted with your email credentials.
- The patchset preparation UI and other more specialized forms of letting sr.ht send emails for you are proving to be a better approach to this problem.
REPORTED RESOLVED WONT_FIX
Space to scroll a full page
^u/^d to scroll a half page
Right now, if someone asks what Markdown rules sr.ht uses, there's a standard we can point to. And if sr.ht's behavior does not match that standard, sr.ht can be corrected. This is desirable. If we add extensions without standardizing them, then (1) others can't create compatible implementations and (2) our implementation is poorly understood.