vikarti.anatra/safing-web
1
0
Fork 0
mirror of https://github.com/safing/web synced 2025-04-17 09:29:08 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request from safing/feature/blog-improvements

Browse source 
Blog improvements
This commit is contained in:
Dave Gson 2021-04-23 13:10:23 +02:00 • committed by GitHub
commit b5e8eb233f
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
31 changed files with 522 additions and 297 deletions

2
_includes/next_previous_item.html
View file

@ -1,4 +1,4 @@
<div class="flex pt-24 justify-center grid grid-rows-2 grid-cols-2 row-gap-12 md:grid-rows-1 md:row-gap-0 md:col-gap-16 max-w-3xl mx-auto">
<div class="flex mt-24 justify-center grid grid-rows-2 grid-cols-2 row-gap-12 md:grid-rows-1 md:row-gap-0 md:col-gap-16 max-w-3xl mx-auto">
{% if page.next.url %}
<div class="text-left row-start-1 row-end-2 col-start-1 col-end-3 md:row-auto md:col-auto">
{% if page.next.category == "blog" %}

15
_includes/portmaster_plug.html Normal file
View file

@ -0,0 +1,15 @@
<a href="{{ site.portmaster_url }}" style="opacity: 1;" id="portmaster-plug">
<div class="w-full" style="height: 260px;">
<img class="hidden lg:block absolute" style="margin-top: 11rem; margin-left: 54.5rem; z-index: 1;" src="/assets/img/shapes/circle-md-2.png" alt="">
<div class="absolute mx-auto right-0 left-0 rounded-md flex items-center overflow-hidden" style="background-color: #647cbf; max-width: 950px; height: inherit;">
<img class="absolute right-0 bottom-0 hidden lg:block max-w-5xl lg:max-w-full" style="margin-right: -28.8rem; margin-bottom: -14.1rem;" src="{{ site.img_url }}page-specific/portmaster/full-interface.png" alt="">
<div class="text-center mx-auto lg:text-left lg:ml-20">
<span class="text-white font-bold block lg:max-w-sm" style="font-size: 2.8rem; line-height: 41px;">Discover the Portmaster</span>
<span class="text-white text-md block mt-3 opacity-75">Open Source. Free Forever.</span>
<button type="button" style="background-color: #ffff; color: #647cbf; margin-left: -8px;" class="mt-3 transform scale-95 hover:scale-90 lg:inline-flex px-8 py-2 border border-transparent text-sm md:text-xs leading-5 font-extrabold rounded-full text-white hover:bg-indigo-500 focus:outline-none focus:border-indigo-700 active:bg-indigo-700 transition duration-150 ease-in-out uppercase">
Take Back Control
</button>
</div>
</div>
</div>
</a>

4
_includes/project_tablecard.html
View file

@ -56,7 +56,7 @@
<img style="min-width: 19px;" src="{{ site.assets_url }}icons/files.svg" alt="">
{% endif %}
</div>
<h1 class="pl-3 font-bold text-lg pr-16 ">{{ card.title }}</h1>
<h4 class="pl-3 font-bold text-lg pr-16 ">{{ card.title }}</h4>
</div>
</div>
</div>
@ -74,7 +74,7 @@
</div>
</div>
<div>
<div class="flex py-3" style="margin-left: 1rem;">
<div class="flex pt-3" style="margin-left: 1rem;">
<div>
<img src="" alt="">
</div>

18
_layouts/blog.html
View file

@ -3,7 +3,12 @@ layout: page_container
---
<div class="text-center">
<h1 class="text-5xl tracking-tight font-extrabold leading-none pb-2 pt-8 text-center">{{ page.title }}</h1>
<h1 >{{ page.title }}</h1>
{% if page.summary %}
<p class="text-left max-w-2xl mx-auto">
{{ page.summary | markdownify }}
</p>
{% endif %}
<p>{{ page.date | date: "%B %-d, %Y" }} • Written by <a href="{{ site.team_url }}#{{ page.author | slugify }}">{{ page.author | capitalize }}</a></p>
<div class="flex mx-auto justify-center pt-5">
<a href="{{ site.twitter_url }}" class="opacity-55 hover:opacity-100 ease-in-out duration-150" target="_blank">
@ -19,11 +24,20 @@ layout: page_container
</div>
{% if page.progress_update %}
<div>
<div class="progress-update">
{% else %}
<div class="content" id="blog">
{% endif %}
{{ content | replace: '<!--break-->', '<a class="anchor" id="continue"></a>' }}
{% if page.progress_update == null %}
<p>{{ page.date | date: "%B %-d, %Y" }} • Written by <a href="{{ site.team_url }}#{{ page.author | slugify }}">{{ page.author | capitalize }}</a></p>
{% endif %}
</div>
<hr>
{% if page.portmaster_plug == true %}
{% include portmaster_plug.html %}
{% endif %}
{% include next_previous_item.html %}

2
_layouts/podcast.html
View file

@ -6,7 +6,7 @@ container_class: "podcast pt-40 lg:pt-40"
<div class="text-center">
{% assign title_length = page.title | size %}
<span style="font-size: 12rem; font-weight: 800; margin-top: -9rem; opacity: 0.05;" class="z-0 ml-0 w-full left-0 text-center absolute bg-top">#{{ page.title | slice: 2, 2 }}</span>
<h2 class="tracking-tight font-extrabold leading-none text-center" style="max-width: 632px; margin: auto; font-size: 3rem;">{{ page.title | slice: 7, title_length }}</h2>
<h1 style="padding-top: 1.5em;">{{ page.title | slice: 7, title_length }}</h1>
<p>{{ page.date | date: "%B %-d, %Y" }}</p>
<div class="flex mx-auto justify-center pt-5">
<a href="{{ site.twitter_url }}" class="opacity-55 hover:opacity-100 ease-in-out duration-150" target="_blank">

2
_layouts/video.html
View file

@ -6,7 +6,7 @@ container_class: "podcast pt-40 lg:pt-64"
<div class="text-center">
{% assign title_length = page.title | size %}
<span style="font-size: 12rem; font-weight: 800; margin-top: -9rem; opacity: 0.05;" class="z-0 ml-0 w-full left-0 text-center absolute bg-top">#{{ page.title | slice: 2, 2 }}</span>
<h2 class="text-5xl tracking-tight font-extrabold leading-none py-10 text-center">{{ page.title | slice: 7, title_length }}</h2>
<h1 style="padding-top: 1.5em;"">{{ page.title | slice: 7, title_length }}</h1>
<p class="opacity-55">{{ page.date | date: "%B %-d, %Y" }}</p>
<div class="flex mx-auto justify-center pt-5">
<a href="{{ site.twitter_url }}" class="opacity-55 hover:opacity-100 ease-in-out duration-150" target="_blank">

35
_publications/2019-11-30-hiring-a-designer-from-the-privacy-community.md
View file

@ -9,31 +9,38 @@ custom_thumbnail_name: hiring-a-designer-from-the-privacy-community
cover_image_source: https://unsplash.com/photos/66O6CE7QvwI
redirect_from:
- /blog/2019/11/29/hiring-a-designer-from-the-privacy-community/
summary: >
_Sidenote: shoutout to [The Hated One](https://www.youtube.com/channel/UCjr2bPAyPV7t35MvcgT3W8Q/), this would not have happened without him!_
---
_Sidenote: shoutout to [The Hated One](https://www.youtube.com/channel/UCjr2bPAyPV7t35MvcgT3W8Q/), this would not have happened without him!_
## First, We Applied for a Big Grant
### First, We Applied for a Big Grant
Back in June we applied for our biggest grant so far. If it was successful, we would receive a grant of around 160.000€ with an additional 150.000€ loan which we would need to pay back in the next years. This meant - with over 300K to work with - we could hire our first employees, pay a code audit, pay our lawyer and even pay us founders our first salaries - which we'd see as a very welcome change indeed. So after weeks and months of preparation and work, on the 5th of June 2019 we sent off our application.
## A Long and Uncertain Wait
### A Long and Uncertain Wait
So off it went, and even though finishing an application was relieving, we knew this did not mean much. It was only a _chance_ of getting this money. And on top of that, we knew we would have to wait until September to get the notice. So we still had to count with a negative and it was with this mentality we went into the next few months.
## We Decided to Gamble
### We Decided to Gamble
Then August came around. We were invited to an official review of our application. This meant we made it to the second round - 🎉 (but still no certainty). In the application we already mentioned we would hire three employees, but only one of them we already had a candidate for. As a result, they told us *if* we received the grant, we would have to fill one of the positions until they would send us the first batch. Hiring is no easy feat, and we were beginners at that. Was it worth taking the risk of investing a lot of hours into hiring a person if we may not even get the grant in the end? We would waste our time and the time of applicants. We made a leap of faith and just went for it.
## The Hiring Process Starts
### The Hiring Process Starts
The next days I worked on our job description. A big shoutout to ghost.org - [their style and structure](https://careers.ghost.org/visual-designer/en) was great inspiration! After we distributed it through a few channels we for a responses. Raphael pre-filtered many of the applications and with a few we set up a video call. The grant was restricted to Austria 🇦🇹, so even though we are open for remote workers, this position needed to be filled anywhere in Austria.
It was fun getting to dive into this area from an employers perspective. So far we've only sat on the other side of the table. One thing I learned was that you really get much more interested if an application sticks out from standard, generic descriptions. And then in our situation you _really_ stick out if you are already into privacy and burning for our mission. We had two applicants who restricted their work to _only_ privacy projects. One of them could not move to Austria, which was a dealbreaker, and the other one was Luke.
## Then Luke Appeared on the Scene
### Then Luke Appeared on the Scene
_Sidenote: [Luke talks all about his side of the story in the podcast]({{ site.podcast_url }}2019/11/29/hiring-a-designer-from-the-privacy-community/)_
<div class="notification-podcast">
<img src="{{ site.img_url }}icons/mic.svg">
<a href="/podcast/2019/11/29/hiring-a-designer-from-the-privacy-community/">
<p>
Listen to the accompanying podcast where Luke talks about his side of the story
</p>
</a>
</div>
From the very first email we received from Luke we learnt two things: he burns for privacy and he is outspoken. This was even more affirmed after Raphael and I got to know him via a video call (Luke's from the United Kingdom).
@ -41,13 +48,13 @@ The even crazier thing about this was, Luke found out about us and the job via T
After plenty of interviews and rounds we had the two most promising candidates remaining. The other applicant lived nearby, so we could meet in person, but Luke we only meat digitally.
## Flying Him In
### Flying Him In
Since it's easy to pull off a show for a few hours online, we really wanted to get to know Luke in person before making our decision. We offered him to fly in over the weekend, which he accepted after some suspicion.
We booked the flight the day before we received the result about the grant, which increased the gamble, but hey: [the next day we got it]({{ site.ownership_url }}#influences) 🎉
## His Weekend in Austria
### His Weekend in Austria
The weekend was very fun! For me at least - I know Luke rather very nervous in the beginning. He arrived Friday evening, and all of us met on Saturday for lunch at a pizza place. Luke accidentally ordered a pizza, which turned out to be rather complicated to eat, which made him stress out even more. Imagine his situation: You're going to an interview for a job you're excited about. You know you and another candidate are the only ones left. And then all three founders and you go grab some lunch. All eyes on you - and then you're having troubles eating your pizza.
@ -57,19 +64,19 @@ Luke had to be sure about this too, since it meant he would have to move to anot
The next day we dropped him off at the airport. And that Sunday evening all involved knew: the big decision would be made the next day.
## His Burning for Privacy Was the Dealbreaker
### His Burning for Privacy Was the Dealbreaker
It is rather obvious by now that we decided to hire Luke. But both candidates were promising: both had strengths and weaknesses in different areas and both were outspoken. Being blunt turns out to be especially helpful when us founders are rather hardheaded. So what was the dealbreaker? Luke is burning for privacy. He has a personal privacy project which [you should check out too](https://latestprivacy.org/).
## Starting out in Austria
### Starting out in Austria
It took Luke a few weeks to pack up his things and move to Austria, but soon enough, at the beginning of October he became our lead designer. We are very grateful for his work so far and see him as a perfect fit for the job.
He made us reconsider [our old designs]({{ site.img_url }}/archive/previous_designs/homepage_v2.png) and revamped everything to [look more professional]({{ site.img_url }}/archive/previous_designs/homepage_v3.png), while still being approachable.
He made us reconsider [our old designs]({{ site.img_url }}archive/previous_designs/homepage_v2.png) and revamped everything to [look more professional]({{ site.img_url }}archive/previous_designs/homepage_v3.png), while still being approachable.
_Sidenote: [Luke talks all about his side of the story in the podcast]({{ site.podcast_url }}2019/11/29/hiring-a-designer-from-the-privacy-community/). Also, you can [follow him on Twitter.](https://twitter.com/LukeSeers/)_
## Wrap Up
### Wrap Up
Again, this would not have been possible without [The Hated One](https://www.youtube.com/channel/UCjr2bPAyPV7t35MvcgT3W8Q/)! It was a pleasure talking to him and if you don't know him already, check out his videos. They're a great resource for privacy and related topics.

14
_publications/2019-12-06-the-next-5-steps-for-safing.md
View file

@ -9,31 +9,31 @@ custom_thumbnail_name: the-next-5-steps-for-safing
cover_image_source: https://pixabay.com/photos/architecture-stone-blocks-block-3481302/
---
## A Rough Estimate of What Might Happen in 2020
### A Rough Estimate of What Might Happen in 2020
With our Kickstarter around the corner - launching on the 2nd of January 2020 - we thought this might be a good time to communicate what our next steps are going to be. These are no far fetched, crazy dreams, but instead executable plans. In 2020, we will surely finish several of these steps. And if the campaign goes well enough, we could gain sufficient resources to hire additional talent, helping us complete them all!
## 1. The Safing Privacy Network
#### 1. The Safing Privacy Network
First and foremost, our first step is going to be launching the SPN in June. It is a feature packed privacy network which protects your web connections from meta-data extraction as they travel through the Internet. With the SPN your ISP and the Wi-Fi operator of your local coffee shop cannot collect and sell your browsing habits. It protects the connections of your whole computer, not only you those of the browser. It also enforces DNS over TLS. We're looking forward to completing this first step, but it's just the beginning.
_For more information, you can read [more about our tech]({{ site.portmaster_url }}) or [the SPN whitepaper]({{ site.whitepaper_url }})._
## 2. Community Nodes
#### 2. Community Nodes
As we will start out with hosting all of the servers of this multi-hop network ourselves, this means your meta-data is spread across all of our servers. Even though we open sourced our code and made it very difficult, it is in theory still possible for us to extract your browsing habits. As this is not good enough for us, our primary focus will be adding community nodes to the system. Volunteers will be welcomed to join our cause, creating a decentralized network without a single point of trust. And the best thing about it, we will as a second step split our revenue with contributing community nodes, further encouraging this decentralized network.
_Disclaimer: we would love to launch the community nodes and immediately pay them, but this requires additional development and would slow us down in becoming a trust-less system, which is why we decided to take one step first - then the other_
## 3. Linux Support
#### 3. Linux Support
We will initially be launching the SPN on Windows. Although there will be a Linux version as well, we will wait for the full support until a few months after the launch. This means we can bundle all our resources on polishing Windows. People will still be able to experiment with the Linux version, but non-crucial bug fixes and quality of life improvements will have to wait until the full support. This step will probably be achieved around the time as we also introduce the community nodes - so the wait will not be too long.
## 4. Mac Support
#### 4. Mac Support
The first three steps are our main focus, but as soon as we complete them, we will fully dive into also supporting Mac OS - achieving full desktop support. This moment will be super exciting! I cannot wait for the day where every desktop user can come to our homepage and download the Safing app. We really do not want to exclude any users because of limited support.
## 5. Integrated Application Firewall
#### 5. Integrated Application Firewall
After achieving overall desktop support we will help your computer in becoming a privacy stealth machine. It is a great step to protect your meta-data on its way through the web, but what about all those nasty connections that should never have left your computer in the first place? Connections that are only here to track your behavior. Analytics trackers have infiltrated almost all software we currently use. It is the norm not asking you about it and simply uploading your every mouse move, or even your content to another persons computer - oh wait, right: "the cloud".
@ -41,7 +41,7 @@ As we already intercept your connections, why not enable you to block the faulty
And the best it will be totally free to use. We totally get that not everyone will be able to pay for the SPN and its servers - but why not enable them to get stealthy privacy too? There is no reason not to!
## Our Dream for Stage 1. and further Plans
### Our Dream for Stage 1. and further Plans
That will complete the first stage of our plans. At this point we can finally give away an open source, powerful application firewall. Free for anyone to use, supporting all desktop operating systems. And those who like what we do and can afford it, can then pay for the SPN to support us. We truly cannot wait!

12
_publications/2019-12-20-announcing-the-privacytools-sponsorship.md
View file

@ -8,29 +8,29 @@ author: David
custom_thumbnail_name: announcing-the-privacytools-sponsorship
---
**Today we announce that we have become a sponsor of [PrivacyTools.io](https://opencollective.com/privacytoolsio)**
###### Today we announce that we have become a sponsor of [PrivacyTools.io](https://opencollective.com/privacytools)
We are delighted to be in a position where we are able to share our resources, and equally enthusiastic that we can start this off by supporting the amazing PrivacyTools venture.
## What is PrivacyTools?
### What is PrivacyTools?
[PrivacyTools](https://privacytools.io) is an endeavor which strives to inform, educate and empower privacy-minded people to withstand today's mass surveillance. Their thriving community members do not only help each other out, but also equip and aid all newcomers into the field. The team's openness in all their decision making, criteria and finances continues to validate their gained trust across the privacy scene. If you are able [to spare time](https://www.privacytools.io/index.html#participate) or [money](https://www.privacytools.io/donate/), we encourage you to support them too!
## Their Work Impacted Us Personally
### Their Work Impacted Us Personally
Before the Safing journey started, the work of PrivacyTools already impacted all three of us founders. Their website helped us in numerous ways. Whether to deepen our understanding of the importance of privacy or about arguments we can make for it. And most importantly, their software recommendations and instructions armed us to better fight today's mass surveillance. I fondly remember the first time I proudly configured my `about:config` of Firefox, enthusiastically heading to the next section to install additional privacy enhancing extensions.
## Sharing is Caring
### Sharing is Caring
Being into our journey for more than two years, it is amazing having a look back and realizing how far we have come. But at the same time it's also humbling to see how much of it cannot be credited to us, but instead to others. Fellow travelers, founders or privacy advocates - all generously shared their time and input to help us grow. They pushed us to rethink our strategies, gave valuable input on our designs or even gave us a platform where our voices were heard.
Shorty after receiving a big grant from the Austrian Institution for Research, PrivacyTools presented their sponsorship program via Github. Excitedly, I knew the time had come for us to start sharing our received resources with fellow privacy advocates. We decided this while fully being aware that this might fuel our journey too, or it might not - that's for every reader of this announcement to decide. But to us, that is not a dealbreaker. In either case we are happily supporting a genuine and caring team!
## We Got Vetted via Chat
### We Got Vetted via Chat
After reaching out to the team, we were invited to a team chat to discuss everything further. Being listed as a sponsor is completely decoupled from their software recommendations, but still both parties wanted to get to know each other beforehand. As their team is spread across the whole globe, the chat spanned a few days, asynchronously. It was a very encouraging experience to meet and get to know fellow travelers, who are just as committed to the cause of privacy. If you want to meet the team or other fellow privacy enthusiasts, feel free to [hop onto their chat](https://chat.privacytools.io/) ;) - it's a great place to hang out.
## Privacy Space, Unite!
### Privacy Space, Unite!
Just as mentioned in [the accompanying podcast](https://safing.io/podcast/2019/12/20/becoming-privacytools-first-sponsor/), I really feel the privacy space is maturing. We are not only growing in numbers, but we are also growing tighter together. It is a great community, where one thing is allowed to fuel the other, all here to support one another. We are really hopeful that the 20s will be the decade where we take back our right to privacy. And you can count on Safing to play its part, not only with some kickass software, but also by supporting more and more projects which strive for the same utopia as all of us.

18
_publications/2020-01-22-how-the-spn-compares-to-tor.md
View file

@ -8,7 +8,7 @@ author: David
custom_thumbnail_name: spn-tor
---
## Tor's Mission is Broad, Safing Focuses on Ease of Use
### Tor's Mission is Broad, Safing Focuses on Ease of Use
Tor's mission statement (from [https://www.torproject.org/](https://www.torproject.org/) - in the footer), declares:
@ -18,7 +18,7 @@ We wholeheartedly agree and appreciate Tor's work and outlined broader mission,
We believe that freedom can only flourish when privacy is the default. And privacy will only be broadly adopted if it is easy to use. So "Easy to use" is our focus: we want my mom and your mom to be able to conveniently withstand mass surveillance without having to venture deep into tech. This is what drives us. This is our mission.
## The SPN Protects Your Whole Computer
### The SPN Protects Your Whole Computer
The Tor browser has great coverage, supporting all major operating systems. It protects the browser habits of its users and is a breeze to set up. When one additionally wants to safeguard the whole computer via the Tor network one has to use the [operating system tails](https://tails.boum.org/install/index.en.html), which is great at what it does, but hard and technical to set up and use.
@ -26,11 +26,11 @@ This is one key difference to the SPN. With it, it's a simple plug and play. You
Another detail is that Tor does not transport everything, notably UDP traffic. The SPN will support TCP and UDP (+ variants) from the get go and we will see if we will need and implement anything else.
## Tor Is Maturer
### Tor Is Maturer
Tor was released in 2002, while the SPN launched in August 2020. It goes without saying that Tor is the far maturer project of the two. The SPN is still in its early days.
## The SPN Minimizes Travel through the Open Web
### The SPN Minimizes Travel through the Open Web
Both Tor and the SPN provide privacy by decoupling the person (ip-address) from the destination. This prevents your Internet Service Provider and everyone else from logging your Internet activities. When no other identification is provided you even arrive at the destination anonymously, meaning the visited server cannot know who you are.
@ -48,16 +48,16 @@ With the SPN however, every connection is calculated individually and leaves the
![SPN community](https://safing.io/assets/img/spn/spn-community-web.png)
## Minor comments
#### Minor comments
**The Dark Web Is a Non-Goal for Safing**
###### The Dark Web Is a Non-Goal for Safing
Tor's mission for anonymity also enables people to host content anonymously through onion domains. This is a non-goal for Safing.
**SPN Enforces DoT and Blocks Ads/Trackers**
###### SPN Enforces DoT and Blocks Ads/Trackers
As the [open source Portmaster app]({{ site.github_url }}/portmaster/), which hosts the SPN, sits at the kernel, it can add all sorts of amazing privacy features. Current modules (free & optional) include a DNS Resolver which enforces all your DNS queries to use DNS over TLS (DoT) and a Privacy Filter which blocks malicious or unwanted connections.
**The SPN Costs Money**
###### The SPN Costs Money
Both the SPN and Tor are FOSS. But Tor is free to use while you have to subscribe to the SPN in order to use it. Be aware you are not only paying for the SPN, but also supporting us to develop the free application firewall and enabling us to continue fighting for a brighter future.
## Conclusion: It Depends on Your Threat Model
### Conclusion: It Depends on Your Threat Model
Tor is a great project which has pioneered privacy technology and is a firm player in the space while the SPN has fresh, innovative solutions which tackle uncharted ground and focuses on ease of use before all. Depending on your threat model, the SPN may be an alternative to Tor. Or it might not.

26
_publications/2020-01-22-how-the-spn-compares-to-vpns.md
View file

@ -9,18 +9,18 @@ custom_thumbnail_name: how-the-spn-compares-to-vpns
cover_image_source: https://pixabay.com/vectors/the-globe-globe-the-internet-free-4790044/
---
## Overview of VPN Technology
### Overview of VPN Technology
### VPNs Were Built for Security, NOT for Privacy
#### VPNs Were Built for Security, NOT for Privacy
The VPN technology was developed to allow remote workers to securely connect to a corporate network to virtually check into the office and access internal resources. It does this by establishing a secure tunnel between the worker and the company. The VPN shields the whole route from the worker to the office, never entering the "open Internet".
### Commercial VPNs Are just Proxy Servers
#### Commercial VPNs Are just Proxy Servers
A commercial VPNs does something rather mundane. As an example, let's say you want to connect to "google.com" via a VPN. The VPN client first creates a safe tunnel to the VPN server, which then calls upon "google.com". So a VPN safeguards your connections up until the VPN server, then unpacks their protection and routes it back into the open Internet.
### VPNs do NOT Protect Your Privacy
#### VPNs do NOT Protect Your Privacy
There are many legitimate use cases for a VPN, like securely connecting to your corporate network or "beaming" into another country to enjoy different content or cheaper prices. But VPNs do *not* protect your privacy.
## The SPN Truly Protects Your Meta Data
### The SPN Truly Protects Your Meta Data
Before diving into the SPN, let's recap: A VPN does protect you from your Internet Service Provider (ISP) to collect and process you browsing activities. But in the end this just delegates the problem: now the VPN that can collect and sell all your data, which many of them do.
@ -32,7 +32,7 @@ The SPN however decouples the person from the destination, resulting in true pri
![SPN community](https://safing.io/assets/img/spn/spn-community-web.png)
## VPN Technology is More Widespread (for now)
### VPN Technology is More Widespread (for now)
The VPN technology is widespread and almost every computer and mobile phone supports connecting to a VPN natively.
@ -40,12 +40,12 @@ When launching in June, the SPN will support Windows, with Linux following short
The VPN and SPN both tunnel connections from your whole computer, not only from your browser.
## SPN ♥ Open Source - Everybody Can Inspect
### SPN ♥ Open Source - Everybody Can Inspect
Many commercial VPN providers use bold and misleading marketing claims without any evidence to back it up. The code on their servers and mostly on their clients cannot be investigated. They demand your trust but give little to no proof in return.
The [SPN however is open source / FOSS]({{ site.github_url }}/spn/). We do not believe users should simply 'trust' companies when it comes to their privacy. Instead they should be able to inspect vendors and hold them accountable publicly. Feel free to [check out all of our Github](https://github.com/Safing/).
## The SPN Minimizes Travel through the Open Web
### The SPN Minimizes Travel through the Open Web
After a connection arrives at the VPN server it still has to travel to the desired website. Depending on where your VPN is located, this may lead to a slower Internet experience. As an example, a person who is located in Europe may be connected to a US VPN server while loading a European website. This means the connection has to cross the Atlantic twice (EU -> US -> EU).
@ -57,17 +57,17 @@ With the SPN however, every connection is calculated individually and leaves the
![SPN community](https://safing.io/assets/img/spn/spn-community-web.png)
## Minor comments
#### Minor comments
**SPN Enforces DoT and Blocks Ads/Trackers**
###### SPN Enforces DoT and Blocks Ads/Trackers
As the [open source Portmaster app]({{ site.github_url }}/portmaster/), which hosts the SPN, sits at the kernel, it can add all sorts of amazing privacy features. Current modules (free & optional) include a DNS Resolver which enforces all your DNS queries to use DNS over TLS (DoT) and a Privacy Filter which blocks malicious or unwanted connections.
**VPN - a Very Precarious Narrative**
###### VPN - a Very Precarious Narrative
There is [a great write up by Dennis Schubert](https://schub.wtf/blog/2019/04/08/very-precarious-narrative.html) showcasing the problem of todays commercial VPNs, both from a privacy and security perspective. Feel free to check it out, it also shows the valid use cases of VPNs.
**The SPN Costs more Because it is a New Product**
###### The SPN Costs more Because it is a New Product
While VPN providers basically rebrand the same basic technologies widely available, we built every aspect of the network from the ground up, by hand. This is a huge investment and will require lots of resources to properly maintain and improve. But this is the only way to achieve real privacy. Thank you for enabling us to continue fighting for a brighter future!
## Conclusion: SPN > VPN
### Conclusion: SPN > VPN
The VPN technology was built to securely connect two company locations. However, the SPN was developed from the ground up to protect user privacy. As a result the SPN can easily outperform VPNs in every aspect.

18
_publications/2020-02-04-the-two-steps-it-takes.md
View file

@ -15,9 +15,9 @@ Even with the rise of the Internet, it still takes years until a company becomes
This is that story. And the story of shortcuts.
## Step 1: Creating a Product
### Step 1: Creating a Product
### Grind it out with R & D
#### Grind it out with R & D
There's one question that every company answers before starting out: "What problem are you trying to solve?"
@ -25,19 +25,19 @@ Then you go to the drafting board, you research deep into the issue, you think t
This process is called Research & Development. Nothing novel out there 'just happened', instead, an idea was cultivated and progressed through plenty of trials and errors until it matured into a workable solution.
### The Shortcut: Just Copy Work
#### The Shortcut: Just Copy Work
But what if you do not have the time for all that? It's rather easy actually, you just copy a current solution. Or you only slightly add functionality to an existing product. The devil's advocate would call this stealing, the marketer would simply describe it as rebranding.
I in no way condemn companies taking this approach, there is still another mountain to climb to become successful. I simply ask them not to claim their copied solution is something novel.
**Conclusion**
#### Conclusion
With a novel or rebranded product, you're ready to move ahead. But nothing is gained yet. You are still far away from actually being a success.
## Step 2: Marketing and Growth
### Step 2: Marketing and Growth
### Listen and Put in Honest Work
#### Listen and Put in Honest Work
If you have the perfect solution to a problem but nobody knows about it, was the problem really solved? Was your solution really any good? Honestly, no. This is the reason why marketing is *necessary*.
@ -47,17 +47,17 @@ But talking to your market has become difficult. In today's information overflow
For generic growth, there is no way around listening to your audience, being honest and open, and ultimately building a relationship with your customers. Only time, genuine effort and persistence will get you there.
### The Shortcut: Just Buy Attention
#### The Shortcut: Just Buy Attention
Oh yeah, there is a way around this too. Instead of putting in the work, just buy yourself into the game: With todays ad industry, you can simply spend hundreds of thousands of dollars to buy people's attention and hopefully convert enough of them into customers.
The catch with this however is that you normally have to turn to venture capital, which focuses more on the investor's profit than your customers. There's [this vicious cycle going on](https://forum.privacytools.io/t/what-privacy-services-have-been-sold-or-taken-on-major-investors-we-should-find-out/1834/9) that, ultimately, forces so many companies to sell out on their customers. Avoid this at all cost.
**Conclusion**
#### Conclusion
Marketing is the act of talking and promoting your product to the market. As a result, growth is *only* possible through good marketing. The ethics behind it all is another story, but I assume you can guess my stance on that topic ;)
## Failing One Step Results in Overall Failure
### Failing One Step Results in Overall Failure
Think about different companies and their approach in both these steps. What about those who chose to copy old technology but market it in an honest way? What about those that took the shortcut in both cases? What about the geniuses who researched a break-through solution but failed to present and market it to the world?

16
_publications/2020-07-07-how-safing-selects-its-default-dns-providers.md
View file

@ -26,7 +26,7 @@ One thing that has also sparked controversy with all these new encrypted DNS cli
But now we have the same decision to make. How can we choose a default DNS provider that all our users are at least OK with? How can we do that while abiding to our high standards of privacy and transparency? One of the answers is this blog post. Another is to listen carefully what our users tell us.
## How We Rate DNS Providers
### How We Rate DNS Providers
We have identified three basic criteria for selecting DNS providers:
@ -34,13 +34,13 @@ We have identified three basic criteria for selecting DNS providers:
- __Freedom__ is about not interfering with queries. Additional blocking of Ads, trackers and Malware is okay, but there is zero tolerance for censorship.
- __Technical Quality__ is a mixture of query performance, stability and global coverage. The default resolver should work well for everyone, no matter where they live or travel.
## Our Selection
### Our Selection
Quite foreseeably, we started by taking a look at the secure resolvers that were already vetted by the PrivacyTools Community: <https://www.privacytools.io/providers/dns/>
Instead of just choosing one or two providers, we chose to select a pool of DNS providers as a working set in order to quickly react to changes in this landscape (sorted alphabetically):
<h3>AdGuard <small>(<a href="https://adguard.com/en/adguard-dns/overview.html">Website</a>)</small></h3>
<h4>AdGuard <small>(<a href="https://adguard.com/en/adguard-dns/overview.html">Website</a>)</small></h4>
__4/5 Privacy__
AdGuard is registered in Cyprus, but is developed by Russians. They value privacy and transparency and develop a wide range of ad blocking software, which usually need to be paid for. Their DNS service is free to use.
@ -54,7 +54,7 @@ __4/5 Technical Quality__
AdGuard operates about a dozen servers, focusing on North America, Europe and South East Asia. Their coverage can be improved, but their query performance is pretty good.
➖ Lacking Coverage.
<h3>Foundation for Applied Privacy <small>(<a href="https://applied-privacy.net/">Website</a>)</small></h3>
<h4>Foundation for Applied Privacy <small>(<a href="https://applied-privacy.net/">Website</a>)</small></h4>
__5/5 Privacy__
The Foundation for Applied Privacy is a nonprofit privacy infrastructure provider based in Austria (which is also where we are). This is the only selected provider that is fully stationed and operated within the EU.
@ -66,7 +66,7 @@ __3/5 Technical Quality__
While their query performance is really good, they are only present in one country and only run one resolver, making them prone to outages.
➖➖ Lacking Coverage.
<h3>Cloudflare <small>(<a href="https://cloudflare.com/">Website</a>)</small></h3>
<h4>Cloudflare <small>(<a href="https://cloudflare.com/">Website</a>)</small></h4>
__3/5 Privacy__
Cloudflare is one of the biggest traffic handlers on the Internet and is a publicly traded company based in the US. Although one of the goals of their DNS service is to improve online privacy of users, their sheer size creates a centralization that hurts privacy.
@ -81,7 +81,7 @@ Cloudflare provides both malware and family filtering options. While, as far as
__5/5 Technical Quality__
Cloudflare's DNS service easily sets the bar with their unsurpassed query performance and global coverage.
<h3>Quad9 <small>(<a href="https://quad9.net/">Website</a>)</small></h3>
<h4>Quad9 <small>(<a href="https://quad9.net/">Website</a>)</small></h4>
__4/5 Privacy__
Quad9 is a 501(c)(3) nonprofit organization based in the US. Although they value privacy, there is criticism about the influence Quad9 potentially has from its founding organizations.
@ -97,7 +97,7 @@ While Quad9 is operated in locations where PCH is also present, through which th
_You can find the [exact configuration for each provider here](https://github.com/safing/portmaster/wiki/DNS-Server-Settings)._
## Our Primary Default
### Our Primary Default
While we use a working set of DNS providers, only one will be active at a time. If we configure multiple providers in the default settings, additional providers will act as a fallback in case the Portmaster has any issues with the primary resolver.
@ -115,6 +115,6 @@ Not all changes between providers in the defined working set will be communicate
We would highly appreciate any feedback you have on this selection of providers. If you want to set the DNS provider yourself, [here is how you do it](https://github.com/safing/portmaster/wiki/DNS-Server-Settings).
By doing so, the Portmaster will never use anything else until you make changes again (for global DNS queries).
## Conclusion
### Conclusion
Selecting a default DNS provider is really hard. There is no provider that fulfills all our wishes, yet we have to choose. We hope to have given you a better understanding of this process with this blog post and ask you to please provide feedback if you either do not understand the conclusions we come to or feel uncomfortable with how we are going about this. We listen to what you have to say.

12
_publications/2020-07-07-we-are-updating-portmasters-default-dns-servers.md
View file

@ -8,7 +8,7 @@ author: daniel
custom_thumbnail_name: we-are-updating-portmasters-default-dns-servers
---
## TLDR
### TLDR
On Monday, the 13th of July 2020, we will be changing the default DNS resolvers of the Portmaster to AdGuard, Applied Privacy, Cloudflare and Quad9 (sorted alphabetically). This will **affect all users who have NOT configured their own DNS servers**. If you have set your own preference the Portmaster will never use something else until you make changes again.
@ -27,11 +27,11 @@ At release of this post the default DNS providers is set to:
This means the primary resolver is Quad9 (1). Only when issues arise with Quad9, will the Portmaster fall back to Cloudflare (2). The same applies when a third, fourth, etc., provider is configured.
## You Can Set Your Own Preference
### You Can Set Your Own Preference
A lot of information is shared with DNS providers, which is why trust and empowerment are so important. We know one shoe does not fit all, which is why you can set your own DNS providers of choice, overruling all current and future Portmaster defaults in the process. So the Portmaster will never use anything else until you make changes again (for global DNS queries). We set up a [guide to help you in this process](https://github.com/safing/portmaster/wiki/DNS-Server-Settings).
## The Current Default Impacts Performance
### The Current Default Impacts Performance
Quad9's performance is in a good range for normal DNS queries, but there are performance problems with our DNS-over-TLS client and their DNS-over-TLS server implementation. We are in contact with Quad9 to troubleshoot and resolve this problem. Unfortunately, this process is taking longer than expected, and we do not want to sacrifice DNS query encryption by falling back to plain old DNS. But because these issues frequently have a serious impact on the functionality of the Portmaster, we will need to do something about it. So we went on to explore more alternatives, and may eventually switch back to Quad9 as our primary (1) default resolver.
@ -68,11 +68,11 @@ The new working set of DNS providers will go into production with a Portmaster C
### Future Improvements
__Near-term__
###### Near-term
Right now, selecting a custom dns provider is a bit cumbersome, as it requires understand a little syntax and/or copying seemingly obscure and long strings into your settings. We will provide a one-click interface to switch between multiple options near-term. We will also show the currently used DNS on the Portmaster dashboard, so you know at a glance who is resolving your DNS queries.
__Mid-term__
###### Mid-term
We want all our users to know where their data flows to. We make no assumptions that all Portmaster users will read this blog post. Instead, we will invest in informing our users about important default settings and updates directly in the Portmaster App mid-term.
__Long-term__
###### Long-term
No matter what DNS provider we choose as a default, there will always be the possibility of a provider abusing this trust. There just is no way for a provider to technically guarantee their promises. The only way around this is to mask our users from the provider. We are evaluating options to provide a free [SPN]({{ site.spn_url }}) tier that will provide free access to the SPN for DNS queries only in the long-term. Again, this is _not_ certain and _if_ it comes, will take at least two or three years to arrive.

48
_publications/2020-07-31-progress-update-july.html
View file

@ -31,7 +31,7 @@ cards:
team:
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: Smoother Installation Is Here
- type: p
text: "It was slightly confusing to install a software which did the \"proper\" installation at its first start up. Next to correctly moving this process into the real installation, while at it, Patrick decided to refactor a lot of related code to further smoothen the process. We're happy with the results."
@ -44,11 +44,11 @@ cards:
team:
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: All Went Well
- type: p
text: Through this project Patrick got to tinker around with Github Actions for the first time, which he really enjoyed. Having completed this task not only helps distributing to Arch users, but will also help the stability of all future Portmaster builds.
- type: 'h3'
- type: 'h5'
text: More Security As A Side Effect
- type: p
text: While tackling the installer for the second Linux distribution Arch, Patrick pointed out the opt-in security of their service files. Without defining restrictions, an app like the Portmaster gets root access, so when a malicious actor takes over the Portmaster it would give him the tools to take over the whole system. As a result we defined strict rules so the Portmaster only gets read access for most of the system.
@ -68,11 +68,11 @@ cards:
- Tabitha
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: FFG Proposal Was 32 Pages Long
- type: p
text: Applying for grants takes a lot of work. We defined 14 R&D goals for the coming year. This time the proposal was extra tricky since we decided to write it in German. Most of our previous applications were written in English, so this time translating texts was also part of the work load. But we are happy we could wrap this up. Result coming in September.
- type: 'h3'
- type: 'h5'
text: Netidee Application Submitted Too
- type: p
text: Safing started out with a funding from Netidee four years ago, so applying for another grant felt special. The extent of the defined work packages are smaller compared to the FFG, so it did not take as long.
@ -87,7 +87,7 @@ cards:
- Daniel
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: Three Major Refactors Made Us Slower But More Secure
- type: p
text: "Since our SPN proof of concept back in 2018, three major events resulted in making the final product more secure and stable, but also increased our workload:"
@ -96,7 +96,7 @@ cards:
- the external code audit of our cryptographic library Jess by Cure53 gave valuable technical advice how to further tighten this aspect
- the decision to split the gossiping between network nodes into two levels of communication
- the Portmaster has matured a lot since its release back in April, resulting in a lot of code-refactors on the client side
- type: 'h3'
- type: 'h5'
text: Code Audit By Cure53
- type: p
text: "Back in January we paid some of the best in the field to audit our cryptographic library. Their insight and expertise challenged us, in a very good way. The foundation was solid, but it was clear we could improve things here and there. During these months, we could progress our cryptography library into what it is now. This module is complete, but also added workload to the timeline."
@ -107,7 +107,7 @@ cards:
- type: a
text: Inspect the code of Jess, our cryptography library
href: https://github.com/Safing/jess
- type: 'h3'
- type: 'h5'
text: Refactoring The Gossiping
- type: p
text: "Instead of sending all data from servers to clients, we decided to split the messages into a \"big message\" and a \"small message\". The big message is sent on setup and contains the servers public key and lots of meta-data. The small message contains the servers active links to other nodes and its most current ephemeral keys (for 0-RTT perfect forward & backward secrecy connections). The small message will communicate with clients regularly while the big message will be sent less frequent to prevent unnecessary communication. Naturally, this resulted in a big refactor and a delay in timeline."
@ -116,7 +116,7 @@ cards:
- type: a
text: View the Pull Request of this refactor
href: https://github.com/safing/spn/pull/1
- type: 'h3'
- type: 'h5'
text: "Last Piece of the Puzzle: Client Side Integration"
- type: p
text: "The Portmaster has matured a lot in the last few months, hence this also changed a few components which intercept and resolve network connections. This is the final module we are currently working on until the first testers can join the network. We are so close, but sadly not there yet. Expect the full SPN engine to start very shortly."
@ -132,15 +132,15 @@ cards:
- David
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: We Completed the Server Part
- type: p
text: The Safing API has come very far. It actually already is online, signing in valid users and responding with information on each users SPN subscription status. Setting the API up securely took quite a lot of planning, but we are happy about the result.
- type: 'h3'
- type: 'h5'
text: Designs Are Done Too
- type: p
text: Now in the Portmaster part, we both need to provide an interface where you can log in to the SPN and where it displays your current account status. The designs for this have also been completed by Luke.
- type: 'h3'
- type: 'h5'
text: What is Missing is The Client Side
- type: p
text: The only puzzle piece missing is the frontend implementation, meaning the Portmaster UI actually showing the designs and making the API calls. This project is nearing its completion, so stay tuned!
@ -153,15 +153,15 @@ cards:
team:
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: Watching Filter List Repos
- type: p
text: Next to providing aggregated filter lists to the privacy filter module of the Portmaster, we added a feature to the IntelHub so it watches the different list repositories. With this, we will constantly be informed about ongoing changes and be able to quickly inform our users about any impactful changes.
- type: 'h3'
- type: 'h5'
text: GeoIP Data is Being Aggregated
- type: p
text: The second big part of this work package is to collect and sort GeoIP data so the Portmaster can properly build SPN circuits locally. If you are pinging a server in Europe it would be ineffective to exit the SPN in Asia. Hence, your client needs this data to calculate efficient routes. This data is already being gathered from many different resources and takes our server up to 16 GB of memory when performing an update.
- type: 'h3'
- type: 'h5'
text: Polishing Things Up
- type: p
text: All in all, Patrick is making great progress and this project is nearing its completion. It just needs a few improvements here and there to then be fully deployed. Expect this to be out soon.
@ -173,11 +173,11 @@ cards:
- Daniel
- Thomas (Intern)
progress:
- type: 'h3'
- type: 'h5'
text: Lots of Research Went Into This
- type: p
text: Although this is a cool feature, it could potentially lead to unwanted side effects. Investigating the impact of this module in a vastness of potential edge cases was the first part we tackled before writing a single line of code.
- type: 'h3'
- type: 'h5'
text: Related Bugs Were Found While Implementing
- type: p
text: When starting to implement the Portscan, we found several related bugs in the Portmaster. Even though these delayed progress in this work package, it was super helpful to further mature the Portmaster overall.
@ -193,7 +193,7 @@ cards:
- Patrick
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: Goals Are Specified, Texting Will Start Soon
- type: p
text: Since the roadmap was prioritized not much could be done in this field. But since this project is near and dear to us, David will soon fully focus on getting these texts out of the door.
@ -207,7 +207,7 @@ cards:
- Alex
- Raphael (Intern)
progress:
- type: 'h3'
- type: 'h5'
text: Planning Done, Implementation Pushing Forward
- type: p
text: Having started this in July, we started off with planning & specifying this feature. After that was done Alex moved on to its implementation and already made great progress, soon to be reviewed and polished. This project also gave one of our summer interns the possibility to take part and experience a feature development cycle right from the start.
@ -222,11 +222,11 @@ cards:
- Luke
- David
progress:
- type: 'h3'
- type: 'h5'
text: Next Page And Progress Update Blog Are Done
- type: p
text: Many have come to ask what we are up to and what our plans for the future are. And previously, we communicated deadlines and got into a bunch of uncomfortable situations. But the alternative of just NOT communicating anything is lame too, and certainly nothing we stand for. Both David and Luke ping ponged a lot of ideas until we came up with this approach - hopefully you dig it as much as we do!
- type: 'h3'
- type: 'h5'
text: A Lot More Coming Up in the Backlog
- type: p
text: This is the first step of two, since we also want to share all about our work packages lined up further down the road. What features will be added to the SPN, the Portmaster, etc.. Well, we want to tell you, so we are working on it.
@ -239,7 +239,7 @@ cards:
team:
- Luke
progress:
- type: 'h3'
- type: 'h5'
text: It Just Started
- type: p
text: This project is fairly new, so not too much could be achieved. The goal is to have a unified design both for the main website and the account part of the website. Luke already started out with some early design concepts.
@ -254,11 +254,11 @@ cards:
- Raphael
- Tabitha
progress:
- type: 'h3'
- type: 'h5'
text: Slots Have Been Booked
- type: p
text: We are happy to already have contacted a few folks where we could book some of their sponsorship slots. Also, some local partners reached out to help us out with marketing opportunities. We will not disclose what will come of it just yet, only after the fact. But next month's update will certainly include more information.
- type: 'h3'
- type: 'h5'
text: It's an Evergoing Process
- type: p
text: Naturally, we will not be done after a few marketing gigs, which is why we are still on the look-out for further opportunities to spread the word.

40
_publications/2020-08-31-progress-update-august.html
View file

@ -33,11 +33,11 @@ cards:
- Daniel
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: Hatching from the Egg
- type: p
text: Getting the SPN out was painful, but so relieving. We planned to launch in June, then July and in the end it ended up being beginning of August. Yes, this is natural as things take time, but nevertheless was it stressful. So we are very happy that we finally got it out!
- type: 'h3'
- type: 'h5'
text: Fighting in a Dragon's Den
- type: p
text: "The SPN is buggy in its current form, but this too is normal. We lived through the same when the Portmaster launched back in April. Looking back, we are amazed at how the product matured technically in the last couple of months. The same will happen with the SPN, so after a short gasp of relief, we are back rolling up our sleeves: a lot of bug fixing lies ahead of us."
@ -50,7 +50,7 @@ cards:
team:
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: After Weeks in Staging it's Now in Production
- type: p
text: Patrick tackled most of the workload in July and in the beginning of August, enabling him to run and test the IntelHub for a few weeks in a staging environment. After inspecting the process and some fine tuning, it now is online, serving Portmasters around the world.
@ -65,7 +65,7 @@ cards:
- Luke
- David
progress:
- type: 'h3'
- type: 'h5'
text: Mid- & Long-Term Plans Are Live
- type: p
text: "Don't know about you, but we love the next page! David was a bit bummed out when communication around SPN took his focus away from the backlog. This resulted in a bit of a delay, but right after that tangent, he quickly pushed this forward. As it concluded, we are happy that everybody can have a big-picture overview of our mid- & longterm plans."
@ -83,11 +83,11 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: Earliest Kickstater Backers Got Access
- type: p
text: "As promised, the MARVIN and VISIONARY backers were the first to get access to our closed pre-alpha. The SPN is buggy in its current form, but this is normal. We lived through the same when the Portmaster launched back in April. We know that a lot of bug fixing lies ahead of us, but we are on it."
- type: 'h3'
- type: 'h5'
text: Routing Revamp is the First Step
- type: p
text: "Now that the machine is working in its first form, it became pretty clear what the biggest painpoint is: Routing and Connection Management. Daniel already started to inspect these modules to then greatly improve upon. We will keep you posted."
@ -101,15 +101,15 @@ cards:
- Patrick
- Luke
progress:
- type: 'h3'
- type: 'h5'
text: As Technical Pain Decreased, UI Pain Became More Evident
- type: p
text: "We are happy how much the Portmaster could mature in the last few months. Big thanks to all testers! At the same time, it became more clear that the UI is not really ... easy to use. We decided to prioritize to change that."
- type: 'h3'
- type: 'h5'
text: Planning Done & Ground Work In Progress
- type: p
text: "After collecting suggested ideas throughout the last months Daniel had a kick-off meeting with Patrick and Luke. We will use Angular for the frontend and Patrick already dived deep into the task to prepare and complete some ground work."
- type: 'h3'
- type: 'h5'
text: Design Concepts Almost Kicking Off
- type: p
text: "Luke will soon join the party with all of his might, right after completing the redesign of account.safing.io, which is nearly wrapped up."
@ -127,7 +127,7 @@ cards:
- David
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: Will Be Wrapped Up in the UI Redesign
- type: p
text: "As mentioned last month, the API is already live. The thing missing is the frontend. Since the new UI is being worked on we decided to delay this to prevent double spending our resources."
@ -138,7 +138,7 @@ cards:
team:
- Thomas (intern)
progress:
- type: 'h3'
- type: 'h5'
text: Finished and waiting for integration
- type: p
text: "The Portscan detection is finished in its first version. Before we move it to production we need to clean up the integration with all the other Portmaster modules. This is currently paused while we prioritize the new Portmaster UI and the SPN."
@ -154,7 +154,7 @@ cards:
- Patrick
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: System Overload - No Progress in August
- type: p
text: "Too much things were going on so sadly, we could not start out with this project. It still is a dear project to us, so expect some progress here soon."
@ -167,7 +167,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: An Invisible Ally Almost Ready to Spawn
- type: p
text: "Altough in the end you won't notice, this is an important aspect to us as a company. And there has been lots of progress on this end: We already had two rounds of reviews and being in the third round now, we are getting ever so close to deploying this onto production. It probably won't take too long."
@ -181,11 +181,11 @@ cards:
- Luke
- David
progress:
- type: 'h3'
- type: 'h5'
text: Completed Design and HTML Implementation
- type: p
text: "Luke has been busy completely redesigning the payment side of the website. After spending plenty of time on creating concepts he went on to implement his finished work into HTML and CSS."
- type: 'h3'
- type: 'h5'
text: "Last Part: Integrate HTML into the Backend"
- type: p
text: "As Luke is literally wrapping up the HTML and CSS of his designs as we speak, the only step left will be to integrate the code into our backend framework. This should not take too long, so expect this nice redesign soon!"
@ -196,7 +196,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: We Are Planning and Specifying
- type: p
text: "As all projects, we started out with planning and specifying the requirements. In this case a big part was choosing which payment provider should process the credit card data of our customers. We wanted to have a company residing in the European Union, enforcing them to comply to the GDPR. We picked a winner (we will keep you in the loop) and are now writing the technical specs and clarifying last questions."
@ -209,7 +209,7 @@ cards:
- David
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: "We Have A Date: 18th of September"
- type: p
text: "We already reached out to the PTIO and set up a date for the upcoming AMA. They are super helpful in guiding us through the preparations, giving feedback to the texts and providing us with their great wiki on how we should go about this. We are looking forward to all the incoming questions. We are looking forward to a great time with you!"
@ -227,11 +227,11 @@ cards:
- Raphael
- Tabitha
progress:
- type: 'h3'
- type: 'h5'
text: cron.weekly Newsletter
- type: p
text: "We purchased two sponsorship slots for the amazing cron.weekly newsletter, presenting the Portmaster. This resulted in a few stars over on GitHub and even made some big names stumble upon our website. We have two more slots booked - looking forward!"
- type: 'h3'
- type: 'h5'
text: Sponsored YouTube Video Coming Up
- type: p
text: "Yes, we have joined the YouTube sponsorship game. Happy to learn and grow from these experiences. One video is scheduled to come out in September and we are on the lookout to sponsor more privacy related content."
@ -247,7 +247,7 @@ cards:
- Raphael
- Tabitha
progress:
- type: 'h3'
- type: 'h5'
text: We Are Preparing Documents and Time Sheets
- type: p
text: "Since starting the FFG funding in the summer of 2019, a lot of work went into the outlined research. Documenting our progress and time spent naturally is part of the deal. And with this funding coming to an end, Tabitha and Raphael are collecting all the related documents so we can promptly respond to any requests and questions the FFG may have in regards to the grant. Vital stuff!"

8
_publications/2020-09-02-ama-we-want-your-feedback.md
View file

@ -12,7 +12,7 @@ _Update: [the AMA concluded](https://www.reddit.com/r/privacytoolsIO/comments/iv
---
## We're Doing an AMA
### We're Doing an AMA
What good is a privacy company if it is hiding certain aspects of its business? As we see it, not much really. A (privacy) chain breaks at its weakest link.
@ -20,14 +20,14 @@ That is why you can **Ask Us Anything** in the upcoming AMA event! Ask us things
Learn more about why we do what we do in the first place, what we are up to and what problems we have to face being a privacy first company.
[>>>> Visit the AMA <<<<](https://www.reddit.com/r/privacytoolsIO/comments/iv6mca/we_are_safing_a_forprivacy_counterculture_company/)
[Visit the AMA](https://www.reddit.com/r/privacytoolsIO/comments/iv6mca/we_are_safing_a_forprivacy_counterculture_company/)
## Friday, September 18 at 14:00 UTC
### Friday, September 18 at 14:00 UTC
is when we will be kicking this off on the [r/PrivacytoolsIO](https://www.reddit.com/r/privacytoolsIO/) Subreddit. Don't be disappointed if you won't be able to make it to the start, as it will run for a whole week through September 25.
If you want a __reminder__, you can [subscribe to our newsletter](#newsletter), [follow us on Twitter](https://twitter.com/SafingIO), or [join our Subreddit](https://www.reddit.com/r/safing/).
We will send out reminders when it launches.
If you're late to the party, don't fret.
If you're late to the party, don't fret.
We always love to read an email from you, just send it to [hello@safing.io](mailto:hello@safing.io).

28
_publications/2020-10-02-progress-update-september.html
View file

@ -32,7 +32,7 @@ cards:
- David
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: "Having a Blast"
- type: p
text: "It is hard to express how fun the event was! After a slower start first tens and then hundreds of questions and comments rolled in. Starting at 16:00 the whole team ended up being up until around midnight - followed by us taking shifts over the next days. Thanks for all your great questions and valuable discussions!"
@ -46,7 +46,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Ready for Stage 2"
- type: p
text: "The Portscan got wrapped up by Patrick and Daniel and is ready to be integrated into the Portmaster. This will happen via the \"Adaptive Protection System\" currently in the backlog. We will tackle this project after the SPN has reached a more stable state."
@ -62,7 +62,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Fancy Administration Is Here"
- type: p
text: "Alex did a great job with this module, giving us a nice back office for moderation and insight. As an example, we now see the voluntary survey results with nice charts. Even though you cannot view the new back office yourself, you will benefit from these changes nevertheless."
@ -77,11 +77,11 @@ cards:
- Alex
- David
progress:
- type: 'h3'
- type: 'h5'
text: "Squeezing It Out Before the AMA"
- type: p
text: "The internal goal was to push the redesign out before the AMA event, which turned out to be tighter as expected. But we bundled our resources and pushed it out a few hours before the AMA started - great team effort!"
- type: 'h3'
- type: 'h5'
text: "Retrospective Polishing"
- type: p
text: "Even though we successfully launched the redesign before our deadline, the following week we still had to finetune things here and there: Change navigation to link-only instead of buttons, re-insert crucial information when deleting your account, improve the pre-order process, etc. But it is all wrapped up now - we are ready for the next challenges."
@ -97,7 +97,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "First Big Update Imminent"
- type: p
text: "Though we are not quite yet ready for the first big SPN update, there has been good progress regarding the new navigation system that is responsible for the routing. One of the first things we realized when the first version came out, is that it started to crumble very quickly because we were not yet categorizing the servers into different states in order to dismiss any invalid server configurations that polluted the network state. With this almost done, we will revisit the connection lifecycle management of connections within the SPN and then we will be ready for the first big update. So, stay tuned!"
@ -111,11 +111,11 @@ cards:
- Patrick
- Luke
progress:
- type: 'h3'
- type: 'h5'
text: "Simple And Beautiful Designs"
- type: p
text: "Luke has been busy designing a lot of the Portmaster's features into being both simple and beautiful. Starting from the Monitor page, where you will be able see everything that is happening on your computer all the way to making the multitude of settings easy to understand and accessible for anyone who wants to configure them. In comparison, the current design stands no chance."
- type: 'h3'
- type: 'h5'
text: "Progressing the JS-Frontend"
- type: p
text: "On the other hand, a design is not useful until it has been implemented int othe frontend. That is Patricks current main task and he is speeding through the steps as well. We hope so much looking forward to being able to share all of this with you - next week we will publish a sneak peek in our Newsletter and on our socials - so stay tuned!"
@ -134,7 +134,7 @@ cards:
- David
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Last Steps Bundled With the UI Redesign"
- type: p
text: "We decided to wait until the new UI is done before tackling the last steps of this project. This prevents double spending of our resources. So as soon as the new UI drops this will be integrated after. Hang on tight!"
@ -150,7 +150,7 @@ cards:
- Patrick
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Progress Froze In September"
- type: p
text: "Being honest, this project did not get any attention this month. David, the main bottleneck of this project had a vacation in September and spent his remaining resources on the AMA and helping out with the redesign of account.safing.io. The good news is that in October, this will be his main focus. So expect progress by the next update!"
@ -161,7 +161,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Specification Done, Development Underway"
- type: p
text: "Good news for crypto enthusiasts! After the setback with the credit cards implementation (read below) we decided to pivot and are now working on offering payments via crypto currencies. Bundled in two sub-tasks, the first already had its specification completed and Alex is now working on the implementation. Crypto payments we are coming."
@ -179,7 +179,7 @@ cards:
- Raphael
- Tabitha
progress:
- type: 'h3'
- type: 'h5'
text: "The Linux Experiment"
- type: p
text: "This month it was super fun to see the YouTube videos of The Linux Experiment channel which we sponsored. He is such a nice person to work with and did a great job in showcasing the Portmaster in action! And also his viewers were very pleased to find out about us - big welcome to y'all and thanks!"
@ -195,7 +195,7 @@ cards:
- Tabitha
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: "Waiting for External Conclusion"
- type: p
text: "We wrapped up our report, handed over everything the FFG backoffice needed and are now waiting for the conclusion on their end. Naturally, we do not know how long this will take, but we'll keep you posted."
@ -207,7 +207,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Vendor Denied Us"
- type: p
text: "Sadly, our preferred vendor to process credit card payments denied our application. That is why we decided to pivot onto cryptocurrency payments instead (read above). So for now, this project goes back into the backlog and we will re-evaluate at a later point."

22
_publications/2020-11-02-progress-update-october.html
View file

@ -34,7 +34,7 @@ cards:
team:
- David
progress:
- type: 'h3'
- type: 'h5'
text: "Backend Done, Frontend Task Moved to Backlog"
- type: p
text: "The server part has been done for a while now, which is great! As a result the task to implement the client side feature will be very straightforward. We intended to push this feature directly with the redesigned UI but decided against it to not slow the release down. So off to the backlog it goes."
@ -55,11 +55,11 @@ cards:
- Raphael
- Tabitha
progress:
- type: 'h3'
- type: 'h5'
text: "Our Feet Are Wet"
- type: p
text: "The last weeks and months we reached out to plenty of people in search for new audiences. We sponsored some content creators and were happy with the results. As such we will continue to do so. For now we'll wrap this card up, but naturally we will keep you in the loop about our marketing activities."
- type: 'h3'
- type: 'h5'
text: "We Paid For YouTube Sponsorships"
- type: p
text: "Big shout-out to Nick from The Linux Experiment whom it was a pleasure to work with! We had the chance to sponsor two videos in September, and two happened in October. If you are into Linux, this channel is a must!"
@ -75,7 +75,7 @@ cards:
- Tabitha
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: "Fully Wrapped Up"
- type: p
text: "Throughout the last year, reports were written, time-sheets were filled out and our company expenses were budgeted. Since the FFG funded a lot of this period we handed in all relevant documents for them to review. They were content and we already received the final part of that funding/loan. We are happy to conclude this and already applied for a follow-up funding/loan. More on that next month."
@ -93,7 +93,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Progress Staled As We Focused On the Portmaster Redesign"
- type: p
text: With Luke and Patrick steaming ahead with the UI Redesign, they stumbled over some technical limitations which needed to be tackled by Daniel to not block their progress. Focus will be back on the SPN and this project as soon as the redesign is out.
@ -108,11 +108,11 @@ cards:
- Luke
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Around 90% Of the First Version Are Done"
- type: p
text: In the last weeks Luke, Patrick and Daniel steamed ahead to really make the Portmaster shine. The Portmaster already is powerful, sure, but really not that useable. The upcoming update will make it easy to block domains from the monitor page, set global settings and then overwrite them on a per-app level, as well as change settings based on your current environment. Are you in a coffe shop? Just switch to "Untrusted Mode" and all your settings will adapt to your defined needs. Stay tuned, it will be big.
- type: 'h3'
- type: 'h5'
text: "Speed Improvements On Their Way Too"
- type: p
text: Since Daniel was focusing on some Portmaster ground work he also tackled some nasty bugs which should help a ton with speed issues many users experienced. While at it he also tackled the next card, the prompts are coming back!
@ -124,7 +124,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Prompts Are Coming Back"
- type: p
text: "As Daniel had to shift focus from the SPN to the Portmaster, he went on a side-mission: he tackled the underlying issues which forced us to previously disable connection prompting. With that done they are finally coming back! Prompting is already designed and will be released in a bundle with the UI Redesign. Stay tuned!"
@ -140,11 +140,11 @@ cards:
- Patrick
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Structure Set, Texts Are Being Written"
- type: p
text: "The Portmaster is a powerful tool, and hence it is complex. Showing and documenting this in an easy fashion is a challenge, so David put a lot of thought into finding a big-picture structure with which the docs should be easy to understand and navigate. With that being done, now the texts for each part, module and component are being written."
- type: 'h3'
- type: 'h5'
text: "Design Is Still Primitive And Needs Work"
- type: p
text: "Since Luke is fully invested into the Portmaster Redesign we are just using the very outdated docs design for now. We might release this project in different stages so you get content fast and then make it fancier and more informative as we go."
@ -156,7 +156,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "First Stage Is In Review"
- type: p
text: "Cryptocurrency payments can become rather complicated, that is why we decided to first implement a manual solution and later add complexity to make things more automatic. Alex has finished development of the this first stage and we are now in the review phase, where we will investigate the code, improve parts and make them ready for deployment."

22
_publications/2020-12-03-progress-update-november.html
View file

@ -33,7 +33,7 @@ cards:
- Patrick
- Luke
progress:
- type: 'h3'
- type: 'h5'
text: "The Fresh UI Is Here"
- type: p
text: "We are super happy that this big milestone got reached! The redesigned UI really unravels all of the Portmaster's features which previously were hidden. We still define our software as alpha, so expect bugs - but the Portmaster has become so much more usable. Switching between trust modes, overwriting global settings in specific apps, blocking from the monitor - it is all possible now."
@ -48,7 +48,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Prompting Is Back for Low Volume Apps"
- type: p
text: "Together with the new UI we also re-introduced connection prompting. Instead of allowing or blocking by default, you can make the Portmaster ask per connection. This feature is meant for low volume apps - as browsers and other apps with lots of connections will not work smoothly due to caching."
@ -64,7 +64,7 @@ cards:
- Raphael
- Tabitha
progress:
- type: 'h3'
- type: 'h5'
text: "FFG & Netidee Granted Follow-Up Funding"
- type: p
text: "We are excited to announce that both the FFG and the Netidee granted further funding and loans for the year to come! Big shout-out to Raphael and Tabitha, who continuously work on these crucial tasks to keep our journey going while the devs can focus on what they do best: developing privacy software. As always, we are open about our numbers:"
@ -80,15 +80,15 @@ cards:
- David
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: "The Unexpected Slowed Down Productivity"
- type: p
text: "Our project management tool got to a point where it became really hard to chose what to work on. Which task should you work on next when there are 20 tasks marked as URGENT? And even after chosing one, the task description was often very vague, needing lots of talk and co-ordination before being able to start. It became clear that the mountains of work lying ahead of us needed some serious restructuring."
- type: 'h3'
- type: 'h5'
text: "Step I: Who Calls the Shots?"
- type: p
text: "The first part was to define responsibilities. If our Backlog should only contain the next couple of tasks for every person, who gets to call which tasks those should be? So far we often just let everybody decide with their gut, but this is counterproductive to streamlining progress and features as a team. That is why Raphael has now taken upon the role of Product Owner (another hat for you mate 🎩). Additionally, a clear process was defined so tasks are properly specified before moving into the 'Backlog'"
- type: 'h3'
- type: 'h5'
text: "Step II: Re-Categorize 200+ Tasks"
- type: p
text: "The natural step afterwards was to move all tasks into the new workflow. Most of our old 'Backlog' tasks have now been moved to the 'Idea Phase', while the 'Backlog' remains short and clearly defined. Now everyone can easily pick up a next task after finishing up another one."
@ -110,7 +110,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Did Not Continue as we Focused on the Portmaster Redesign"
- type: p
text: "As is natural, things happen and can take longer than expected as was the case with the UI Redesign. We are happy that is out of the door so Daniel can now dive into progressing the SPN again. Expect progress updates in the next update blog."
@ -126,7 +126,7 @@ cards:
- Patrick
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Blocked by Lack of Resources Too"
- type: p
text: "This big task got blocked by two things: For one, David invested a lot into the Project Managment Cleanup (see above), and second, David needed some technical guidance from Daniel, who himself was working neck deep on the Portmaster Redesign. Both of these projects are done now, so we can tackle this task again. But it probably won't come out before next year. As always, we'll keep you in the loop every month!"
@ -137,7 +137,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Review Round I Completed - Round II Incoming"
- type: p
text: "As this feature adds plenty of code onto our codebase, David suggested to make some bigger restructures in the first Review. Alex worked on these refactors in the last month and so this feature is now ready for Review Round II, where we will take a look at all the details."
@ -150,11 +150,11 @@ cards:
- Tabitha
- David
progress:
- type: 'h3'
- type: 'h5'
text: "Concepts For Intro & Outro Are Done"
- type: p
text: "If you ever listened to our podcast, you'll notice that every episode is a bit different. Sometimes there is a proper intro/outro, sometimes there is not. Tabi and David got together to brainstorm how to streamline our podcast episodes. After multiple sessions, the texts and concepts are done. We even have a new name ;)"
- type: 'h3'
- type: 'h5'
text: "Music & Licencing in the Works"
- type: p
text: "Obviously, we also wanted to add some music to spice things up. For us as a company this is a bit more tricky than for hobbyists, since getting licences for music is harder. We contacted a very talented artist with which we are nearing an agreement. Stay tuned, the next episode will be in the 'new season'."

16
_publications/2021-01-04-progress-update-december.html
View file

@ -32,11 +32,11 @@ cards:
team:
- Raphael
progress:
- type: 'h3'
- type: 'h5'
text: "Here's to 2021"
- type: p
text: "Despite all the circumstances we will continue to work hard and push forward: for Privacy, for Freedom. Thanks for being part of that journey. May fate treat us all kindly."
- type: 'h3'
- type: 'h5'
text: "A lot Was Achieved in 2020"
- type: p
text: "Even with all the torments of 2020, for Safing, the year had a lot of highlights:"
@ -50,7 +50,7 @@ cards:
- the Portmaster recently received a complete UI overhaul
- follow-up funding was received for another full year
- "and most importantly: so many of you got to know us and are joining our forces"
- type: 'h3'
- type: 'h5'
text: "The Team is Recharging Their Batteries"
- type: p
text: "With all that behind us, and mountains to climb ahead of us - it was only natural for us to take some time off and regain our strength. This was a big focus of December, along with tidying up some things that have been lying around for too long. Like a spring cleaning in December."
@ -65,7 +65,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Stabilizing Connection Stability"
- type: p
text: "The SPN is deeply integrated into the Portmaster. If the Portmaster has slow connection processing, it directly affects the SPN. So fine-tuning this was Daniel's focus on in December. Anyone using the Portmaster will have noticed these improvements."
@ -81,7 +81,7 @@ cards:
- Patrick
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "We Adapted Structures to Enable Progress"
- type: p
text: "Deep technical knowledge, that can only come from Patrick or Daniel, has been the bottleneck for this project. And with all the recent focus on Portmaster development it was hard to sit together and talk about documentation - there was just always something more important. The solution to this was to adapt our overall structures. Starting in January, certain time slots are booked solely for 'content creation', such as documentation."
@ -92,7 +92,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Review Round II in Progress"
- type: p
text: "As this feature is adding a lot of code onto our payment system codebase, some bigger restructures were already implemented. Currently we are taking a look at all of the details and looking how we can improve the smaller things."
@ -105,7 +105,7 @@ cards:
- Tabitha
- David
progress:
- type: 'h3'
- type: 'h5'
text: "Music Licence Got Purchased"
- type: p
text: "We are happy to have wrapped up the licencing part for this. Now, we have an amazing artists whose music we can use in our podcast. Looking forward to the results. Publishing the first episode of the new season in January. Stay tuned!"
@ -122,7 +122,7 @@ cards:
- David
- Luke
progress:
- type: 'h3'
- type: 'h5'
text: "Concept Being Defined"
- type: p
text: "This is rather unexpected, but nevertheless very important. We realised people do not understand what we do when visiting our website for the first time. A lot of thought is being put into how we can improve this. Though we have some concepts ready, it is not too fleshed out yet - it is best to just wait and see ;)"

26
_publications/2021-02-04-progress-update-january.html
View file

@ -36,11 +36,11 @@ cards:
- David
- Patrick
progress:
- type: 'h3'
- type: 'h5'
text: "First Documentation Batch Has Arrived"
- type: p
text: "In January, Daniel and David spent a lot of time to finalize the first batch of the documentation: the architecture overview of the Portmaster and all its details. Code references are included, so if you are technical enough, you can dive even deeper and check out the code for yourself."
- type: 'h3'
- type: 'h5'
text: "We Are Happy the First Part Is Done, More to Come"
- type: p
text: "Looking back, we actually started working on this project back in July. As time went, we often had to prioritize something else but finally made space to wrap up this first part in January."
@ -58,7 +58,7 @@ cards:
- Tabitha
- David
progress:
- type: 'h3'
- type: 'h5'
text: "Season 02 Introduces a New Title, Storytelling and Music"
- type: p
text: "Did you know the podcast is already older than a year? Time flies, and we felt it was OK to have an amateurish podcast for a while - but back in November we thought it was time to spice things up. Tabi and David started from scratch and re-evaluated everything from the podcast title to the exact wording in the outro. If you dig podcasts, here is the result:"
@ -75,11 +75,11 @@ cards:
- David
- Luke
progress:
- type: 'h3'
- type: 'h5'
text: "Implementation Took Two Focused Weeks"
- type: p
text: "After realizing the website still confused people, the concept work started back in December. That part concluded in January and then Luke and David tackled implementation in two very focused weeks. This fast pace was only possible because we did not change any structures of the homepage. Still, it was intense to do in that short period, but it was worth it: We are super happy about the result."
- type: 'h3'
- type: 'h5'
text: "Development Focus Still Is SPN"
- type: p
text: "It was easier to explain one product instead of trying to communicate everything we do at once. So even though at first glance, the Portmaster seems to get all the attention, be assured development focus remains on the SPN."
@ -97,15 +97,15 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Sub-Goal Completed: Server Metrics"
- type: p
text: "In order to properly stabilize, scale and understand the network, it is crucial to have proper tools to analyze the SPN and its status. Implementing metrics was the task Daniel tackled and finished in January."
- type: 'h3'
- type: 'h5'
text: "Anomaly Detection Implementation Comes Next"
- type: p
text: "With metrics being done, the next step is to implement anomaly detection algorithms and feed them with the data. We will probably use technology from the European Space Agency which we got access through the ESA-Incubation. Stay tuned for that progress."
- type: 'h3'
- type: 'h5'
text: "Additional Context for Anomaly Detection"
- type: p
text: "Clients navigate through the SPN using advertised links between nodes. In order to scale the network, both the local algorithm creating routes through the network, as well as the server algorithm selecting links it should establish within the network need to be very well understood. The anomaly detection system will help us see where something is going wrong and might also be able to point to the root cause of an unexpected event."
@ -120,7 +120,7 @@ cards:
projects:
- Portmaster
progress:
- type: 'h3'
- type: 'h5'
text: "Navbar, Side-Dash & Widgets Are Ready"
- type: p
text: "The new UI was a big step sure, but it is still off from the concept design. Luke is spending a good amount of time to tackle and polish each sub-design individually. This month, the navbar, the side-dash and the widgets were given a face-lift. They are ready and will be included in the next Portmaster Release. The next step will be the Network Monitor - stay tuned!"
@ -135,7 +135,7 @@ cards:
projects:
- Marketing
progress:
- type: 'h3'
- type: 'h5'
text: "Conceptualizing the Next Push"
- type: p
text: "With both the restructured website and the docs being published, we feel we have finally created a place where new people feel comfortable when they arrive."
@ -151,7 +151,7 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "One Week A Month is Dedicated to Content"
- type: p
text: "The docs are nice, but far from done. That is why we reserved certain slots to progress content such as the docs or the blog. This month we decided we would like to add some fundamental guides as well as compatibility lists to the documentation. Let's see how far we come."
@ -168,7 +168,7 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "One Week A Month is Dedicated to Content"
- type: p
text: "The docs are nice, but far from done. That is why we reserved certain slots to progress content such as the docs or the blog. This month we decided we would like to add some fundamental guides as well as compatibility lists to the documentation. Let's see how far we come."
@ -184,7 +184,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Development Stale Since Focus Lay Elsewhere"
- type: p
text: "January was a full month and as a result this projects was not prioritized that much. This is not a surprise and happens regularly. We are a small team and have to prioritize."

18
_publications/2021-03-06-progress-update-february.html
View file

@ -32,7 +32,7 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: A Big Pain Point Is Now Resolved
- type: p
text: "In the last years, time and time again, people got super confused about our business model. The blame is definitely on us, since we marketed free software while listing \"Pricing\" as one of the main entries in the top navbar. As a result we falsely communicated a paradox: Free but Not Free."
@ -52,7 +52,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Anomaly Detection Evaluation Complete"
- type: p
text: "In February we evaluated different anomaly detection algorithms, one of them coming from the European Space Agency. We are happy to have completed the evaluation stage and have found that it makes most sense to implement this after the SPN has progressed more. As such, we are wrapping up this aspect and re-shifting our focus on advancing the SPN. Finishing this evaluation also allowed us to conclude our ESA Business Incubation."
@ -67,7 +67,7 @@ cards:
projects:
- Portmaster
progress:
- type: 'h3'
- type: 'h5'
text: "Network Monitor Got Polished, Lots of Small Fixes"
- type: p
text: "The new UI was a big step sure, but it is still off from the concept design. Luke is spending a good amount of time to tackle and polish each sub-design individually. This month Patrick fixed a lot of smaller UI bugs, and the network monitor got a face-lift from Luke. The new eye-candy is already live for you to enjoy."
@ -82,7 +82,7 @@ cards:
projects:
- Marketing
progress:
- type: 'h3'
- type: 'h5'
text: "Main Chunk Snoozed to March"
- type: p
text: "Though we had a lot of other stuff going on in February, we did not completely ignore this area. Some talks already happened which might bear fruit in the coming months. But in terms of creating a proper concept for the next steps, the main chunk of that will happen in March. Stay tuned."
@ -96,11 +96,11 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "Contribution And Installation Guide Have Arrived"
- type: p
text: "Our previous installation guide lived on GitHub, but we migrated it over to the docs since we rather want to host our docs independently. Along with the migration we finetuned the guide and also created a contribution guide which describes how to best support us at our current stage."
- type: 'h3'
- type: 'h5'
text: "Settings Reference and DNS Configuration Incoming"
- type: p
text: "We think the next big feature will be really cool. A Settings Reference where all of Portmaster's configuration options are listed and explained. Similar to something like Mozilla's description of the `about:config`. This is not live just yet, but might see the light of day in March. We shall see. Also, we want to migrate our guide on DNS Configuration over to the docs."
@ -115,7 +115,7 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "First Batch Is Live, Second Is Around the Corner"
- type: p
text: "The first release in this regard included a Status Page for mobile and guides on both Linux distribution and VPN compatibility. It is all rather rough and simple, but we are iterating from there."
@ -131,7 +131,7 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "Concept Is Done, Implementation Pending"
- type: p
text: "Luke started off with conceptualizing how the design of the documentation should be updated. Naturally its design will be similar to the rest of the website to fit into the overall experience. With a rough version completed the next step is to implement the concept into HTML and CSS."
@ -145,7 +145,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Review Round III Defined Next Steps"
- type: p
text: "In February we spent plenty of time to thoroughly review this large module and left no stone unturned. Some refactors and improvements were implemented in the process while others are being developed as we speak."

25
_publications/2021-03-24-broad-spn-access-postponed-to-q3-here-is-why.md
View file

@ -6,25 +6,18 @@ title: "Broad SPN Access Postponed to Q3 - Here Is Why"
date: 2021-03-24
author: david
custom_thumbnail_name: broad-spn-access-postponed-to-q3-here-is-why
summary: "Different factors made us prioritize Portmaster before SPN development in the second half of 2020. Since the start of 2021 we are focusing on SPN development again - by Summer a lot will have happened and you will notice all of the impact. We are sorry for this delay."
---
**TLDR: Different factors made us prioritize Portmaster before SPN development in the second half of 2020. Since the start of 2021 we are focusing on SPN development again - by Summer a lot will have happened and you will notice all of the impact. We are sorry for this delay.**
<br/>
---
<br/>
#### In August 2020 We Decided to Shift Our Attention to the Portmaster
### In August 2020 We Decided to Shift Our Attention to the Portmaster
Back in August 2020, we re-evaluated our approach and decided to focus on Portmaster development. There were multiple factors to this:
**1. the SPN is tightly integrated into the Portmaster.**
###### 1. the SPN is tightly integrated into the Portmaster.
The SPN builds on one of the main Portmaster features, intercepting network connections. The SPN relies on this working as much as the Portmaster does. And back then, this aspect was far less mature. So it did not matter how far we would come with the SPN since clients could not reliably connect to the Safing Privacy Network.
**2. the User Experience depends on the Portmaster too**
###### 2. the User Experience depends on the Portmaster too
It is kinda crazy to see where we were at. Remember this?
@ -32,23 +25,23 @@ It is kinda crazy to see where we were at. Remember this?
Our previous User Interface was ok - coming from techy developers - but for broader adoption it was clear we needed something simpler and nicer. You can see how that huge work package progressed over the months in the update blogs of [August](https://safing.io/blog/2020/08/31/progress-update-august/), [September](https://safing.io/blog/2020/10/02/progress-update-september/), [October](https://safing.io/blog/2020/11/02/progress-update-october/) and [November](https://safing.io/blog/2020/12/03/progress-update-november/).
**3. Marketing the SPN with a ugly and buggy Portmaster was very challenging**
###### 3. Marketing the SPN with a ugly and buggy Portmaster was very challenging
On the marketing front, we were fighting an almost impossible battle. Get people to try our software or even pre-order a product which was really not that great. Only the toughest of Early Adopters stayed around - big shoutout to you all! But to truly progress, we simply needed more users to understand and improve the product.
#### In Retrospect We Are Happy About This Decision
### In Retrospect We Are Happy About This Decision
Looking back, we believe this was the right call. The Portmaster has become more mature from a technical perspective which in return benefits the SPN mid-term too. Also, the new Portmaster UI let us present the software on our website and has made the software more accessible.
#### Since 2021 Our Development Focus Returned to the SPN
### Since 2021 Our Development Focus Returned to the SPN
With the new year we re-shifted our technical development towards the SPN. The main thing we had to do in Q1 was to evaluate anomaly detection algorithms. Due to funding from the ESA-BIC we were contractually required to wrap that project up. This was successful and will come in handy down the road.
#### Dedicating Q2 to SPN, A Lot Will Happen There
### Dedicating Q2 to SPN, A Lot Will Happen There
Anyway, we are happy that all this work "for the future" is wrapped up, allowing us to focus on things the SPN needs _today_ in order to stabilize the network and ultimately let more users join. Overall, we can now fully dedicate our technical attention to developing the SPN, while the Portmaster will only receive bug fixes and minor updates. We are sure you will notice the impact of this in the coming months.
#### We Are Sorry For This Delay
### We Are Sorry For This Delay
Again, we are sorry for the caused delay and take full responsibility. If you are already using the Portmaster and/or were excited for the SPN let us know how you feel about all of this. We always appreciate hearing from you.

1
_publications/2021-04-06-pitching-safing-and-privacy-on-national-television.md
View file

@ -6,6 +6,7 @@ title: "Pitching Safing and Privacy on National Television"
date: 2021-04-06
author: david
custom_thumbnail_name: pitching-safing-and-privacy-on-national-television
portmaster_plug: true
---
### It Started With An Invitation From the Austrian Version of Shark Tank

28
_publications/2021-04-08-progress-update-march.md
View file

@ -31,7 +31,7 @@ cards:
projects:
- Portmaster
progress:
- type: 'h3'
- type: 'h5'
text: "We Revamped DNS Attribution On Windows"
- type: p
text: "Ever since the release of the Portmaster, we deactivated the Windows DNS-Client since it had no documented negative impacts. But as numerous reports came about side-effects, we looked for ways how to approach this differently. Happy to have released this in March and there is a long blog post on the full journey."
@ -45,11 +45,11 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "Wrapped Up The Final Blocks In A Focused Week"
- type: p
text: "During March Luke already spent a good deal on bringing the design up to speed with the rest of the website. In March's last week David and Daniel also focused on Documentation. That was the time where we could ping-pong the last adjustments of this project to then push everything out. We are happy finally having a unified design for every part of the website."
- type: 'h3'
- type: 'h5'
text: "All Our Sites Now Support NoJS"
- type: p
text: "Oh, another cool thing happened in this regard. Finally the day arrived where no JavaScript is required to use any of our websites. It might add a few small features here and there - if you choose to enable it anyway - but everything is fully functional without it. CSS and HTML do the job just fine."
@ -64,11 +64,11 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "VPN Compatibility Table Arrived"
- type: p
text: "David and Daniel's final week in March was dedicated to documentation. Next to the redesign, the Settings Handbook and the DNS Configuration Guide, we also added a table for VPN Compatibility. It is not too full yet, but with your help more reports will follow."
- type: 'h3'
- type: 'h5'
text: "It Is Now Easier Than Ever To Contribute"
- type: p
text: "Thanks for all your reports and ideas so far! As our project spans over multiple projects we knew it was not very convenient to know where to report what. That is why we completely revamped the Contribution Guide with easy overviews and links where and how to participate."
@ -83,11 +83,11 @@ cards:
projects:
- Marketing
progress:
- type: 'h3'
- type: 'h5'
text: "We Will Focus On Value Content"
- type: p
text: "David spent a good amount on our concept for the next marketing steps. With a few different available approaches, we want to decide our main energy towards \"Value Content\". Meaning we will produce blogs which do not mainly talk about us, but about a relevant privacy or technology topic. Going in-depth and providing value to the reader we will then share the article on different platforms and only have a small plug for Safing - probably at the end of the post."
- type: 'h3'
- type: 'h5'
text: "Sponsorships, Pitches & Events Will Happen From Time to Time Too"
- type: p
text: "Last month we sponsored another video of The Linux Experiment, big shout-out to all the lovely people joining from there. Events in this fashion, or smaller out-reaches online where we pitch our software in a more direct fashion will happen from time to time too. But the main focus will be to create some juicy, relevant content. On that note we also plan to cooperate with other creators - stay tuned!"
@ -102,7 +102,7 @@ cards:
projects:
- Back Office
progress:
- type: 'h3'
- type: 'h5'
text: "Final Meeting Held In March"
- type: p
text: "The past two and a half years flew past rather quick. In such moments it is always encouraging to look back and see how far we have come since. Anyway, in March we ultimately concluded the ESA Business Incubation, handing in our end-report and having our final meeting."
@ -120,7 +120,7 @@ cards:
team:
- Daniel
progress:
- type: 'h3'
- type: 'h5'
text: "Broad SPN Access Postponed to Q3 - Here Is Why"
- type: p
text: "A short Update on the SPN: Different factors made us prioritize Portmaster before SPN development in the second half of 2020. Since the start of 2021 we are focusing on SPN development again - by Summer a lot will have happened and you will notice all of the impact. We are sorry for this delay."
@ -135,11 +135,11 @@ cards:
projects:
- Portmaster
progress:
- type: 'h3'
- type: 'h5'
text: "Cleaner Buttons & New Monitor Page"
- type: p
text: "Patrick and Luke finished the new monitor page - now you can see all connection individually, ordered by most recent. You can also filter to only show blocked connections. We also repositioned a few buttons to make the navigation clearer."
- type: 'h3'
- type: 'h5'
text: "Turning Off Animations Increased Performance"
- type: p
text: "And a strange one: the big green shield animation as well as other smaller ones was the cause for a big performance hit. Even though this is purely done with CSS, this weighed in on the CPU. Oh Electron... Nevertheless, we are happy we could speed up the UI now."
@ -153,13 +153,13 @@ cards:
projects:
- Website
progress:
- type: 'h3'
- type: 'h5'
text: "Contribution Guide & Settings Handbook"
- type: p
text: "David and Daniel's final week in March was dedicated to documentation. Next to the redesign, the Settings Handbook and the DNS Configuration Guide, we also added a table for VPN Compatibility and revamped our Contribution Guide."
- type: p
text: "Thanks for all your reports and ideas so far! As our project spans over multiple projects we knew it was not very convenient to know where to report what. That is why we completely revamped the Contribution Guide with easy overviews and links where and how to participate."
- type: 'h3'
- type: 'h5'
text: "Next Steps: Software Compatibility and Mac Status Page"
- type: p
text: "There are still a few smaller tasks we need to tackle, such as the Mac Status page and fully deprecating the GitHub Wiki. But step by step, we are getting there."
@ -173,7 +173,7 @@ cards:
team:
- Alex
progress:
- type: 'h3'
- type: 'h5'
text: "Technical Backend Feature Complete"
- type: p
text: "This month saw great progress. Alex and David went through the first crypto module and from a technical perspective everything is in place now. The remaining part is to polish the front end of the website so the user experience becomes smooth when paying with crypto. Not too lang to go until you all can pay with crypto currencies too."

45
_sass/_global.scss
View file

@ -450,7 +450,7 @@ input:checked {
}
@keyframes notification {
100% {
100% {
opacity: 1;
}
}
@ -474,3 +474,46 @@ input:checked {
grid-template-columns: repeat(7, minmax(max-content, 1fr))
}
}
#portmaster-plug:hover button {
--transform-scale-x: 1.04;
--transform-scale-y: 1.04;
}
/*
Grabs External Links only:
1. make sure it is NOT an internal link like: href="/guides/" by filtering it starts with http
2. exclude all links that contain "safing.io" which is super unlikely to hit external links
3. also exclude "localhost", which basically is 2. for local development
4. exclude social icons on top of content, which is currently grabbed with :not opacity-55, kinda dirty
*/
#page-container content a[href^="http"]:not([href*="safing.io"]):not([href*="localhost"]):not([class*="opacity-55"]):after {
background-image : url("/assets/img/icons/external.svg");
display : inline-block;
height : 10px;
width : 17px;
content : "";
background-repeat : no-repeat;
background-position-y: 0px;
background-position-x: 4px;
background-size : 10px;
}
/*
Grab Internal Setting links to add a cog
1., 2. from other docs pages, the href will include some form of /settings-reference(/)#
*/
#page-container content a[href*="portmaster/settings#"]:before,
#page-container content a[href*="portmaster/settings/#"]:before {
background-image : url("/assets/img/icons/cog.svg");
display : inline-block;
height : 20px;
width : 20px;
content : "";
background-repeat : no-repeat;
background-position-y: 5px;
background-position-x: 1px;
background-size : 17px;
}

279
_sass/_page_container.scss
View file

@ -10,116 +10,206 @@
}
}
#page-container content .progress-update {
h4{
font-size: 1.125rem;
margin: 0;
padding-left: .75rem;
font-weight: 700;
}
hr{
margin: 0;
border-top-width: 1px;
}
}
#page-container content {
p {
padding-top: 1.8rem;
color: #898989;
margin-top: 1rem;
color : #545454;
}
strong {
color: black;
}
a:hover {
opacity: .5;
transition-duration: 150ms;
transition-timing-function: cubic-bezier(.4, 0, .2, 1);
color: #353535;
}
a {
--text-opacity: 1;
color: #667eea;
color: rgba(102, 126, 234, var(--text-opacity));
text-decoration: inherit;
background-color: transparent;
--text-opacity : 1;
color : #667eea;
color : rgba(102, 126, 234, var(--text-opacity));
text-decoration : inherit;
background-color : transparent;
transition-property: background-color, border-color, color, fill, stroke, opacity, box-shadow, transform;
strong {
--text-opacity: 1;
color : #667eea;
color : rgba(102, 126, 234, var(--text-opacity))
}
}
a strong {
--text-opacity: 1;
color: #667eea;
color: rgba(102, 126, 234, var(--text-opacity));
a:hover {
opacity : .5;
transition-duration : 150ms;
transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1)
}
h1 {
font-size : 3rem;
font-weight: 600;
color : #000;
}
h2 {
font-size: 1.875rem;
padding-top: 4rem;
font-weight: 800;
font-size : 1.8rem;
margin-top : 2rem;
font-weight : 500;
color : #000;
border-bottom : 1px solid #d7d7d7;
padding-bottom: 0.5rem;
}
h3 {
font-size: 1.2rem;
padding-top: 1rem;
font-weight: 800;
font-size : 1.4rem;
margin-top : 2.5rem;
font-weight: 500;
color : #000;
}
h4 {
font-size: 1.1rem;
padding: 0.5rem 0;
font-size : 1.2rem;
margin-top : 1.5rem;
font-weight: 500;
color : #000;
}
h5 {
font-size : 1.1rem;
margin-top : 1.5rem;
font-weight: 500;
color : #000;
}
h6 {
font-size : 1rem;
margin-top : 1.5rem;
font-weight: 500;
color : #000;
}
ul {
padding-top: 2rem;
padding-top : 1.25rem;
padding-left : 1.85rem;
list-style-type: disc;
color : #545454;
li {
padding-left: .25rem;
li ul {
padding-top : 0.05rem;
padding-left : 1.25rem;
list-style-type: disc;
color : #545454;
}
}
}
ul li {
padding-top: 0.4rem;
pre {
padding : 16px;
overflow : auto;
font-size : 10%;
line-height : 1.45;
background-color: #f7f7f7;
border-radius : 3px;
padding-top : 1rem;
display : flex;
margin-top : 1rem;
code {
background-color: transparent;
padding-left : 0;
padding-right : 0;
color : black;
font-size : 0.8rem;
font-weight : 500;
max-width : 5rem;
display : inline;
}
}
hr {
margin-top : 3rem;
margin-bottom : 3rem;
border-top-width: 2px;
}
code {
color : #ba00bf;
font-weight: 500;
font-size : .875rem;
word-break : break-word;
&::after {
content: "`";
}
&::before {
content: "`";
}
}
em {
font-weight: 400;
}
ol {
padding-top : 0.1rem;
list-style-type: decimal;
padding-left : 1rem;
color : #545454;
li {
padding-top: 0.4rem
}
}
blockquote {
padding-left: 1rem;
margin-top : 1.55rem;
color : black;
opacity : 1;
border-left : 4px solid #ddd;
}
.content {
max-width: 750px;
margin: auto;
max-width : 750px;
margin : auto;
margin-top: 3rem;
ul {
padding-top: 0.1rem;
list-style-type: initial;
padding-left: 1rem;
color: #898989;
}
ol {
padding-top: 0.1rem;
list-style-type: decimal;
padding-left: 1rem;
color: #898989;
}
blockquote p {
font-weight: bold;
padding-left: 2rem;
color: black;
opacity: 0.6;
}
p {
padding: 0.5rem 0;
}
p img {
--transform-translate-x: 0;
--transform-translate-y: 0;
--transform-rotate: 0;
--transform-skew-x: 0;
--transform-skew-y: 0;
--transform-scale-x: 1.1;
--transform-scale-y: 1.1;
transform: translateX(var(--transform-translate-x)) translateY(var(--transform-translate-y)) rotate(var(--transform-rotate)) skewX(var(--transform-skew-x)) skewY(var(--transform-skew-y)) scaleX(var(--transform-scale-x)) scaleY(var(--transform-scale-y));
box-shadow: 0 0px 90px 0 rgba(59, 93, 199, 0.1), 0 0px 5px 0 rgba(0, 0, 0, 0);
margin-top: 5rem;
max-width: 100%;
height: auto;
border-radius: .375rem;
display: block;
margin-bottom: 4rem;
margin-top: 5rem;
--transform-rotate : 0;
--transform-skew-x : 0;
--transform-skew-y : 0;
--transform-scale-x : 1.1;
--transform-scale-y : 1.1;
transform : translateX(var(--transform-translate-x)) translateY(var(--transform-translate-y)) rotate(var(--transform-rotate)) skewX(var(--transform-skew-x)) skewY(var(--transform-skew-y)) scaleX(var(--transform-scale-x)) scaleY(var(--transform-scale-y));
box-shadow : 0 0px 90px 0 rgba(59, 93, 199, 0.1), 0 0px 5px 0 rgba(0, 0, 0, 0);
margin-top : 5rem;
max-width : 100%;
height : auto;
border-radius : .375rem;
display : block;
margin-bottom : 4rem;
margin-top : 5rem;
}
.podcast h2 {
padding-top: 1rem;
font-weight: 500;
font-size: 1rem;
padding-top : 1rem;
font-weight : 500;
font-size : 1rem;
padding-bottom: 0.5rem;
}
@ -128,3 +218,46 @@
}
}
}
.notification-podcast {
font-size : .85rem;
background-color: #5c85ff;
width : fit-content;
width : -moz-fit-content;
overflow-wrap : break-word;
padding-left : 1.25rem;
padding : 1.25rem;
margin-bottom : 1.25rem;
margin-top : 1.25rem;
display : flex;
border-radius : .375rem;
width : 100%;
p {
color : #fff !important;
margin-top: 0 !important;
}
img {
width : 1.5rem;
margin-right: 1.25rem;
height : 1.5rem;
align-self : center;
max-width : 100%;
display : block;
border-style: solid;
}
a {
color : white !important;
padding-left : .25rem;
padding-right : .25rem;
text-decoration: underline !important;
}
a:hover {
opacity : .5;
transition-duration : 150ms;
transition-timing-function: cubic-bezier(0.4, 0, 0.2, 1);
}
}

6
assets/img/icons/cog.svg Normal file
View file

@ -0,0 +1,6 @@
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24">
<g fill="none" >
<path stroke="#667eea" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M13.7678 10.2322c.976311.976311.976311 2.55922 0 3.53553-.976311.976311-2.55922.976311-3.53553 0-.976311-.976311-.976311-2.55922 0-3.53553.976311-.976311 2.55922-.976311 3.53553 0"/>
<path stroke="#667eea" stroke-linecap="round" stroke-linejoin="round" stroke-width="2" d="M14.849 4.12l.583.194c.534.178.895.678.895 1.241v.837c0 .712.568 1.293 1.28 1.308l.838.018c.485.01.925.289 1.142.723l.275.55c.252.504.153 1.112-.245 1.51l-.592.592c-.503.503-.512 1.316-.02 1.83l.58.606c.336.351.45.858.296 1.319l-.194.583c-.178.534-.678.895-1.241.895h-.837c-.712 0-1.293.568-1.308 1.28l-.018.838c-.01.485-.289.925-.723 1.142l-.55.275c-.504.252-1.112.153-1.51-.245l-.592-.592c-.503-.503-1.316-.512-1.83-.02l-.606.58c-.351.336-.858.45-1.319.296l-.583-.194c-.534-.178-.895-.678-.895-1.241v-.837c0-.712-.568-1.293-1.28-1.308l-.838-.018c-.485-.01-.925-.289-1.142-.723l-.275-.55c-.252-.504-.153-1.112.245-1.51l.592-.592c.503-.503.512-1.316.02-1.83l-.58-.606c-.337-.352-.451-.86-.297-1.32l.194-.583c.178-.534.678-.895 1.241-.895h.837c.712 0 1.293-.568 1.308-1.28l.018-.838c.012-.485.29-.925.724-1.142l.55-.275c.504-.252 1.112-.153 1.51.245l.592.592c.503.503 1.316.512 1.83.02l.606-.58c.351-.335.859-.449 1.319-.295z"/>
</g>
</svg>
Side by side

After

(image error) Size: 1.4 KiB

6
assets/img/icons/external.svg Normal file
View file

@ -0,0 +1,6 @@
<svg xmlns="http://www.w3.org/2000/svg" id="afa95051-7da0-49c8-913a-2d3dc8cd0db7" data-name="Layer 1" viewBox="0 0 20 20">
<g fill="none" >
<path stroke="#667eea" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.5" transform="translate(-2 -2)" d="M18 13v6a2 2 0 01-2 2H5a2 2 0 01-2-2V8a2 2 0 012-2h6"/>
<path stroke="#667eea" stroke-linecap="round" stroke-linejoin="round" stroke-width="2.5" d="M13 1h6v6M8 12L19 1"/>
</g>
</svg>
Side by side

After

(image error) Size: 467 B

7
assets/img/icons/mic.svg Normal file
View file

@ -0,0 +1,7 @@
<svg viewBox="0 0 24 24" xmlns="http://www.w3.org/2000/svg">
<g fill="none">
<path d="M0 0h24v24H0z"></path>
<path stroke="#fff" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.8" d="M12 15v0c-1.657 0-3-1.343-3-3V6c0-1.657 1.343-3 3-3v0c1.657 0 3 1.343 3 3v6c0 1.657-1.343 3-3 3z"></path>
<path stroke="#fff" stroke-linecap="round" stroke-linejoin="round" stroke-width="1.8" d="M18 10v2c0 3.314-2.686 6-6 6v0c-3.314 0-6-2.686-6-6v-2M12 18v3M7.82 21h8.36"></path>
</g>
</svg>
Side by side

After

(image error) Size: 505 B