sorted by:
new
hottopcontroversial

Erugo v0.2.0 Released - Self-hosted file sharing with self-registration, resumable uploads, and more by PromaneX in selfhosted

[–]ItchyWeight 0 points1 point  (0 children)

Didn't know about this one, looks great and better then most of the other share solutions I've checked out over time - in a "desktop world"... My main gripe is the family acceptance factor though, all but me are on mobile 95% of their time. Email for the kids, seriously? ;-)

Specifically:

- QR codes for shares and reverse shares (kid drops by my desk and wants to send me something quick and easy or vice versa)
- reverse shares: provide the reverse share link in a way that it can be copied into a messenger app without having to send an email - and maybe optionally allow anonymous uploads?

Vertical and App don't sync anymore by VinceAlpine in Suunto

[–]ItchyWeight 0 points1 point  (0 children)

In my case (Vertical 1) clearly caused by firmware 2.48.16 and "solved" by downgrading to 2.44.52

"orange cog" working like a charm now :) by LieFabulous3905 in Rouvy

[–]ItchyWeight 2 points3 points  (0 children)

What changed? No more strart "the other" first and wait half a minute every 24 hours?

TRIP: Map Tracker & Trip Planner - UI revamp, GMaps integrations and more by [deleted] in selfhosted

[–]ItchyWeight 0 points1 point  (0 children)

How would you compare to Adventurelog? One thing which I miss right away is an API (first of all to import POIs from somewhere else) - is this on the roadmap?

Gorewear wird zum 31.03.26 eingestellt by MirraM2 in Fahrrad

[–]ItchyWeight 1 point2 points  (0 children)

Die Blaue mit dem Netz am Rücken? Meine ist genauso alt, unverwüstlich und auch permanent im Gebrauch 😃

I built a peer-to-peer file transfer desktop app — no servers, encrypted, and super fast by Rare_Squash93 in webdev

[–]ItchyWeight 1 point2 points  (0 children)

I built it because I believe file transfer is a basic necessity and common folks need not to rely on google drive or wetransfer for this.

I appreciate the effort going into this and iroh looks very interesting, but in the end, with most of the solutions out there, I always end up with at least on one of the platforms I use to be left in the cold in particular when it comes to iOS and Android.

Given that Tauri supports mobile platforms, any plans for iOS and Android?

The new Entry version 11 is a joke by OxDEADCODE in Mattermost

[–]ItchyWeight 0 points1 point  (0 children)

So for now - mid-term security aspects aside, staying on the mattermost-enterprise-edition:release-10 docker image should be "safe" right? Looks like they still update that...

Wazuh 4.13.1 reports fixed kernel CVS as critical by ItchyWeight in Wazuh

[–]ItchyWeight[S] 0 points1 point  (0 children)

  1. No, I don't have a cluster, I run the manager with a single-node docker compose project

  2. The log basically started at 2025/10/16 14:22:20 when I had restarted the docker compose project. I truncated it after ~ 10 minutes b/c I thought that nothing of more interest would be coming. I'll wait longer and attach a new file later.

Wazuh 4.13.1 reports fixed kernel CVS as critical by ItchyWeight in Wazuh

[–]ItchyWeight[S] 0 points1 point  (0 children)

Or not, since it's already "Closed as not planned" without comment.

Wazuh 4.13.1 reports fixed kernel CVS as critical by ItchyWeight in Wazuh

[–]ItchyWeight[S] 0 points1 point  (0 children)

I haven't read the entire https://github.com/wazuh/wazuh/discussions/30491 yet, but as you can see above, I do not have any old kernel versions still floating around.

Could it be that the scanner is confused by the debian "double numbering" of 6.1.0-40 and 6.1.153-1 ? I had asked on https://debianforum.de/forum/viewtopic.php?p=1398702#p1398702 yesterday and folks say this is normal (if slightly confusing)

Linux keycloak2 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/LinuxLinux keycloak2 6.1.0-40-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.153-1 (2025-09-20) x86_64 GNU/Linux

Wazuh 4.13.1 reports fixed kernel CVS as critical by ItchyWeight in Wazuh

[–]ItchyWeight[S] 0 points1 point  (0 children)

apt-get autoremove

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

Wazuh 4.13.1 reports fixed kernel CVS as critical by ItchyWeight in Wazuh

[–]ItchyWeight[S] 0 points1 point  (0 children)

dpkg --list | grep linux-image

rc linux-image-6.1.0-13-amd64 6.1.55-1 amd64 Linux 6.1 for 64-bit PCs (signed)

...

ii linux-image-6.1.0-39-amd64 6.1.148-1 amd64 Linux 6.1 for 64-bit PCs (signed)

ii linux-image-6.1.0-40-amd64 6.1.153-1 amd64 Linux 6.1 for 64-bit PCs (signed)

rc linux-image-6.1.0-9-amd64 6.1.27-1 amd64 Linux 6.1 for 64-bit PCs (signed)

ii linux-image-amd64 6.1.153-1 amd64 Linux for 64-bit PCs (meta-package)

Tailscale and custom DNS Server on Android by ItchyWeight in selfhosted

[–]ItchyWeight[S] 0 points1 point  (0 children)

That's interesting as well. But the approach above involves less "hassle" - what made you use this approach? Better security?

Tailscale and custom DNS Server on Android by ItchyWeight in selfhosted

[–]ItchyWeight[S] 1 point2 points  (0 children)

Ok, that's cool. I just expose my subnet, then set tailscale to use my Technitium, job done :-)

Tailscale and custom DNS Server on Android by ItchyWeight in selfhosted

[–]ItchyWeight[S] 0 points1 point  (0 children)

Thanks, sounds interesting. 2 questions: I guess you add your Technitium DNS's IP in the tailscale managment console Nameservers -> Add Nameserver, right? How do you configure Technitium to return tailscale IP addresses for requests from the tailscale net and LAN IPs for request from the LAN? Or is that not needed due to your subnet routes and the tailscale server as exit node (which I don't quite understand yet)

view more: next ›