You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're a bit stuck at the moment to release TcMenu 4.5.0.
Over the past year the cost of Windows code signing certificates has spiraled to a level that the project can no longer afford. What used to cost us about £100 a year on a three year term, now costs over £600-£800 for the same term. We simply cannot justify spending this amount on a certificate for Windows deployment. We can release the same UI on MacOS for £89 a year, which is far more reasonable.
Given that I've fixed the immediate issue of ESP32/Arduino 3.3/IDF5 support without the need to release TcMenu itself, there's probably no immediate rush for this release, a few extra weeks wait is not really an major concern.
I've applied for an Open Sign certificate and we'll see where that leads, but in summary if that is not successful, we'll need to take a call between releasing on Windows with a self signed certificate, or crowd funding for the cost. As I've said before, we don't track users, so we don't really know how many people are using it, other than there seems to be about 60 clones a month, and around 300 direct visitors, but we don't even know how successful the crowd funding would be.
In the worst case, it will be released from the nightly build self signed with a checksum.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We're a bit stuck at the moment to release TcMenu 4.5.0.
Over the past year the cost of Windows code signing certificates has spiraled to a level that the project can no longer afford. What used to cost us about £100 a year on a three year term, now costs over £600-£800 for the same term. We simply cannot justify spending this amount on a certificate for Windows deployment. We can release the same UI on MacOS for £89 a year, which is far more reasonable.
Given that I've fixed the immediate issue of ESP32/Arduino 3.3/IDF5 support without the need to release TcMenu itself, there's probably no immediate rush for this release, a few extra weeks wait is not really an major concern.
I've applied for an Open Sign certificate and we'll see where that leads, but in summary if that is not successful, we'll need to take a call between releasing on Windows with a self signed certificate, or crowd funding for the cost. As I've said before, we don't track users, so we don't really know how many people are using it, other than there seems to be about 60 clones a month, and around 300 direct visitors, but we don't even know how successful the crowd funding would be.
In the worst case, it will be released from the nightly build self signed with a checksum.
Beta Was this translation helpful? Give feedback.
All reactions