if only its that easy, but i still need to sit in the office for 12 hrs and pick up phone calls because AI cannot do one single specific task at my job (sorta like captcha thing but for human)
also 
nothing a VPN canât fix.
or are they outlawed in HK too?
There are also some LLMs you can run locally, without requiring an internet connection. That being said if youâre not a programmer already then youâll have to wait for someone else to build / set up the tools for you 
Iâve got an uncensored ChatGPT4 with 90% functionality on my PC, locally. LoL. Seems to work really well. Though I do have to clear it more frequently than I would like. It filters nothing. 13 billion parameters, and it will be 30 billion within weeks. I love it.
Finally have a better reason than gaming to have serious hardware.
1 Like
Might need to start using some sort of tire sealant.
laughs in polyurethane longboard wheel
2 Likes
I think the people has spoken
1 Like
New drinking game everybody, take a shot a and read a paragraph of Shakespeareâs 12th night; repeat until entertaining
1 Like
Iâm curious, what issues have you run into using the newest tool on older firmware? As far as I knew, the only remaining bug was during remote setup, which has now been fixed.
I was under the impression that all the important bits like detection results and current limits were calculated based on the firmware present on the ESC, not the version of the tool running.
While Vedder does actively push for folks to run the latest firmware, he has also advertised full backwards compatibility in the latest tool versions, and that is his reasoning for only allowing that version of the tool to be distributed.
I was talking about finding older tool versions. Youâre talking about something else which is related, but not the same thing.
Right, and Iâm asking why you need the old tool if the new one is fully backwards compatible. Do you just not like how it looks?
Also, anyone is free to compile an old version of the tool if theyâd like. Iâve done it before using only the included instructions.
Maybe I want the old one. Maybe I am tracking down a problem and I want to narrow down independent variables. Maybe I donât trust VESC. Maybe VESC has a lot of bugs, and I want to use the same version I have on the skate already because itâs safer. Maybe it doesnât matter.
Thatâs the whole thing, it doesnât matter why I want it. They intentionally make it hard to get, and itâs one of the many things wrong with VESC.
Iâm sure youâre a zealous fan of the newest offering, but the real world is more nuanced than that. Itâs just an added complication that doesnât need to be there. And with VESCâs track record of bugginess, itâs not welcome all the time. Sometimes it is. When it is, I will gladly try out the newest version.
Yes of course, but not posting the binaries on the source control âreleasesâ page is not only abnormal, and not only intentional, but itâs a dick move.
1 Like
Which brings me back to my original question:
It sounds to me like youâre making much ado about a problem that doesnât exist anymore due Vedder listening to the community and implementing a solution that meets both his and our wants: a continuously updated Tool that changes nothing about the functionality of old firmware while implementing features for the newest firmware.
Then compile it, or donât replace your copy of the old version when updating. Not continuing to distribute old software when a newer version has been released is not at all an uncommon practice and shouldnât be attacked as though itâs some cardinal sin. Of the 100 apps on my computer, 65 do not distribute old versions unless minimum system requirements have changed.
My point is this:
There are many elements of VESC that could use improvement and should be talked about, but continuing to bring up a problem that has already been resolved due to the communityâs input isnât productive and takes away from our (already shaky in Vedderâs eyes) credibility.
1 Like
Youâre actually the one making much ado.
You continue to bring it back up, and donât realize at all that your needs arenât the same as everyoneâs needs.
Go touch some grass. I just got back from a skate.
1 Like
Unlike Vesc, most of those apps on your computer are thoroughly tested for bugs by teams of professional developers before being released to the general public. Benjamin doesnât seem to do any real-world testing before releasing his new firmware which has caused dangerous bugs to pop up that have endangered riders in the past. Having older versions of Vesc tool readily available is kind of nice when there is a good chance that the newest release introduces an issue that makes it unusable. It is understandable that people would be cautious about switching to newer versions given Vedderâs poor track record.
3 Likes
Itâs also the case that Trampa only tests their ESCs (as they probably should) and not any other VESC hardware. They also prohibit other hardware makers from releasing the software. So by extension, they also prohibit other manufacturers from having âknown safe and tested firmwaresâ available on their sites.
So, in effect, they also in a broad sense prohibit other hardware makers from doing things in a safer manner. And they make it super easy for noobs to be the bone breakers for untested software through dark patterns.
But itâs fine. Because Trampa can make more money this way.
2 Likes
I agree with this completely, and I disagree with Trampaâs stance that itâs always best to run the latest VESC firmware.
My argument is solely regarding VESC Tool, which is fully backwards compatible with any firmware version you choose to run, and no longer bugs you to update the firmware at any point.
I havenât experienced any bugs or glitches from running different versions of VESC Tool on a given firmware version aside from setting up a remote.
Untrue. MakerX and Spintend both host custom (and likely tested) firmware files on their websites without issue.
However, as Iâve said, I do agree that VESC Tool should not prompt the user to upgrade their ESCâs firmware because of the poor track record with bugs and safety issues.
If by âdark patternsâ you mean forcefully prompting the user to update their firmware to the latest, perhaps untested version, the newest version of VESC Tool completely eliminates this problem!
This isnât friendly at all to noobs and forces them to go get a tool from somewhere else to use the files, which they may well then use incorrectly.
You canât see the forest for the trees here. Try putting yourself in a position of a complete noob whoâs never programmed anything before.
Basically, you fail to
and you continue
thinking narrowly about your own use cases.
1 Like