Why do you need the API key? Why not just do it like a traditional escrow service: you receive both the money and the item traded to a steam account you own. Then once both are received you send the money and you send a trade request giving the item to the receiver?
Not updating a web browser is a fantastic way to make your computer very insecure.
I understand the desire to keep things the same but personally I would value security above that.
And what is safe?
C has well defined, tested, and documented specifications which layout exactly how to use C safely.
Languages like Rust are more safe but nothing is just safe. If you are an inexperienced developer it is still very easy to write insecure code in Rust.
Sure, moving to safer languages is good. But it is impossible to rule out the use of a language so established that every major operating system is written in it. It is practically impossible to not use C - safe languages are normally bootstrapped by it and eventually your “safe” code will run in an environment programmed in C.
C++ can be safer but that does not mean it is safe. The fact you have out of bounds accesses, even if it is rare, is not really acceptable in a language that would like to be considered “safe”.
Could you clarify what you mean by “coming through education”?
I would’ve thought that population representation is the definition of underrepresented because it shows they are underrepresented in the population.
But I am interested if there is another way to measure this.
Which network do you connect it to? Do you connect it to your home network which all your other devices are connected to and through which all your internet traffic is sent?
Do you use it in your house? Does it then record everything it can see and hear within your house?
It was a while ago but the ones I remember were email subscriptions, custom javascript, and custom instance support in the iOS app.
Thank You for clarifying the reasoning. That does make more sense and makes it more justified. I still think it would be better to at least have the write.as fork be open source even if you can’t ensure stability/any sort of support.
I self-hosted a writefreely instance for a while but I found many features were proprietary and only available in the paid managed hosting (write.as). All features that I didn’t need that much and could workaround however it just made me feel quite dissatisfied with the project.
People self hosting are not likely to be the same people who would pay for managed hosting so it makes no sense to lock features off for them.
I forked the codebase and added stuff myself for a while because even after funnelling users to their commercial option they still do hardly any development, see how long this one line PR I made took to be merged: https://github.com/writefreely/writefreely/pull/429.
Now I just have a simple python script that makes everything I need in a blog [0] (markdown, resources, mathjax, atom feed and all completely static with no JS). There is no need to have complicated blog services, just compile static html.