Use tag-based node authentication. Login as a user and then switch the device to use a tag. I just recently did that and retained the usual 6 months expiry. I can also disable key expiry completely.
Skill issue. Not to mention the ongoing effort required to maintain and secure the service. But even before that, a lot of people are behing CGNAT. Tailscale makes punching a hole through that very easy. Otherwise you have to run your own relay server somewhere in the cloud.
>Yet if I spent one hour making my app one second faster for my million users, I can save 277 user hour per year. But since user hours are an externality, such optimization never gets done.
I have never been convinced by this argument. The aggregate number sounds fantastic but I don't believe that any meaningful work can be done by each user saving 1 second. That 1 second (and more) can simply be taken by me trying to stretch my body out.
OTOH, if the argument is to make software smaller, I can get behind that since it will simply lead to more efficient usage of existing resources and thus reduce the environmental impact.
But we live in a capitalist world and there needs to be external pressure for change to occur. The current RAM shortage, if it lasts, might be one of them. Otherwise, we're only day dreaming for a utopia.
I am not a system programmer but, from my understanding, Torvalds has expressed strong opinions about microkernels over a long period of time. The concept looks cleaner on paper but the complexity simply outweighs all the potential benefits. The debate, from what I have followed, expressed similar themes as monolithic vs microservices in the wider software development arena.
Sure. Till an extent. And if you run some mission-critical application, definitely.
But most applications run fine from local storage and can tolerate some downtime. They might even benefit from the improved performance. You can also fix the durability and disaster recovery concerns by setting up on RAID/ZFS and maintaining proper backups.
Inability to build a business easily nor allow others to build one. The union culture is way too strong. There is a joke that the Kerala model of development requires a rich oil state nearby.
There are hundreds of people selling pre-built components, landing pages, templates etc. This at least gets you up and running and not stressing over design. As a dev who lacks design sense, this was immensely helpful.
Other option as sibling points out is to use bolt or lovable and give it explicit instructions on what kind of design to use. For example, with lovable, try this prompt "use neo brutalist design."
If you don't have a lot of services to access, you can hard code the tailscale IP address in /etc/hosts.
My personal /etc/hosts is at 10 services all hard coded since the internal IP address of a machine on tailscale is static. Way cheaper and easier to deal with than setting up a separate DNS resolver.
Of course that won't work if you have hundreds or thousands of services to work with.
If I may ask which model are you using? I have tried OCR'ing my bank statements in AI studio and the results have been less than optimal. Specifically it has a tendency to ignore certain instructions combined with screwing up the order.
Some pointers on what worked for you would be greatly appreciated.
After reading the book my understanding was to not even ask this question. See if they have already tried to solve the problem by looking for another app or going to excruciating lengths to solve it another way. If yes, then they will probably buy your product.
so in a quick glance, this does not look like nginx/caddy. It is not a binary you download, install and just configure to talk to your upstream servers. Rather a set of packages which you assemble to fulfill a particular use case. You basically end up writing a "new" reverse proxy just for your use case.
Not sure how useful this would be for anyone except very large businesses or someone like cloudflare itself.
No one can say for sure how the entire thing is going to turn out. As investors, there's no harm in placing multiple bets as long as a small number of those bets end up giving an outsized return.
Not really true. ADATA pretty much demonstrated that you could get away with swapping the controller at least 3 times and slowly shaving off performance so that people won't notice until they actually did. And the performance was down by 25%-40% in the third swap. This sets a precedent and sooner or later other manufacturers will follow.
My pet peeve with the whole debacle is that words and promises no longer matter especially when marketing ends up using words like "upto."
Give me a minimum, maximum and specs written in stone and I won't care if you change out components. As it is now, the entire thing has become a game of whack-a-mole, SSD reviews are loosing their relevance and given enough time (+current trajectory) we could easily end up in SSD market which is more like fast fashion than anything else.
Eh. Governments should absolutely not get in the business of creating or running an app store. Mobile computing is, effectively, a necessity in the modern world but the web already serves as a great independent distribution platform. We should rather focus on not enabling the technology giants to gimp the web for their business moats.