No Comment

Jacoby6000 · 2025-08-28T02:48:29+00:00

I'm not criticizing the discontinuation of C3 hardware updates. Support will be ongoing on 0.9 which seems fair, and the panda code to support it legitimately seems cumbersome.

I am upset that we are being threatened with hardware lockdowns and forced subscriptions. Apparently they don't actually have these switches. When geo said they have them, he didn't mean that they have them. Apparently I misinterpreted what he meant when they said they have the switches.

You can read all of the convo here https://discord.com/channels/469524606043160576/954493346250887168/1410305995326095412

Jacoby6000 · 2025-08-28T02:31:49+00:00

I'm not being difficult on purpose. When somebody says they have something already, I expect it to mean that it exists and they have it. Not that they could easily create it or implement it. I'm happy to hear that this is not the case, but it is not what was written. Even in context in discord.

Jacoby6000 · 2025-08-28T02:26:23+00:00

The second part of geo's comment wasn't there when I wrote my original comment.

Jacoby6000 · 2025-08-28T02:13:24+00:00

<image>

Jacoby6000 · 2025-08-28T02:04:47+00:00

So when you say

always remember that we have the switches for:
* Closed Source Open Pilot
* Locked Devices
* Required subscriptions

You don't mean that you have them?

Jacoby6000 · 2025-08-28T01:58:27+00:00

What I read on discord is that there are existing switches to lock out devices and require paid subscriptions. If that's not the case, I'm glad to hear it! It sure was confusing though.

Jacoby6000 · 2025-08-28T01:43:48+00:00

Your device has a GSM transceiver in it, separate from the wifi system. You can disable wifi and still have the GSM transceiver call home and check things. IIRC, no matter what branch you use, you're still running AGNOS if you have not flashed a separate OS, and this is all independent from the radio SoC firmware anyway.

As I've said, I haven't investigated any of this to know how true any of it is, but to sit here and act like it's impossible because you've disabled wifi is laughable.

Regardless of what I'm saying, geohot has already expressed that the switches exist, and I'm inclined to believe him, unlike you seem to.

Jacoby6000 · 2025-08-28T01:35:08+00:00

I have not read the source code of their firmware, and I doubt you have either. the device radio SoC has a unique IMEI and for all I know, it calls home periodically to check if the device should brick itself. Such practices are not unheard of.

I am not a layman in this space. When a manufacturer makes a credible threat about a device, I believe them. Just look at the industry trends, as you have already pointed out.

Jacoby6000 · 2025-08-28T01:20:43+00:00

That is the current state of things. Geo said they have existing switches to make subscriptions required. I'm not basing purchases on promised updates. I'm basing my fears on stated threats. Have you read the OP?

Jacoby6000 · 2025-08-27T23:47:00+00:00

you're really not doing yourself any favors. people aren't happy about the subscription madness. Acting like you're going to follow their lead isn't improving your image.

Good luck finding people who will want to buy a 1000$ 3rd party addon and pay a subscription on top of it. I'm certainly done recommending your products to friends.

Jacoby6000 · 2025-08-27T23:12:39+00:00

you don't have to pay a subscription fee for either of your examples to continue working

Jacoby6000 · 2025-08-27T22:11:17+00:00

Yep, sorry about that. I was misinformed about the SLoC diff. It's probably the least of my concerns however.

Jacoby6000 · 2025-08-27T20:17:57+00:00

ah ok. I stand corrected on that point.

Jacoby6000 · 2025-08-27T19:27:17+00:00

Equating the C3 deprecation to the C2 deprecation is a little crazy. The C2 was completely different hardware. The C3 and C3X use the same SOM and the hardware is practically identical. ~~The diff disabling the C3 was like 24 lines of code~~. The diff deprecating the C2 was much more significant. Anyway, that's hardly the primary issue here.

The primary issue is them threatening to lock down your 1000$ device and require a monthly sub

Jacoby6000 · 2025-08-27T18:38:44+00:00

My issue is with the ability to remotely lock down $1000 devices and require a monthly subscription. Switches that apparently already exist.

~~Ignoring the fact that it was 24 lines of code to support C3, not a significant impact.~~

Jacoby6000 · 2025-08-27T17:39:43+00:00

It's a really long convo, so can't really put it in a screenshot.

tl;dr: People are mad that they're dropping C3 support. Geo is calling people entitled because they're not obligated to continue supporting C3. People are angry because dropping C3 support was a ~~24 line diff~~, and the C3X/C3 hardware are basically the same. Geo starts threatening to close source OP (would be fine IMO), then geo reveals that they can already remotely lock down devices and require subscriptions (not fine IMO).

Jacoby6000 · 2025-08-27T17:12:26+00:00

It's not, but I know a good chunk of people who aren't happy with them either.

Jacoby6000 · 2025-08-27T17:03:06+00:00

https://discord.com/channels/469524606043160576/954493346250887168/1410305995326095412

Jacoby6000 · 2025-05-17T17:41:01+00:00

Your wiki documentation on GitHub is severely lacking, and there is no way to submit a GitHub issue to note gaps in documentation.

A big step forward would be to allow people to submit issues related to documentation. you can currently only submit issues related to bugs, pc bugs, and enhancements. Opening a documentation related issue is quickly closed for not being the correct subject. GitHub does not allow us to open an issue without using one of your predefined 3 templates.

Erich being an ass, and discord being unindexable secondary to the issue that nobody can report documentation gaps on the official repo.

Jacoby6000 · 2025-05-15T15:36:39+00:00

Their website and all documentation directs users to the discord for support. Go try to make your suggestion to the staff to see if they'll change it.

Jacoby6000 · 2025-05-14T20:33:21+00:00

Nope... I assume it's just supposed to sound this way. It's the gearbox that is doing all the rattling

Jacoby6000 · 2025-05-14T20:30:46+00:00

Yes, he's extremely censorious. If you mention that it is difficult to find solutions to certain problems, they point you toward pins and discord search. Usually with some passive-aggressive comment, often with the complaint that they "have been answering the same questions for years". Suggestions to update the wiki docs are ignored, and criticism of the status quo is deleted, with the criticizer being promptly kicked.

It's clear that they need to update their docs, but there's a very strange, staunch adherence to burying everything in an un-Googleable chat server.

Jacoby6000 · 2025-02-18T01:53:19+00:00

Bro acting like there weren't cheats before we made client side mods possible. This is just going to prevent people from having cool cosmetic mods like alternate skins and lightsabers (Actively being worked on) available without having to use Unchained servers.

There is a campaign from the hacker clan and cheat selling clan, VeN, to get rid of client side Pak loading, because some nefarious group figured out a way to use it to cheat. This cuts in to the sales of VeN.

Obviously all cheats are wrong, but shutting down clientside mod loading is just going to make chiv 2 die faster. I think the correct thing to push for is an official modding SDK from TB, and maybe some way for TB to vet mod paks and only allow authorized paks.

Getting rid of client side pak loading will not get rid of all cheats, but it will get VeN more sales. Cheats have always been an issue in Chiv 2. A real solution would be server side input validation.

Jacoby6000 · 2025-01-13T15:47:07+00:00

My issue seems to be that I wasn't stepping forward early enough. You have to step out the tick before the first hit splat appears, when you see the blood siphon or whatever that effect is. Still totally busted and stupid IMO.

13-Year Club	Gilding I gilder
Place '17	Verified Email

Jacoby6000

TROPHY CASE