ActuallyRuben

This does make me wonder, what is this graph actually about?

Dan ben ik toch blij dat mn werk voor mijn OV reizen betaalt

I like jumping on the bandwagon as much as the next guy, but do you have any evidence of these accusations?

There's three things I'd expect that reddit could do in retaliation:

• They're able to identify the people using an API key for this, and either deny them API access, or straight up ban them
• They further restrict free API access, rendering this option useless
• They take legal action against the app developers

And even if they don't take any action, ask yourself this: do you really want to keep using reddit, with the way they're acting right now? All this feels like a big middle finger towards their oldest users.

Are you checking your profile on a different instance? Comments in communities that aren't (yet) replicated to that instance won't show up

Stel dat het bijvoorbeeld vergelijkbaar is aan bitcoin dan is er juist helemaal geen privacy, want alle bitcointransacties zijn publiek.

Er bestaan al cryptocoins met betere privacy, Monero bijvoorbeeld. Bij Monero zijn zender, ontvanger en bedrag ontraceerbaar bij elke transactie.

Of ze zoiets toepassen is natuurlijk een tweede vraag, maar technisch is het mogelijk!

Lemmy does not have a built-in wiki feature. docs.beehaw.org is a separate website hosted using GitHub pages, with the source available here: https://github.com/beehaw-org/beehaw-org.github.io/

Is there a reason you don't want it to be federated? This would require every user to make a separate account, just to access your community, instead of being able to join and post using accounts from other instances.

Additionally creating an instance for just a single subreddit/community seems overkill. Have you considered creating a community on an existing instance?

Copy the link from the federation-link-hexagon-thing button and paste it into the search bar on your instance. The post should get fetched, and should show up as a result.

Looks like they changed up some things in the lemmy-ansible repository, resulting in the docker guide being outdated.

Take a look at this nginx config file instead: https://github.com/LemmyNet/lemmy-ansible/blob/main/templates/nginx_internal.conf It splits incoming requests and directs them to either the UI server or the backend server.

It honestly reminds me of the time 4chan stole Shia Labeouf's flag, locating it from a livestream with only the flag and the sky visible.

https://www.vice.com/en/article/d7eddj/4chan-does-first-good-thing-pulls-off-the-heist-of-the-century1

Try updating your docker-compose version. Any top-level property starting with x- should be accepted as an extension, whether compose can understand it's contents or not. In this case the x-logging section is used as a fragment to set up default logging settings for each service.