My system was configured perfectly one day, then I started vi and now I can’t exit. Send help.

Tumbleweed gang rise up!

Fake news!!1!!1!

Those are UDP packets.

Blasphemy. Hannah Montana is a god.

The one with dozens of us! Dozens!

You’ll know when you see it.

Ackchytually …

Great stuff, welcome to the Tumbleweed club, we meet at the dumpster behind Wendy’s every Tuesday. I tried Pop!_OS for a while and was quite impressed. However I have an irrational disdain for GNOME and Ubuntu so their derivatives are out for me. I hereby declare OpenSUSE and KDE the cool kids club. Tuesdays, dumpster behind Wendy’s.

Tumbleweed KDE gang rise up!

@OP, join us in Tumbleweed land. I tried arch btw but it drove me crazy. I don’t have endless hours on end to spend on DIY when I am in a hurry to get things to just work™. Tumbleweed with KDE is a refreshing take on the bleeding-edge rolling release distro with sensible defaults and much less teeth gnashing. With arch btw I felt like the whole thing was held together with duct tape and prayers. And I’m certain whatever I did in arch btw, there’s an “ackchyually, …” guy who is going to say that that was wrong.

This statement implies using arch btw as a buttplug is pleasurable and/or comfortable.

EncryptKeeper’s explanation is perfectly concise and informative if you have a cursory grasp of self hosting and networking.

If it’s not making sense to you, I would suggest revisiting some of the technical fundamentals of self-hosting, which admittedly is quite an advanced topic that most people don’t, and do not need to care about.

You would be equally well-served, perhaps more so (if you don’t really care about privacy or terms of service) by sticking to regular cloud services. The road to self-hosting is arduous and if done wrongly, causes you more harm than good. Especially if your technical foundation is not yet strong. Which your posts suggest is the case.

https://i.postimg.cc/NB5Lp7ZS/195124.png Its right here with the most recent update, and no obvious way to remove them. I don’t want OneDrive, I don’t want Office 365. Get it out of my face.

In Soviet Russia, Arch BTW use you!

I find it ludicrous that people are even suggesting “just use nouveau”, when one of the big use cases for Nvidia GPUs is scientific computing / AI workflows and the mesa drivers are simply not an option. Buy a Ferrari? Just use it like a donkey cart and you’ll be fine.

Personal data point - It works a whole bunch better for me than Nvidia, had nothing but problems with proprietary drivers and a 3080 Ti, but seeing no graphics related glitches (so far) on my 7900 XTX that I bought just to run Tumbleweed with KDE. Using the amdgpu drivers

And I have no skin nor bias in the game. I literally have both AMD and Intel CPUs as well as Nvidia GPUs on top of the 7900 XTX I just bought. Running all sorts of OSes too. This thread is far far too tribal and all the OS neckbeards are rearing their ugly heads. People, use whatever makes you happy and productive, and enjoy your computing experience instead of trying to ruin others’.

Tried running a 3080 Ti with (all KDE flavors of) Arch, Tumbleweed, Ubuntu, Fedora and Nvidia drivers, X11 works okay-ish but screen glitches galore in Wayland, GPU refuses to grab the output unless iGPU is blacklisted, etc. etc. Hardware video decoding on Firefox and other Chromium-based browsers simply refuse to work because Nvidia. I’m not going to use Nouveau since I’m using it for AI content generation.

Switched to a 7900 XTX, reinstalled and haven’t had a graphics-related issue thus far. ROCm is obviously in its early days but it should get better over time. A

For those folks who are seeing zero issues with their Nvidia setup and crapping on others, check your driver variant with lspci -k | grep -A 3 -E "(VGA|3D)" and see if its Nouveau.

Tumbleweed gang rise up!

I bought a 7900 XTX to replace my 3080 Ti just so I can run KDE/Wayland without the DE shitting its pants.

This is 100% me but for Lemmy.

Can confirm, I bit the bullet for a CR2004 last year and it took me a couple of weeks at least to set it up the way I wanted. Powerful, but steep with a capital S.

I did exactly this last year to monitor my cats at home while I was on holiday.

I bought two of these - REOLINK RLC-811A: https://www.amazon.com/gp/product/B09873G7X3

I assigned static IPs to both of these, and blocked all of their outgoing traffic to the public internet (in case Chairman Xi or Strongman Putin wants to also see what my cats are up to).

I then spun up a local motioneye container: https://github.com/motioneye-project/motioneye

The cameras by default (I think) provide rtsp streams, so I added the two streams (rtsp://somehostname.local:554/h265Preview_01_main) to motioneye and verified that I was able to view the camera streams on my local LAN.

The last step was simply to use cloudflare to as an authentication frontend to proxy my local motioneye container to my public domain name. Worked a treat!

Hope this helps, cheers.