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

It’s because the original image macro that this is based on was about piracy, saying something along the lines of “I bring a certain ‘just torrent it’ vibe to the conversion that the riaa just doesn’t like.”

Their reuse of the macro is indirectly an answer or a continuation of it that can be seen as acknowledging the original message.

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.

If you’re ok with just file storage sftpgo has been solid for me for years now. Does sftp ftp and WebDAV (like nextcloud). Webui isn’t as pretty but it’s fast. Mobile apps will be various sync apps with sftp or WebDAV support. On Android folder sync pro is pretty good for keeping documents and pictures backed up

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.

Full disclosure: I’ve never used 1Password so can’t really comment on it compared with others, but I’m currently running a selfhosted Bitwarden re-implementation (vaultwarden) and am generally pretty happy with it. I’ve only ever used LastPass as a password manager before (aside from a seeding algo back in the day), and while I really don’t like their business practices or security history, their extension has or at least had a bit better consistency on Firefox than Bitwarden does, at least with regards to detecting username/password fields and detecting when a new credential is being created and asking it to be saved automatically. That being said, it’s something that I can live with considering it’s free software. As far as I’m aware, in terms of features all the big players in that space are pretty evenly matched, though I do remember some advanced feature that 1Password offered over others; maybe related to privilege access management in enterprise.

Newsgroup.ninja, because I support fellow ninjas and pirates.

Have a backup block on Usenet Farm which I’ve basically never needed.

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.

Oh, I forgot it even had an invite code. It’s been quite a while since I registered. Thanks for reminding me!

probably ee3(dot)me. It’s register only though, and somewhat limited selection. No ads though

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.

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.

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.

Loving the new interface. Seems like it fixed quite a few of the small issues I’ve had with the UI. Subscribing to a new community from the sidebar is fixed on desktop. Expanding an image, then voting on the post doesn’t collapse the image anymore. Voting on posts and comments seems to be almost instant now (probably related to upgrade, but not 100% certain). The “Darkly-Compact” theme is amazing, much more like old.reddit. Haven’t seen anything about whether or not @TheDude devoted more compute resources to the instance, but everything seems so, so much more snappy than a few days ago. Read that @db0 somehow tweaked the query parameters for the PG database, which helped reduce the server load (announcement link here). Maybe that would be worth looking into as well to optimize even further.

Edit: Looks like @phiresky has been contributing to Lemmy on GH, I wonder if that’s what db0 meant. Though not seeing any commits directly related to DB queries.

I’m so conflicted rn. On one hand I hate Facebook but on the other I love cinnamon buns. Random app idea (you’re welcome), app on home screen and when pressed places order of 4 cinnamon buns for delivery. “Piping Hot Buns” coming soon to iOS and Android.