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.
> 

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

---
 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]

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?

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

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.
> 

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

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

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

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).