There goes the argument of non technical users falling for scams. The tables have turned!

I do wonder if this would be negated by containered applications

What kind of patch cables are you using here?

Requiring accounts with X days or X karma lead to subs where people would literally post just to get upvotes and the creation of bot accounts.

This is awesome! Did you install the censors in the breaker box?

It averages $25 per month - which is hosting 16tb of storage (running 1tb nVME parity and 3x 8tb HDD) to host 5x Virtual Machines and 33x Docker Containers (which includes MariaDB, Postgres, InfluxDB, and Redis containers that receive a good amount of traffic), and a lot of the storage used for media/photo storage/consumption.

With cloud storage, I was hitting $70/month and that was without having all the backups of photos/media that I now have running on the home server.

I run a UPS for my home server and have Telegraf collect metrics, which I then feed into Grafana (via influxdb) to create a dashboard that uses my local kWph pricing to plot daily/monthly/quarterly/annual costs to run the server.

It might not be super helpful for some, but it’s helped me justify hosting applications at home with NAS instead of paying for cloud hosting

Example of the Dashboard:

One of the things I’ve enjoyed about lemmy; posts/comments feel far more engaging and don’t get drowned in thousands of comments that often don’t contribute much if anything.

When a vulnerability at this level happens and a patch is created, visibility is exactly what you need.

It is the reason CVE sites exist and why so many organizations have their own (e.g. Atlassian, SalesForce/Tableau )

It is also why those CVE will be on the front page of sites like https://news.ycombinator.com to ensure folks are aware and taking precautions.

Organizations that do not report or highlight such critical vulnerabilities are only hurting their users.

Mandatory for the admin creating weak passwords or writing them on sticky notes.

If you go to your profile, there is a setting to turn it private; after that you should have an option on your posts to keep them private or public

I wish there was a simpler way to keep PixelFed private; I get that there is a lot of focus on the fediverse, but this can also serve as a private image/video sharing platform for close friends and family.

Being public by default creates a blocker for the average person joining it.

Sounds like you’re really missing the threads experience; why aren’t you there and posting 250 characters at a time?

It would not be that simple, considering they’d be running multiple instances and require more effort to aggregate, deduplicate, and stage that data - vs just having a single clean database for it

It does actually matter, because that is what is happening.

Head over to the gaming@beehaw.org link that you shared as an example and notice that the posts are 3+ days old and all the recent posts are from instances other than beehaw; this clearly shows that Lemmy.world has not been receiving any data from beehaw for some time already.

As for hurting Lemmy and driving people to threads, is a baseless argument; anyone wanting an experience that Threads offers is not coming to Lemmy; they would either already be there or would be coming from Twitter/Mastadon. Lemmy at its core is very far from what Threads/Twitter/Mastadon try to be.

So many folks on here are jumping on and claiming that decentralization is a one way or that people don’t know anything, but have failed to read the specifications themselves.

https://www.w3.org/TR/activitypub/#block-activity-outbox

Servers SHOULD NOT deliver Block Activities to their object.

https://docs.joinmastodon.org/spec/activitypub/

ActivityPub defines the Block activity for client-to-server (C2S) use-cases, but not for server-to-server (S2S) – it recommends that servers SHOULD NOT deliver Block activities to their object.

So as I mentioned before, Lemmy.world should be blocking those servers at the instance level, preventing it from sharing any data to any identified Facebook instances.

Sure this doesn’t stop Facebook from spinning up other instances, but that will improve a lot more effort on their side and will quickly be identified and blocked by the communities, just like all their urls for ads, api, etc. have been for years.

Anyone can do anything; the point is handing it over automatically and neatly into a database and ready for use.

Because we, the users of Lemmy.world, do not want our data handed over to Facebook

Sure, but then I doubt anyone will be coming after you for patents

Patent laws aside, having a printer big enough to print a vehicle or even parts of a vehicle to assemble would not be cheap.

Then you would have to go through the hoops of getting the vehicle certified as road safe to even drive it on public roads.

So having the machinery to print it, the resources to print it, the know how to assemble it, and the procedures to have it certified as road safe, would be enough of a barrier before folks would be concerned with patents.

First rule of email: don’t use comic sans font.