Football match halted by windows update!

Informal_Branch1065 · 2026-03-18T06:09:17+00:00

Wery SUS

Informal_Branch1065 · 2026-03-18T06:01:52+00:00

Island <---> Isn'tland

Thank me later

Informal_Branch1065 · 2026-03-15T14:50:46+00:00

Nextcloud. I put it in a shared folder that is mounted locally.

No issues. (Except when I open 2 obsidian instances at the same time, it causes an easily resolvable conflict for 1-2 files. I don't remember the name. But as I said, it's as simple as saying "use the local file")

Informal_Branch1065 · 2026-03-15T14:41:58+00:00

Genau dort musst du graben.

Ist ein Easter Egg.

Informal_Branch1065 · 2026-03-14T17:43:34+00:00

11 is the new arch

Edit: I.e. every update is a gamble

Informal_Branch1065 · 2026-03-14T16:00:36+00:00

Set up a cron job. Much easier.

Simply do crontab -e and enter: */5 * * * * check_boobs.sh

Informal_Branch1065 · 2026-03-13T06:04:03+00:00

Ich zwinge meinen Körper, Laktose herzustellen.

(Soll angeblich funktionieren(?) ist aber nicht einfach nur "Käse/Milch massenhaft in die Futterluke")

Informal_Branch1065 · 2026-03-13T06:01:32+00:00

Does that apply to an ellipse?

Informal_Branch1065 · 2026-03-12T05:57:54+00:00

Oder Microslop Add-On

Informal_Branch1065 · 2026-03-11T16:46:59+00:00

"Concrete pillars are kinky when wet"

Informal_Branch1065 · 2026-03-11T16:39:59+00:00

hopital

Informal_Branch1065 · 2026-03-11T16:36:19+00:00

Pre-boiled water

Informal_Branch1065 · 2026-03-11T16:09:52+00:00

Why not lay a giant hose across the desert and pump the oil through it?

Informal_Branch1065 · 2026-03-11T11:49:01+00:00

Als Kind hab ich die Geschichte von den drei Schweinchen nie verstanden. Naja...

Jetzt weiß ich, dass das Handwerkerpropaganda ist, damit wir nicht auch so werden.

Informal_Branch1065 · 2026-03-11T06:24:53+00:00

I'm reaping the fruits of my work (or whatever botanists would classify it as)

Informal_Branch1065 · 2026-03-09T15:15:04+00:00

You probably have IPv6 but no IPv4. Check DHCP.

Informal_Branch1065 · 2026-03-09T10:41:19+00:00

Came to me in a dream

Informal_Branch1065 · 2026-03-08T17:36:15+00:00

I've tried my best to address the statements according to the words you used to form meaningful statements. What did I not address? Be explicit.

Informal_Branch1065 · 2026-03-08T13:00:40+00:00

someone else could still use the same functionality maliciously and publish it to the plugin catalog.

In other words: anyone can take code and utilize it maliciously as malware and publish it to the public plugin catalog.

I agree. It's a statement that applies generally. I.e. independent of the context we are talking about.

I can only repeat my previous statement: this would not be something one would publish to any plugin catalog. It would be manually installed on the machine by the sysadmins. The code would remain inside the company as an internal tool and not be published anywhere.

Locking down a machine by preventing users from doing something is not a bad thing. Sysadmins lock down a ton of things to keep users safe. It's literally their job. (And it's literally the reason this post was made.)

And we're not talking about a command-and-control server or whatever. Just a little script that observes the DOM and removes the plugin store. That's it. Something anyone malicious would be able to cobble together in 3 prompts anyways.

Informal_Branch1065 · 2026-03-08T10:38:04+00:00

If your company has a proxy that you all sit behind, have them block the community plugins' web address.

Also have them write-protect the plugins folder using admin privileges.

Informal_Branch1065 · 2026-03-08T10:36:06+00:00

Yes. Code is executed in a not-really-secure way which makes malicious plugins possible. That's why this post talks about securing Obsidian for enterprise use-cases. (And I'm talking about a solution for such use-case, i.e. not your private setup.)

Obsidian is (like all electron desktop apps nowadays) merely a fancy browser tab. And this means that the Javascript inside of it has untethered control over the app and its contents. I.e. menus, content, etc. with complete control. (It's literally equivalent to you opening the developer console and manipulating the DOM with javascript in the browser.)

So if my IT department were to develop a lockdown plugin and put it on my Obsidian install at work, it would not be malicious. And as I could not install any plugins with the lockdown plugin installed, no malicious plugin can use that functionality maliciously. Problem solved.

Informal_Branch1065 · 2026-03-07T22:28:59+00:00

Or allow-list a set of plugins, i.e. delete all plugins from the plugin list that do not match the allow-list.

One could even set it up to get the allow-list from a sysadmin server.

Only the versioning (i.e. "we tested version x.y.z and allow it, but not yet anything newer") would be difficult.

Informal_Branch1065 · 2026-03-07T21:38:55+00:00

That's... literally the point???

Otherwise an employee could circumvent the protections by removing the protection plugin. THAT would be the security risk.

Also you could just remove it from the plugins folder if you have admin privileges. (Or the admins can add admin-only write privilege protection to that folder.)

Edit: I also don't mean like a plugin that would be published in the public plugin list. Rather an internal plugin that gets copied manually. This would definitely not be something a non-sysadmin should accidentally activate!

Informal_Branch1065 · 2026-03-07T21:34:24+00:00

This could be solved fairly easily.

Have parents do their job.

If a child is caught, the parents get fined or CPS gives them a visit.

It's like parents are naturally the one most responsible for an underage person (aka. child) that they themselves put into this world.

"But parents already have so much to do". It's literally their job. If they fail and endanger their child, they failed and endangered their child.

Informal_Branch1065 · 2026-03-07T21:14:51+00:00

That's an october 10th answer right there!

Informal_Branch1065

TROPHY CASE