If you have any questions, inquries, remarks, or complaints concerning this website or the Ayeri language in general, feel free to send a message to: infosee detailed contact information.@ ayeri. de, or
Copyrights and Such
Benung. The Ayeri Language Resource (https://ayeri.de) is owned and edited by Carsten Becker (in the following referred to as “this website” and “I”, respectively). Hosting is obtained from NFSN, Inc. Unless noted otherwise, all materials presented on this website are copyright © by Carsten Becker, all rights reserved.
If you’re sharing my stuff on the internet, that’s awesome, but please be so kind to give credit, for example, by putting a link back to my site so other people may know where to find out more. If you have questions about using materials from this site in what goes way beyond personal use (say, you want to use an image from “Examples” in a book you intend to sell), please contact me first. If you feel that your rights are violated by any content on this website, please write a notice to the above e-mail address before taking legal action.
This website is built with WordPress (GPLv2). Web fonts (Open Sans Condensed by Steve Matteson, Lobster by Pablo Impallari) tied in with Google Fonts. Some icons used are from the elementary Icons icon set by Daniel Foré (GPL). Avatar images shown next to comments are provided by Gravatar and are thus in the responsibility of every individual commenter, and shown here in good faith, as WordPress fetches these images from a commenter’s Gravatar account automatically, if available.
Ayeri is a fictional language spoken by fictional people in a fictional setting, and as such is not related to any naturally existing languages. It is thus not to be confused with Azeri, a Turkic language spoken in Azerbaijan and its surrounding countries. Ayeri’s vocabulary is entirely a priori, this means, no real-world languages have been used specifically as sources of vocabulary. Due to the language’s sound and spelling aesthetic being inspired by Austronesian languages, it is not surprising if overlaps with existing words in those languages happen accidentally.
Privacy and Commenting policy
Logging, Tracking, etc.
This website logs traffic in order to recognize attacks against it and to be able to react to attacks so as to prevent them in the future. The data saved by a visitor’s access includes their IP address, files accessed on this website, referring link, time of access, and the visitor’s browser/operating system. The logs are kept in a directory which is not publicly accessible and purged weekly. Retention of information about a visit is thus limited to a maximum of 7 days. Logged information is not used to generate user profiles. Periodical anonymization of IP addresses in the log file ensures that only the first 24 bits (out of 32) of an IPv4 or the first 48 bits (out of 128) of an IPv6 are kept. This allows to trace back a website access to an IP network, but not to an individual visitor. Statistics are provided by Statify, which only counts page views but does not record any other data.
Moreover, as a way to basically crowdsource finding gaps in the dictionary and thus to get inspiration on what to make up words for next, dictionary queries which fail to return any results are logged seperately from the server’s access log. A visitor’s IP is not logged in the dictionary error log, only the failed query itself.
Additionally, as a means to prevent spam, every visitor’s IP address is screened for recent cases of malevolent behavior by Cleantalk. Cleantalk may block comment fields or site access altogether for IP addresses recently associated with notorious comment spammers and those which have engaged in denial of service attacks. Cleantalk makes information on blocked access attempts available to a website owner for a period of 8 days, including the full IP address of a blocked visit.
By commenting on an article, a visitor’s e-mail address is automatically saved by the WordPress installation this website runs on, and their IP is anonymized to 127.0.0.1 for permanent keeping. However, this contact information is equally regarded as confidential. Any factual private information visitors choose to include in the publicly readable part of comments – that is, “Name”, “Website”, “Comment” – they publish at their own risk. I, as the website owner, reserve the right for myself to moderate or delete comments if I notice them to be abusive, for instance, if they contain harassment or spam. Also see NFSN.net’s hosting policies. Please contact me if you want your comment removed after posting it at the address provided above.
|ct_checkjs||temporary||browser session||Cookie set by Cleantalk spam protection service|
|ct_cookies_test||temporary||browser session||Cookie set by Cleantalk spam protection service|
|ct_sfw_pass_key||temporary||browser session||Cookie set by Cleantalk spam protection service|
|ct_timestamp||temporary||1 day||Cookie set by Cleantalk spam protection service|
|PHP Session ID||temporary||browser session||A PHP session ID cookie stores values passed from page to page within the website; it is canceled when you close your browser window.|
|viewed_cookie_policy||persistent||1 year||The plugin 'Cookie Law Info' saves whether you clicked to agree that you're aware of this website possibly setting cookies in your browser.|
- 2014-02-11: Added link to NFSN.net’s hosting policies
- 2014-03-11: The WP SlimStat traffic analysis plugin has been removed completely and all its accumulated data has been deleted in accordance with German jurisdiction. A passage about which data is gathered in server logs and by Bad Behavior has been added for clarification.
- 2014-03-24: Currently trying out AVH First Defense Against Spam as a replacement for Bad Behavior. Text changed accordingly.
- 2014-03-31: AVH FDAS queries the ZEN list of Spamhaus, not just SBL/XBL. Text changed accordingly.
- 2014-06-05: AVH FDAS removed, back to Bad Behavior. Text changed accordingly.
- 2014-12-04: Server log retention shortened to 1 week. Comments save IPs generally as 127.0.0.1.
- 2015-04-05: Additional information on cookies. Youtube and Twitter embeds set third-party cookies on this website.
- 2015-04-17: Bad Behavior makes it basically impossible to use caching plugins, so going back to AVH FDAS.
- 2015-05-08: Caching creates more problems than it solves for now; AVH FDAS in addition proved rather toothless in keeping bad bots out, so yet again back to Bad Behavior. Improved wording in places.
- 2015-12-06: Removed third-party cookies from cookie list and replaced it with a general disclaimer that embedded content may set cookies in a user’s browser.
- 2016-01-31: Added statement on the dictionary logging queries with zero results.
- 2016-03-09: Added warning about embedded content from third-party websites potentially gathering user data.
- 2017-03-02: Exchanged Project Honeypot DNSBL for cloud-based solution from Cleantalk.
- 2017-11-09: No Bad Behavior plugin anymore because it put users’ IPs in pages which were then cached, so others could see those IPs. Also, the server logs can’t be fitted to German privacy requirements, which means no logging.
- 2018-01-08: Logging reactivated (with anonymization routine in place) due to bad bots. Updated Logging and Cookies sections.