-
-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safing journey and Android Support #1655
Comments
Kein kommentar? |
This issue has been automatically marked as inactive because it has not had activity in the past two months. If no further activity occurs, this issue will be automatically closed in one week in order to increase our focus on active topics. |
Still relevant. |
Hey, sorry, this got lost in the weeds.
Yes, this was expected to be a peak.
Our goal never was to be funded by community donations.
There is an early beta version that includes just the SPN. Some more details: We started sharing the growth progress in the news widget, because we saw people reaching out and wanting to see Safing and Portmaster succeed. Bottom line: Safing is still on track and growth is steady. The best place to get regular updates on Safing and Portmaster, is to (re)watch our Safing Live every other week: https://www.youtube.com/c/safingio |
@dhaavi I'm not interested in reading every update, I just want to follow when the Android app is available as it's the main blocker for me using SPN. Is there a GitHub issue or mailing list I can follow for just the Android app progress? |
You can subscribe to the newsletter at the bottom of our homepage: https://safing.io/ |
What would you like to add or change?:
I don't have discord so i'm asking here instead.
When the pc security channel covered portmaster, a wave of newcomers purchased the spn, this peak seemingly dropped.
What's the current status of safing being funded purely by "community donations"?
What's the progress of portmaster for android? Portmaster for android would be just so amazing.
Why do you and others need this?:
The text was updated successfully, but these errors were encountered: