ciaovietnam

The email returned by OAuth providers is not always verified and thus cannot be trusted, anyone relies on the email as the ID is open to compromise. The sub claim should always be used as the ID, if you can prove that "the sub claim changes in about 0.04% of logins" then it's Google flaw and they should fix it, otherwise it isn't and there is no need to add another ID to the claim.

Please give LiteGUI a try (https://github.com/SiteGUI-platform/litegui), like Wordpress it was built for freelancers/agencies to create more plugins/apps/themes easily.

What kind of integration between your todos and knowledge? If you haven't found one, how about building your own todo app that fits your needs. I have a demo here https://community.sitegui.com/blog/creating-the-first-applic...

We were able to leverage Anthropic AI to build BuilderAI for generating composable apps on top of our low-code platform. Thanks for making this possible. Here is the demo if you are curious https://youtu.be/oz35He-9M8s

SiteGUI has a strategy to mitigate stored XSS in the third party templates while Wordpress and other CMSes may not. Stored XSS is one of the main reasons that Wordpress sites often get hacked/hijacked.

In fact, the lowcode/nocode platforms produce very well structured code behind the scene and they can train LLMs to build apps following their well defined structure, which means their apps can still take advantage of the LLMs but will have less bugs than just letting the LLMs produce a stand-alone app. Of course, the LLMs can produce more versatile apps than lowcode/nocode platforms but I don't see the LLMs as the competitors.

With QR code and modern banking system, this is more convenient for customers than ever. Customers can make order online, choose QR code direct bank transfer as the payment method, the store then display a QR code (containing the amount, charge ID and relevant bank account info) and the customer just uses their mobile banking app to scan the QR code and authorizes the payment. 5 seconds later, the online store gets a webhook notification from their bank/processor showing the payment has been received, along with the charge ID to finalize the order. The QR code payment system has been very successful in other countries but not in the US yet.

Exactly. For individual, hobbyist developers, just showing their work might already be a strong incentive but for profit seeking companies, the motivation to open source their code hinges on tangible benefits like you said. We're developing a digital platform with a marketplace for 3rd-party developers to contribute and make money from their contributions, at one point we had to decide whether we should open source our code, the pros and cons in doing that etc. And we came to conclusion that, in our case, by proving both cloud and open sourced version will definitely help drive more attention to our cloud offerings and attract more developers to provide/sell their own applications on the marketplace. However, we have to keep our focus on our cloud version first and delay the release of the open source version for at least 1 year or until our cloud gets enough traction/attraction. I don't know if this will work out well in the end but we have got to try.

Don't worry about the Deleware franchise tax, what you should be worried is the US federal corporate tax which is significantly higher than that of Singapore. Cayman Islands? Good luck finding a credit card processor to process your customer payments.