HomeSearchPrevious dayNext day

00:11:32<fireonlive>https://dl.fireon.live/irc/6f550dde0607b550/image.png
00:11:38<fireonlive>😏😏😏
00:11:43<fireonlive>💦💦💦
00:12:11<@JAA>*bonk*
00:13:11<fireonlive>😵‍💫
00:21:29<fireonlive>https://dl.fireon.live/irc/eaf5181de76b70b0/image.png
00:21:34<fireonlive>🤔
00:22:36<@JAA>Yeah, that's a thing.
00:24:01<fireonlive>I guess you could always hitch a ride at the end of the day if worst came to worst :)
00:40:57toss quits [Client Quit]
00:43:20programmerq quits [Ping timeout: 240 seconds]
00:44:36jacksonchen666 (jacksonchen666) joins
00:46:33programmerq (programmerq) joins
00:50:20emberquill08 quits [Client Quit]
00:51:05emberquill08 (emberquill) joins
00:51:50wickedplayer494 quits [Ping timeout: 240 seconds]
00:55:14wickedplayer494 joins
01:41:50nulldata quits [Ping timeout: 240 seconds]
01:48:19nulldata (nulldata) joins
01:55:40supermariofan67|m joins
02:10:22qwertyasdfuiopghjkl quits [Client Quit]
02:13:56qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
03:00:30pseudorizer quits [Quit: ZNC 1.8.2 - https://znc.in]
03:01:11pseudorizer (pseudorizer) joins
03:08:05threedeeitguy390 quits [Quit: Ping timeout (120 seconds)]
03:08:53threedeeitguy39 (threedeeitguy) joins
03:15:01nulldata quits [Client Quit]
03:15:30nulldata (nulldata) joins
03:46:34qwertyasdfuiopghjkl quits [Remote host closed the connection]
04:05:27qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
05:13:39<fireonlive>this is since dead, but TIL the makers of TrueNAS went into storage crypto (chia)? https://chiaforum.com/t/truepool-by-the-makers-of-truenas/10200 “TruePool”
05:15:37<fireonlive>via reddit they shut down 2022-02-01 … or 2022-01-02…
05:16:55<fireonlive>https://www.reddit.com/r/opensource/comments/18j4tfr/truenas_silently_changing_license_and_being_made/ (found via the truenas/ixsystem’s employee’s bio on reddit here)
05:17:28icedice quits [Client Quit]
05:18:07<fireonlive>one way to get people into your storage crypto: sell the hardware and make the os and have an official app on said os :3
05:43:04qwertyasdfuiopghjkl quits [Remote host closed the connection]
05:46:59DogsRNice quits [Read error: Connection reset by peer]
05:57:51<fireonlive>https://x.com/swiftonsecurity/status/1735901684776185959?s=12
05:57:51<eggdrop>nitter: https://nitter.net/swiftonsecurity/status/1735901684776185959
06:17:04<fireonlive>the behind the scenes video to the reporter giving the middle finger to the world has been released!
06:17:13<fireonlive>you can see the full countdown https://x.com/bnodesk/status/1735676615097540615?s=12
06:17:14<eggdrop>nitter: https://nitter.net/bnodesk/status/1735676615097540615
06:48:57hitgrr8 joins
06:51:21qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
07:03:01<@JAA>In today's episode of my successful(?) series Shitty One-Liners That Should've Been Scripts, I present you this disgusting hacky multitail for Docker logs, taking as arguments any number of container names at the end and prepending the source container name to each output line:
07:03:08<@JAA>bash -c 'function cleanup { local pids=($(ps -o pid,cmd | grep "[d]ocker" | awk "{print \$1}")); if [[ ${#pids[@]} -eq 0 ]]; then return; fi; kill ${pids[@]}; }; trap cleanup EXIT INT TERM; for c; do ec="$(sed "s/[.[\*^\$()+?{|]/\\&/g" <<<"${c}")"; ${hack:-d}ocker logs -ft --tail 1 "${c}" |& sed "s,^,${ec} ," & done; wait' bash foo bar baz
07:03:19<@JAA>(foo bar baz are the container names.)
07:08:59<@JAA>It would've been much easier had it not been a one-liner, but where's the fun in that?
07:47:21qwertyasdfuiopghjkl quits [Remote host closed the connection]
07:48:41qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
07:59:18<project10>I'm scaroused by that one-liner
08:00:06<@JAA>:-)
08:01:04<@JAA>I think `${hack:-d}ocker` is my favourite part.
08:01:38<project10>yeah that stood out to me as well :)
08:03:15<@JAA>There are far better ways (like using a fucking script instead of `-c`), but it's to avoid matching the Bash processes themselves in the `ps | grep`. :-P
08:32:00<project10>the best one-liner that implements the same is: `docker compose -tfn0`. It even has color d=}
08:33:34<@JAA>But then I'd need Docker Compose installed.
08:37:56c3manu (c3manu) joins
08:38:49systwi quits [Ping timeout: 272 seconds]
08:42:21<@JAA>I suppose you meant `docker compose logs -tfn0`. And does that take arbitrary container names, or does it have to be Compose services etc.?
08:46:08<project10>yeah, typo on the command. It does indeed only do things in the compose file, not arbitrary container names as yours does. Not quite equivalent :)
08:50:29systwi (systwi) joins
09:33:38Jens quits []
09:34:08Jens (JensRex) joins
10:00:02Bleo1826 quits [Client Quit]
10:01:18Bleo1826 joins
11:54:50Naruyoko quits [Ping timeout: 240 seconds]
13:07:50Arcorann quits [Ping timeout: 240 seconds]
13:10:12project10 quits [Quit: Ping timeout (120 seconds)]
13:10:31project10 (project10) joins
13:16:35qwertyasdfuiopghjkl quits [Remote host closed the connection]
13:16:51jacksonchen666 quits [Ping timeout: 250 seconds]
14:20:10icedice (icedice) joins
14:30:49ScenarioPlanet (ScenarioPlanet) joins
14:45:05<nulldata>https://www.theverge.com/2023/12/15/24003542/openai-suspends-bytedances-account-after-it-used-gpt-to-train-its-own-ai-model
14:59:14riku_ (riku) joins
15:01:21riku quits [Ping timeout: 272 seconds]
15:08:17riku_ is now known as riku
15:27:14DogsRNice joins
15:38:24Aoede quits [Quit: ZNC - https://znc.in]
15:53:01Aoede (Aoede) joins
15:57:52Aoede quits [Client Quit]
16:00:55decky_e quits [Read error: Connection reset by peer]
16:01:19decky_e joins
16:10:11<DogsRNice>https://twitter.com/thewapplehouse/status/1734989837101371580
16:10:11<eggdrop>nitter: https://nitter.net/thewapplehouse/status/1734989837101371580
16:11:11<DogsRNice>"too bad" is such a good response when arguing with someone stupid
16:20:52icedice quits [Client Quit]
16:36:52Naruyoko joins
16:37:37systwi quits [Ping timeout: 272 seconds]
16:39:00Aoede (Aoede) joins
17:09:46systwi (systwi) joins
17:12:27jacksonchen666 (jacksonchen666) joins
18:38:49c3manu quits [Remote host closed the connection]
18:47:30<fireonlive>https://github.com/francoismichel/ssh3
18:51:52<@JAA>Great name that surely won't lead anyone to think it's actually SSH. (Why not sshttp3?)
18:53:41<@JAA>> While SSHv2 defines its own protocols for user authentication and secure channel establishment, SSH3 relies on the robust and time-tested mechanisms of TLS 1.3, QUIC and HTTP.
18:53:45<@JAA>lol
18:59:31<@JAA>> you can now use your classical HTTPS cerificates to authenticate your SSH3 server. This mechanism is more secure than the classical SSHv2 host key mechanism.
18:59:49<@JAA>... until someone MITMs your server connections and gets their own LE certificate. :-)
19:00:36<@JAA>The OpenID stuff might be interesting, and I guess it'd be useful for bypassing shitty firewalls.
19:01:03<@JAA>Eww, it uses single-hyphen long options.
19:33:40rohvani joins
19:42:46ScenarioPlanet quits [Client Quit]
19:51:59BlueMaxima joins
20:07:39qwertyasdfuiopghjkl (qwertyasdfuiopghjkl) joins
20:50:18hitgrr8 quits [Client Quit]
21:03:20DogsRNice_ joins
21:06:20DogsRNice quits [Ping timeout: 240 seconds]
21:39:50Earendil7 quits [Ping timeout: 240 seconds]
21:49:58<that_lurker>-+rss- MongoDB is actively investigating a security incident: https://www.mongodb.com/alerts https://news.ycombinator.com/item?id=38667596
22:07:07<Barto>uff
22:14:31<@JAA>It's not a security breach, it's just web-scale data access!
22:53:24<Terbium>"believe that this unauthorized access has been going on for some period of time before discovery" That's not good
22:53:39<Terbium>I wonder how long "some period" is
22:55:27<joepie91|m>judging from the phrasing, so do they
23:46:06Arcorann (Arcorann) joins

HomeSearchPrevious dayNext day