The only ones that really bother me are crippleware.
Either provide the full product, for a limited time/usage, OR, just skip it.
The last fucking thing ANYONE needs is to work through the UI of an app, get everything staged, then get a fucking "buy me" prompt when they click "ok" to start the process.
As far as the 7/14/30 day trials, I'm fine with those, as long as the above is respected, otherwise, GTFO.
Cool amongst peers, sure, but chicks still never paid any attention to me, even after I started carrying around a DTMF tone generator and the knowledge of how to use it... ;)
I found that upgrading mine with a full keypad -- including the ABCD column on the right -- did wonders for my rep. And of course a switch to toggle oscillators, so I could send red box tones.
Ironic considering that the sole reason I ever BlueBoxed was due to computers.
I wanted to connect to BBSes at 300bps that were long distance from my home.
I started blue boxing entirely to access those BBSes.
After I got started, I got really into it. A friend and I did some dumpster dives at the local CO, we learned how to connect to inward operators directly, and using the right jargon were able to essentially control parts of the phone system. We explored and exploited diverters, voice conferencing systems, voice mail systems and more. That friend and I even created our own box, we named the PSI-box (Phone speaker interface). Hold your phone up to your speaker NO MORE!
It led to many things, but what started it was a computer. ;)
> Ironic considering that the sole reason I ever BlueBoxed was due to computers.
Same. The reason I was interested in phone technology back in the mid 1980s is because I wanted to connect to long distance BBSes using my Commodore 64 and long distance phone calls were prohibitively expensive for a teenager (or almost anyone really) back then.
This eventually lead to X.25 networks and ARPANet and early Internet usage and my career as a software developer.
When you consider who's running it, it makes perfect sense.
Only a moron of the scope of Musk would own an EV company, and then become a literal Nazi online alienating the left leaning people, you know, the kind of people interested in climate change, technology and EVs, and cater non-stop to right wingers, the kind of people who think climate change is a hoax, "EVs are for pussies", and love coal rolling.
Yes, because recalls are a good thing, because the manuf. has acknowledged the issue and is trying to address it.
No, because what glue sniffing idiot thought glue would be the best option, instead of just riveting the damn thing down, and never worrying about the pretty little piece of garbage coming loose and sticking the accel pedal down.
Fasteners are very expensive from a production perspective because they take a long time to install. This is why products these days are designed to be assemble with conformal, friction, or snap fit as much as possible.
Deciding to sub in fasteners in the production line would have involved addition of at least one new position in the line to install the fasteners.
Agreed, to a point, but we're talking about the accel pedal in a vehicle with more torque than god.
Glue is insufficient. It was insufficient with it was decided. It was insufficient when it was implemented and while I'm not a car designer, I can
state that glue, in this case? Predictably insufficient.
This is a Support task, not a Dev task. Support should be working the tickets and reporting unsolvable issues with the code, so the Devs can address.
You've been dealing with bad support teams, because your experience is not how support is supposed to work.
Also, we Ops folks truly appreciate undocumented work arounds by the Devs. We love spending hours pouring over a given system, trying 107 different versions of some framework, causing lots of downtime, and working nights/weekends, just to learn that some UNDOCUMENTED cludge fucking bullshit is what's actually causing the issue.
Do better man. You're shitting on more than just the users.
With open source, you're usually reporting to devs. With commercial software, usually to tech support or to nobody.
> You've been dealing with bad support teams, because your experience is not how support is supposed to work.
Yes, I know -- but it is how the majority of support actually is, if there is even support available at all. In a whole lot of cases, there is none.
I'm talking about software meant for consumer use. Software for business use is much better on these issues, although you still do find them. At my workplace, we recently took a large financial hit (and almost lost an important customer) because of bad and unresponsive tech support from a supplier. It happens.
Most of us purchase these services, and pay happily, until the inevitable enshittification step, then it's back to the high seas, because I'm willing to pay for services, but I'm not willing to pay more, to get less, because some assclown has quarterly numbers to make.
