~j3s

Minneapolis, MN

https://cyberia.club

ops necromancer.

~j3s/cyberia

Last active 6 months ago

~j3s/reply-example

Last active 6 months ago

~j3s/announce

Last active 7 months ago
View more

Recent activity

Re: I upgraded my sr.ht install and the meta.sr.ht process won't start properly 3 days ago

From to ~sircmpwn/sr.ht-discuss

> The second issue I had was that the oauth2 page would error out. For this 
> I had to add a section in my apache config to also proxy requests to 
> /query to 127.0.0.1:5100/query.

This is the thing that fixed everything for me! I didn't have to mess with /etc/hosts
at all.

Using the config here as a reference:
https://git.sr.ht/~sircmpwn/sr.ht-nginx/tree/master/meta.sr.ht.conf

Other symptoms were:

- services would timeout if you tried to visit them on the web, however if you 
  restarted nginx occasionally some or all of the sr.ht services

Re: I upgraded my sr.ht install and the meta.sr.ht process won't start properly 3 days ago

From to ~sircmpwn/sr.ht-discuss

> Hm, I'm not sure. Someone else encountered this, too, but I'm not sure
> that they made any progress. I can investigate further tomorrow if you
> don't mind me popping into your server to look around -
> 
> https://meta.sr.ht/~sircmpwn.keys

Sure, that'd be great!

ssh sircmpwn@rosewater.cyberia.club

Re: I upgraded my sr.ht install and the meta.sr.ht process won't start properly 3 days ago

From to ~sircmpwn/sr.ht-discuss

> Do you have the API service running? metasrht-api?

Yep, it's running and responding to queries

rosewater:/var/log# service meta.sr.ht-api status
 * status: started

rosewater:/var/log# tail /var/log/meta.sr.ht-api.log
2020/11/23 23:32:35 Running on :5100
2020/11/23 23:32:35 Prometheus listening on :36949

rosewater:/var/log# netstat -plunt | grep 5100
tcp        0      0 0.0.0.0:5100            0.0.0.0:*               LISTEN      4506/metasrht-api

I upgraded my sr.ht install and the meta.sr.ht process won't start properly 3 days ago

From to ~sircmpwn/sr.ht-discuss

Hiya, I'm having an issue with our sourcehut installation. The meta.sr.ht
service is throwing the following error:

[CRITICAL] WORKER TIMEOUT

# Versions and stuff

Install type: latest Alpine Linux (3.12.1) apk package-based install.

Versions are the latest available:

rosewater:/var/log# cat /etc/alpine-release
3.12.1
rosewater:/var/log# uname -a

[gmni] build failure on void linux 2 months ago

From to ~sircmpwn/public-inbox

Hi! Thought you might want to know about this build failure.

Builds fine on commit 30660fc160a15504274d40d4a5ec1b31539f8c2f

Breaks on commit 02f6af661513683f0c6c1465c5ff1dd8f03a30c9

== info

OS: Void Linux
$ uname -a
Linux nostromo 5.8.10_1 #1 SMP Fri Sep 18 09:39:06 UTC 2020 x86_64 GNU/Linux
$ openssl version
LibreSSL 3.1.4

Re: Session timeouts discard drafts 3 months ago

From to ~emersion/alps-dev

Hi! I ran this by my friend Forest, and he came up with the following proof
of concept for auto-saving drafts.

Please note that the following JavaScript is included for feedback purposes
only and it's not the final product - I intend to shrink it down a lot before
final submission.

But first, I'd like your feedback. To use this, start composing a message via
the alps interface, and paste the following code into the console of your
browser. The message should begin auto-saving.

It also does some really gross scraping to get Draft IDs, I'd clean that up and
have the backend return the Draft ID instead.

Re: Session timeouts discard drafts 3 months ago

From to ~migadu/alps-devel

Hi! I ran this by my friend Forest, and he came up with the following proof
of concept for auto-saving drafts.

Please note that the following JavaScript is included for feedback purposes
only and it's not the final product - I intend to shrink it down a lot before
final submission.

But first, I'd like your feedback. To use this, start composing a message via
the alps interface, and paste the following code into the console of your
browser. The message should begin auto-saving.

It also does some really gross scraping to get Draft IDs, I'd clean that up and
have the backend return the Draft ID instead.

Re: Session timeouts discard drafts 3 months ago

From to ~emersion/alps-dev

> Is the session cookie expiring?

Correct. If the session cookie expired, clicking on "Save Draft"
redirects you to the login page. If you try and click "back" you
see only the login page as well, so there's no obvious path to
retrieve your email - it is "lost" at this point.

> -login-key

After some trial and error I enabled this option. I used the following
code to generate a fernet key:

package main

Re: Session timeouts discard drafts 3 months ago

From to ~migadu/alps-devel

> Is the session cookie expiring?

Correct. If the session cookie expired, clicking on "Save Draft"
redirects you to the login page. If you try and click "back" you
see only the login page as well, so there's no obvious path to
retrieve your email - it is "lost" at this point.

> -login-key

After some trial and error I enabled this option. I used the following
code to generate a fernet key:

package main