On Wed, Sep 27, 2023 at 03:15:32PM +0200, Jackson Chen wrote:
> @@ -41,6 +41,7 @@ labels {
>  resolved {
>      tags "resolved,partying_face"
>      icon "https://foo.com/resolved.png"
> +    resolved 1
>  }

You have one small typo here, should be "priority" instead of
"resolved". I fixed this in a follow-up commit.

Thanks a lot for your contribution!

On Thu, Aug 17, 2023 at 05:51:24PM +0200, Jackson wrote:
> That actually wasn't true, since I didn't actually pull the changes. Also,
> because go 1.21.0 still hasn't landed in my distro, I had to cross compile
> the binary (which wasn't a pain, fortunately).

Well if that does become a problem, I can backport the fix. Go 1.21.0 is
only really needed since I like the structured logging.

This should be fixed now. You can either build from source or use the
docker dev image.
If it still does not work for you, comment on this issue please:
https://todo.xenrox.net/~xenrox/ntfy-alertmanager/21

On Tue, Aug 15, 2023 at 05:57:01PM +0200, Jackson wrote:
> Console log:
> Cross-Origin Request Blocked: The Same Origin Policy disallows reading the
> remote resource at https://ntfy-alertmanager.jacksonchen666.com/silences.
> (Reason: CORS request did not succeed). Status code: (null).
Ah I don't actively use the web app, so I haven't run into this yet.
I will add the necessary changes for it to work.

> P.S. For ~xenrox specifically, would accept a patch for priority config in
> resolved alerts? (Sending 2 emails feels a little odd, I can start a new
> thread if needed)

Yes sure, that sounds useful. There probably should be some more
settings regarding labels and resolved alerts [1], but for me the

For match-end results we have two options:
1. Let an admin enter match results
2. Write an own sourcemod plugin

I would suggest we use the first option at the beginning or simply don't
modify the elo at all, until the system becomes more mature.

I have created a wiki with useful information/tips:
https://man.xenrox.net/~xenrox/10man-wiki/

I have implemented the API for faceit.xenrox.net [1].
It needs the steamID64 and returns the elo [2]. In case the user has no
Faceit account, the elo will be set to the default 1000. If a wrong
steamID64 is entered, the API will return `404`.

[1]: https://git.xenrox.net/~xenrox/faceit_checker/refs
[2]: https://faceit.xenrox.net/api/elo/76561197990016304

Structure:
1. Backend/API: GraphQL or REST in Go. I would lean more towards GraphQL
since I am currently working with that and maybe you can learn something
as well. Would use PostgreSQL as a database. Talks to my future
faceit.xenrox.net API to get the Faceit elo.

2. Teamspeak bot in javascript: Similar to the old source [1] but uses
the API now.

3. Frontend in Vue, React or Next.js.

Feature ideas:
- Invite system instead of free for all (how to implement ts3
  registration?)

Hello,

yes it surely will be ported.
Starting next week I will have more time to work on srhtctl. I will
probably finish my work for trackers/tickets and lists/patches and then
go on to work on the port.

Is there any other feature you would like to have?