Privacy Policy for “- Tower of Hanoi -” iOS Game

“- Tower of Hanoi -” iOS game (Game) was developed for end user (User) by Dmytro Siedukhin (Developer). Beyond the information Apple Inc. provides to Developer that User can decide to provide, Game logs no information about User. Also Game uses no third-party analytics or advertising frameworks. Game does not collect, transmit, distribute or sell User data.

Changes To This Privacy Policy

Developer may update this Privacy Policy from time to time. Thus, User is advised to review this page periodically for any changes. Developer will notify User of any changes by posting the new Privacy Policy in this blog.

This policy is effective as of 2024-01-22

Contact Us

If you have any questions or suggestions about this Privacy Policy, do not hesitate to contact Developer at alphaomega11111111@gmail.com.

– 河內塔 – iOS 遊戲的隱私權政策

-河內之塔- iOS 遊戲（遊戲）由 Dmytro Siedukhin（開發者）為最終用戶（用戶）開發。 除非Apple Inc. 向開發者提供用戶可能決定提供的信息，否則本遊戲不會記錄有關用戶的信息。 此外，該遊戲不使用第三方分析或廣告框架。 遊戲不會收集、傳輸、分發或出售用戶資料。

本隱私權政策的變更

開發者可能會不時更新本隱私權政策。 因此，建議使用者定期檢查此頁面是否有任何變更。 開發者將透過在此部落格上發布新的隱私權政策來通知用戶任何變更。

本政策自2024年1月22日起施行

聯絡我們

如果您對本隱私權政策有任何疑問或建議，請隨時聯絡開發者：alphaomega11111111@gmail.com。

Политика конфиденциальности для iOS-игры «- Ханойская башня -»

Игра «- Ханойская башня -» для iOS (Игра) разработано для конечного пользователя (Пользователь) Дмитрием Седухиным (Разработчик). Помимо информации, которую Apple Inc. предоставляет Разработчику, которую Пользователь может решить предоставить, Игра не регистрирует никакой информации о Пользователе. Также приложение не использует сторонние аналитические или рекламные фреймворки. Игра не собирает, не передает, не распространяет и не продает данные Пользователя.

Изменения в настоящей Политике конфиденциальности

Разработчик может время от времени обновлять настоящую Политику конфиденциальности. Таким образом, Пользователю рекомендуется периодически просматривать эту страницу на предмет любых изменений. Разработчик уведомит Пользователя о любых изменениях, опубликовав новую Политику конфиденциальности в этом блоге.

Эта политика действительна с 22 января 2024 г.

Связаться с нами

Если у вас есть какие-либо вопросы или предложения по поводу настоящей Политики конфиденциальности, не стесняйтесь обращаться к Разработчику по адресу alphaomega11111111@gmail.com.

Політика конфіденційності для iOS-гри “- Ханойська вежа -“

Гра для iOS «- Ханойська вежа» (Гра) розроблена для кінцевого користувача (Користувач) Дмитром Сєдухіним (Розробник). Окрім інформації, яку Apple Inc. надає Розробнику, яку Користувач може вирішити надати, Гра не реєструє жодної інформації про Користувача. Гра також не використовує сторонні аналітичні чи рекламні фреймворки. Додаток не збирає, не передає, не поширює та не продає дані Користувача.

Зміни цієї Політики конфіденційності

Розробник може час від часу оновлювати цю Політику конфіденційності. Тому Користувачеві рекомендується періодично переглядати цю сторінку на предмет будь-яких змін. Розробник повідомить Користувача про будь-які зміни, опублікувавши нову Політику конфіденційності в цьому блозі.

Ця політика діє з 22 січня 2024 року

Зв’яжіться з нами

Якщо у вас є запитання чи пропозиції щодо цієї Політики конфіденційності, не соромтеся зв’язатися з Розробником за адресою alphaomega11111111@gmail.com.

Privacy Policy For “AppFinder” Android Application

Dmytro Siedukhin (Developer) built the “AppFinder” app (App) as an ad supported app. App is provided to App user (User) by Developer at no cost and is intended for use as is.

This post is used to inform readers regarding Developer’s policies with the collection, using, and disclosure of Personal Information if anyone decided to use App and become a User.

If User choose to use App, then he agree to the collection and using of information in relation to this policy. The Personal Information that Developer collect is used for providing and improving App. Developer will not use or share User’s information with anyone except as described in this Privacy Policy.

Information Collection And Use

For a better experience, while using App, Developer may require from User certain personally identifiable information. App also collects information about User’s device, such as list of applications that are installed on User’s device for providing App functionality (this list includes applications’ names, launcher icons and information that is needed for launching applications when and only when User clicks the application item in the list inside App). The information that Developer requests in App will be retained on User’s device and is not collected by Developer in any way.

App does use third-party services that may collect information used to identify User.

Links to the privacy policy of third-party service providers used by App

• Google Play Services
• AdMob

Log Data

In a case of an error in App Developer collects data and information (through third-party products) on User’s device called Log Data. This Log Data may include information such as User’s device Internet Protocol (“IP”) address, device name, operating system version, the configuration of App when utilizing it, the time and date of using App by User, and other statistics.

Cookies

Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. They are sent to user’s browser from the websites that user visit and are stored on user device’s internal memory.

App does not use these “cookies” explicitly. However, App may use third-party code and libraries that use “cookies” to collect information and improve their services.

Service Providers

Developer may employ third-party companies and individuals due to the following reasons:

• To facilitate App;
• To provide App on Developer’s behalf;
• To perform App-related services; or
• To assist Developer in analyzing how App is used.

Developer informs User that these third parties have access to their Personal Information. The reason is to perform the tasks assigned to them on Developer’s behalf. However, they are obligated not to disclose or use the information for any other purpose.

Security

Developer value User’s trust in providing User’s Personal Information, thus Developer is striving to use commercially acceptable means of protecting it. But no method of transmission over the Internet, or method of electronic storage is 100% secure and reliable, and Developer cannot guarantee its absolute security.

Links to Other Sites

App may contain links to other sites. If User clicks on a third-party link, he will be directed to that site. These external sites are not operated by Developer. Therefore, Developer strongly advises User to review the Privacy Policy of these websites. Developer has no control over and assumes no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children’s Privacy

App do not address anyone under the age of 13. Developer do not knowingly collect personally identifiable information from children under 13 years of age. In the case Developer discovers that a child under 13 has provided Developer with personal information, Developer immediately deletes this information from Developer’s servers. If you are a parent or guardian and you are aware that your child has provided Developer with personal information, please contact Developer so that he will be able to do the necessary actions.

Changes To This Privacy Policy

Developer may update this Privacy Policy from time to time. Thus, User is advised to review this page periodically for any changes. Developer will notify User of any changes by posting the new Privacy Policy in this blog.

This policy is effective as of 2024-01-17

Contact Us

If you have any questions or suggestions about this Privacy Policy, do not hesitate to contact Developer at alphaomega11111111@gmail.com.

Privacy Policy For “Hanoi Towers” Android Game

Privacy Policy

Dmytro Siedukhin (Developer) built the “Hanoi Towers” game (App) as an ad supported app. App is provided to App user (User) by Developer at no cost and is intended for use as is.

This post is used to inform readers regarding Developer’s policies with the collection, using, and disclosure of Personal Information if anyone decided to use App and become a User.

If User choose to use App, then he agree to the collection and using of information in relation to this policy. The Personal Information that Developer collect is used for providing and improving App. Developer will not use or share User’s information with anyone except as described in this Privacy Policy.

Information Collection And Use

For a better experience, while using App, Developer may require from User certain personally identifiable information. The information that Developer requests will be retained on User’s device and is not collected by Developer in any way.

App does use third-party services that may collect information used to identify User.

Links to the privacy policy of third-party service providers used by App

• Google Play Services
• AdMob

Log Data

In a case of an error in App Developer collects data and information (through third-party products) on User’s device called Log Data. This Log Data may include information such as User’s device Internet Protocol (“IP”) address, device name, operating system version, the configuration of App when utilizing it, the time and date of using App by User, and other statistics.

Cookies

Cookies are files with a small amount of data that are commonly used as anonymous unique identifiers. They are sent to user’s browser from the websites that user visit and are stored on user device’s internal memory.

App does not use these “cookies” explicitly. However, App may use third-party code and libraries that use “cookies” to collect information and improve their services.

Service Providers

Developer may employ third-party companies and individuals due to the following reasons:

• To facilitate App;
• To provide App on Developer’s behalf;
• To perform App-related services; or
• To assist Developer in analyzing how App is used.

Developer informs User that these third parties have access to their Personal Information. The reason is to perform the tasks assigned to them on Developer’s behalf. However, they are obligated not to disclose or use the information for any other purpose.

Security

Developer value User’s trust in providing User’s Personal Information, thus Developer is striving to use commercially acceptable means of protecting it. But no method of transmission over the Internet, or method of electronic storage is 100% secure and reliable, and Developer cannot guarantee its absolute security.

Links to Other Sites

App may contain links to other sites. If User clicks on a third-party link, he will be directed to that site. These external sites are not operated by Developer. Therefore, Developer strongly advises User to review the Privacy Policy of these websites. Developer has no control over and assumes no responsibility for the content, privacy policies, or practices of any third-party sites or services.

Children’s Privacy

App do not address anyone under the age of 13. Developer do not knowingly collect personally identifiable information from children under 13 years of age. In the case Developer discovers that a child under 13 has provided Developer with personal information, Developer immediately deletes this information from Developer’s servers. If you are a parent or guardian and you are aware that your child has provided Developer with personal information, please contact Developer so that he will be able to do the necessary actions.

Changes To This Privacy Policy

Developer may update this Privacy Policy from time to time. Thus, User is advised to review this page periodically for any changes. Developer will notify User of any changes by posting the new Privacy Policy in this blog.

This policy is effective as of 2024-01-17

Contact Us

If you have any questions or suggestions about this Privacy Policy, do not hesitate to contact Developer at alphaomega11111111@gmail.com.

New Programming Language

Show me the developer who never dreams about creation of his own operating system or at least programming language.  Well, if you found him, you can sow this idea in his mind. It’s so beautiful to step into world of low level abstractions. Let’s do this!

Git. Detached HEAD In Submodule

Every time you work with big project has submodules you meet the problem of detached HEAD. After git submodule update command if you type git status in any submodule you’ll get something like this:

$ git status
Not currently on any branch
# nothing to commit (working directory clean)

Certainly, you want to go back to your branch like git checkout master to continue your work. In case of forgetting this you may have fun attaching your next “lost” commits to the normal developing branch (You did it still, didn’t you? Here is the solution). But how to turn back the commits got after updating submodules and lost after master branch checkout? Great book about Git is keeping silence, but in my case the following helps:

git merge origin/master

Or you can use

git rebase origin/master

if usually use git pull --rebase instead of git pull to keep your tree fine and beauty.

If you’ve some notes about it or know some other way to do it, please, leave a comment.

Adapting the configuration for Equalizer parallel 3D rendering

Recently I’ve met such interesting thing as a framework for distributed and parallel rendering of 3D models. It’s an open-source one called Equalizer, which is designed by Stefan Eilemann, Maxim Makhinya and others (you can find all names on their site and download the engine with installation instructions as well). The good feature of the source code pack is that it has couple of examples of Equalizer usage. The eqPly one is the tool of parallel and distributed visualizing of 3D PLY-models. But in my case it has one lack: it’s impossible to set the configuration file name in the command prompt. So if you want to use eqPly and have the same problem, let’s do it.

First, we find that default configuration file name was set in your_equalizer_dir/libs/client/global.cpp file. So you can change the std::string Global::_configFile variable as you want. Next. we need to open the file your_equalizer_dir/examples/eqPly/localInitData.cpp and insert in LocalInitData::parseArguments routine something like this:

TCLAP::ValueArg<std::string> configArg( "d", "config","rendering configuration file name", false, eq::Global::getConfigFile(), "string", command );

You can find the proper place to insert this code by watching the similar parsing items in the function. Then by the same way insert the following code in this function:

if(configArg.isSet( ))
{
    eq::Global::setConfigFile(static_cast<std::string>(configArg.getValue()));
}

Now rebuild the engine and have fun with –config command prompt option.

But do you see that entering the –config and –model options all the time you need to call the eqPly is boring? So let’s write shell script something like this (of course, if you have *nix OS):

#!/bin/sh
EQ_SRC="/your_equalizer_dir/examples/"
MODEL="./screwdriver.ply"
if [ $# -gt 0 ]; then
    CONFIG=$1
else
    CONFIG="${EQ_SRC}configs/4-window.all.eqc"
fi
COMMAND="./eqPly --config $CONFIG --glsl --noOverlay"
if [ $# -gt 1 ]; then
    MODEL=$2
fi
COMMAND="${COMMAND} --model $MODEL"
$COMMAND

So you can set the configuration file name by the first and the model file name by the second argument. Don’t forget to change acces mode of the script:

chmod +x ./render.sh

Where render.sh is your script name.

Now it works, for example, like this:

render.sh 2-window.2D.eqc

The result video is below

Insufficient storage problem

Every Android developer meets the insufficient storage problem earlier or later. There could be varied reasons for this trouble, but the result is still not good: you can’t install apps on your phone. If freeing memory on SD card and uninstalling some apps help –  you are lucky. But usually the trouble appears again after that in some time. The more effective way is to use Android Debug Bridge(adb) shell. In this case you need to type in your operating system command prompt something like this:

$ adb shell

Of course, if you haven’t the path to adb in you system PATH variable, you need to use the appropriate absolute or relative path to it. Then run such commands:

$ cd /data/local/tmp

$ rm * -rf

The most likely you’ll see this message:

rm failed for -rf, No such file or directory

Don’t pay attention for it! It’s a joke from Android). Then type

$ exit

to leave the adb shell. Now the folder where  installed apps are uploaded in USB debugging mode is clear. Try to install your application again.

In my case it helped, if not in yours – congratulations! You have a chance to find the solution by yourself). This was tested on such devices: Samsung Galaxy S I, S II, Nexus S and Samsung Galaxy Tab. Probably, it works on other Android devices.