Your friendly neighbourhood sh.it.head

A Reddit refugee after 8 years of Reddit-ing

  • 4 Posts
  • 16 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • Assuming the NAT type is one that supports peer to peer connectivity, you could try using Ethernet instead of wireless (of course this only helps when docked). This would alleviate issues with WiFi signal not being strong enough, potentially increase bandwidth, and reduce latency. Ethernet can’t improve the connection beyond the incoming connection from the ISP, it only will improve issues that stem from wireless connectivity.

    I live in the countryside with my family, so maybe that’s why my Internet is so wonky?

    it could very well be this, when I visit my parents in the countryside the internet is sometimes not good enough, and other times it is adequate (satellite internet, so weather can impact it).


  • I understand why they wouldn’t want to suddenly change the branding of existing projects though.

    I’m not sure if I agree, I feel like the long term damage of keeping the names is greater than changing them now to Fedora Plasma Atomic (Formerly Kinoite) / Fedora Atomic Workstation (Formerly Silverblue). Leaving them as is, is just going to create more confusion in the future to new users who won’t immediately understand why the naming convention is different for the other spins and will create more confusion for documentation / support threads online.



  • Thank you for the very thorough reply! For god knows what reason I get this error: error: app/org.mozilla.firefox/x86_64/stable not installed when running the xdg-open firefox-reader command, yet manually running flatpak run --user org.mozilla.firefox about:reader?url=https://example.com works just fine. I’ll have to troubleshoot it when I have a bit more time ;p

    Thanks again for your very thorough write up and the linked articles. Have a good day :)

    Update: It seems like on my system, the --user flag was the issue, removing it made the script function. I am using Fedora Kinoite (Immutable version of KDE Plasma), so perhaps it is just a difference in how flatpak is configured between distros? I’ll have to read into it more later.


  • I’ll keep my answer focused on KDE Connect as I no longer use a TWM. You can most definitely use KDE Connect in non-Plasma environments. For non-Plasma (and non-Gnome * ) environments you can just install the kdeconnectd package. Then, to start the KDE Connect daemon manually, execute /usr/lib/kdeconnectd. You can schedule this to autostart as a systemd unit, or in the config for your TWM (I know in sway/i3 you could start it, I’m assuming it is similar for many other options)

    If you use a firewall, you need to open UDP and TCP ports 1714 through 1764. If you use firewalld specifically, there’s an option to enable KDE Connect rather than manually specifying it. This also let’s you have it only work on private networks and not public if you so chose.

    See Arch wiki for more details

    *For gnome I would recommend using gs-connect even if you have a tiling extension

    £ KDE-Connect: does that work on TWMs? Is there a good implementation? Can I use GSConnect elsewhere too?