she/her
Computer Science student. Network Assistant. Eagle Scout
From Cara Salter to ~sircmpwn/sr.ht-discuss
On 7/3/24 04:04, Drew DeVault wrote:
> No, this is not currently possible.
Is this a planned feature?
From Cara Salter to ~sircmpwn/sr.ht-discuss
On 11/5/23 04:44, Coutinho de Souza wrote: > I was unable to find the constraints, i. e., memory size and cpu cores, > of the build VMs on the docs, be it by the wiki[1] or by looking through > the files directly[2]. > > The only mentions I've found were on the mailing list regarding people > who had out of memory problems[3][4]. I neither want to grow the memory > size nor the number of cpu cores; I just want to know how much they are, > so that I can adequate my projects to them -- e. g., limiting the number > of and the max allowed memory for `nix-eval-jobs`[5]. > > So I ask: > > 1. Is there already a place in which I can find both how much memory and
From Owen Salter to ~sircmpwn/sr.ht-discuss
On 2021-05-22 17:07, Chris McGowan wrote: > Judging from the logs you pasted, it looks like the authorized keys lookup to your meta instance failed to find a matching public key. > > Relevant lines: > >> 2021/05/22 21:18:16 non-200 response from meta.sr.ht: 404 >> 2021/05/22 21:18:16 Unknown public key > > Have you added it to your local account? > > Disclaimer: I'm not really familiar with sr.ht's internals so the above is a total guess. > > Note: apologies if this double sent. My mailer was apparently "upgrading" my mail to HTML by default. >
From Owen Salter to ~tristan957/public-inbox
Howdy, On 2021-04-08 02:16, Tristan Partin wrote: > Owen, > > I am so stupid! I never saw this email in my inbox. I have been > iterating on my website quite a bit recently, and finally got enough > blogs down to realize the mistake I made here. Ended up fixing other > pagination issues as well. No worries! I figured at some point you'd need the fix. > > I ended up finding your blog. Cool that your site looks a lot like > mine. I made quite a few changes around how it is configured, so if > you wanted to pull updates from the source html files, it should be
From Owen Salter to ~sircmpwn/sr.ht-dev
--- config.example.ini | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/config.example.ini b/config.example.ini index d166434..a356883 100644 --- a/config.example.ini +++ b/config.example.ini @@ -106,6 +106,11 @@ webhooks=redis://localhost:6379/1 # sr.ht instance so you probably want to patch these before enabling this. welcome-emails=no # # Origin URL for the API[message trimmed]
From Owen Salter to ~sircmpwn/sr.ht-discuss
On Mon, 2021-01-18 at 10:20 -0500, Drew DeVault wrote: > Try setting: > > [meta.sr.ht] > api-origin=http://localhost:5100 That worked! Want a patch for config.example.ini?
From Owen Salter to ~sircmpwn/sr.ht-discuss
On Sun, 2021-01-17 at 19:55 -0500, Robby Zambito wrote: > Specifically, the symptoms I am experiencing are: I can reach the > /query > publicly, and I recieve this response: {"message":"Authentication > error: > Authorization header is required. Expected 'Authorization: Bearer > \u003ctoken\u003e'"} > > And I am unable to reach my meta service. In the meta.sr.ht logs I am > seeing: > > [2021-01-17 19:55:26 -0500] [3037] [INFO] Booting worker with pid: > 3037 > [2021-01-17 19:55:56 -0500] [3022] [CRITICAL] WORKER TIMEOUT
From Owen Salter to ~sircmpwn/sr.ht-discuss
On Mon, 2020-12-14 at 13:38 +0000, aue oiae wrote: > this is actually a much bigger question... > > for one, on the somewhat analogous github, stars also help to give a > metric to projects. which, like most indexes, have a lot of confusion > added and might be mostly detrimental. Personally I like the fact that sourcehut doesn't have any of these crap gamification "metrics" that have plagued github. > > as for the actual question, we indeed lack good ways to bookmark > things > contextually. >
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
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