Age Verification
This website contains age-restricted material including nudity and explicit content. By entering, you confirm being at least 18 years old or the age of majority in the jurisdiction you are accessing the website from.
I am 18+ or older - Enter
I am under 18 - Exit
Our parental controls page explains how you can easily block access to this site.

Derniers messages - Page 694

  Forum

Wyldanimal
MODÉRATEUR
Inscrit en Mar 2008
17192 message(s)

Moving iStripper data to a new location

Tout sur iStripper
15 September 2020, 35 réponses
Before windows.
DOS had it's configuration files
Config.sys
Autoexec.bat

Both user editable.
Editing of these was expected and common to make the current running instance of DOS
compatible with the App you were going to use.

It was common to have 10's or 100's of variations that you would rename so that DOS was tailored to your Applications requirements.

It was NOT Hacking to edit and change these...



Windows,

In years past, each Application had it's Own .ini file where needed.
In this file were user adjustable Settings / Variables.

It was not Hacking to open an ini file with a text editor and edit one of the values.

Later, ALL of the ini files were consolidated in to what is known as the registry.
They still function just like ini files, but now located in a common repository.

Editing of an Applications Registry values is not Hacking by definition of hacking.

This is the *****
today, persons with little knowledge, have loosely defined a term to the point where everyone
now thinks that it what it means..

Editing an value in the registry is NOT Hacking.
and telling people that it is, is just promoting the ***** even more.

Currently, there is now more apps going back to the ini files type of configuration
only instead of ini files, XML files are now used...

Many apps now have a combination of Registry values and a local XML file
to hold the configuration values.

These once again, unless security is set
are user editable.

When instructed to make an edit
It is NOT hacking to edit these values...


A call to Customer Support
Caller:
The App isn't scaling to my screen resolution...

Support:
There is a registry value for that.
Use registry editor and find the Key XYZZY/PLOUGH/
Please change AutoScale from a 0 to a 1

That is NOT hacking....



TheEmu
Inscrit en Jul 2012
7424 message(s)

Moving iStripper data to a new location

Tout sur iStripper
15 September 2020, 35 réponses
@Wyldanimal

it is a hack of iStripper not a hack of the registry. At the abstract level it makes no difference at all where iStripper keeps the string holding the directory path (that is just an implementation detail) or what tool you use to alter it is is still a hack. In practice of course there is a huge difference in the way that the hack is acheived but whether you use the registry editor or a hex editor makes no difference in principle you are taking advantage of knowing how to change an implementation detail rather than using an intentional user interface feature of the program you are hacking.

Now if Totem provided documentation that said that this registry value was a supported user interface that that would change it from not being a hack to a recognised way of configuring the program. But Totem do not say this in any user level documentation (only a couple of moderators).

This is all a very ***** thing for this particular case - but it is a major thing in the general case.

As an example, if I remember correctly, Totem have in the past changed the name of at least one of the registry keys used to save some of its configutation (I think that used for the models directory). Changes such as this will typically invalidate any previous registry edits using the old name - though the developers can choose to be nice and support both names - whereas using some fully supported mechanism should not encounter any such problems.