Deep Client Updates?

Auspicious K
by Auspicious K · 14 posts
9 months ago in Help & Support
Posted 9 months ago · Author
@DataMine


That is very strange and definitely should not be happening., do you still have the shortcut on your desktop? I'm curious what the target is. If you installed v13 in the same place as v12, then the shortcut should work just fine.
I don't sadly, deleted and manually replaced with one for V13. (Both the install-generated V12 and V13 shortcuts had the issue.) V12 shortcut has always worked fine for me though, until I tried it today. Both were installed in the same folder as the vanilla client and VU files. -Since I didn't update IMVU to revert the DC, I didn't want to install V13 to a new folder and have dupe files that messed with it. I'd of manually uninstalled V12 first, but no idea which files are the DC's, if said files are even separate from IMVU's.

I'll take a note of the target and pathing if I get the issue next time I run VU though. Fingers crossed it was a one-off fluke, but wanted to bringing it up on the offchance. Or incase anyone else ran into the same.

Yeah, that's normal. At the time, v13 was built off the most recent update, a new one didn't come out till the next day (go figure) but IMVU doesn't always show the dialog for minor updates so I don't think you'll see it even today.
Ohh ok, I getcha. I'm not exactly complaining, considering what was in the changelog for the update. "Updated communication security to permit continued comm with IMVU servers." ..because I totally want more of what I'm specifically trying to cut out with your guys' client haha. Also I found it funny that there was a typo in their changelog. Version 546.0 specifically.
Posted 9 months ago
Auspicious K wrote:
I'll take a note of the target and pathing if I get the issue next time I run VU though. Fingers crossed it was a one-off fluke, but wanted to bringing it up on the offchance. Or incase anyone else ran into the same.

Alright. Usually problems with IMVULite are caused by left over files from the previous version. It's recommended to delete the old folder first if you're gonna install the update in the same location.

Auspicious K wrote:
because I totally want more of what I'm specifically trying to cut out with your guys' client haha

I assume you mean the tracking and what not?

Auspicious K wrote:
Also I found it funny that there was a typo in their changelog. Version 546.0 specifically.

Yeah, I noticed that too lol.
Posted 9 months ago · Author
@DataMine


Alright. Usually problems with IMVULite are caused by left over files from the previous version. It's recommended to delete the old folder first if you're gonna install the update in the same location.
Ok, sweet, thanks for the heads-up! Which folder and/or loose files belong to the Deep Client? I've had zero issues since updating the DC and creating my own shortcut, but handy to know so I can manually delete them for a fresh install if ever needed.

I assume you mean the tracking and what not?
Yeah, exactly that and the chat monitoring. Not a big fan of feeling like I need to look over my shoulder if I indulge in lewder things, or happen to make a bad taste joke to a friend in private. The fact their changelog lists something to specifically counter your guys' clients and give them more snooping power is concerning. I know ever facet of the internet tracks, gathers and uses or sells your data, but not with the lingering risk of limiting free speech and banning you if you say the wrong thing in someone else's eyes. (Within reason.)
Posted 9 months ago
@Auspicious K


Auspicious K wrote:
Which folder and/or loose files belong to the Deep Client?

Assuming you installed it into the vanilla location, everything inside of the AppData\Roaming\IMVUClient folder.

Auspicious K wrote:
The fact their changelog lists something to specifically counter your guys' clients and give them more snooping power is concerning.

We must've interpreted the update notes differently. To me there wasn't anything about countering our clients or giving more snooping power. In fact, there wasn't even any code changes related those things either.

Auspicious K wrote:
but not with the lingering risk of limiting free speech and banning you if you say the wrong thing in someone else's eyes. (Within reason.)

I agree (except for the within reason part).

Create an account or sign in to comment

You need to be a member in order to leave a comment

Sign in

Already have an account? Sign in here

SIGN IN NOW

Create an account

Sign up for a new account in our community. It's easy!

REGISTER A NEW ACCOUNT