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

They did. Its called airmessage. Has been around for almost 3 years now

Ah you’re probably right about the mobile clients. I’m not a mobile watcher really. I can say though that the jellyfin desktop app and jellyfin mpv shim both have skip-intro integration, though I’ve only tested it with jellyfin MPV shim.

Skip-intro is an unofficial plugin ATM but can vouch that it works decently well. Can’t compare it to the Plex implementation since it has been quite a while since I’ve had Plex deployed.

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

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.

Correcting the link for non lemmy.world users. !unixporn@lemmy.world

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

Thanks for sharing! I’ll definitely be looking into adding this to my infra alerting stack. Should pair well with webhooks using ntfy for notifications. Currently just have bash scripts push to uptime-kuma for disk usage monitoring as a dead man trigger, but this should be better as a first-line method. Not to mention all the other functionalities it has baked in.

Edit: Would also be great if there was an already compiled binary in each release so I can use bare-metal, but the container on ghcr.io is most-likely what I’ll be using anyway. Thanks for not only uploading to docker hub.

They mostly do by default, which is pretty annoying. But there are ways around it. I’m currently self-hosting a Miniflux instance where I can set per-feed whether or not it will try to parse the full text of each article. Most of the time that works, but on the off chance it doesn’t I fall back to Morss by prepending the feed with http://fulltext/

I have reservations about running either the agent or portainer itself on something external to my lan.

I don’t feel like it’s safe enough personally either, so I just have portainer edge-agent nodes connected to the primary on my intranet through through vpn tunnels. I really, really would prefer not to ever open ports on my local firewall, but being able to monitor and control remote docker hosts is also pretty convenient, so my solution has been decent for me.

It’s available on 1.19.3. Using it with my Gitea instance currently. Behind a flag in the config.ini I believe. Not at all stable yet, and not feature complete compared with Github Actions, but I’ve done a bit of testing with it and it’s been pretty smooth sailing.

Man, I wish I could find a good colo solution that wouldn’t kill me with fees. VPS isn’t bad cost-wise, but I’d really like to be able to throw as much hardware as I want at it without paying $1k/mo.