~spacekookie

Berlin | Edinburgh

https://spacekookie.de

Mediocre programmer extraordinaire [she/her] 🏴 Compilers are your friends. Sometimes I type things into computers to make them sad. I also do Rust things. Books are my drugs 📚

Feel free to send me patches to my public inbox or open issues to any of my projects on the meta tracker!

555F 2E4B 6F87 F91A 4110 669E 9073 4A9E 619C 8A6C

Trackers

~spacekookie/meta

Last active a month ago

#103 Anonymous users can't do most write activities a month ago

Comment by ~spacekookie on ~sircmpwn/todo.sr.ht

While I do like the idea of e-mail issue reporting, I do think that anonymous tickets are important too. Considering how easy it's to create an account, I don't think that just letting anyone post an issue is really that much worse when it comes to spam.

#123 Optionally remove namespaces a month ago

Ticket created by ~spacekookie on ~sircmpwn/meta.sr.ht

For projects hosting their own sourcehut it would be really useful to disable namespaces to get rid of redundant elements in the path (i.e. git.project.net/project/repo) and instead putting everything in the root namespace (git.project.net/repo)

#121 Deleting accouns 2 months ago

Ticket created by ~spacekookie on ~sircmpwn/meta.sr.ht

It should be possible to delete accounts

#31 Mirroring repos to other remotes (e.g. GitHub) 2 months ago

Comment by ~spacekookie on ~sircmpwn/dispatch.sr.ht

Why did you mark this as wont_fix ~pwr?

#222 Display repository language statistics 2 months ago

Ticket created by ~spacekookie on ~sircmpwn/git.sr.ht

This is a bit of a fluff feature, but something I do actually enjoy a lot from Github and Gitlab is an indicator of the percentage of languages in a repository indicated by a colourful bar somewhere.

I'm wondering if this is something you'd be interested in adding in the future

#31 Mirroring repos to other remotes (e.g. GitHub) 2 months ago

Comment by ~spacekookie on ~sircmpwn/dispatch.sr.ht

I'm wondering if this could be implemented via the webhooks feature. At least looking at the docs, you can get webhooks for repo update events (such as push, etc).

However the workflow feels a bit clumsy, having to first create an API key or authorising an application to access the events.

So I guess implementing this task by listening to events internally is probably a better solution.

I'd be curious in helping implement this. I haven't looked to extensively at the core source code yet so I don't know how I'd get access to an event listener in a dispatch task. Any help there would be appreciated.