The mayor’s office. It’s always in the mayor’s office.

This is the most infuriating part. The best solution to these issues is to remove the need to move in the first place, and WFH for the people that want it and who can do it removes a huge amount of traffic with comparably little cost (company laptop, a screen and maybe a desk and chair, many of which could just be taken from the office).

They will not… combine us? Just forget about the whole “almost every community is on lemmy.ml and lemmy.world” thing. :P

This is why people say not to use USB for permanent storage. But, to answer the question:

• From memory, “nofail” means the machine continues to boot if the drive does not show up which explains why it’s showing up as 100GB: you’re seeing the size of the disk mounted to / .
• If the only purpose of these drives is to be passed through to Open Media Vault, why not pass through the drives as USB devices? At least that way only OMV will fail and not the whole host.
• Why USB? Can the drives ve shucked and connected directly to the host or do they use a propriety connector to the drive itself that prevents that?

What happens if the instance which hosts the community is down but other instances are online? I just made a post to a community on an instance that doesn’t exist anymore, but will other instances get that post, or is it reliant on the instance which hosts the community coming back online?

The general idea that somebody who works a lot of hours is a good/hard worker in contrast to the amount of work actually completed.

They cry about not being able to serve ads while serving ads that are straight malware and scams. It’s especially funny when a platform goes out of their way to censor (suppress ad revenue) on videos which have even a chance of being misinformation and then proceed to play back to back ads of somebody selling their get rich quick webinar.

Redhat has entered the chat

Many instances purged their images after the lemmyshitpost incident. Perhaps that’s what you’re seeing.

Oh I completely misunderstood! I thought it was a forwarder, not dynamic DNS. My bad! Makes total sense!

Out of curiosity, why use a forwarder if you run your own DNS? Why not handle resolutions yourself?

And their landing gear is seems

Soooo…. the work of self-hosting with none of the benefits? It sounds like this has all the core problems of Twitter.

The more SSIDs being broadcast the more airtime is wastes on broadcasting them. SSIDs are also broadcast at a much lower speed so even though it’s a trivial amount of data, it takes longer to send. You ideally want as few SSIDs a possible but sometimes it’s unavoidable, like if you have an open guest network, or multiple authentication types used for different SSIDs.

The APs know who the Wi-Fi clients are and just drops traffic between them. This is called client/station isolation. It’s often used in corporate to 1) prevent wireless clients from attacking each other (students, guests) and 2) to prevent broadcast and multicast packets from wasting all your airtime. This has the downside of breaking AirPlay, AirPrint and any other services where devices are expected to talk to each other.

When buying disks do some research for the exact model to ensure they are not SMR drives if you plan on using them in RAID. Some manufacturers will not tell you if they are SMR drives and this can do anything from tank write performance to make the RAID reject the drive entirely.

See: https://arstechnica.com/gadgets/2020/04/caveat-emptor-smr-disks-are-being-submarined-into-unexpected-channels/

Seperate DB container for each service. Three main reasons: 1) if one service requires special configuration that affects the whole DB container, it won’t cross over to the other service which uses that DB container and potentially cause issues, 2) you can keep the version of one of the DB containers back if there is an incompatibility with a newer version of the DB and one of the services that rely on it, 3) you can rollback the dataset for the DB container in the event of a screwup or bad service (e.g. Lemmy) update without affecting other services. In general, I’d recommend only sharing a DB container if you have special DB tuning in place or if the services which use that DB container are interdependent.

The snowy mountains are incredible! There’s a series of Shiey videos for B&H where he surfs trains, camps and does a pushbike ride through the mountains: https://redirect.invidious.io/watch?v=V9huXurs678

Ah my bad. Memmy didn’t display the code block in your OP or this post. I see it on the web version.

That error might be less about needing X11 and more about wanting D-Bus. Since D-Bus isn’t running, it’s trying to start it by itself using X11, which also doesn’t work.

Does the error actually make Lemmy quit out?

FWIW I have a sanitised copy of my Lemmy k8s config on Gitlab that might help: https://gitlab.com/conorab/k8s-lemmy