Sponsored Content
Top Forums Web Development Discrepancies Between Our Mobile Detection Code and Google Analytics Regarding Chinese User Agents Post 303040163 by Neo on Thursday 24th of October 2019 10:31:08 AM
Old 10-24-2019
... and most of the new traffic seems to be coming from mobile.

Before stats showed about 7 to 9 percent of the site's traffic was from mobile; but today at around 9AM Eastern US, 67% of the traffic was mobile:

Image

This is a huge change in Google search referrals and site traffic patterns.

Need to do some analysis and see what is going on, seems too "strange" to have such a dramatic change / shift.

My first indications are we are seeing an increased amount of mobile activity from China, which I suspect might be bots indexing site content using a mobile user agent, unfortunately.
 

5 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

SED Search and Replace Question for Google Analytics

Well, I'm losing my regex ability in sed! Please help. I need to search for this text in multiple html files in a directory: </body> and add the following lines in front of the text above: <script src="http://www.google-analytics.com/urchin.js" type="text/javascript"> </script> ... (11 Replies)
Discussion started by: Neo
11 Replies

2. Google Chrome OS

Google Chrome Mobile?

I know that Google Chrome came out with the Android under a Unix based system, but did it come out yet for Windows Mobile? I have Windows Mobile 6 on my device. (0 Replies)
Discussion started by: Anna Hussie
0 Replies

3. Shell Programming and Scripting

User Agents Identifier

Hi, Can anyone help me write a script tp determine the web browser from a user agent. A user agent is stored in a file and consists of hundreds of lines e.g. 37050 Mozilla/5.0 (Windows NT 6.1; WOW64; Trident/7.0; rv:11.0) like Gecko 29404 Mozilla/5.0 (Windows NT 6.3; WOW64)... (4 Replies)
Discussion started by: cyberfrog
4 Replies

4. Web Development

Quick Fix for Google Search Console "Page is not mobile friendly"

Over the past 10 plus years, we have countless posts where the user did not use CODE tags or they used ICODE tags incorrectly. This has has the results of this site penalized by Google for having pages which are "not mobile friendly". So, working quietly in the background, in the thankless... (0 Replies)
Discussion started by: Neo
0 Replies

5. What is on Your Mind?

Google Search Console - Mobile Usability - No Errors or Issues - New Milestone

For the first time in the history of the site Google Search Console (GSC) has unix.com showing "no mobile viewability errors". This is no small achievement considering the hundreds of thousand of lines of legacy code we run at a site which has been around much longer than Facebook or LinkedIn: ... (0 Replies)
Discussion started by: Neo
0 Replies
GSMPB(8)						      System Manager's Manual							  GSMPB(8)

NAME
gsmpb - GSM mobile phone phonebook manipulation program SYNOPSIS
gsmpb [ -b baudrate ] [ --baudrate baudrate ] [ -c ] [ --copy ] [ -d destination device or file ] [ --destination destination device or file ] [ -h ] [ --help ] [ -i ] [ --index ] [ -I init string ] [ --init init string ] [ -p phonebook name ] [ --phonebook phonebook name ] [ -s source device or file ] [ --source source device or file ] [ -t character set ] [ --charset character set ] [ -v ] [ --version ] [ -V ] [ --verbose ] [ -X ] [ --xonxoff ] [ -y ] [ --synchronize ] DESCRIPTION
gsmpb can store or retrieve phonebook entries residing in a GSM mobile phone's phonebook to or from a file. A synchronization mode is also available. gsmpb reads entries from the source which can be a mobile phone (if a serial device file is given) or a file (if a file name is given). The source is never modified. gsmpb writes phonebook entries to a destination file or device. Depending on the mode the source is copied to the destination file, thus overwriting the destination, or the destination is synchronized with regard to the source which is the default (details see below). If "-" is given as the parameter for the --source or --destination options, the phonebook is read from standard input and/or written to standard output, respectively. Phonebook entries names are encoded using the GSM default alphabet in the mobile phone, whereas they are stored using the Latin-1 encoding in phonebook files. When reading phonebook entries from a mobile phone entry names are converted from the GSM default to Latin-1. Charac- ters that can not be converted to Latin-1 are encoded as character code 172 (Latin-1 boolean "not"). When writing file-based phonebook entries to a mobile phone a conversion to the GSM default alphabet takes place. Characters that can not be converted are encoded as GSM delta (code 16). If the default character set has been changed using the --charset option no conversion takes place. Error messages are printed to the standard error output. If the program terminates on error the error code 1 is returned. OPTIONS
-b baudrate, --baudrate baudrate The baud rate to use. The default baudrate is 38400. -c, --copy This causes the contents of the source to be copied to the destination. After this operation the destination has exactly the same contents as the source. -d destination, --destination destination The destination device or file. -h, --help Prints an option summary. -I init string, --init init string Initialization string to send to the TA (default: "E0"). Note that the sequence "ATZ" is sent first. -i, --index If the index position is given, gsmpb preserves the assignment of entries to memory slots in the mobile phone's phonebook. This can be used to backup phonebook entries with their position into a phonebook file or to change the position of entries by editing a phonebook file and writing them back to the mobile phone. If this option is given the phonebook file used as the source must con- tain indices for every entry. Additionally, these indices must be unique, ie. it is not allowed to assign one entry twice to a spe- cific position in the mobile phone's phonebook. -p phonebook, --phonebook phonebook The name of the phonebook to read from or write to. This is only used for device sources and destinations. Commonly available phone- books are: FD SIM fixdialling-phonebook LD SIM last-dialling-phonebook ME ME phonebook MT combined ME and SIM phonebook SM SIM phonebook TA TA phonebook -s source, --source source The source device or file. -t character set, --charset character set Set the character set to use for phonebook operations (default is the GSM default alphabet). -v, --version Prints the program version. -V, --verbose Prints out a detailed progress report. -X, --xonxoff Uses software handshaking (XON/XOFF) for accessing the device. -y, --synchronize This causes the contents of the source to be synchronized with the destination (default). Synchronization in this con- text means: - If the source contains an entry with a name that does not exist in the destination this entry is added to the desti- nation. - If the source contains an entry with a name that can also be found in the destination, the entry in the destination is overwritten (ie. the telephone number is updated). Exception: More then one entry with the name exists in the destination. In this case the new entry ist just added. - Entries in the destination that do not exist in the source are deleted. Note that synchronization has the following properties that differ from copying: This algorithm does not change the location of unchanged entries in the destination phonebook. The synchronization function is not case-sensitive when comparing names. PHONEBOOK FILE FORMAT
Phonebook entries are stored in phonebook files that are meant to be human-readable and -editable. There is one phonebook entry per line, and each line has the format: index|text|phone number The fields have the following meanings: index The index of the entry which must be a positive number. The index may also be empty. Indices can be used in conjunction with the --index option to store the entry into a specific position in the mobile phone. text Descriptive text for the entry. The text may con- tain the special characters '', '|', carriage return (ASCII code 13), or line feed (ASCII code 10). These must be written "\", "|", " ", " ", respectively. The text should only contain charac- ters that can be encoded using the GSM default alphabet (see comments above). phone number Phone numbers can only contains the digits 0-9 and the '+' sign. A '+' sign denotes an international number. EXAMPLES
The following invocation of gsmpb synchronizes the mobile phone's SIM phonebook with the file $HOME/.phonebook: gsmpb --synchronize -b 19200 -d /dev/mobilephone -s $HOME/.phonebook -p "SM" AUTHOR
Peter Hofmann <software@pxh.de> BUGS
Report bugs to software@pxh.de. Include a complete, self- contained example that will allow the bug to be repro- duced, and say which version of gsmpb you are using. COPYRIGHT
Copyright (C) 1999 Peter Hofmann gsmpb is free software; you can redistribute it and/or modify it under the terms of the GNU Library General Pub- lic License as published by the Free Software Foundation; either version 2, or (at your option) any later version. gsmpb is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied war- ranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PUR- POSE. See the GNU Library General Public License for more details. You should have received a copy of the GNU Library General Public License along with gsmpb; see the file COPYING. If not, write to the Free Software Foundation, 675 Mass Ave, Cambridge, MA 02139, USA. SEE ALSO
gsminfo(7), gsmctl(1), gsmsendsms(1), gsmsmsd(8), gsmsms- store(1). gsmpb v1.10 Sat Jun 16 22:10:00 UTC 2012 GSMPB(8)
All times are GMT -4. The time now is 05:55 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy