petrichornetrainfall

The best way for me when i was learning the basics was to have a separate device to experiment and test things on, and not worry about having to wipe and lose anything, and any time I got something working right I would make the changes to my “main”. But that’s was a while ago and things improved since then, and also everyone learns different.

So I would recommend trying to follow any linux communities on lemmy or reddit to absorb new info (a lot might be wrong or outdated), maybe follow some youtubers ( a few popular tech ones are making the shift to linux and learning from scratch too), and honestly even just memes will help. Just keep in mind that a lot of people state outdated opinions as facts, or repeat wrong info they heard from someone else.

For more accurate but less hand-holding info, start trying to find good actual forums for Linux, like a disto’s (spin or flavor of linux) forum or “discourse”. As long as you read or search for things before posting, people will generally be nice and willing to help out. Just try to provide any info you can when you post, and don’t have any attitude.

Advanced and more technical info can be found on an apps or distros website or github.

If you have specific questions about the Bluetooth keyboard, let me know in the reply and I’ll try to help!

P.S ignore all distro recommendations till you get more experience, in the beginning the biggest hurdles will be switching from windows to Linux, difference between distros do matter but are much smaller than people sometimes make them out to be. You should stick with one, preferably whatever a buddy or favorite YouTube is using, and save distro hopping till later.

So a lot of documentation in general typically only covers beginner or expert levels, with almost no intermediate.

It’s always “here’s how to say hello world” or “here is how to extend our implementation at a low level”.

So it’s nice to have examples of intermediate use cases for power users who need to do more than the most basic examples, but don’t plan on submitting PRs to add or change functionality.

More info, guides, and examples are always better than less (as long as it’s accurate).

I’ll definitely have to take advantage of the hardware acceleration.

In regards to gaming, what kinds of games have you typically used this for? I’m not thinking about using this for competitive shooters or something like that where every ms counts, but what about games like a souls like where timing a parry or something matters, have you tried anything like that?

Lacking those features is perfect fine for me, I’m looking more for a remote display and input implementation anyway.

One last question, have you experimented with any compression or “enhanced” encryption for the ssh connection? If so, has that impacted the responsiveness at all?

You have no idea how grateful I am to you right now.

This has been on my personal project backlog for awhile now. I have run into so many issues and headaches with possible rdp or vnc solutions for my desired use case, especially with wayland being a must have.

I have recently fell in love with ssh and was planning on looking more into waypipe as a possible route to take as I kept seeing it recommended, but the examples and documentation i found was always “generic” or surface level and didn’t have enough of the pieces I needed to scrape together.

I’ve been putting it off due to only having surface level knowledge about all the pieces, and you merged like 10 of them in one go.

My biggest question to you is what is performance like? Like picture quality, audio delay, and latency/responsiveness around mouse and keyboard inputs? How does it compare to using something like an ipkvm, rdp, rust desktop, etc?

What’s between code berg and framework?