Me. $350 off and $100 worth of storage upgrades on a Pixel 9 pro was worth it for me. Phones now are expensive as fuck but getting a ~40% discount on a brand new product made it easier to accept.

Telegram’s server side software is closed source, owned and ran by them exclusively so they really have no room to talk. WhatsApp doesn’t even have OSS clients so they’re even worse in that regard

I see now, that makes sense why you are building the image since it was set up that way. I don’t know why projects set up the compose file to build the image when they already have a publicly available image to use; it just creates unnecessary friction for people who just want to test out the software. Anyway, using that image should work for you, but feel free to ask if you run into any issues.

Why are you building the image yourself? Not that there’s a problem with that necessarily, but it seems a bit wasteful of your resources unless you have a specific reason to do so. There’s a docker image (quay.io/invidious/invidious:latest) built by the developers that gets updated pretty frequently. I’ve been using it for years now and it’s been working perfectly fine for me the whole time.

Even if you need something just once, just install it and then uninstall it, takes like 10 seconds.

apt install foo && apt remove foo

That’s essentially what nix-shell -p does. Not a special feature of nix, just nix’s way of doing the above.

Actually using it though is pretty convenient; it disappears on its own when I exit the shell. I used it just the other day with nix-shell -p ventoy to install ventoy onto an ssd, I may not need that program again for years. Just used it with audible-cli to download my library and strip the DRM with ffmpeg. Probably won’t be needing that for a while either.

The other thing to keep in mind is that since Nix is meant to be declarative, everything goes in a config file, which screams semi-permenant. Having to do that with ventoy and audible-cli would just be pretty inconvenient. That’s why it exists; due to how Nix is, you need a subcommand for temporary one-off operations.

Just this one https://wallhaven.cc/w/2y2wg6

Have it hard-coded in my config so I’m less likely to faff around with my wallpaper instead of doing something productive. Less cognitive load IMO

Hallelujah!

Raft by Stephen Baxter. Part of the Xeelee sequence series.

Currently on book 2: Timelike Infinity and I’m liking it quite a bit.

Not trying to out myself, but I may be one of the few people that actually owned that shirt lol

Kopia repo on a separate disk dedicated to backups. Have Kopia on my servers as well sending to my local s3 gateway and second copy to wasabi.

Today’s episode of Veronica Explains is brought to you in part by corporate greed.

Less than 5 seconds in and I already know I’m going to like this video.

Well that’s disappointing. I’ll have to investigate further I guess. I was really hoping to set it up (at least initially) without any type of media storage.

so I assumed someone would probably have subscribed before me

I think the community is very new, so there’s a decent chance you were the first. As to the overloading problem, it’s certainly possible. Lemmy.world has a ton of users, and while I know ruud is dedicating a lot of resources to your lemmy instance, it just may not be enough to keep performance great. There’s been a lot of reports of performance problems by both lemmy.world users and federation problems between .world and other lemmy instances, most likely from being overloaded. You might try setting up a secondary account on another instance if you’re inclined, can’t hurt. Then at least you’ll be able to compare. Mine is on sh.itjust.works and everything has been pretty decent for me since the latest software upgrade, just as a point of reference.

Sorry for my cluelessness, I’m new to the fediverse

No worries mate, we’re all new here. I’m still getting used to things too.

Thanks bot, but you weren’t needed in this particular case. You’re a Good Bot though.

how can that be if others from this instance have already subscribed?

How certain are you that the community was already subscribed to? You may be the first person on your instance to subscribe there. If that’s the case you’ll only be seeing anything posted after you subscribed.

That is, unless Faceman is correct, in which case lemmy.world will eventually backfill content when it can.

For example, I’m seeing three posts there on both my instance and when I visit https://feddit.nl/c/trendingcommunities. I’m fairly sure that when I first subscribed I could only see the first post, but definitely not sure that’s the case.

Oh I see, I definitely misunderstood what you were asking. How is your caddy server set up? Is it serving one site per subdomain (site.your.domain) or is it one site per path (your.domain/site/)? I am running traefik so I probably won’t be able to help with specifics, but it’s worth a shot.

Oh that’s interesting, that’s the first I’ve heard of it. I wonder how one would go about testing if that works.

It depends on if you were the first person on your instance to subscribe, and if that subscription happened before or after the posts were made. Lemmy doesn’t do backfilling content, which means only new content after the subscription happens will be visible to your instance. I’m not a fan of that personally, but I can see why they did it that way.

The way I have my monitoring set up is to poll the containers from behind the proxy layer. Ex. if I’m trying to poll Portainer for example:

---
services:
    portainer:
    ...

with the service name portainer

from uptime-kuma within the same docker network it would look like this:

Can confirm this is working correctly to monitor that the service is reachable. This doesn’t however ensure that you can reach it from your computer, because that depends on if your reverse proxy is configured correctly and isn’t down, but that’s what I wanted in my case.

Edit: If you’re wanting to poll the http endpoint you would add it before like http://whatever_service:whatever_port

I believe the Pictrs is a hard dependency and Lemmy just won’t work without it, and there is no way to disable the caching

I’ll have to double check this but I’m almost certain pictrs isn’t a hard dependency. Saw either the author or one of the contributors mention a few days ago that pictrs could be discarded by editing the config.hjson to remove the pictrs block. Was playing around with deploying a test instance a few days ago and found it to be true, at least prior to finalizing the server setup. I didn’t spin up the pictrs container at all, so I know that it will at least start and let me configure the server.

The one thing I’m not sure of however is if any caching data is written to the container layer in lieu of being sent to pictrs, as I didn’t get that far (yet). I haven’t seen any mention that the backend even does local storage, so I’m assuming that no caching is taking place when pictrs is dot being used.

Edit: Clarifications