Abstract: Systems and methods are provided for filtering atmospheric conditions from LiDAR point clouds. The method includes generating, using a LiDAR system, at least one point cloud, wherein the LiDAR system includes a processor. The method further includes, using the processor, identifying and isolating one or more ground points within a point cloud of the at least one point cloud, wherein the one or more ground points indicate a ground portion within an environment of the point cloud, filtering out the ground portion from the point cloud, generating an initial processed point cloud, identifying and isolating one or more atmospheric condition points within the initial processed point cloud, wherein the one or more atmospheric condition points indicate one or more atmospheric conditions within an environment of the processed point cloud, and filtering out the atmospheric condition points from the initial processed point cloud, generating a final processed point cloud.

Abstract: Methods, systems, and apparatus, including computer programs encoded on a computer storage medium, for presenting non-suggested content items to a user of a social network account are described. In one aspect, a method includes storing social network account data indicating preferred categories of content and non-preferred categories of content associated with a particular social network account. Suggested content items corresponding to the preferred categories of content are identified, and non-suggested content items corresponding to the non-preferred categories of content are identified. A graphical user interface is provided for presentation to a user of the particular social network account. The graphical user interface presents information about the suggested content items and information about the non-suggested content items. Feedback data is received based on a user interaction in response to presentation of the information about the non-suggested content items.

Abstract: In general, the subject matter described in this specification can be embodied in methods, systems, and program products for determining if a web application is cached. A source web application that is executed by a web browser that is installed on a computing device determines that the web browser is to navigate to a target web application. The source web application determines whether resources for the target web application are cached at the computing device. The source web application performs actions to request resources for the target web application based on the determination whether resources for the target web application are cached, wherein the actions comprise requesting resources for the target web application using a first address if the target web application is determined to be cached and using a second address if the target web application is determined to not be cached.

Abstract: A system and a computer-implemented methods for email management are disclosed. The method includes storing messages for electronic mail accounts provided by remote electronic mail server systems. The method further includes determining that the remote electronic mail server systems each have a different hostname than the others of the remote electronic mail server systems. The method further includes displaying messages from a first one of the electronic mail accounts and displaying a hostname of a first remote electronic mail server system providing the first one of the electronic mail accounts. The method further includes receiving a request to view messages from a second one of the electronic mail accounts. The method further includes displaying messages from the second one of the electronic mail accounts and displaying a hostname of a second remote electronic mail server system providing the second one of the electronic mail accounts.

Abstract: The methods track abnormal events on mobile client devices, such as web application crashes, and use that information to associate the abnormal events with device characteristics. A first method executes on mobile client devices. When a web application starts, the method looks for a crash indicator cookie in persistent memory. If the cookie does not exist, the method creates and stores it. If the cookie already exists, the method collects information about the client device, such as device type, browser type, and operating system, and sends the information to a web server. The web application deletes the cookie when the application terminates normally. A second method executes on a web server. This method receives information from client devices relating to abnormal events for web applications. The information includes device characteristics of each client device. This method stores the information and associates a pattern of abnormal events with device characteristics.

Abstract: A server system receives a first request for a data item from a web application on a client device, wherein the first request includes an identifier of the data item. In response to the first request, the server system calculates a first checksum of the data item and sends the data item and the first checksum to the web application, for storage in the local database. The server system receives a second request for the data item from the web application, calculates a second checksum of the data item and compares the first and second checksums. The server system, determines that the data item has been updated by comparing the first checksum to the second checksum; and in response to determining that the data item has been updated, the server system a reply to the web application a indicating that the data item has been updated.

Abstract: In general, the subject matter described in this specification can be embodied in methods, systems, and program products for determining if a web application is cached. A source web application that is executed by a web browser that is installed on a computing device determines that the web browser is to navigate to a target web application. The source web application determines whether resources for the target web application are cached at the computing device. The source web application performs actions to request resources for the target web application based on the determination whether resources for the target web application are cached, wherein the actions comprise requesting resources for the target web application using a first address if the target web application is determined to be cached and using a second address if the target web application is determined to not be cached.

Abstract: A server system receives a first request for a data item from a web application on a client device, wherein the first request includes an identifier of the data item. In response to the first request, the server system calculates a first checksum of the data item and sends the data item and the first checksum to the web application, for storage in the local database. The server system receives a second request for the data item from the web application, calculates a second checksum of the data item and compares the first and second checksums. The server system, determines that the data item has been updated by comparing the first checksum to the second checksum; and in response to determining that the data item has been updated, the server system a reply to the web application a indicating that the data item has been updated.

Abstract: The methods track abnormal events on mobile client devices, such as web application crashes, and use that information to associate the abnormal events with device characteristics. A first method executes on mobile client devices. When a web application starts, the method looks for a crash indicator cookie in persistent memory. If the cookie does not exist, the method creates and stores it. If the cookie already exists, the method collects information about the client device, such as device type, browser type, and operating system, and sends the information to a web server. The web application deletes the cookie when the application terminates normally. A second method executes on a web server. This method receives information from client devices relating to abnormal events for web applications. The information includes device characteristics of each client device. This method stores the information and associates a pattern of abnormal events with device characteristics.