November 5, 2021 • Written by David
A list of work packages we've fully wrapped up this month. Expand any to find out more about its conclusion.
After v0.1, focus on stabilizing the typical issues that arise with early software. Fix bugs, improve performance & stability. Detect failures in the network and react accordingly. Deliver to more and more pre-orders as the network matures.
As of October 12th, the SPN entered the "Broader Testing" phase. This is an exciting step for us and takes Safing "full circle", meaning all our planned products are live. Of course we have a lot of work ahead of us, but the nature of our work is now different. Instead of building huge projects from scratch, we can now iterate and improve on what is already here. Expect a lot of progress in the next months, both for the Portmaster and the SPN.Read the SPN Status Page for the latest info on the network
People report confusion around the network monitor. The dots feel like buttons but actually are not clickable. Rethink this section to make it more user friendly.
After Luke finished the designs for this feature back in August Patrick went ahead and tackled its implementation. Only a few obstacles got in the way, and we also added some attached explainer pop-ups.
We are happy this is now live. You now get a super simple overview of how many connections every app makes, giving you insight how many of them are allowed or blocked. This is such a welcome improvement that we will be updating our product screenshots on the homepage to display them. Until then, you have the chance to compare how it previously looked with how it is now.
Enable you to pay for the SPN with cryptocurrencies such as Bitcoin, Ethereum and Monero
The last few weeks David joined Alex to push this feature over the finish line - from a technical perspective. (this is also why I, David, skipped last month's progress update ;). Anyway, progress was good and after the finishing touches we deployed everything to the Safing Account server.
Even though we achieved this great milestone, you cannot just yet pay the SPN with crypto currencies. For that to happen, the Back Office needs to set up some structures and then enable this. Like setting up the crypto addresses you will pay to, double check the accounting requirements, etc. You can follow the progress in the new Crypto Card.
Conclude the current FFG and Netidee grants by submitting the required end reports.
As noted in the last update, the back office already came very far with these tasks. Final touches were made to the end reports and off they went. Some additional applications also were sent. An update to our numbers on our finances page is scheduled to come out in the next weeks.Check Out Our Ownership & Finances
Expand any work package to find out more about its progress, obstacles and sub-achievements.
Prepare to get rid of SPN pre-orders by implementing the In-App login into the Portmaster.
Currently, people who want to use the SPN have to (1) pre-order & wait and (2) log in via a special access code. Both is not so convenient, which is why we are working on the In-App Login to improve all of this. A lot of brain muscle went into specifying this feature in order to keep user privacy fully present. We will document how all of this works, but getting it out of the door is the current focus. Daniel is already fully working on the implementation - stay tuned.
The current installation experience is sub-optimal. Prompt users to reboot their system after installation to mitigate issues. Revisit our linux distribution, improve the PKGBUILD and add packaging for RPM and Arch. Also, submit Portmaster to AUR.
The install process of the Portmaster is already pretty old. It is not super horrible, but since then, a lot of things have changed and this process just needed some cleaning up. As an example, we re-added the mention that a reboot is required after install, after wrongly thinking this was no longer the case. In the end we were left dumbfound when many reports came in that were fixed by rebooting the system. Totally on us! Anyway, in terms of progress this already got far. Will likely get out mid November.
We hear all you Linux lovers! A much requested feature was packaging for RPM as well as submitting to the Arch User Repository. Since Patrick dived into the whole install experience he also reworked and improved these areas. Coming up is an improved PKGBUILD, AUR submission as well as an RPM package.
Portmaster users regularly run into different compatibility issues, breaking system integration, DNS or specific apps. Implement self-checks so the Portmaster can notify users about these issues. Improving their understanding of their state might also help in their issue reporting.
This is a big one: so many reports come in where the Portmaster is in one weird state or the other. Either system integration failed, or its operations were interfered, or DNS just completely failed. All of this is understood by us after some research, but why not let the Portmaster do self-checks in order to inform the user of what is going on?
Daniel went into this task and fully wrote its specification: what can the Portmaster self-check? When does it make sense to inform the user? Where would this be displayed at first? All of this is clear now and is now awaiting implementation.
Current Portmaster settings are complicated. Especially settings connected to the Network Ratings are hard to grasp for new users. Re-imagine and simplify.
The Portmaster has a high learning curve - we know. But what is the biggest learning difficulty for new users? Most definitely the Network Ratings with their complicated settings. That is why we tasked Luke to completely re-imagine the Portmaster settings without this feature requirement.
Off he went, and the results are amazing! Simple On/Off switches anyone? Yes, they are coming. But of course we do not want to remove one of our most unique feature, especially when many of you have invested time in learning and configuring it. So what we will probably start off with is to hide it away by default where advanced users can unlock it again.
Now that the tech is in place, set up the required back office structures in order to activate this feature.
It has not been too long since the tech is on the server, so now the Back Office has to align time to tackle this task in the near future. We definitely want to bring you cryptos sooner than later, we just are evaluating where to squeeze in the time for this to happen.
Work packages we for one reason or the other decided to postpone. Click on a package to find out the exact reasons why.
Describe how the Portmaster updates itself in more detail. What is the purpose of each resource? How do we protect your privacy in the process?
If you read this far, you know a lot is happening at the moment. This task just did not make the cut at the moment, hence we are postponing it. We still plan to add these docs in the future, we just have to wait and see when we will wear our writing sweaters again.