The Free Site   |  vBuddy - social networking for webmasters   |  Cheap Web Hosting - starting at $5
Skip to main content.

This page’s menu:

How to create a useful stalker list?

Sometimes the organized stalking activities TIs experience are compared with Stasi tactics. I am wondering that if anyone wants to share one's o/s offender information with others. For the Stasi victims, they have stasi offender list and it is available for downloading.

Since our governments are not willing to admit the existence of "organized stalking," I think we better create the list of stalkers for our case. From my experience, it seems the same perps participate in stalking in the same area, and sometimes travel to few cities. In my case, the perps I met in Aarau were able to come to Lenzburg and Zofingen for their activity. So, if we can find a way to create a list and if other TIs notice the same people stalking in nearby area where the stalkers are listed, we might be able to prove the connection of the stalkers on the list with the organized stalking just like Stasi informants did. For example, if a TI moved to another city and saw a suspicious car (say, this car follow TI's car every day the TI leaves home) parked outside of his home, the TI might find the number on the license plate matched with the number on another TI's offender list. This makes much better proof for bringing the case to the local police. As an example, you can check out stasi offender list publicly shared on the Internet. ma_stasi.zip (about 1.5MB)

Here is the advantages/disadvantages of creating the o/s offender list.

Advantages:
Disadvantages:
Things important for creating o/s offender lists.
  1. Standardization of incidents/clues behind the data collection. (crucial evidences related with the person to be listed in, or heavily sensitized TIs just add people walking around him.)
  2. Standardization of data collection (how to separate people names, stores/restaurants/organizations/companies, license plate numbers)
  3. Standardization of data format. (file format & the way organize data)
  4. File distribution (security)

1-1. Standardization of incidents/clues wold make easy to read others' list. For example, a TI wants to record a man wearing a T-shirt with a specific US city name for NLP anchoring, the TI might want to write down “Detroit” as the incident information. For other TIs, they might not understand what means by “Detroit.” Others might wonder if the man is from Detroit or Detroit was used in the conversation. To avoid confusion, it is better to keep simple but helpful information on the list. To record the incident like the example, “Logo-anchoring, clothes (T-shirt), 'Detroit'” would be useful clue. The first part identifies the type of sensitization technique, then the material used (in the example, it was clothes, and put () for the category, then the actual information. “Hinting, cellphone, 'I am visiting hospital'” would explain the incident a TI met someone on the cell phone and talking 'I am visiting hospital' for hinting. Not all the incidents would be easy to be written down in this way, but if I think using the same style will make the list easy to read.

1-2. Using the same style would be hard for the TIs with severe sensitization problem. In such case, they should record “what” and “how” in the information. “when” “who” “where” will be on other column, so the information should cover “what” and “how” the incidents taken place. TIs can rewrite this part to make it easier to read later if they kept enough information when record it.

2-1. To keep the list useful for searching, I think offenders, organizations, and vehicles should be collected in different lists.

3-1. Not all TIs have access to the same software like MS Access or Oracle database. The professional database software should be an excellent tool for storing the people list, but the specific file format will make others who do not own the software not view the list. For that reason, I think CSV format will solve the problem. CSV format is widely used among spreadsheet software like Excel and readable for database software. To create CSV file, people can use text editors to spreadsheets like Excel. If you do not have one, you can download free office suites (OpenOffice, NeoOffice) from their official websites. For more information about CSV list, please check out this page.

3-2. File format should be in the same style. If the list is formed in the same way, people can easily understand how to read the data. For example, if a TI collects a data and put the offenders' names on the first column and put the incident information at the bottom, he might get confused to see a list comes with the offenders' names on the last column. This format issue might be debatable for improvement in future. I will explain the mondately fields necessary for creating a list here. The first column is to show who collected the data. I created the list based on location and perp recognizing. It is hard to know the perp's name as they are usually strangers in the area. But people could easily recognized stranger's sex, ethnicity, and age. Such information can help TIs living in the close location to exchange information about them. Organizations and vehicles information will be stored in different list.

CSV format:

O/S List: TI's name, location of sighting, date of sighting(from when to when), sex, ethnicity, body type, facial structure, age, sensitization info (NLP Anchoring with rosary and coke bottle,etc) last name, first name, affiance (religious organization, etc), address, phone number.

Store/Restaurant/Organization List: TI's name, location, organization name, sensitization information (e.g. beggers appeared and asked money or use the form discussed in 1-1), address, (optional: relation with the people in O/S list)

O/S vehicle list: TI's name, license number, location of sighting, date of sighting, (*optional: relation with the people in O/S list)

4-1. Security issue might be a type of concern. Some TIs might be falsely accused of distributing files of stranger list. I think we might need to use password for the distribution if we want to post it on a public domain. Say, using “fedame” (derived from fedame.org) or something we share common as the password. That way, people knowing the password can open the file. When you share your file with someone else, you might want to write an agreement for downloading/opening file. Such as “I put this file in the purpose to exchange the organized stalkers information in the area of XXXXX. If you are not a TI or against anti-organized stalking/Gegen Stasi 2.0 movement, please do not take the file.” If someone download it and claimed you about the contents, then the person might broke the agreement of the usage of the file, you see? Also, sharing information in public is healthy as we, TIs, are not collecting information for secret agenda or anything. It is better to keep the file on the Internet rather than someone try to destroy the information in the hard drive. We really do not have much privacy these days, we can exercise this lack of privacy for the public safety sake. We keep the sensitive file as open source comes with certain copyrights. It is not TIs but the offenders who will get problem if we act openly.

*TI's name can be used as the ID key. That way, each person on the list will have a unique ID to be addressed from another lists. For instance, if I decide to use my real name for TI name, then it would be “MiyokoGoto” on the first column. Then I decides to add “P” for “People” list, and “O” for organization list, and “V” for vehicle list, each data on the three lists have unique IDs. “MiyokoGotoP000001” would be used for the first person on my o/s offender list. Just like that, “MiyokoGotoO000003” shows the third listing on my organization list, and “MiyokoGotoV000004” is for the forth listing on my vehicle list. This is easy to figure out any mistake on the list if a duplication is available. And what if someone found the same car license number on another TI's list? And how can these TIs call the perp on the o/s offender lists? If a TI list the driver as “TIAP000032” on his list, and the car is listed as “TIAV000008,” there is a way to explain who the driver is. Otherwise, the TI might have hard time to make a notice of the driver each time explain about him. For the ID part, I think we do not have to use real name if it is uncomfortable for you. Instead, using the nickname like what we use for login here could be enough for identification. To avoid confusion, use of only one's first name should be avoided. There are many people with the same first name around the world. 6 to 10 letter for identification should be enough to say unique, I guess. And I thought 6 digit would be enough for listing. If someone can collect that much information, I think that would list almost entire people living in the area. It's just a common sense, you know.

updated 01/01/09