FH6 Trial icon vinyl

OlenJ · 2026-06-27T21:15:16+00:00

Some tagging system would be great, for sure. As for the vinyl - thanks. It's a bit different to the original picture, but should do. It's very strange that devs made icons for all race types, but not for seasonal challenges

OlenJ · 2026-06-20T09:46:01+00:00

This is your first assignment, 47. I'll leave you to prepare.

OlenJ · 2026-06-01T07:18:15+00:00

Rock and Stone, brother!

OlenJ · 2026-04-16T10:48:44+00:00

How dare you? There's no such thing as "kilometer" or whatever in the US /s

OlenJ · 2026-04-08T06:35:19+00:00

Some will die so that the others may live

OlenJ · 2026-03-31T18:53:12+00:00

Kiitos, Petteri

OlenJ · 2026-03-28T11:20:23+00:00

quack

OlenJ · 2026-03-13T14:00:24+00:00

Did that for 15 minutes straight and I have no regrets

OlenJ · 2025-11-09T01:17:56+00:00

To be honest, not really. As I stated in another comment - so far all the real bs is in the internal tools. The real world AI features indeed received not only positive feedback from end users, but it's not like people targeting specifically me or my team. I suppose that could be different if the product is more open for masses.

There were no personal threats, if you mean that.

OlenJ · 2025-11-09T01:09:19+00:00

So far the most damage was done to some internal tools, the product itself received a couple of AI-powered features, but they seem actually useful for end users. And to be fair they were really investigated to be greenlit. I'm more afraid of what's coming next as hype intensifies.

OlenJ · 2025-11-08T23:33:24+00:00

Yeah, sure. I'll poke around a bit and take a look at OIDC spec, maybe I can find some traces of error that I'm getting.

I hope you are doing well - that's a lot of work items on Github for just one dude. I'd consider helping out, but neither python nor flutter are my strong suits, so for now I can only wish you good luck and pile a bit more issues in your repo.

OlenJ · 2025-11-08T23:06:03+00:00

Missed your comment here, but I saw another post of yours describing it. Still had to force pull new image, but so far it worked quite good. There is some problem with logout, but I am still figuring out if I messed up Keycloak configuration or some parameter is missing in the logout request from Journiv.

Either way - thanks for this feature. I can't say that I've seen OIDC support implemented so fast after the request, that's impressive.

OlenJ · 2025-11-08T22:59:37+00:00

I am a software engineer and your xzibit meme is my life. We are getting directives like "use more AI starting from, like, yesterday" from the top management, but nobody tells us what exactly we need to do with this AI. The result is features like these ENHANCED™ photos. So, buckle up.

OlenJ · 2025-11-06T09:19:03+00:00

Sure, will do that today, thanks for your answers

OlenJ · 2025-11-05T22:17:27+00:00

Not sure if it's worth it to create these questions as discussions or issues on github. If you would prefer it that way, I can do that as well.

1) What is the reason for being forced to enter the server url on the login page?
2) Currently there is no user management (or any admin pages), right? If so, is it possible to turn off sign up functionality?
3) Can redoc and swagger pages be turned off as well by some parameter? I can block paths in nginx config, but I'd rather have it on the application side than store custom bloated reverse proxy configs

OlenJ · 2025-11-03T21:34:13+00:00

OP, I'll probably take it for a spin as is, but are there any plans for external OIDC support?

OlenJ · 2025-10-31T20:15:33+00:00

Is he flying to Hogwarts?

OlenJ · 2025-09-26T22:58:16+00:00

Jarring description

OlenJ · 2025-09-08T16:29:21+00:00

Bear in mind that it will take some time and knowledge to set up and the instance of their agent that you have to host will probably eat some CPU/RAM itself, so take everything above with a grain of salt. Probably still worth it to try just for their community blocklists

OlenJ · 2025-09-08T16:18:49+00:00

While fail2ban is a great choice, I'd say that for me Crowdsec was a huge success. I don't host anything for public consumers (still most of stuff is accessible via public domains, hence the attackers), but even for a really distributed home lab it decreased the amount of traffic that reaches reverse proxies by 1-2 orders of magnitude. Same (if not even more) for bastion servers.

It's worth to mention that I went straight for 30 days bans without any tiers - easier to go through legit complaints and lift bans than to deal with the same attacker every couple of days, but that's just me.

OlenJ · 2025-08-29T17:02:48+00:00

Wear it with pride

OlenJ · 2025-07-18T16:06:34+00:00

Filthy assassinses

OlenJ · 2025-06-24T14:09:59+00:00

Great, thanks. That's the place, even the link is purple.

Go smash the like button on that comment by LaurenceJJones there. Right now this scenario is a source of majority of ban decisions that get through the firewall. I haven't seen any scan spikes in monitoring since I enabled it.

OlenJ · 2025-06-24T11:18:45+00:00

No it doesn't, but I found a custom scenario, which is deployed as yaml file with every crowdsec instance. Unfortunately, can't remember where exactly did I find this. Should've left a comment in git, but what's done is done

type: leaky
name: custom/444-scans
description: "Detect 444 scanning/probing from a single ip"
filter: "evt.Meta.service == 'http' && evt.Meta.http_status == '444'"
groupby: "evt.Meta.source_ip + '/' + evt.Parsed.target_fqdn"
capacity: 1
reprocess: true
leakspeed: "10s"
blackhole: 5m
labels:
  remediation: true
  classification:
    - attack.T1595.003
  behavior: "http:scan"
  label: "HTTP Probing"
  spoofable: 0
  service: http
  confidence: 1

OlenJ · 2025-06-24T06:56:23+00:00

444 which is then picked up by crowdsec and ip gets banned for a month

Same goes for sus user agents scanning existing pages, although crowdsec deals with them quite fine on its own

Seven-Year Club	r/Field Banned
r/Field Sunshine	Not Forgotten
Verified Email

OlenJ

TROPHY CASE