Recent Posts

Discontinuing DevTube

We're very sorry but this time we have a really bad announcement to make!
For those who don't know: DevTube is the GGC-Projects instance of the federated video hosting platform #PeerTube and it was probably the most popular service of GGC-Project.
Unfortunately, videos are big and so the storage usage kept growing and did now come to a point where we can't handle that anymore without massive additional costs.
The GGC-Project initially started on a small virtual server, but had to move to a dedicated server after a few months already as the former lead admin noticed that it has become too big.
Since then we've had 3 terabytes of storage which was sufficient for a few years.
With less then 200 gigabytes left, and storage usage growing fast, we came to the result that we can't just go on with the current setup as the server would be completely full in only a few months.
On the other hand, the quality of moderation has significantly decreased as all team members, including myself, are very busy with other things like paid work, programming and the many other services that GGC-Project offers.
With the ongoing attempts to put spam on our platform, this was another thing that we couldn't just ignore and continue as usual, pretending nothing ever happened.
As consequence, we have made the difficult decision that it's time to bring things to an end and discontinue our DevTube service early next year.
Registrations are already closed, no new accounts can be created, existing accounts can continue to upload new videos.
At the 1st February, we will close uploads for all existing accounts, so that you have the whole January to find a new home for your videos, existing videos are still online and can be viewed in February.
At the 1st March, we will shut down the PeerTube server software, making all existing videos unavailable to the public, you should have downloaded backups and moved to another instance by now, alternatively you can still request backups by writing a mail to our support the whole March.
At the 1st April, we will completely remove all PeerTube contents and data from our servers, now it's too late to request backups of your videos, everything is gone.
We have selected a timeframe like that to make sure everything notices the changes early enough and has enough time to migrate to another server.
If you use other GGC-Project services, there's no need to panic, everything will continue to work as always.
PeerTube is the only service we'll be shutting down due to it's extremely high usage of storage.
This makes place for other services to continue for multiple years without needing any hardware upgrades, and makes them even faster and more reliable by removing a big part of the load from our servers.
We've been happy to serve you with freedom and hope that our unavoidable decision hasn't destroyed your trust in our platform that we're operating to build a better internet without surveillance, tracking and ads.
If you have any questions, feel free to contact the GGC-Project support at or comment directly under our blog post.

Taking over GGC-Project and

Nikisoft keeps growing and extending the range of free services!
Free software,free as in freedom,not only free beer,is more than just a way of development - it's a lifestyle.
We feel the spirit of freedom when working on our services,making sure everyone can utilize digital freedom without bigger knowledge about computers.
That's the main reason why we keep open source service providers alive and put even more work on ourselves.
GGC-Project has been a good partner of Nikisoft for years - They've always been the first to deploy our software updates and they've always been providing great free services that we used to make our software or even for personal purposes.
As the leader of GGC-Project wanted to step back in December,it was clear that GGC-Project with all of it's great services and happy users has to be kept alive.
Now he can focus on new projects,creating own open source software himself and maybe some day,things will be reversed and we deploy his software - We will see 😃
During the first weeks in GGC-Project leadership,we improved privacy even further by disabling more logs with a strict no-log policy as ultimate goal.
Additionally we installed some software updates,that finally enables livestreams for #PeerTube ,a thing many people have been waiting for for a long time.
Another thing we already did is bringing some services like #Nitter and #Searx back online which have been offline for months after putting one of the old servers down.
#Invidious and #Bibliogram are still offline unfortunately but we have plans for them,too.
Our vision for GGC-Project is to keep the project with all of its services alive,extend it with other useful open-source projects and keep the community growing.
GGC-Project has always been a community project,it wouldn't have been possible without all the users who have given feedback and the team members who have helped the main administrators,therefore I'm happy to announce that the team stays the same,except the former lead administrator.
We made the transition possible with zero downtime as the infrastructure stays the same,too.
Now that everything has gone well,however,we will evaluate where it makes sense to combine the Nikisoft and GGC-Project infrastructure.
For example,we're planning to move the mail addresses from a proprietary service provider to the GGC-Project #Mailcow installation and we're looking forward to launch a combined status page which provides an overview about the whole Nikisoft service network.
Shortly after taking over GGC-Project,we received a notice from the leader of that he wants to hand over the legal responsibility for personal reasons. is a chat server in the #Matrix network open for public registrations.
It was build together with Nikisoft from the very beginning to provide a GDPR-compliant messaging solution to the world for free.
The technical operation of has always been handled by Nikisoft,so nothing changes here.
Also the former leader is still part of the project so basically the only visible difference is the address in the imprint.
With this change in responsibility we feel like it's time to officially list as one of Nikisofts free privacy-respecting services.
We want to make clear at this point that is here to stay,we'll keep the current infrastructure which is fully independent from the other services and keep operating as a separate project to ensure that the service quality stays as high as it's always been.
Especially in recent days when alternative messaging platforms are experiencing a massive growth,we see a big chance in giving Matrix to the masses,making the future of communications independent and decentralized.
That's all for now,thank you very much for going the long way together with us and reading our service update.
If you have any feedback or questions,do not hesitate to contact us - It works as a comment directly below this post using any ActivityPub compatible software.

CloudFirewall 2.0.0 and what we've done to get there

About one month ago we released the first very big update for our #CloudFirewall #Firefox add-on.
We decided to wait some time with writing this post as many sad things happened with Firefox in recent times and we have to respond to that somehow,more on that later.
The biggest change with the new Cloud Firewall version is that it does now support translations into multiple languages. Very big thanks to for implementing all code needed for supporting translations as well as writing the first translation.
With version 2.0.0 Cloud Firewall already supports the languages English,German and French and we're sure that there will be even more in future versions.
You can help translating Cloud Firewall on our translations platform - If your language isn't available,just contact us anywhere and we'll add it.
The previous Cloud Firewall version unfortunately had some bugs which we didn't notice for a quite long time - That's now all fixed.
It wasn't possible to change the settings in the last version: While the page was displayed correctly,the Javascript event listener which should have listened on user input wasn't setup correctly so no changes were stored and after reloading the page,everything was reset to the default values.
The only thing which could be changed was which cloud providers should be blocked as global default.
Another problematic thing was that predefined rules for well-known sites were ignored.
Normally pages get blocked based on the owner of their IP address which will be detected correctly even if the predefined rules don't work and you'll see no wrong behavior here.
Unfortunately some pages are a special case,for example Discord which rents their origin servers at Google Cloud but proxies every request through CloudFlares network.
So Discord should be blocked for both Google Cloud and CloudFlare as they're using both services.
Unluckily the IP detection code will block it only for CloudFlare as the origin servers are hidden and no Google IP is ever seen but we know that they're using it from their status page.
Similar things happen for example for Instagram: It belongs to the Facebook company but the servers are hosted on Amazon - The IP detection would only block it for Amazon but it should be blocked for Facebook,too.
You see that the missing predefined rules lead to a lot of false-negatives which resulted in less privacy and we're very sorry that that happened.
A non-privacy-related but still annoying bug was that you couldn't set exceptions for pages if they are directly affected and not only their subressources.
I don't have any idea how I should explain the reason as the internal logic of Cloud Firewall is very complicated but it's fixed now.
Let's have a quick look on the next version
Thanks to a contribution by the next version will get a completely new design.
It will work without Bootstrap and therefore reduce the size of the add-on.
Along with that we'll try to heavily improve the structure of the pages to make it easier to understand and look less buggy.
There will be many small optimizations which should lead to a cleaner overall experience.
We don't have any date planned for the next release and it may take some weeks or even a few months as there's much to do in other projects and the current Cloud Firewall version does its job pretty good.
What the hell happened with Mozilla?!?!
Maybe that's what many of you thought when reading about mass layoffs at #Mozilla and no,we don't have a answer to that question,too.
Other alarming developments in the Firefox world are the lack of a working extension support in the new Firefox for #Android and a new big deal with #Google ,the worlds largest threat against privacy.
There are many reasons why we find it important to expand support for Cloud Firewall to other browsers while,of course,still maintaining Firefox support as main priority.
Maybe the current version 2.0.0 will already arrive in some other browsers.
We'll have a look at what needs to be done to support Firefox forks like #Waterfox which already support the modern #WebExtensions and how much we'll have to rewrite to support Firefox forks on a older code base which stick to the old extension format like #PaleMoon or #Basilisk
The latter will be harder to support but if it's not impossible,we'll think about the question if it's worth it as these browsers are a important contributor to diversity in a browser-world where nearly everything runs on top of the same code base written by the worlds biggest privacy threat.
And for those who prefer browsers based on #Chromium we even see a chance of bringing Cloud Firewall to the #Opera add-ons store which would effectively make it available to every user of Opera and #YandexBrowser
This won't be so easy as the API which is responsible for the core functionality of Cloud Firewall is only available on Firefox but maybe we can workaround that somehow by directly throwing HTTPS requests to any DoH (DNS over HTTPS) server but we'll have to see how much of an impact this will have to performance.
My personal guess is that it will be much slower than using the native DNS API in Firefox.
On the other hand,Yandex Browser for Android still has unlimited support for extensions while the new Firefox hasn't so that might be the only chance to continue Cloud Firewall support on the Android platform.
Developing decent support for multiple browsers will be one of the hardest changes that can be done to Cloud Firewall but we feel that it's needed so we'll look what can be done as soon as possible.

Times are changing - So are services

Today we finally gave an update to the list of services on our homepage.
Yes,this blog was quite quiet during the last few months but we still did much work to make the web a better place,mostly with minor updates for #Halcyon which aren't worth longer posts.
The more important news are our two new #Mastodon #GlitchSoc instances and in addition to our first instance . was launched as a totally new service at the beginning of the year to provide a new home for many Spanish people who were moving away from #Twitter to the #Fediverse .
There weren't many Spanish instances back then so we decided to create one,even without anyone from the Nikisoft team being able to read or write Spanish but is a big help in that case.
Some months later,we've taken over as the former administrator wanted to leave while keeping the service up and running.
As always,we wanted to help the free and open social network and therefore made the decision to take this instance over and give it a safe future.
In response to the huge additional need of resources,we expanded the disk space for media on our server hardware and should be well prepared for the next months and then we still have three slots left for another additional hard disks.
As of now,the bandwidth doesn't seem to be a limiting factor - we were very worried about that at the beginning.
All three instances are running on the same machine so that we could setup a VDO (Virtual Disk Optimizer) partition which does deduplication on the media and saves us tons of disk space.
They all seem to have a more or less active community with some people who post on a regular base and we're happy to provide them a free home in the social media world.
On other news,we made the decision to discontinue our services YouFail and ChromeOS Forum and took them down already,including the remove of all links from our information page.
Both sites have never been popular and only wasted resources on our servers as well as money for the domain so we thought it would be better to take them offline,nobody will miss them anyway.
In future we're planning to provide even more services,as always free of trackers and free to use.
In the coming months,important changes to our infrastructure will be made allowing us to scale further and protect the privacy of our users even better.
We're planning to migrate from #CloudFlare as content delivery network and protection suite to the paid Swiss company #KeyCDN because many of our users are worried about the privacy at CloudFlare.
As is billed on a per-use base instead of different fixed-price plans for enhanced features,we will be able to make use of even more features while paying a fair price based on our organic growth.
By migrating to KeyCDN,we will be able to save much bandwidth and traffic due to their improved caching features where edge nodes ask a central KeyCDN cache server first before they ask our own application server.
We expect huge improvements on performance and scalability for our Mastodon media delivery by that.
Additionally we're planning to migrate all of our domains step by step from to as our old provider has made some decisions like preventing all #Tor users from accessing their service and all webpages of their users or uploading backups of all user data to Google Cloud and we're not willing to support that by wasting even more money at this company.
We're a bit sad that it had to come to such an end because we've been using their service for many years but #Hostsharing seems to be a very good alternative which fully respects privacy by not using any third-party services on their website,allowing access using Tor and not transferring user data to third-parties in other countries.
Unfortunately the remaining time of the domains can't be transferred so we have to make all transfers short before the domain expires to prevent the waste of even more money.
For the main domain this means that we have to wait almost three years while we can start to transfer the first domain in one or two months already.
That's all for now and we hope that you like what we did and what we're planning to do.
As always,we're happy about your feedback which you can submit by replying to this post using a ActivityPub compatible software like Mastodon or privately using our contact form at
We'll soon post a follow-up which exclusively covers the development of #CloudFirewall which recently made a new milestone with the release of version 2.0.0

Cloud Firewall - A content blocker for Firefox

We took over the #CloudFirewall add-on for #Firefox which allows you to block six of the biggest cloud providers in a easy way.
Cloud Firewall supports blocking #Google , #Amazon , #Apple , #Facebook , #Microsoft and #CloudFlare by switching just a single toggle.
Unlike other blockers, CloudFirewall doesn't only rely on domains but checks the IP addresses of websites so that it doesn't only block websites which belong to those cloud providers but also all websites which rent their servers there but may be unrelated otherwise.
It was created as a research project by Gokulakrishna Sudharsan earlier this year but unfortunately he abandoned the project and also removed it from the #Mozilla add-ons store.
As many of these big cloud companies are known for collecting user-data, we found it useful for protecting your privacy and protecting your right to choose where you want to see content from, too and so we decided that the development of this add-on must continue.
Now Cloud Firewall is already available on the Mozilla add-ons store again and the source code is available under GPL 3.0 at #NotABug
The biggest change we did for the first version was adding a detailed and user-friendly page with information about which content was blocked on the website currently opened.
It was already possible to copy this information to the clipboard in many formats before (and still is) and you could paste it into a text editor but it wasn't as good to read as it is now.
Other changes are fixes of some well-known false positives like or NoMoreGoogle which were blocked when block Google was checked while, in fact, they aren't hosted at Google or the problem that the popup had a design glitch when the domain name was too long, for example at Onion V3 domains.
We did also change the links for the repository and the credits and changed the cloud order to GAFAM(+C).
As the priority was going online again as soon as possible, that's all we've done for now but there are plans for turning on or off each cloud provider per domain and support translating the interface into different languages by accepting translations from the community.
Another important thing we have to do is checking if the plugin also works with forks of Firefox such as #IceCat , #Waterfox , #TorBrowser or #Fennec
You can download Cloud Firewall for free from
The source code is available on NotABug at nipos/cloud-firewall.
If you find any problems, want a new feature or have any question, you can comment here or create a issue on NotABug.


A Firefox extension that automatically blocks connections to the 6 biggest...

No More Google

Privacy-friendly alternatives to Google that don't track you

No More Google
Cloud Firewall – Get this Extension for 🦊 Firefox (en-US)

Download Cloud Firewall for Firefox. Block connections to pages and web...

Searx App for KaiOS: First version released!

We're proud to announce that we've finished our first mobile app and it's a search app made for feature phones running #KaiOS and released under AGPL 3.0.
It makes use of the Searx API which is also free and open source software and can be used on many public servers.
#Searx can ask many big search engines which can be selected by the user in the background anonymously and combines them into one big results page.
Some people may not know what KaiOS is so here is a short summary:

KaiOS is a operating system for smart feature phones like the Nokia 8110 or the JioPhone.
Phones with KaiOS have WiFi and the ability to install and run apps but they have keys instead of a touchscreen. KaiOS is based on the abandoned #FirefoxOS open source project and all of its native apps are written in HTML, CSS and Javascript. That makes it easy to write apps for it - You only need #Palemoon or an older #Firefox version and a USB cable to make your apps run on the phone.

The reason why we chose Searx as backend is quite simple: It offers a public API without the need to register for a token and without being dependent on a single provider.
As long as we don't experience a outage of the whole internet, that should make our app fail-safe.
To give users as much freedom as possible, you have full control over the Searx instances you want to use - You can select one out of currently five from our list or add other instances and delete predefined ones.
We try to offer as much customization opportunities as possible:

  • You can select the language you want to get results in
  • You can select the source of the autocomplete (or turn it off)
  • You can select the mode for safe search (off/moderate/strict)
  • You can select the search engines you want to use in the different categories

The app is able to search in all categories offered by the Searx API.
Image search allows you to easily download images from the results by pressing the left button.
Like always we try to offer our software in as many languages as possible - Currently only English and German but help in translating is always welcome.
You can translate the project on our Pootle instance or by forking the project and submitting a properties file using a pull request.
The source code of the app is available on NotABug.
There is no information website about the app currently and there is no Mastodon project account.
If you have feature requests or bug reports, please use the NotABug issues or comment on this blog post.
Currently the app is not available in the official KaiOS Appstore because their seems to be a bug at their publishing platform but you can install is manually by downloading the ZIP from NotABug and installing it using WebIDE (Palemoon/Firefox).

Halcyon 2.4.0 adds sharing and more

Yesterday we've released #Halcyon version 2.4.0 which is a bit bigger than usual updates so it's time for a blog post once again.
The biggest and most important thing is that every Halcyon instance has a share page now at /intent/toot where you can link to from your website.
We already have a small script and a documentation page for using the share button,see here
It looks pretty much the same as Twitters share page and also allows writing without being logged in and then login when sending just like they do.
To make a redirect easy,we kept the API similar to #Twitter - You can simply rewrite to
Additionally we're planning a #Firefox extension which should automatically replace all Tweet buttons with Toot buttons so that you can use the share feature also on bigger sites which don't care about the fediverse.
Another thing that changed in version 2.4.0 is that there are small overlays when hovering a mention now.
#Mastodon does not have such a feature but Twitter has it and it's quite useful so we decided to add it to Halcyon.
When hovering over a mention,it will now show some basic information about the user like display name,about me and count of toots,followers and followings.
One of the bugfixes is that Pleroma users weren't able to add new accounts to lists caused by Pleromas change of the user ID format what wasn't fixed in Halcyon at this point.
Another bugfix is that Halcyon does now keep your scroll position when you aren't on top of the timeline and there are new posts appearing.
We're proud to announce that our language support still keeps growing.
There's an Arabic translation now which is unfortunately incomplete but we added it anyway.
This means that Halcyon does now support 13 different languages and we expect this number to grow even more in future.
If you want to help with translating Halcyon,you can do that on our Pootle instance.
Your help is also needed for existing languages as we added new strings for translation with this version.
We hope that you like what we're doing.
Feel free to give us feedback as comment to this post,as NotABug issue or as mention to
We're always happy about constructive feedback,feature requests and bug reports. - Our new Mastodon instance

It's been quite a while since we've taken online the last public service for everyone.
Working on open source software is important for the whole community and it needs much time and resources but our server was quite bored all the time.
So additionally to the open source development stuff which will of course continue,we do now host a regional #Mastodon instance for public registration.
The #Fediverse is a great network with many nice people and it's built completely with open source software.
It's important for us to support a network of this sort and that was the right time to give something back to the network.
We had planned putting online a new Mastodon instance for a long time but then we saw that a small German instance would go offline soon and decided to take it over.
Continuing an existing service and making sure that all existing users don't lose their digital home is much better than creating a completely new service out of the nothing.
You can find the instance at but it's mainly meant for people near Muenster and most posts are in German.
The instance runs with the #GlitchSoc software (Git repo) which is a fork of Mastodon which allows more settings for users as well as server admin.
For example GlitchSoc makes the 5000 chars limit instead of 500 chars possible and that's important for heaving real conversations and not just a short message.
Additionally we do now have a #Halcyon instance at so you can use it with the easy and beautiful design of Twitter. runs on a HP ProLiant DL380 G6 server with two Intel Xeon Quad Core CPUs,32GB memory and 4x72GB RAID5 HDDs so there is still much space for new users.
Feel free to check it out and give comments how you like it.
For the next few weeks or months,there are even more free public services planned but you have to wait for the details until it comes online.


A glitchy but lovable microblogging server. Contribute to...


Ein kostenloses und werbefreies soziales Netzwerk für Personen aus Münster...

Mastodon hosted on

New blog with new design and ActivityPub support

It was absolutely time for bringing a new blog online.
The previous one was already quite outdated when we brought it online but we decided for it anyway because it was simple and free and we didn't have that big server capacities back then.
In the old situation it was a big advantage that it was centralized and hosted for free on MyBlogs servers so we had no trouble with it.
The downsides were the third party ads which ignore your privacy and couldn't be turned off - And for us that we had to rely on a third party we couldn't control.
We learned our lessons when there were some server outages but due to the software being proprietary,there wasn't a quick and easy solutions so we stayed there a little longer and longer and...
After our big success with the #Mastodon client #Halcyon and a growing number of users which could theoretically visit the blog,it was clear that something better would be needed sooner or later.
It's later now and the new and much better and more modern blog is finally online.
It was clear that the next blogging software must be open source and run on our own infrastructure which grow enough to handle all the traffic - At least we hope so,let's try if it's true.
Another of our requirements was the #ActivityPub support because we're doing much in the ActivityPub network so it wouldn't make sense not to have our blog there.
With this requirement the amount of available software wasn't that big anymore: Only Wordpress,Plume,WriteAs and were left.
The biggest blogging software is #Wordpress but it's totally bloated and nearly every theme includes some third-party shit and ActivityPub support is only available using addons which are still in alpha stage so this one fell out of the decision quite early.
#WriteAs and #Plume are both very cool softwares which are built for ActivityPub Support from the very beginning and they are free of trackers and not that bloated so good choices but they're made for instances with more users what you can see in the way it's built and we think that's great for the big majority but not for our simple and small blog which should just contain some project updates.
Only #MicroblogPub is left at this point and that has been my personal favourite from the point when I first heard about it but when it also made the best points in the direct comparison,it was clear what software we have to use. is a single-user blogging software written in #Python which is open source and has only a few dependencies.
In it's original version you can see that it's meant for short posts even if it doesn't have a hardcoded character limit and should be used more in the way of a lightweight,single-user Mastodon instance.
To make it look more like a normal blog,we've rewritten most of the frontend source code using PureCSS which looks modern and isn't that bloated.
We made our modified source code available in the NikisoftBlog NotABug repository to make it easy for other people to run their own ActivityPub based blog.
We hope that you like what we did here and we're happy about comments,bug reports and feature requests in the comments (you can just reply to this post using a ActivityPub supporting software) or in our #NotABug issues.
But when requesting a feature,please keep in mind that this is a low priority project which we mainly do for our own use and as long as we don't attract hundreds of users,it may take some time until feature requests are implemented because we also have to work on our more popular projects.
Like this post?You can also follow this blog now using every ActivityPub compatible software.


A self-hosted, single-user, ActivityPub powered microblog. - tsileo/

nipos/nikisoftblog fork with new design and some customizations for running the...

Zanata outage and our reactions

On the 28th March 2019 Zanata,the translation platform we use for community translations of Halcyon,went down for the first time.
It was down for quite a few days but every service has some server problems sometimes so we didn't expect that as a big problem and just continued to use it when it was back online.
There was nothing what would make us think about this happening again soon or even going down forever.
Unfortunately it happened again and was reported on the 26th April 2019 at Zanatas issues page.
This time the outage was one week long - it ended today,the 30th April 2019 - and we gave up the hope that it will work again some day,what was of course wrong but we expect further outages.
While trying to find out more about the service status we found that Zanata is no longer maintained,the Git repository hasn't had any update for months and Red Hat doesn't have a team for managing Zanata anymore.
Knowing this it was clear that we needed a new translation platform but when searching for hosted solutions,we could only find paid ones but good software for hosting a own translation site.
We decided that Pootle looks interesting and may be worth giving a try so we did it and are quite happy with the results.
Yes,selfhosting Zanata would have been possible too as it's open source but it's written in Java what would have put a quite heavy load on our servers and the project is no longer maintained so,thinking of running in long term,that would have been a bad idea in general.
When trying to setup Pootle,we experienced very many problems and it took hours to find the cause and fix it but now we can warn anyone who wants to setup his or her own Pootle instance.
Please don't use MariaDB/MySQL for it as it messes up collations somehow what prevents the initdb command from working and will cause some unexpected error 500s later when trying to use it.
We finally decided to run the whole installation process again using PostgreSQL as database backend and initdb worked just fine and we have yet to experience the first error 500.
First we thought new translations which were made after the release of Halcyon 2.3.0 would be lost but luckily Zanata came back online to allow us downloading backups.
Because Zanata is no longer maintained and outages are getting more often,we consider it bad as long term solution and decided to go with our Pootle instance now even if Zanata may work as a short term solution again.
We imported all data to our new Pootle instance,luckily with zero data loss for the translations,only new user accounts are required.
Pootle seems well maintained with a quite active Git repository so this should do the job for a long time hopefully.
At least we will no longer have to worry about data loss as results of outages because everything is stored on our own servers now.
If you want to help translating Halcyon,you can do that on our Pootle instance from now on.