Setting up a watchdog and crash kernel might help or let you diagnose it

I enjoyed consuming this.

I’m not the OP and only did a bad job cross-posting it but I do encourage you to print a bunch of these out!

¯\(ツ)/¯

So long as one of the presets is the primary channel all messages share the same frequency and airtime. Add secondary channels doesn’t do anything to lower utilization of the defaults so long as they remain the primary channel.

Take a look at https://diskprices.com/ for the best price per TB. Backblaze has been pretty great about sharing their hardware specs and builds. Maybe get some ideas from them https://www.backblaze.com/blog/open-source-data-storage-server/

In st. louis there’s #MeshSTL but it doesn’t have open encryption and still uses the LongFast slot. I don’t buy the politeness argument and all the meshes around here that are getting high air time are just moving to LongTurbo entirely.

Ssh includes a built in socks proxy. What are you actually trying to accomplish?

Let us both hope for those kind of scaling problems due to popularity 🤞

Wow, bold decisions for what it’ll support and not. I like that it’s laser focused on a specific use case. What do you think about the impact to instances’ federation queue when a bunch of single user instances follow a community? 10x the traffic and queue for 10 single user instances than one instance with 10 users.

I ask this as someone that ran a full single user lemmy instance right up until recently and switch to a public piefed due to the traffic multiplication and other concerns.

Buy any pi meshtastic hat (good luck finding one in stock), install meshtastic daemon, profit?

Why not a tor relay? If you’re not an exit it is pretty darn safe. How about a tor snowflake proxy too? Even easier and safer.

Thanks for rapidly creating new content. What is this, one per day?! c/funhole deserves all of it.

Wahoo! Best of luck!

I didn’t intend and don’t think the stick bit stuff will or could be a complete solution for you. You’ve got some oddly specific and kinda cruddy restrictions that you’ve got to workaround and when they get that nonsensical one ends up solidly in “cruddy hack” territory.

From the article:

group + s (pecial)

Commonly noted as SGID, this special permission has a couple of functions:

If set on a file, it allows the file to be executed as the group that owns the file (similar to SUID) If set on a directory, any files created in the directory will have their group ownership set to that of the directory owner

You could run something like https://pypi.org/project/uploadserver/ in screen or run a cron every minute that just recursively sets the correct permissions.

Maybe some sticky bit https://www.redhat.com/en/blog/suid-sgid-sticky-bit

Thanks for creating front content. Much better than C8!

Thanks… I hate it.

Thank you for creating finger-mouth content