Having grown up in the commercial tv era is why I despise ads.

Thanks for sharing! Have been thinking of writing a script to identify active communities and based on criteria, subscribe to them on my personal instance; this will be really helpful for it!

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.

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.

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

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

Does codium handle updates for the extensions?

This is what training new folks looks like. Even something as simple as a browser; watching someone click into the address bar and hit enter just to refresh the page, hurts my soul.

Wow - I had Aquamail from 2015 and loved that app; so sad to see another company go for the shitification of their product.

Does docker really spin up a VM to run containers?

I would suggest signing up for a free Cloudflare account and setting up any DNS for your Pi through there, using the Cache feature.

Once that is done, setup an automated script that will pull down Cloudflare IPs into a file (you can use a cronjob to run this daily):

#!/bin/bash

set -e

cf_ips() {
  echo "# https://www.cloudflare.com/ips"

  for type in v4 v6; do
    echo "# IP$type"
    curl -sL "https://www.cloudflare.com/ips-$type/" | sed "s|^|allow |g" | sed "s|\$|;|g"
    echo
  done

  echo "# Generated at $(LC_ALL=C date)"
}

cf_ips > allow-cloudflare.conf
(cf_ips && echo "deny all; # deny all remaining ips") > allow-cloudflare-only.conf

Then in your web server config to only accept connections from Cloudflare IPs:

server {
	listen 80 default_server;
	listen [::]:80 default_server;
	server_name example.com;
        root /var/www/html;

	include /etc/nginx/allow-cloudflare-only.conf;
}

I prefer this method over UFW/iptables block as it allows you to control the IP block per web config, so if needed, you can make exceptions by not adding the include /etc/nginx/allow-cloudflare-only.conf; into that specific site’s conf file.