This is literally like saying "Dropbox is just a remote server, you could easily rent your own, install rsync, and that's it."
You would be technically totally correct. But there is a reason people use Dropbox and pay money for it. Convenience is value.
Also, I think you dont fully understand what this app does. Your script is dramatically underestimating the complexity of keyboard, TouchID, cables, Intel vs. Silicon, the Intel bugs, the M3 model hardware API bugs, the logic behind closing/opening, plugging and unplugging, complex scenarios, restarts, UI, translations etc.
The app has even price parity, meaning people in less developed countries pay much much less for it. There's no reason to make the life of people harder who just sell something tiny for a price of a coffee, and on top even give it away for free during testing phase.
Use your skill to build alternatives of big shady corporate software, not harming indie devs.
Can you honestly say you didn't use an LLM to write your app?
> Also, I think you dont fully understand what this app does.
I honestly do not care what your app does. There were people in the comments trying to understand how it worked, so I vibe coded this. I have no interest in competing with your app.
> Use your skill to build alternatives of big shady corporate software
I do, but I also don't keep simple concepts draped behind paywalls.
What? the app was of course built with usage of AI, this is industry standard. Nobody writes code character by character by hand anymore. Software engineering is not "coding" alone.
I also get strong reddit moderator personality vibes from you.
That’s what I thought. I wonder if that’s true though. I’m sure 80% take no time but actually productizing it takes forever. Now you’ve got a maintenance burden too. I’m really curious how long it would take to implement harvest and the ecosystem around it these days.
Home grown product isn't going to match a saas product's features. But you dont need most of it anyway. so home grown gets the job done. Till it hits entropy or the roi is gone. Problems will show up a few months / years down till it isn't worth the effort or the savings.
Saas products that survive this AI wave are going to come out stronger on the other end.
It took me about 10 days to update an existing business app that I used to include functionality replacing harvest time tracking, invoicing (with a far superior QBO sync, saving us days of people time per month), and forecasting (Forecast was never well integrated with Harvest).
Yes, we are picking up a maintenance burden but the 10x price increase in our case made it a very easy cost/benefit equation, and I decided that as a primary technology in a consulting business it was worth controlling it.
I have a long list of features to add to the app, things that Harvest and Forecast never did to help me plan and run the business. It’s worth noting that 100% of our payments are ACH so I did not have to do Stripe integration or other payment processor integration.
But we were finally able to model the notion of the “prime contractor” which is a part of our business. Sometimes we have both an end-client and an intermediary (prime contractor) for the same project, meaning different legal entities for the bill-to and ship-to entities. We had workarounds in Harvest and QuickBooks for this but now it’s directly modeled into our app and it saves us a lot of them.
Time tracking and invoicing are unavoidable complexity in a consulting business, particularly at scale when you’re spending lots of time dealing with edge cases like invoice reinsurance (driven by time card mistakes, changes to purchase order numbers, or the need to move time from one purchase order to another).
We’ll probably have some weeks where we need to spend 2-8 hours to maintain the Harvest/Forecast functionality. And other (most?) weeks where we spend no time. The real takeaway here is we finally have a tool that perfectly models our business, and saves days of person-effort every month. It will probably allow us to delay hiring incremental operations personnel. That alters the break even calculation significantly.
If it's an internal app, you stop adding features when you have all the features you need.
I've vibe-rebuilt several apps for myself and after a certain point I don't feel like anything is missing so I just stop touching it entirely except to fix a rare bug here and there.
I argued this before. I think it makes no sense for eg an estate agents to vibe code a CRM, but if you're a tech firm (or a big firm with a tech department) I think it is worth a shot, especially if you only use 50% of the features in the software you pay for.
You can also tell Claude to setup scheduled tasks.
This is very helpful when you want Claude to do something specific, like analyze the next phase. Review past performance etc. I have found this to be a little better than Goal. However, cron tasks only continue for 7 days.
> Not to mention the many inconveniences this would bring about.
This is what reinforces the problem.
When we choose conveniences, we reinforce them. This makes it harder to get away from the things that brings us that convenience.
Conveniences to be able to get a hold of anyone in seconds rather than waiting. Believe it or not, there was a time when we were just, not available. It was OK.
Did that mean that things were a little more challenging? Of course, road trips or going anywhere new meant more upfront planning. Not knowing where your children were brought anxiety which meant rules. However, it was all manageable. By ALWAYS choosing conveniences, we shut the door on alternative options which in turn make it harder to deal with inconveniences.
The other side of this coin is that not everything about the past was better.
I’m struggling to see how having anxiety about losing your children is better. I’m struggling to understand how knowing where they are would lead to having fewer rules.
I struggle to figure out how my friends being more available to text is a negative. What was character-building about calling them on a landline or losing contact with them entirely as an alternative?
I got chicken pox as a kid, that doesn’t mean my kids should get it.
I’ve had arguments like this with my parents about urbanism. When they grew up, the city was dirty, crime-ridden, etc. They also grew up during a time when the automobile was like the tech industry of their day. It was an innovation that changed their lives for the better in their opinion and lived experience. Their house got bigger, their car got bettter and lasted longer and their neighborhood got cleaner and safer, in their eyes.
My parents feel like trying to use the car less and switching to public transit or cycling more is like denying progress. What was the point of all that innovation and progress if we are “going backwards” in their eyes?
The end result of these discussions isn’t that I don’t believe in urbanism anymore, but I’m now more accepting of their point of view on the subject. I see their viewpoint as more valid than I used to. There’s nothing horribly wrong about their way of life even though I don’t necessarily want to adopt many aspects of it.
I am not saying that those things have no value. The opposite is definitely true. However, you are accepting a lot of baggage by reinforcing the systems that bring those conveniences. Now, you MUST have a cellphone or you are a Luddite. You MUST have a cellphone or you can't read a menu at a restaurant, unlock the door to your hotel room or access your bank funds.
You now have lost digital sovereignty to large corporations because you need to be able to get a hold of your kids within seconds.
All conveniences come with costs that you and society must bare.
Last two sentences of your first paragraph are definitely not the sort of thing I was trying to say is okay.
I also don’t think some of the conveniences I talked about have much of a cost. My kids having a cell phone with basic phone and texting capability isn’t a digital sovereignty issue.
And I’m not sure if digital sovereignty matters if the alternative is digital abstinence.
That’s like saying “When you buy a Toyota Camry your life is beholden to Toyota, you should just walk to your destination.” The trade-off isn’t really even, is it?
> My kids having a cell phone with basic phone and texting capability isn’t a digital sovereignty issue.
Of course it is, the first version of Twitter was a texting platform. You can't draw some line and say that this is the end of the baggage that comes with this convenience because that is not how the world works. The inevitability of social pressure means "keeping up with the Joneses" so your kids need to communicate with others, not just you.
Just because it doesn't come in the form of an app doesn't mean it is safe or come without risks.
Telecoms (calling and texting) are literally regulated utilities. I’m confused at where the baggage is.
I’m failing to see how Twitter is relevant.
I’m failing to see the “keeping up with the Joneses” factor here. I am talking about basic cellular service not a $1,000 iPhone loaded up with brain rot apps.
Regulated in what way that is relevant to the concern about digital sovereignty or privacy?
> I’m failing to see how Twitter is relevant.
My point is that voice and text ONLY (dumb phones) isn't some significant change from apps in terms of the concerns I am raising.
> I am talking about basic cellular service
If you and your children can maintain that situation, great, it doesn't change that society has NOT accepted that. That society sees you as unusual for not conforming. Which is the entire point of my argument. The pressure to conform doesn't yield because of a single person's choice and many use the arguments you are using to maintain their children's access to a $1,000 iPhone loaded up with brain rot apps.
I gotta be honest I don’t care enough about this subject enough to keep going lol
I am really just not in any pickle and don’t lose sleep over any of this. That was my original entire point is that sometimes it’s acceptable to allow things to be convenient.
Car dependency is an excellent parallel. People buy cars on the promise that they should expect freedom of movement, but then they arrange their lives so they can only go where roads have been paved, and arrive where buildings have been demolished for parking lots. They become financially dependent on oil extraction in the Middle East. They become incapable of getting anywhere alone when they lose the ability to drive, due to ailments or age.
So why do we do it? Because we can't imagine living without the convenience of our phones.
And similar to a phone, I don’t usually think that the answer is to just not own one at all.
I’m all for reducing trips and being more mindful about car dependency but I’m not personally going to sell my car because I can afford it and it makes my life better.
Are you imagining a modern society that developed without cars as being more of a burden to live in, or are you imagining the current society, developed with cars, as being more of a burden to live in when just getting rid of cars? Because yeah, getting rid of a car is going to make most people's lives harder. That's kind of what makes it a dependency.
When cars became popular, a lot of urban areas were developed under the assumption that all destinations would be reached by car from that point in time onward. There was no need to consider the idea that someone might not be able to or want to reach a destination without one.
I’m fine with cars being a beneficial convenience, an attainable luxury for the masses, but I think that any area with sufficient population (which isn’t very much) can support the idea of families being able to reach a significant percent of their daily destinations without a vehicle, and perhaps even preferring to do so.
It also saves a tremendous amount of resources and cost of living to reduce car trips per week per person by even a small amount.
When smartphones became popular, a lot of social functions developed under the assumption that all participants would have a smartphone, and have it with them at all times, connected. There has been no need to consider the idea that someone might want to participate without one.
You're arguing that car dependency is fine (for you). I'm arguing that car dependency is a good analogy for phone dependency.
I'm not a parent and a bit autistic so excuse the unemotional reply but surely there are other ways not to have anxiety about your children surely?:
Teach independence/self-defence/street smarts, encourage weight lifting for older kids, therapy/meditation for yourself (some anxiety is natural of course!), move to a safer city, have more children (easier to pair them up on adventures, plus less subconscious physiological fear of losing your one and only child), distract yourself and stay busy, go with them to places the first few times to assure yourself then take off your training wheels. Or just say no to certain things.
It doesn't seem to me a special case of anxiety that can only be addressed by spy apps and knowing you might be able to instantly contact them.
Knowing where they are isn’t necessarily “installing spy apps,” it can just mean being able to call them or text them.
“Move to a safer city” is a lot more expensive than a phone plan. A lot of people don’t have that luxury.
I agree that all the things you talk about are life positives but the way I see it, giving a kid who is old and mature enough to use one a cell phone is like a $15/month cost proposition for an outsized benefit of being able to contact them.
lol, have my kids carry a phone or have more kids so the can be paired up.
That’s a wild thing to say out loud. And absolutely doesn’t solve the problem. Kids need to have their own friends and own social circles if you want to teach independence.
The configuration change was never a full protection from this vulnerability because the problem is with how PHP processed the request well before the configuration or your PHP code was executed.
> because the problem is with how PHP processed the request well before the configuration or your PHP code was executed.
That's what I wrote? You can't do anything once PHP executed. It could still be worse, because you can still prevent PHP from running, because there is still the webserver before. If it were in the webserver itself, you couldn't do anything, short of stopping the server from running.
> The configuration change was never a full protection from this vulnerability
It is, if the configuration change prevents PHP from running. That's how you could say it is overblown. You are not vulnerable if you don't run PHP.
You kept talking about some configuration change that makes things "overblown", without making it clear you meant "turn off PHP". So yes that's misinformation.
It's not overblown if the only non-patch fix is "turn off PHP".
And that's assuming you actually meant "turn off PHP" the entire time? Your earlier phrasing suggests you have something that leaves PHP running in mind, but if that's entirely hypothetical then again we're back to misinformation. (And when you argue it's Turing complete, that only means that a patch must be possible. It doesn't mean there's a config fix.)
My first statement was "Not having made the claim", to indicate that I do not necessarily think that. My second was "took down my website too" to indicate, based on what understanding I did and plan to act on.
> And when you argue it's Turing complete, that only means that a patch must be possible. It doesn't mean there's a config fix
The config could be, run a simulation on the input data to decide whether it would allow for RCE and then decide whether to run PHP or not. I sure hope nobody is actually doing that, but it is sure possible.
> And that's assuming you actually meant "turn off PHP" the entire time?
I did mean "only execute PHP, when you know the input doesn't trigger it", the policy of never invoking PHP at all, does satisfy that.
> The config could be, run a simulation on the input data to decide whether it would allow for RCE and then decide whether to run PHP or not. I sure hope nobody is actually doing that, but it is sure possible.
That is not a config. That's a whole new program.
> My first statement was "Not having made the claim", to indicate that I do not necessarily think that. My second was "took down my website too" to indicate, based on what understanding I did and plan to act on.
But with everything else you still made it sound like you were supporting it.
> I did mean "only execute PHP, when you know the input doesn't trigger it", the policy of never invoking PHP at all, does satisfy that.
It satisfies it, but in a way that doesn't make the exploit overblown.
It's obvious that you can avoid a PHP exploit by turning off PHP. That's not nearly enough to make the worries overblown.
"It could be even worse" is the only conclusion we can draw from it being in php and not the web server. And that conclusion is basically meaningless.
That's the distinction between being able to do something or not if you do not have control over the webserver, as is likely the case for a lot or PHP websites, so I wouldn't say it's meaningless.
https://github.com/kxrm/displayoff/blob/main/displayoff.c
reply