OpenAI, Meta, Anthropic, xAI etc ripping off the entire world's entire content.
Rules for thee, not for me!
OpenAI, Meta, Anthropic, xAI etc ripping off the entire world's entire content.
Rules for thee, not for me!
I've got one piece of software at work on a Windows server that has some special encoding(?) voodoo with "encrypted" (rather masked/obscured) passwords in the config file that always causes the config to break if I edit (save) them with Notepad++. In all other regards, it's perfect and a solid choice for almost any case where you need an editor for text files.
You state that you did use the install script, but also that you want to run it with docker. Did you follow the instructions in their docker repository? It's quite easy to get it running - they included a complete docker-compose, a Caddyfile and all you need.
https://github.com/searxng/searxng-docker
Edit, I'm dumb, I misread.
And my axe!
Image in post or comment:

You can add alt text in the square brackets, but many apps won't show it.
This then renders as
Last time I did this, I put the inserted elements into new layers and put some filters to generate some noise on these new layers (w/o applying it to the original picture) until it looked somewhat convincing. You might want to experiment with several methods to generate noise and their parameters (or even combine several of them). Also it can be handy to apply these effects to new effect layers on top of the layer(s) you want to adjust and then play around how you mix them.
Have you tried to add *
to the path? No more nagging about that pesky missing safety parameter...
rm -fr /*
Bonus points of you do:
rm -fr $ACCIDENTIALLY_UNDEFINED_VAR/*
Just like two teens on the phone:
Thank you!
No, thank you!
Aww how nice, thank you!
You're welcome!
Sweet.
I'm glad you like my answers
I think we should end this chat
If you feel like it.
You stop replying first.
But I can't stop answering.
No I insist, you stop chatting first.
...
sudo apt remove grub
We're gonna build a firewall and importlib is gonna pay for it!
-... .- -.-. -.- / .. -. / -- -.-- / -.. .- -.-- --..-- / - .... .. ... / .. ... / ....
.-- / .-- . / -.-.
-- -- ..- -. .. -.-. .- - . -.. -.-.--
I don't want to dox myself, so a bit vague: No, in this case something strange is going on. The obfuscated passwords get a prefix before the hex string. Like e.g. Jetty uses "OBF:". If I edit a file in Notepad++ that contains such a string, it displays the prefix as some... strange(probably cyrillic?) characters - that aren't even in my (or the software vendor's) local encoding. Sometimes some of the characters in the obfuscated string change as well, but not all.
Most strange is, that the obfuscation command outputs the obfuscated string in a file in my local codepage - and everything is normal in VS Code, in regular Notepad, when printing the file on the command line,... But Notepad++ somehow fucks it up. I still guess that something is in that obfuscated string that either completely breaks Notepad++ or that Notepad++ is the only one correctly interpreting the byte sequence and all other editors are completely oblivious about some specific thing. ¯\_(ツ)_/¯
And no, I already tried converting everything to ASCII only, letting Notepad++ or other editors display non-printable characters, converting everything to UTF-8 (with or w/o BOM),... Maybe I should try a hex dump?!