~muirrum

https://devosmium.xyz

High School Senior. Aspiring Sysadmin. Eagle Scout

My code may not be good, but it (mostly) works

~muirrum/hackagotchi-devel

Last active 4 months ago

~muirrum/hackagotchi-announce

Last active 4 months ago

~muirrum/fll-scoring-announce

Last active 4 months ago

~muirrum/fll-scoring-devel

Last active 4 months ago

~muirrum/public-inbox

Last active 5 months ago

~muirrum/campmaster-constantine-announce

Last active 5 months ago

~muirrum/campmaster-constantine-devel

Last active 5 months ago
View more

Recent activity

Re: Copying labels between trackers 16 days ago

From Owen Salter to ~sircmpwn/sr.ht-discuss

On Thu, 2020-10-01 at 03:14 +0000, Noam Preil wrote: 
> 
> Perhaps it would also be good to have some sane optional defaults? Or
> at 
> least a way to conveniently import them.
+1 on this, i think some good defaualts might be "bug" and "feature".

Cheers,
Owen

Re: How can we make the project hub more accessible? 29 days ago

From Owen Salter to ~sircmpwn/sr.ht-discuss

On Tuesday, September 22, 2020 2:57:51 PM EDT Pedro Lucas Porcellis wrote:
> Maybe simply enforce that on the project creation process?
> 
> Instead of a tiny dismiss button, replacing that with a Publish Project
> button; Instead of a "new project checklist" expand that into a more
> "onboard-like experience", guiding people on how to do the process, etc.
I like this idea. I think making it clearer that completing/dismissing the 
checklist will make the project discoverable would be an improvement.

-- 
Best,
Owen Salter

Re: How can we make the project hub more accessible? 29 days ago

From Owen Salter to ~sircmpwn/sr.ht-discuss

On Tuesday, September 22, 2020 1:26:11 PM EDT Robin Krahl wrote:
> Part of the problem might be that there is no indication whether a Git
> repository is part of a project when visiting the repository.  If there
> were links to the project and maybe the associated trackers and mailing
> lists, it would be easier to notice the difference and it would be an
> incentive to create projects (to make it easier to navigate).
I think that just having project components link back to the project home 
would be a step in the right direction.

-- 
Best,
Owen Salter

Fwd: Re: Pinning repositories 30 days ago

From Owen Salter to ~sircmpwn/sr.ht-discuss

On Sunday, September 20, 2020 6:53:54 PM EDT Brett Gilio wrote:
> Other forges seem to support pinning repositories on account pages, as well
> as in project hubs. This may be useful especially in hub.sr.ht where
> there is a specific repository which may be considered "primary". For
> example, in orcircd[0] I have several component repositories, several of
> them being auxillary and one of them being an RFC implementation
> subproject. It would be beneficial if I could "pin" the primary
> ~brettgilio/orcircd git repository to the top of this listing.
I like this idea, it would be very useful to me to be able to designate which 
repository is the "main" repository.
> 
> In theory this could perhaps be based on which project is selected as
> the README source, or could be independent of that customization (in
> cases where multiple repositories could appropriately be pinned).

Re: Pinning repositories a month ago

From Owen Salter to ~sircmpwn/aerc

On Sunday, September 20, 2020 6:53:54 PM EDT Brett Gilio wrote:
> Other forges seem to support pinning repositories on account pages, as well
> as in project hubs. This may be useful especially in hub.sr.ht where
> there is a specific repository which may be considered "primary". For
> example, in orcircd[0] I have several component repositories, several of
> them being auxillary and one of them being an RFC implementation
> subproject. It would be beneficial if I could "pin" the primary
> ~brettgilio/orcircd git repository to the top of this listing.
I like this idea, it would be very useful to me to be able to designate which 
repository is the "main" repository.
> 
> In theory this could perhaps be based on which project is selected as
> the README source, or could be independent of that customization (in
> cases where multiple repositories could appropriately be pinned).

[PATCH sr.ht-docs] Fix OAuth documentation link 3 months ago

From Owen Salter to ~sircmpwn/sr.ht-dev

---
 api-conventions.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/api-conventions.md b/api-conventions.md
index eb5e6be..f505bd1 100644
--- a/api-conventions.md
+++ b/api-conventions.md
@@ -19,7 +19,7 @@ share yours!
## Authentication

All services are authenticated with OAuth via meta.sr.ht. For more information,
consult [the meta.sr.ht OAuth documentation](meta.sr.ht/oauth-api.md).
consult [the meta.sr.ht OAuth documentation](/meta.sr.ht/oauth-api.md).
[message trimmed]

[PATCH] Fix pagination 3 months ago

From Owen Salter to ~tristan957/public-inbox

Small error caused the pagination to try to put the previous page's URL
where the next page's should be, causing an error generating the first
page.
---
 layouts/_default/list.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/layouts/_default/list.html b/layouts/_default/list.html
index 5800688..25d0a3e 100644
--- a/layouts/_default/list.html
+++ b/layouts/_default/list.html
@@ -23,7 +23,7 @@
					</a>
				{{ end }}
[message trimmed]

[PATCH meta.sr.ht] Fix spelling in validate password 4 months ago

From Owen Salter to ~sircmpwn/sr.ht-dev

---
 metasrht/blueprints/auth.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/metasrht/blueprints/auth.py b/metasrht/blueprints/auth.py
index df88fee..657435a 100644
--- a/metasrht/blueprints/auth.py
+++ b/metasrht/blueprints/auth.py
@@ -105,7 +105,7 @@ def validate_email(valid, email):

def validate_password(valid, password):
    valid.expect(len(password) <= 512,
            "Password must be between less than 512 characters.", "password")
            "Password must be less than 512 characters.", "password")
[message trimmed]

Re: Communication etiquette 5 months ago

From Owen Salter to ~sircmpwn/sr.ht-discuss

On 5/20/20 5:44 PM, Drew DeVault wrote:
> If harsh language scares cryptocurrency enthusiasts off of the platform,
> then the platform will be better for it. This is by design.  You're
> welcome.
> 
> Seriously, I have a zero tolerance policy for cryptocurrency garbage. I> will consider almost any feature in earnest, except for anything related
> to cryptocurrency. It is a disease and it has no place on this website
> or even on this planet.
I understand that, but I also think that it's not a good idea to be this
abrasive. This person was just trying to make a contribution in good
faith. They may have ideas beyond Brave that would benefit sr.ht, and
now won't submit them.
> 
> I acknowledge that I have been abrasive on other matters in the past,

Re: Communication etiquette 5 months ago

From Owen Salter to ~sircmpwn/sr.ht-discuss

On 5/20/20 5:39 PM, Sam Whited wrote:
> I know it's probably not a huge number of users so it may not weigh that
> heavily on your decision making, but I'd also like to second this. I've> had at least one person that I can't get using Sourcehut because they've
> seen several comments like this and are just worried that it will create
> a bigger cultural problem in the ecosystem going forward and that they
> won't be able to get proper support when things go wrong.
I agree. There's a right way to respond to people submitting tickets,
and it's not with swearing. I can start to understand if someone's being
persistently in bad faith, but this person seemed to genuinely want to
contribute, and didn't deserve the response.

~Owen