I decided to try Nextcloud after not using it for 10 years, and after testing it a bit I find myself turned off by the email (and other profile options) being visible to "everyone" by default.

I found how to disable the profile by default : email still visible Hide the email in profile settings of user manualy : still visible completely remove email : no notifications

In addition to that, from what I understand, even if I change the default setting to private the other profile options, they are automatically shared with anyone you connect to the Talk app?? I was really hoping to try it out, but that's another turnoff.

It does not seem to be a problem to most users so they have not done anything since 2019 about it (from the github issues and forum threads I found). It is an instant turnoff to me, I am questionning using it only for myself and use something else to share with family.... if you have a solution for the user info privacy, I am all ears.

I just want a multiuser file sharing app that works with authentik and works with android/windows/linux. Bonus points if it does not encrypt files on the server.

Edit to add : I tried seafile and it kept going down and corrupted a lot of files after an unexpected server shutdown. It shared the corruption to all the local files on every app/pc I had it shared to. Never figured out a way to restore the healthy files from a backup (that's a me problem but still not a fun experience). Thankfully I was the only user, I try to test out the apps a few months/year before sharing.

TLDR : what alternatives do you have to nextcloud or seafile ?

Hey everyone,

We've built an open-source, privacy-preserving alternative to Ring cameras using a Raspberry Pi Zero 2W (called Secluso). It uses end-to-end encryption to send videos from the camera to a mobile app, which is available both in Google Play Store and Apple App Store. We also support Obtainium for people that do not wish to use Google Play.

We've put in a lot of effort to make it easy to set up! You can set up our camera on your own Pi in less than 5 minutes with minimal technical expertise using our easy-to-use GUI deploy tool. Here are our setup guide and open source release.

The image shows a Pi in an official Raspberry Pi enclosure that you can use for your camera. We've also been working on a HAT for the Pi to add night vision, audio, temperature monitoring for safety, all in a compact form factor. You can see the HAT and an enclosure for the whole camera in the photo.

We've been working on this for almost 2 years now, and we look forward to we look forward to seeing what you all think!

GitHub: https://github.com/TechSquidTV/Cliparr

Major Updates:

• HLS Streaming (Now uses the media server's transcoded stream as the default source, which better matches expected behavior)
• Subtitle Burn-in. Use any font on your system to overlay subtitles on the output. Subtitles come from your media server; ensure to download or select them.

Assuming the user will not be connecting over vpn, but is both remote and non-technical, how would you expose Jellyfin to them securely?

For the past few years I’ve been building and maintaining website/blog at www.pragmaticcoding.ca. It has mostly about programming, and more specifically it’s ended up having a lot of content about JavaFX with Kotlin.

Lately, I’ve been spending all of my time building out my own homelab and self-hosting the services that I need. I’ve got a little stack of M910Q’s running in a Proxmox cluster with an HP T740 running OPNSense.

One of my big successes so far has been to replace my Google Home devices streaming music all over the house with a SnapCast network using RaspberryPi Zeros as the streaming clients. I've been working on documenting how to do this, and the result is a three part series that explains what SnapCast is, how it works and how to combine it with Mopidy to stream music around the house.

I have to admit that this one got away from me. It was all one article until I noticed that Jekyll was estimating it at oven 1/2 hour to read, which is way, way too long. So it became three parts, which also gives me the opportunity to release it over time, and make sure that each part is nice and clean before I post it live. Part I is an introduction to SnapCast and explains how it works and how to set up a SnapCast server in Proxmox.

If you're interested, take a read and let me know what you think.

Just made LiftTrace public after months of development. It's a self-hosted weightlifting / training log that runs in a single Docker container on your own hardware, with a PWA frontend and a signed Android APK. Sister app to NutriTrace under the same TraceApps umbrella.

What it does:

• Diary with sets, reps, RPE, warm-up flagging, supersets, rest timer
• Smart Add — type or speak your workout ("bench 3x5 @ 225, A1: curls 3x12, A2: pushdowns 3x12") and the AI parses it into structured sets
• Programs with mesocycles, weekly templates, coach prescriptions for trainer / athlete pairs
• Exercise library seeded from wger + Free Exercise DB (~1,500 exercises with images), plus your own custom uploads
• Statistics: volume, PRs, frequency heatmap, body weight trends
• OIDC SSO for Authentik, Keycloak, Pocket ID, Authelia, Auth0, Google, etc.
• Workout History Import from Strong, Hevy, FitNotes, and Jefit CSVs (so you don't lose your history switching over)
• Radio player built in for Subsonic / Jellyfin / Plex / Emby plus internet stations (because lifting and lockscreen media controls > switching apps mid-set)
• AI coach with live workout context — bring your own Claude / OpenAI / Gemini key, or point it at Ollama / LM Studio / any OpenAI-compatible endpoint
• Android app with offline-first SQLite, biometric sign-in, native ExoPlayer, optional WorkManager reminders

Self-hosted principles:

• AGPL-3.0, source is open, no telemetry, no central server, no analytics, no cloud sync to anybody else
• Single Docker container + bind-mounted volumes for DB and uploads
• Your data stays on your hardware. Back up with cp, restore with cp.

Quick start:

services:
  lifttrace:
    image: ghcr.io/traceapps/lifttrace:latest
    ports: ["3002:3003"]
    volumes:
      - ./data/db:/data/db
      - ./data/uploads:/data/uploads
    environment:
      - DB_PATH=/data/db/lifttrace.db
      - UPLOADS_PATH=/data/uploads
      - JWT_SECRET=change-me

If you haven't seen it yet, we recently made the announcement that starting July 1, 2026, the price of "Jellyfin Premium+ One Super Unlimited (with Ads)" will increase to $0.00 USD*. There has been a lot of enthusiasm regarding charge backs, and we're simply blown away by the community's response.

As we've had a high volume of inquiries, I'd ask if you could please wait until I'm off the support email shift to reach out about this issue. I've attached our schedule so you'll know when it is safe to reach out.

Thanks, and happy streaming!

*Example price in USD. Exact pricing in other currencies may vary.

Honest question, because I know multiple people who are not looking to jump ship since they already have the Plex Pass.

I wanted to shared my enthusiasm, which makes me feel like a little boy (despite me being 50+) fascinated by how such complex systems can be managed so easily by novices. I started using Proxmox recently. I had a machine running one VM with various docker images installed. But NVMe was tiny. So I setup another node and got it to share the same NFS share on the NAS, where I had saved full backups of the VM. Once added the NFS share to the new node (with a bigger ZFS local partition) I simply restored the VM from the NFS share that had been backed up from the original node. It seemlessly imported and started. Then I cloned on the new node so that I could get it on the new ZFS partition. Now the next task is to get a bigger NVMe on the original machine, install Proxmox from scratch, and add to cluster so that it shared the backup NFS share. I just then need to understand how to get HA up and running so that VMs are always synced flawlessly. Proxmox is super brilliant. I feel like I have a data center at home :-) I could not imagine this system was so flexible and relatively easy to use. The people that deliver and contribute to this stuf are super cool. A couple of proxmox nodes, a Truenas scale NAS and a good backup strategy and your data is really safe and rock solid ... I hope :-)

cross-posted from: https://discuss.online/post/40125235

Picked up an ix500 scansnap and wondering about suggested workflows for going paperless. My intention is to scan a bunch of documents, but haven't delved deeply into how this will actually flow on the software level. I know I'll need to OCR the scanned documents, and my base setup is:

• Pi with SSD storage running compose version of Paperless-ngx to filesystem mounted folders.
  • Folders can also be accessed over Samba
• ix500 statically assigned over wifi as network scanner.
• A literal filing cabinet, for things I should keep physically.
• Ubuntu computer for browsing

I feel a bit overwhelmed, but am excited to get started. Will be scanning personal document, work docs, whatever else I need to digitize and recycle. All suggestions appreciated!

So I go starlink as Openreach can't reach us with full fiber, in the starlink app I looked at our first month's data and we had used nearly 500gb. This month so far, we are up to 765gb.

Is that a lot for a homelab house?

I also don't have all my services here, I have most at OVH.

Features

• Bulk Food Import via paste JSON or upload CSV (Settings → Import & Export)
• Live nutrition preview on the Add to Diary sheet (macros update with portion / unit / servings)
• Mass-aware unit conversion when scaling nutrition (g ↔ oz ↔ lb, ml ↔ cup, tsp ↔ tbsp)
• Custom Units in Settings ("shot", "scoop", "stick", etc.)
• Scan Label: snap a photo of a nutrition label and the AI Assistant fills in the values
• Smart Share / View on OFF: existing Open Food Facts products link straight to their wiki page for editing; new ones get a Share button to contribute back
• Connection status banners across every integration with one-tap Test / Sync / Disconnect
• Settings auto-save by default; no Save button to remember
• Day rollover at midnight when the app stays open overnight
• Barcode scanner now fully on-device on Android, no Google Play Services required (works on GrapheneOS / CalyxOS / e/OS)
• Custom nutriment order from Settings is reflected everywhere (food editor, meal editor, diary nutrition bar)
• Vitamin D, Calcium, Iron, and Potassium visible by default on new installs (FDA Nutrition Facts label mandatory fields)
• Svelte 5 + Vite 6 + Express 5 + bcryptjs 3 framework upgrade (main bundle ~22% smaller)

Fixes

• Disabling user management no longer triggers the setup wizard on every reload (#34)
• Data APIs in single-user mode no longer return 503 "Setup required" on every call (#34 part 2)
• Single-user mode: only the first food item added each day was visible in the UI. SQLite quirk on null user_id. Includes a one-time migration that recovers items already in the database (#37)
• Food saves on Android no longer duplicate the previous food (#32)
• "Most Used" / "Recently Used" food sort on Android now reflects real usage
• MyFitnessPal Reports → Export CSV imports cleanly now (aggregate-per-meal shape)
• Wellness scores refresh if today's sleep finishes syncing after the morning snapshot
• Import Nutrition History action row no longer overlaps the duplicate-date radios (#33)
• Barcode scanner no longer gets stuck re-opening the camera after a scan
• Barcodes that don't match anything in OFF now drop you in the food editor with the code prefilled instead of a dead-end toast, so you can contribute the product back
• Open Food Facts contribution now sends correct per-serving values and uploads your product image (both were silently broken)
• AI Assistant respects AI_ENABLED=true and the full AI_* env-var set; toggle, settings card, and chat all honour the proxy (#36)
• kcal / kJ values are consistent everywhere now: food editor, diary footer, meal totals, statistics, goals, weekly summary email, push notifications (#38)
• AI Assistant Gemini models updated to 2.5 Flash + Lite (Google retired 2.0 Flash and 1.5 Flash)
• nodemailer updated to 8.0.7 (patches an SMTP command-injection advisory)
• Several smaller things, see the full changelog

Signed APK + docker image on the release page.

Self-hosted, AGPL-3.0, no telemetry, no account needed. docker compose up and go.

Hi all! i finally come around publishing a small side project i am running at my home for the last few years. This past month i have revamped it by rewriting the C++ backend and improving the web UI (single page HTML+CSS+AlpineJS) for a broader public.

LazyNVR is a different take on hosting webcams and centralizing access to them. Instead of working on the cameras feed, which is CPU/GPU heavy and doesn't scale much, it relies on cameras on-board capabilities to detect motion and upload recorded videos to your own server.

If you own IP cameras from brands like Dahua, Reolink and many others, you can leverage their on board motion detection capabilities and off-load your server computational power using LazyNVR.

I have some 15 cameras and tools like Frigate or MotionEye just kill my server CPU, but all my cameras can detect motions and automatically record a video and upload it to my server using different protocols (like FTP, sftp, and such). So LazyNVR was born.

The server is written in C++ and basically detect incoming videos, recode (without re-encoding) them to an MP4 web streammable format, and store them well sorted. It will also keep your incoming folders clean and purge stored videos when they are too old. The server will also fetch and refresh still live images from the cameras.

The client is a WEB GUI, actually a single HTML file with CSS and some AlpineJS, which will show the still live images and the list of all the recorded videos letting you download or view them directly.

I am running over 15 cameras from my RaspPi with basically 0% CPU overhead.

I have published LazyNVR on Codeberg (here https://codeberg.org/LazyNVR/lazynvr-sources) because well, i think it's better than GitHub. And there is also a pretty lazy web site on https://www.lazynvr.it/ (which mostly redirect to Codeberg).

Currently there are docker images for AMD64 and ARM64, but it's pretty easy to compile directly, with the provided instructions in the Codeberg Wiki.

Please, feel free to try it!

Mandatory AI disclaimer: i don't use AI for coding. Zero code (C++ or Javscript) has been written by or with AI support in this project. I have used AI extensively for the CSS stuff that i hate, but reviewed and mostly edited it anyway. I have also used AI for research and to write the dockerfile faster, since i am no docker expert. I have personally written the dockerfile anyway, and personally tested as well. The logo has been created with AI, probably it shows.

So I've gotten to the point where my homelab has moved to a fun way to mess around with tech to starting to replace things like google photos and OneDrive. So as my next project I plan to add resiliency and backup solutions as low-cost/efficiently as I can. I'm thinking that 3 physical machines is a good and safe next step.

I purchased 7 used 4TB SAS drives for my planned storage as I was able to get them for a pretty good deal.

I plan to have a second machine in another state with family that I can setup to run as an off-site backup while the third can run at home or encrypted and put in the cloud (existing OneDrive or b2/S3 glacier) but cloud is obviously a long term cost/subscription.

Ente, a encrypted Google photos replacement, wants three S3 buckets in a production environment, I currently have 1. Until now I've been mirroring photos to Google photos and I have manual exports on my PC/external drives.

So my questions are:

1. What's the most cost effective way to backup proxmox VMs and the trueNAS storage while at the same time being able to move ente from "development" single S3 to the recommended S3 buckets?
2. Hardware is expensive, inefficient and/or loud. What can I get away with that's sub $100 and will be quiet enough to exist in living spaces?
3. Should I add resiliency for networking/DNS/etc on another device or just focus on making these devices just backups?
4. Automation and deployment of additional software. I'm comfortable with docker-compose and see recommendations for kubernetes/Ansible/k3s but I'm not sure if those are worth doing vs just unattended upgrades for security and manual upgrades that I've been doing.
5. Exposing and linking the devices. I have a consumer router w/o layer 3 and ipv6 still scares me with big numbers. So far, I've just exposed wireguard but eventually I need to start exposing ente and other services... For now, and the backups should I create a separate wireguard VPN service as a site-to-site or is there a better option?
6. If I host an S3 bucket at another location, ente needs it to be exposed to the internet as the app communicates directly with the S3 buckets: https://ente.com/help/self-hosting/administration/object-storage?

For hardware: Last I checked arm has some catching up when it comes to proxmox and trueNAS so I'm thinking an old tiny/mini office PC however there's the added complexity of getting SAS drives connected to them and looking decent. If I can source a midsized office PC locally I can probably recreate my existing setup with the off-site backup. I do have a 8GB CM4 thats underutilized since all it's doing is making my ancient printer work wirelessly via cupsd.

My current setup is a single ancient optiplex running proxmox. Within proxmox I have a debian VM running my docker stack and trueNAS with my "large" storage pool

• Dell optiplex 7010
  • Proxmox
    • Debian - docker/portainer - smb mounted TrueNAS
      • Ente Photos w/ S3 object storage via Garage
      • network stack (Adguard, nginx proxy manager, wireguard easy)
      • other services with mounted DB or media stored on trueNAS
    • TrueNAS - 2x4TB HDD via pcie passthrough/HBA card
      • SMB fileshare
      • Garage S3 bucket
    • Windows sever/AD (mostly for learning and managing windows devices)

TL;DR how do I securely/cheaply implement backups and S3 redundancy across multiple locations now that my homelab has important stuff.

cross-posted from: https://lemmy.world/post/47170057

I just stumbled this fork that seems focused on giving Linux hosts a good boost. It promises no-headache Virtual Display support out of the box, and Bazzite seems like the primary target.

So you don't want to port-forward on your home router or have Cloudflare decrypt all your traffic? Check out Towonel.

Most open source Cloudflare Tunnel alternatives involve setting up a VPS, terminating TLS there on a reverse proxy, then setting up a Wireguard tunnel to your server at home.

Towonel is different: it does not decrypt your traffic on the VPS and you can easily share one, so not every self-hoster has to buy and maintain a VPS.

Check it out!

Mastodon link: https://gts.erwanleboucher.dev/@eleboucher/statuses/01KS4YNA2SYMSP0FSKJVNJA155

Voiden is an offline-first, git-native API tool built on Markdown.

Instead of keeping API requests inside a cloud workspace, Voiden stores them as .void files that can live with your codebase, be versioned in Git, reviewed in PRs, and reused across a team.

We have now released the beta of @voiden/runner, a headless CLI for running those .void files outside the desktop app.

The runner executes the request, prints the result, and exits with a standard exit code that CI systems can use.

Important bits:

• runs on Node.js 18+
• works in terminal, CI/CD, Docker, and cron jobs
• supports REST, WebSocket, gRPC, and GraphQL
• supports JSON and CSV output
• supports request chaining through runtime variables
• works with core Voiden plugins like scripting, assertions, faker, advanced auth, and GraphQL

This is still beta, so APIs and flags may change.

The goal is to make .void files executable API workflows, not just files used inside the desktop app.

Github: https://github.com/VoidenHQ/voiden

Voiden CLI Runner : https://github.com/VoidenHQ/voiden/tree/beta/packages/voiden-runner

Visit Voiden here : https://voiden.md/

I don't know a ton about the internals of federated systems, it's been on my todo list for a while but it keeps getting pushed down by other things. But I still like that the fediverse exists and I'd like to pitch in, even if it's only a few bucks of processor time / month.

Are there compute tasks that could be offloaded to a network of volunteers? Monitoring tools that could be run from outside the system? Something else I'm not thinking of?

So, I've been running offsite copies to OVH S3 bucket via PBS running as an VM but I ran into an issue that verification of the backups is so slow that they're practically unusable.

Copies run nightly and I've set the storage to keep last 4 copies in place. Bigger VMs, like my immich-instance with a bit over terabyte of data, take several days to verify and logs show data rates at around 5MB/s or less. So, with the current schedule I'm running it'll mean in practise that backups expire before they're verified.

I could keep the copies longer, but that'd cost more, or run copies less frequently, which risks losing data if hardware fails at unfortunate moment (which it most likely will). Tuning settings are on default and based on what I've read, adding more runners wouldn't really help that much.

PBS VM itself shows very little load on proxmox monitoring and I've got plenty of bandwidth to use, so the verification shouldn't have any bottlenecks on my end at those speeds. Cache usage is at around 60% with ~30GB of total space available.

Does anyone have any ideas on how to speed that up? Or should I just give up and do something totally different? I attempted to run backups to Hetzner storagebox over cifs-mount, but that's pretty much the same or worse with performance.

Plex has announced a massive price increase on the service's Lifetime Plex Pass. On July 1, the lifetime subscription option will go from $249.99 to $749.99, an increase of 200%. The price hike will only apply to new subscribers, with no changes to monthly or annual subscription pricing.

Just wanted to share my feelings about the arr* stack, will keep it short !

First, thanks to all those beautiful people giving their free time to work on all thoses services ❤️ !

At first I wasn't that impressed and didn't understood all the hype arround all thoses services and only used sonarr to rename my files I had manually imported. It did a great job as a file renamer service, however I was still managing everything manually from hard links to qbittorrent organization creating in the end a total messed up file system with a lot of duplicated hardlinks and files scattered in different directories, renamed differently, etc.....

Also, after the most known french piracy tracker had been hacked and shut down (finally !), a lot of new trackers opened like wildfire and had over 10 trackers to keep an eye on. Searching the web, I came across Prowlarr and seeing how It connects directly to sonarr I got curious.

That's the exact moment when I finally unsterstood what's all the hype about the ARR stack ! My god, what an amazing piece of software stack...

First came jellyfin, sonaar, then prowlarr, radarr, seerr and now I discovered profilarr. It's amazing to see how everything perfectly communicates with each part of the stack and everything is perfeclty automated and god does it work well... I'm impressed and still baffled how something so good is free and open source !!

Im still scratching the surface of this powerfull stack, but does it feel good to just ask seerr and after a few minutes having my media perfectly organized in qbittorrent, filesystem directories, renaming scheme, hardlinks, quality profiles, config synchronization......... 💥🤯

It does have it's own quirks right and there, and can become kinda weird if you do not know what you are doing (thanks Trash guides ❤️❤️) and seeing from all the issues the arr stack seems to hit a wall with the current code implementation. But IDK, i'm not a programmer so I may be wrong here.

And there seems always something new to complement the arr stack !

So that's it :) Just wanted to share my feeling and appreciation with all of you ! Happy self-hosting !!