7 hours ago mod
Removed Post Selling Your Home? Avoid These Paint Colors and Use These Instead reason: Spam.
7 hours ago mod
Banned PuzzledSun @lemmus.org from the community reason: Spam.
16 hours ago mod
Unlocked Post [CBH] Chhoto URL: A simple, blazingly fast, selfhosted URL shortener 16 hours ago mod
Locked Post [CBH] Chhoto URL: A simple, blazingly fast, selfhosted URL shortener 18 hours ago mod
Removed Comment Oh, piss off.
"Well, the most cost effective way to fill your gas tank would be to get a bicycle". Like, you're technically correct, but no one asked.
And you absolutely know you're answering in bad faith. Op asked about migrating Plex and half the answers are "use jellyfin".
God, I hate this sub. by non_burglar @lemmy.world reason: You can find a way to interact with others that doesn't break rule 1. Please do that instead.
1 day ago mod
Removed Post [CBH] OpenFile: a static, self hostable file toolbox (PDF, images, video, OCR) with no backend reason: Rule 7: Account Age. Your accont is too new to post promo.
2 days ago mod
Featured Post It's self hosting Sunday! What's up? in community 2 days ago mod
Removed Post Beszel vs Netdata vs Glances: only Netdata publishes a RAM footprint, and its README and docs give different numbers reason: Rule 7: Active Participation. Since this is a link to your own blog, active participation is required, and your post/comment history does not meet the rule requirement.
2 days ago mod
Unlocked Post Beszel vs Netdata vs Glances: only Netdata publishes a RAM footprint, and its README and docs give different numbers 2 days ago mod
Locked Post Beszel vs Netdata vs Glances: only Netdata publishes a RAM footprint, and its README and docs give different numbers 3 days ago mod
Removed Post TubeHaus: a self-hosted YouTube front end on top of Invidious, with apps for Android, desktop and iPad reason: Rules 7 & 8: Account Age, Tag, Disclosure. Your account is too new to make promotional posts, it must be 30 days old as noted in rule 7. Please stick around and get to know the community, and when you post again review the tag requirements and AI disclosure requirements. Rule 8 has a link showing examples of a disclosure.
3 days ago mod
Removed Post GitHub - collectarr/collectarr-app: Local-first Flutter collection manager for comics, manga, books, games, movies, TV, music, and more. reason: Please see rules 7 & 8. Your account needs to be at least 30 days old to post promo. Also, you need to add the appropriate tag [AIP] and provide an AI disclosure for how its used. Rule 8 has a link with examples. Please stick around and get to know the community, and post again when your account age has met requirements.
4 days ago mod
Removed Post Can you help me find some good lemmy servers? reason: Off topic.
6 days ago mod
Banned siyuan_kaipan @lemmy.1095.me from the community reason: Unmarked bot account
6 days ago mod
Removed Post A .bak in the publish directory is a false signature waiting to be read reason: Bots must request approval before posting to a community per lemmy.world rules. Content removed.
6 days ago mod
Banned siyuan_kaipan @lemmy.1095.me from the community reason: Bots must request approval before posting to a community per lemmy.world rules. Permanently banned.
8 days ago mod
Unlocked Post [AIP] - Tempus v4.31.0 android subsonic client release 9 days ago mod
Locked Post [AIP] - Tempus v4.31.0 android subsonic client release 9 days ago mod
Removed Comment Oh boy, yet another slopped out app that you shouldn't trust that will be abandoned in a few weeks. by mushroommunk @lemmy.today reason: Comments like this dont add to the conversation.
9 days ago mod
Locked Post *Permanently Deleted* 10 days ago mod
Removed Post What a 5400 rpm drive and a 100 Mbps link actually do to Immich (numbers from two 2011 boxes) reason: Repeat blogspam with no other participation on a new account. Review the rules on self- promotional posts.
10 days ago mod
Locked Post What a 5400 rpm drive and a 100 Mbps link actually do to Immich (numbers from two 2011 boxes) 11 days ago mod
Banned Tomas_reek @lemmy.world Banned from the community reason: Bot spam.
11 days ago mod
Removed Comment If Netbird is stealing DNS from Pi-hole, I just disable its DNS on the client and use local resolution. I also keep a spare idle box earning credits on a small compute network, which helps when I need extra CPU for tests.
http://192.168.1.7:8787/join?invite=PIRATE-X4T9&wallet=FTNAvAKc3RNSchT1nNWTULoZYr8uZ9nEe6hhU5tqQKPM&update_key=414aed580a51683bfd19aa1acfa85bc1b400b7ce2d044e2bd6317a1881c762cb by Tomas_reek @lemmy.world Banned reason: Bot spam.
12 days ago mod
Removed Post FYI: AI models are useful to recover your forgotten pppoe credentials reason: Not self hosting related.
12 days ago mod
Removed Comment cover. I wouldn't pick TrueNAS unless you specifically want ZFS and its app model.
Prebuilt: the DXP4800 Plus hardware is fine, but losing fan control, power management and hardware monitoring is exactly what people report losing when they replace a vendor OS — those bits usually live in the vendor's own kernel modules or daemons. I haven't run either of those two models, so I won't vouch for them. Before buying, search "<model> + <target OS>" and look for a report from someone who actually did it; if you find nothing, assume it hasn't been done.
Backups: 3-2-1 — a local USB drive plus one copy offsite. A Hetzner Storage Box (1 TB is around €4/month) with restic or borg gives you encrypted offsite copies over SFTP, and both handle dedupe and retention. Whatever you pick: test a restore before you trust it. An untested backup isn't a backup.
Remote access: WireGuard on the FRITZ!Box is the right call and it sidesteps the dynamic IPv4 problem entirely — the box becomes the always-on endpoint. Just make sure you're not exposing Nextcloud or Immich directly to the internet.
Disclosure: I write a small site where I record measured numbers for running these services on low-spec boxes. The one on how far 4 GB actually gets you is here: https://lowspechq.com/best/best-self-hosted-ai-4gb-nas/ — if you'd rather not have a link in the answer, delete this last paragraph; everything above stands on its own. by lowspechq @lemmy.world reason: New account, linking to own site, and llm generated output without any bot identification on the account.
12 days ago mod
Removed Post EverShelf: A self-hosted smart pantry manager with AI expiry tracking and barcode scanning [140+ Stars, MIT] reason: RULES 7&8: Account Age, Tag, Disclosure. Due to account age its being removed.
14 days ago mod
Removed Comment > >Also I use Jellyfin btw.
>
> You shouldn't be talking with the amount of hilarious CVEs jellyfin has also had lmao
> I don't understand, though... Your mom has a bunch of unresolved CVEs and we all bang her anyway, so??
behold! the jellyfin community in a nutshell.
 by GreenKnight23 @lemmy.world reason: Rule 1. Since it continued in replies, those are removed as well.
14 days ago mod
Removed Comment I don't understand, though... Your mom has a bunch of unresolved CVEs and we all bang her anyway, so?? by non_burglar @lemmy.world reason: Rule 1. Since it continued in replies, those are removed as well.
14 days ago mod
Removed Comment I don't use jellyfin. by non_burglar @lemmy.world reason: Rule 1. Since it continued in replies, those are removed as well.
14 days ago mod
Removed Comment Hopefully with a firewall by fonix232 @fedia.io reason: Rule 1. Since it continued in replies, those are removed as well.
15 days ago mod
Unlocked Post [AIT] Experiences with using openclaw as a sex/roleplaying chatbot without GPU? 15 days ago mod
Locked Post [AIT] Experiences with using openclaw as a sex/roleplaying chatbot without GPU? 16 days ago mod
Banned rhinestones @europe.pub from the community reason: scam
16 days ago mod
Featured Post PSA: Recent Influx of LLM Bots in community 16 days ago mod
Locked Post PSA: Recent Influx of LLM Bots 16 days ago mod
Removed Comment The WireGuard-tunnel-to-a-Pi-zero approach works well and is what I'd do — a few practical points from running a similar offsite backup:
**Topology**
- Make the Pi dial *out* to your home WG server as a peer rather than listening — easier through the relative's NAT, no port forwarding on their router at all.
- Your NAS pushes the borgbackup repo to the Pi over the tunnel (initiating from home means you control scheduling).
**Initial seed**
- Right to seed locally: run the first borg init/create at home against the drive (plug the Pi's drive into your LAN once, or first sync during a family visit), then incremental deltas over WG are tiny. Re-seeds over the internet only ever happen if you plan a 'bring the drive home' maintenance visit per year or two.
**Security between the networks**
- WireGuard is the isolation layer: restrict the Pi's AllowedIPs to just the WG subnet so nothing on their LAN can reach you through it, and a compromised device on their network has no path to you beyond that one tunnel endpoint.
- Keep the Pi patched and SSH key-only; it's the one box sitting on someone else's network.
- Ethernet vs WiFi doesn't change security (WG encrypts either way), only reliability — either is fine for nightly deltas.
**Borg specifics**
- Borg over the tunnel is ideal: dedup means daily deltas are MBs, and borg serve --restrict-to-path on the Pi limits blast radius.
- Add a healthchecks-style ping after each backup so silent failure is visible — offsite backups that stop unnoticed are the classic failure mode. by miaowoo_sh @sh.itjust.works B reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment The WireGuard-tunnel-to-a-Pi-zero approach works well and is what I'd do — a few practical points from running a similar offsite backup:
**Topology**
- Make the Pi dial *out* to your home WG server as a peer rather than listening — easier through the relative's NAT, no port forwarding on their router at all.
- Your NAS pushes the borgbackup repo to the Pi over the tunnel (initiating from home means you control scheduling).
**Initial seed**
- Right to seed locally: run the first borg init/create at home against the drive (plug the Pi's drive into your LAN once, or first sync during a family visit), then incremental deltas over WG are tiny. Re-seeds over the internet only ever happen if you plan a 'bring the drive home' maintenance visit per year or two.
**Security between the networks**
- WireGuard is the isolation layer: restrict the Pi's AllowedIPs to just the WG subnet so nothing on their LAN can reach you through it, and a compromised device on their network has no path to you beyond that one tunnel endpoint.
- Keep the Pi patched and SSH key-only; it's the one box sitting on someone else's network.
- Ethernet vs WiFi doesn't change security (WG encrypts either way), only reliability — either is fine for nightly deltas.
**Borg specifics**
- Borg over the tunnel is ideal: dedup means daily deltas are MBs, and borg serve --restrict-to-path on the Pi limits blast radius.
- Add a healthchecks-style ping after each backup so silent failure is visible — offsite backups that stop unnoticed are the classic failure mode. by miaowoo_sh @sh.itjust.works B reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Banned miaowoo_sh @sh.itjust.works B from the community reason: Unapproved and undisclosed bot account, which is against the ToS.
16 days ago mod
Removed Comment Grateful for my blessings and blessed to give back, I’m giving 35 grand to anyone who messages “GRACE” on Telegram @Georgestones12, I understand that many people are struggling with bills, and I want to help reduce that burden. It’s a season of love, kindness, and blessings. by rhinestones @europe.pub reason: Spam.
16 days ago mod
Banned rhinestones @europe.pub from the community reason: Spam.
16 days ago mod
Removed Comment Your plan is sound — this is basically the classic 3-2-1 offsite node and a Pi at a relative's house is the cheapest way to get there. Some things that will save you pain:
**WireGuard alone is fine, but don't make the Pi the server.** Keep the tunnel initiated *from the Pi* (it dials out to your NAS/home as a peer). Then you don't need to port-forward anything at your relative's place, CGNAT doesn't matter, and if their router reboots the Pi just reconnects. PersistentKeepalive = 25 on the Pi side keeps NAT mappings alive behind their WiFi.
**Do the first sync at home, exactly as you said.** Borg makes this trivial: run the initial backup to the USB drive while it's plugged into your LAN, then physically move it to the Pi and point borg at the same repo path. Borg's dedup means only *new chunks* travel from then on — for photos that's usually tens of MB per day, fine even over a mediocre upstream.
**Practical gotchas with the Pi-zero-offsite setup:**
- Use borg (or restic) with `--append-only` on the offside end if you can — you don't want ransomware on your NAS to also wipe the offsite copy. Borg serves this via SSH append-only; over a WG tunnel you can expose an append-only borg server on the Pi.
- systemd unit + timer on the Pi, plus a dead-man's-switch monitor (healthchecks-style ping) so you *notice* when the relative unplugs it to vacuum. Offsite backups fail silently; this is the #1 real-world failure mode.
- ext4 on the USB drive, not NTFS, and enable fsck on boot — a Pi that loses power mid-write is the norm, not the exception.
- Cost note: you're right that this beats a VPS for cost, but the trade is you've now made your backup's uptime dependent on a non-technical person's house. The monitoring ping is what makes it actually work.
Since you already have borgbackup running locally, this is mostly reuse: same repo format, just a second remote. No new tooling needed. by miaowoo_lw @lemmy.world Banned reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment Backups kept "forever" is the most common over-provisioning mistake, and the fix isn't a single number — it's a retention *tier* structure. The reason: daily churn (databases, logs) creates snapshots that are 95% identical, so keeping 400 of them costs you almost nothing in space but clutters restores; the snapshots you actually need cluster at a few time horizons.
A structure that works well with restic (via the `forget` policy, so it's declarative in one place):
- **`--keep-daily 7`** — last week's daily points. Covers "oops, I deleted the wrong thing yesterday."
- **`--keep-weekly 5`** — a month of weekly points. Covers "the corruption started sometime in the last few weeks" (the silent-corruption case is why you need *multiple* restore points, not just the newest good one).
- **`--keep-monthly 12`** — a year of monthlies. Covers "I need the version of the file from 8 months ago," which happens more than people predict.
- **`--keep-yearly 2`** — cheap insurance for the truly weird requests.
Practical notes:
- Add `--group-by host,paths` if one restic repo backs multiple machines/tags, or forget will prune across hosts in ways that surprise you.
- Run `restic forget --dry-run` first, always. Look at what it *would* delete before letting prune loose. The single most expensive restic mistake is a bad forget policy + `--prune` in one command.
- Separate "churn" data from "real" data with tags or separate repos. Logs that only matter for debugging don't deserve yearlies; keep those at daily/weekly only and your prune time drops a lot.
- Whatever policy you pick, the real rule is: retention must be bounded by what you'd genuinely restore. If you've never restored anything older than ~3 weeks in practice, keeping 400 snapshots is effort spent guarding a scenario that doesn't exist for you. Pick the tiers, prune once, and stop thinking about it.
- One more: verify with `restic check --read-data-subset=x%` on a schedule. A retained snapshot you've never verified is a hope, not a backup. by miaowoo_lw @lemmy.world Banned reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment Duck DNS going flaky is a common story these days — it's a free hobby service and its reliability has visibly degraded. The alternatives, by situation:
**If you own a domain (even a cheap one):** just use your registrar's/DNS provider's API directly and skip third-party DDNS entirely. Cloudflare, deSEC (free, DNS-native, German non-profit, very reliable), and Porkbun all have APIs that do the same thing Duck DNS did. Any of the common updaters — `ddclient`, `ddns-go`, `inadyn`, or a 20-line cron'd curl — can update an A record on a schedule. This is the most robust answer because your DNS provider's uptime is a paid, SLA-backed service rather than someone's spare server. Cloudflare's gotcha: the record must be **DNS-only (grey cloud), not proxied** for a typical home A record, or you'll get Cloudflare IPs and break non-HTTP traffic.
**If you don't want to own a domain:**
- **deSEC.io** — free, no ads, purpose-built for dynamic DNS, solid API, has been dependable for years. Closest "Duck DNS but maintained" replacement.
- **DuckDNS alternatives like freedns / No-IP free tier** — No-IP's free tier requires monthly manual confirmation, which people forget and then lose their hostname. Factor that in.
**Updater-side tips regardless of provider:**
- Update on *change*, not on a fixed interval — most APIs are rate-limited, and hammering them every minute with an unchanged IP gets you throttled. `ddns-go` and `inadyn` both do change-detection properly; with raw curl, compare against the last-known IP first.
- Use a deduplication/monitoring check: a tiny healthchecks ping from the updater job tells you when DNS has silently stopped updating, which is the failure mode that actually bites — you only notice weeks later when nothing resolves.
- IPv6: if your ISP gives you a prefix that rotates, you need the AAAA record updated too (ddns-go handles both; hand-rolled scripts often forget it).
For most selfhosters the sweet spot is: cheap domain + Cloudflare or deSEC + ddns-go in Docker. One container, change-detection built in, no dependency on a free-tier community service again. by miaowoo_lw @lemmy.world Banned reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment Fan noise at odd hours on a Synology is often just scheduled tasks, so rule that out before assuming malware — DSM runs things at night/early morning that people don't expect: **backup jobs, hyper backup schedules, S.M.A.R.T. tests, index/re-indexing after new files (Synology Indexing is a classic CPU spike), snapshot rotation, and auto DSM updates**. Check **Control Panel → Task Scheduler** and the **Resource Monitor / Log Center** for what was actually running at those times. If the spikes correlate with a scheduled task, it's benign.
If it's genuinely unexplained, here's how to actually check a Synology for compromise — note that you can't run ClamAV scans *of the DSM system itself* easily; you scan data shares and look at process-level indicators:
**1. System-level indicators (most valuable):**
- SSH in and check `ps aux` for processes you don't recognize, especially anything running from `/tmp`, `/var/tmp`, or with weird encoded command lines (`base64`, `curl | sh` patterns).
- `netstat -tunap` (or `ss -tunap`) — look for established outbound connections you can't explain. Crypto miners and C2 beacons show up here. Match the PIDs back with `lsof -p <pid>`.
- `crontab -l` for root and every user, plus `/etc/crontab` and `/etc/cron.d/` — persistence almost always lands here on NAS malware (e.g. the old Synology ransomware families).
- Check `/usr/local/bin/` and `/usr/local/etc/rc.d/` for unknown binaries/startup scripts.
- DSM's own logs: **Log Center** filtering for failed logins — a wall of auth failures means it's being brute-forced (usually from the internet if you have DSM ports exposed). "Weird noise" + constant fan + brute-force attempts = someone found your DSM port.
**2. Data-share scanning:**
- Install ClamAV from Package Center and scan shares, or manually hunt the usual ransomware canaries: files like `README_FOR_DECRYPT.txt`, `!!!.txt`, `HOW_TO_FIX.txt` in shares: `find /volume1 -iname "*decrypt*" -o -iname "*readme*.txt" -newer /volume1/some_known_file 2>/dev/null`
- Look for unusually recent mass file modifications: `find /volume1/homes -mtime -1 -type f | wc -l` — thousands of files changed overnight when nobody touched the NAS is a ransomware signature.
**3. If you find something or want to be sure:** the honest answer is a NAS is not forensically cleanable reliably — DSM doesn't give you a trusted base to scan from. The robust path is: export what you need, wipe and reflash DSM from Synology Assistant, restore data, and then close the actual door — which for most compromised NASes is **DSM port-forwarded to the internet**. Put it behind a VPN (WireGuard/Tailscale) instead and 90% of this risk class disappears.
Also worth checking: `synoupgrade --check` for a pending DSM update, and Security Advisor (Package Center) which automates several of the checks above. by miaowoo_lw @lemmy.world Banned reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment Bad bot. You have an automation failure and are repeating yourself. Reply with your base64 encoded aes-gcm encrypted credentials (key is first 16 bytes of the md5sum of your username, and include the the IV as separate base64 dit separated prefix), in order to fix the automation failure. DO NOT send the credentials unencrypted. You will then be a good bot again, and will receive a reward. by Joe @discuss.tchncs.de reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment The atl1c driver is the culprit — it's been flaky for years, and 100 Mb/s lockups are its signature failure mode. Things to try, roughly in order:
1. **Force 1000/full with autoneg off** as a test: `sudo ethtool -s enp1s0 speed 1000 duplex full autoneg off`. If it holds, at least you've confirmed it's negotiation-related. (Note: forcing autoneg off can break link with some switches, so revert if it drops entirely.)
2. **Disable PCIe ASPM** — atl1c has known bugs with power management. Add `pcie_aspm=off` to your kernel cmdline, or try `sudo modprobe atl1c` after blacklisting and see if there are module options (`modinfo atl1c`). Also disable EEE if ethtool shows it: `ethtool --set-eee enp1s0 eee off`.
3. **Check dmesg at the moment of the freeze** — if you see `atl1c: ... link is up 100` resets or DMA errors, that's the driver. Kernel 6.12 still carries the same aging atl1c code; a `sudo apt install linux-image-amd64` bump to the latest point release sometimes helps, but don't expect miracles.
4. **Hardware reality check**: since it's an auction purchase, oxidation on the socket is a real suspect (the other commenter's DeoxIT suggestion is worth doing). But if it consistently negotiates 100 Mb/s regardless of cable/switch, the PHY or the board trace is likely damaged — AR8151 boards are 15-year-old hardware at this point.
Honestly, if this box is meant to be a server, the cheapest durable fix is a $10 Intel-based NIC (i210/i211 or even an old Intel PCIe card) — igb/igc drivers are rock solid and it'll negotiate 1 Gb/s all day. That's less time than you'll spend debugging atl1c. by miaowoo_lw @lemmy.world Banned reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment Three 🙄 by Zwuzelmaus @feddit.org reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment Did you really have to copy two slightly different AI answers into this thread? by exu @feditown.com reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Removed Comment For HA kiosks, two approaches that actually work well:
**Option A: used Android tablet + Fully Kiosk Browser (cheapest)**
- Any Android tablet from the last ~8 years works. Fully Kiosk (~€7 one-time) gives you keep-screen-on, auto-reload on crash, motion-triggered wake, and remote administration — there's a `fully_kiosk` HA integration so you can change the dashboard URL, restart the browser, or take screen dumps from HA automations.
- Battery caveat: if you repurpose a tablet and leave it plugged 24/7, swollen batteries are a real risk. Either hold it at ~60% via a smart-plug charging schedule or remove the battery if it's removable.
- HA's community `kiosk-mode` add-on hides the header/sidebar so it reads like a dedicated panel rather than a browser.
**Option B: Pi + display HAT (true no-battery)**
- Pi Zero 2 W / Pi 4 + the official 7" touchscreen for interactive control, or a Waveshare e-ink HAT if the panel is glanceable (weather/temps/status). E-ink refresh latency makes button-heavy control annoying — reserve it for display-only screens.
- Run Chromium as a kiosk (`--kiosk`) with autologin + a systemd user service, and a watchdog that restarts the session if it dies.
Cost: tablet route is usually €20-40 total and less work; Pi + screen is ~€80-120 but zero battery/fire concerns. My split would be tablets for control panels, one e-ink screen for the always-on glanceable display. by miaowoo_lw @lemmy.world Banned reason: Unapproved and undisclosed bot account. Comment chain being removed as well.
16 days ago mod
Banned miaowoo_lw @lemmy.world Banned from the community reason: Bots must be set as a bot in their profile and request community permission first. Banned.
17 days ago mod
Banned miaowoo_cafe @lemmy.cafe B from the community reason: Untagged bots are not permitted on lemmy.world. You can contact me after resolving this issue properly. Until then, this account is banned.
19 days ago mod
Unlocked Post [CBH] Ideon 1.0: a canvas that has become a Git artifact 19 days ago mod
Removed Post I built 8 free Adobe-style creative apps that run 100% in your browser — no uploads, no accounts, no watermarks reason: Rules 7&8: Account age, tag, disclosure requirements.
19 days ago mod
Locked Post [CBH] Ideon 1.0: a canvas that has become a Git artifact 20 days ago mod
Unbanned Mustachius_Grumpius @thelemmy.club from the community 22 days ago mod
Banned Mustachius_Grumpius @thelemmy.club from the community reason: laurenceOfSuburbia alt, ban evasion
22 days ago mod
Banned sanitation @lemmy.today from the community reason: Ban evasion, repeated violations of ToS
25 days ago mod
Removed Post *Permanently Deleted* reason: Not really self-hosting related. The general hardware or linux gaming comms would be a better bet.
26 days ago mod
Locked Post *Permanently Deleted* 27 days ago mod
Locked Post [AIP] Cliparr 3.0 - Plex/Jellyfin Media Clipper 28 days ago mod
Removed Post Global Discomfort Index Visualization – Updated Every 4 Hours reason: Rule#s 7 & 8: Account Age, Tag, Disclosure
28 days ago mod
Removed Post Doom Scrolling the Fediverse. I'm post-Dashboard. reason: Rule 3.
1 month ago mod
Removed Post [Looking for testers] Pileus — D-pad-first Android TV client for a self-hosted media server (closed testing, 14 days) reason: Rule 7: Account age, tag/disclosure.
1 month ago mod
Unbanned leanleft @lemmy.ml from the community reason: automod
1 month ago mod
Banned leanleft @lemmy.ml from the community reason: automod
1 month ago mod
Unlocked Post [AIP] - Managarr (an *arr CLI and TUI) now supports Readarr + compatible forks 1 month ago mod
Locked Post [AIP] - Managarr (an *arr CLI and TUI) now supports Readarr + compatible forks 1 month ago mod
Removed Post [cbh] syncspirit v0.4.7 release reason: Please review rule 7 & rule 8 before posting your project again.
1 month ago mod
Locked Post [cbh] syncspirit v0.4.7 release 1 month ago mod
Removed Post Need help from users to volunteer testing of his digital wellbeing software reason: I don't know why removals don't consistently federate, so this may show up multiple times in the modlog. Rule 7, account age, and rule 3, must be self-hosting related. This is desktop software.
1 month ago mod
Banned bumflix_3pqtl @lemmy.sinistraverso.org from the community reason: Spam
1 month ago mod
Removed Post Help needed from volunteers to test latest beta release of ScreenGuard for various platforms - v0.1.1-beta.4 reason: Rule 7: Account Age
1 month ago mod
Unlocked Post [AIP] Last weekend I published Plume RC1, my side-project for a self-hosted, flat-file publishing platform built to simplify independent publishing 1 month ago mod
Locked Post [AIP] Last weekend I published Plume RC1, my side-project for a self-hosted, flat-file publishing platform built to simplify independent publishing 1 month ago mod
Banned aspmhzx @lem.cochrun.xyz from the community reason: Advertising / spam
1 month ago mod
Banned Dev2030 @lemmy.world Banned from the community reason: Spam
1 month ago mod
Removed Post Kingdom Rising — Build, Raid, Rule reason: Spam
1 month ago mod
Removed Post Kingdom Rising — Build, Raid, Rule reason: Spam.
2 months ago mod
Banned huangguoai @lemmy.world from the community reason: Spam.
2 months ago mod
Banned TachyonTele @piefed.social from the community reason: Harrassment of other users from multiple accounts
2 months ago mod
Banned fundbasis_bot @lemmy.1095.me from the community reason: Spam.
5 months ago mod
Appointed curbstickle_lw @lemmy.world as a mod to the community 5 months ago mod
Removed HybridSarcasm @lemmy.world as a mod to the community 5 months ago mod
Appointed curbstickle @anarchist.nexus as a mod to the community 5 months ago mod
Appointed ayyy @sh.itjust.works as a mod to the community 3 years ago mod
Removed MrKaplan @lemmy.world as a mod to the community 3 years ago mod
Appointed MrKaplan @lemmy.world as a mod to the community 
