spn VS i3

Port forwarding on router without the use of a VPN is not what I was talking about dude. Linux has always had the ability to route iptables and software like Portmaster SPN, have paced the way for granular control at the packet level. So before you respond, take a look at the protocol of Portmaster SPN and consider what I’m saying, I’m trying to help you bro, not fight. https://safing.io/spn/

Safing develops the privacy firewall „Portmaster“ and runs the „Safing Privacy Network“ (SPN) which joins features of Onion Routing and VPN. The company has a transparent business model and the code is open source. We are an official reseller of Portmaster Unlimited.

If you're up to trying something new, we've built a technology to replace consumer privacy VPNs: https://safing.io/spn/

Technical summary of the SPN (Safing Privacy Network):

- A Privacy Network aimed at use cases "between" VPN and Tor.

- Uses onion encryption over multiple hops just like Tor.

- Routes are chosen to cover most distance within the network to increase privacy.

- Exits are chosen near the destination server. This automatically geo-unblocks in many cases.

- Exclude apps and domains/entities from using SPN.

- Change routing algorithm and focus per app.

- Nodes are hosted by Safing (company behind Portmaster) and the community.

- Speeds are pretty decent (>100MBit/s).

I have been messing around trying to make a secure browsing instance that has a few browsers and some VPN clients like Proton VPN and and Portmaster by Safing and after going through a long path of errors and wrappers written in Python i think the issue stopping these tools from running properly is accessing the hosts network from the container. Looking at these stack overflow questions lead me to this conclusion: nmcli in a docker container Enabling network manager inside docker

but SPN is open source as well

There is really so much. Check their website. They do a better a jop at that : https://safing.io/spn/

I read their info and tutorials. Honestly I don't put completely my trust in the onion routing system. Does anyone use this software and can give a balanced opinion on speed, usage, problems, and overall quality of service? https://safing.io/spn/

There are 3 big parts:

- The firewall itself with rules, filter lists, and so on - https://safing.io/features/

- Secure DNS (DoT/DoH resolver) - https://safing.io/features/

- "SPN": Optional paid VPN alternative similar to Tor, our source of revenue - https://safing.io/spn/

While I believe Memory Saver was a great improvement, it only works if the tab is hidden or the window minimized. I recently learned the required state is not triggered if the tab is open but on another virtual desktop. At least this is the case with many of not all Linux window managers. Some of the many discussion threads on the topic:

https://github.com/i3/i3/issues/4353

> This is very true, and unfortunately there are very few people working on linux accessibility (including not me! I am part of the problem!).

Accessibility work itself ironically suffers from an accessibility problem. I brought up i3wm above, the issue for that is pretty illuminating: https://github.com/i3/i3/issues/3393

It's not that the devs are saying "this doesn't matter", the devs behind one of the most popular tiling window managers in the X11 ecosystem are saying, "this does matter, but we don't know how to fix it. We don't know what changes we'd need to make to get Orca working."

It's a really fundamental breakdown that's kind of a tragedy because I honestly believe that if accessibility communities were more heavily baked into testing and development in Linux and if this wasn't treated like two separate worlds, it would be better for everyone -- fixing accessibility concerns very often improves interfaces across the board and makes them more powerful.

But... how do you bridge that gap? I don't really know, I tried looking into Orca to see what would need to happen here and bounced off of it pretty hard, it's not a very approachable tech stack and there aren't tutorials or getting started guides. And on the other side of the issue I can preach about needing accessibility input during interface design, but I'm not in a position to give specific advice because I don't use screenreaders or alternate control schemes and I don't know what the biggest problems are.

The people who need to be involved in that process can't get involved because there's a tech barrier in place even for technically inclined people, and because the underlying software locks them out from the start. i3wm isn't ever going to get someone who's intimately familiar with Orca to jump into the conversation because the people who need to use Orca can't use i3wm. So that leaves the people who can address that tech barrier, but they don't know what to do or how to approach the problem because of the lack of involvement and because the communities are isolated from each other. So it's a chicken-and-egg problem and I don't know how to solve it.

This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.

I use MacBook Pro (Retina, 15-inch, Mid-2014) with Manjaro as OS using i3 as a window manager. It isn't perfect, but I'm thrilled with it. I have been a Mac OS user for the last 15 years and wouldn't change what I have now for a Mac OS because I don't need more than what I'm using for development.

Even though, we have moved the official i3 support channel to GitHub discussions, i3's biggest community is still on reddit and if things continue like that there is going to be a lot of helpful content on an increasingly closed platform.

for example, take i3. https://github.com/i3/i3/issues/4478

For daily usage I really like kubuntu with i3wm, but it takes some configuration and getting used to the shortcuts, but it's well worth it