Optimize tpc.googlesyndication.com/icore_images [Google PageSpeed Suggestion]

PageSpeed Insights is a google powered tool located at https://developers.google.com/speed/pagespeed/insights/ . It gives suggestions on how to speed up your site.

If you’re an adwords user, you may encounter the suggestion to compress images located at https://tpc.googlesyndication.com/icore_images/  Unfortunately, you will not be able to compress these images, as they are located on google’s servers as part of their ad infrastructure.

I’ve submitted a bug report to google via their complaint form requesting they optimize their ad infrastructure images. I encourage anyone coming to this page to submit a complaint at https://support.google.com/adwords/contact/aw_complaint.

PLEASE SUBMIT A COMPLAINT TOO!!

NetGear R6300v2

Receiving “Firmware is Invalid” message for the auto-upgrade.

Firmware Upgrade Assistant

 

A new version has been found. Do You want to upgrade to the new version now?

Current Firmware Version

1.0.1.72

New Firmware Version

1.0.4.8_10.0.77

Release Notes

 1.   [New feature & Enhancement] Added No-IP DDNS support.

 2.   [New feature & Enhancement] Added CE DFS channel support.

 3.   [New feature & Enhancement] Improved 2.4G and 5G WiFi stability.

 4.   [New feature & Enhancement] Improved USB performance.

 5.   [Bug Fix] Fixed BitComet throughput drop issue.

 6.   [Bug Fix] Fixed UPnP IGRS issue.

 7.   [Bug Fix] Fixed UPnP Traffic Meter in AP mode.

 8.   [Bug Fix] Fixed FBwifi unstable issue.

 9.   [Other] Removed repeater function (WDS).

 10.   [Enhancement] New WiFi driver to comply with FCC 5G new rule.

East Forest – Choose Good [Individual Soul Album]

Human beings are crossing a midline and the average age of the soul is becoming mature and with recording, all humans are being enhanced with their introspection, and how they learn to go within and introspect. and it’s time for an intervention on earth, there’s a permutation going on

With recording, all humans are being enhanced with their introspection, and how they learn to go within and introspect. …and it’s time for an intervention on earth, there’s a permutation going on.

Lyrics from Choose Good from the album The Education of the Individual Soul by East Forest.

Thoughts on the meaning? Comment below!

Spotify desktop client communication failed. [Fixed]

After receiving the below error message, and being unable to fix the problem with the ‘advanced users’ suggestion, I found the solution to be to set your DNS to google’s DNS servers of 8.8.8.8 and 8.8.4.4
Spotify desktop client communication failed.

Having trouble logging in to Spotify?

  • You must have an existing Facebook-connected Spotify account to use the “Login with Facebook” button.
  • If you have a Facebook-connected Spotify account, you can also login using your Facebook email address and password as your Spotify username and password. (These won’t be stored.)
  • Internet Explorer 11 users: to use the “Login with Facebook” button, add https://login.spotify.com to the Trusted Sites security zone.
  • Advanced users: in order to use the “Login with Facebook” button, ensure that login.spotilocal.com resolves to 127.0.0.1. Network security protections might interfere with this.
  • Still need help? Visit Spotify Community for more information.

Flags / Options for pngcrush

Here’s the list of flags / options for pngcrush-1.8.11 – January 2017 Version.

A couple common flags are “-ow” to overwrite the original file with the crushed file and “-brute” to ‘brute-force’ all optimization methods (slowest, but most compression)

usage:
pngcrush [options except for -e -d] infile.png outfile.png
pngcrush -e ext [other options] file.png ...
pngcrush -d dir/ [other options] file.png ...
pngcrush -ow [other options] file.png [tempfile.png]
pngcrush -n -v file.png ...

options:

-bail (bail out of trial when size exceeds best size found)
-blacken (zero samples underlying fully-transparent pixels)
-brute (use brute-force: try 148 different methods)
-c color_type of output file [0, 2, 4, or 6]
-check (check CRC and ADLER32 checksums)
-d directory_name/ (where output files will go)
-e extension (used for creating output filename)
-f user_filter [0-5] for specified method
-fix (salvage PNG with otherwise fatal conditions)
-force (write output even if IDAT is larger)
-g gamma (float or fixed*100000, e.g., 0.45455 or 45455)
-huffman (use only zlib strategy 2, Huffman-only)
-iccp length "Profile Name" iccp_file
-itxt b[efore_IDAT]|a[fter_IDAT] "keyword"
-keep chunk_name
-l zlib_compression_level [0-9] for specified method
-loco ("loco crush" truecolor PNGs)
-m method [1 through 150]
-max maximum_IDAT_size [default 524288L]
-mng (write a new MNG, do not crush embedded PNGs)
-n (no save; doesn't do compression or write output PNG)
-new (Use new default settings (-reduce))
-newtimestamp (Reset file modification time [default])
-nobail (do not bail out early from trial -- see "-bail")
-nocheck (do not check CRC and ADLER32 checksums)
-nofilecheck (do not check for infile.png == outfile.png)
-noforce (default; do not write output when IDAT is larger)
-nolimits (turns off limits on width, height, cache, malloc)
-noreduce (turns off all "-reduce" operations)
-noreduce_palette (turns off "-reduce_palette" operation)
-old (Use old default settings (no -reduce))
-oldtimestamp (Do not reset file modification time)
-ow (Overwrite)
-q (quiet) suppresses console output except for warnings
-reduce (do lossless color-type or bit-depth reduction)
-rem chunkname (or "alla" or "allb")
-replace_gamma gamma (float or fixed*100000) even if it is present.
-res resolution in dpi
-rle (use only zlib strategy 3, RLE-only)
-s (silent) suppresses console output including warnings
-save (keep all copy-unsafe PNG chunks)
-speed Avoid the AVG and PAETH filters, for decoding speed
-srgb [0, 1, 2, or 3]
-ster [0 or 1]
-text b[efore_IDAT]|a[fter_IDAT] "keyword" "text"
-trns_array n trns[0] trns[1] .. trns[n-1]
-trns index red green blue gray
-v (display more detailed information)
-version (display the pngcrush version)
-warn (only show warnings)
-w compression_window_size [32, 16, 8, 4, 2, 1, 512]
-z zlib_strategy [0, 1, 2, or 3] for specified method
-zmem zlib_compression_mem_level [1-9, default 9]
-zitxt b|a "keyword" "lcode" "tkey" "text"
-ztxt b[efore_IDAT]|a[fter_IDAT] "keyword" "text"
-h (help and legal notices)
-p (pause)

These notes were also printed with the info statement on the program.

| Copyright (C) 1998-2002, 2006-2016 Glenn Randers-Pehrson
| Portions Copyright (C) 2005 Greg Roelofs
| This is a free, open-source program. Permission is irrevocably
| granted to everyone to use this version of pngcrush without
| payment of any fee.
| Executable name is pngcrush
| It was built with bundled libpng-1.6.28
| and is running with bundled libpng-1.6.28
| Copyright (C) 1998-2004, 2006-2016 Glenn Randers-Pehrson,
| Copyright (C) 1996, 1997 Andreas Dilger,
| Copyright (C) 1995, Guy Eric Schalnat, Group 42 Inc.,
| and bundled zlib-1.2.11, Copyright (C) 1995-2017,
| Jean-loup Gailly and Mark Adler,
| and using “clock()”.
| It was compiled with gcc version 4.2.1 Compatible Apple LLVM 8.0.0 (clang-800.0.42.1).

If you have modified this source, you may insert additional notices
immediately after this sentence.
Copyright (C) 1998-2002, 2006-2016 Glenn Randers-Pehrson
Portions Copyright (C) 2005 Greg Roelofs

DISCLAIMER: The pngcrush computer program is supplied “AS IS”.
The Author disclaims all warranties, expressed or implied, including,
without limitation, the warranties of merchantability and of fitness
for any purpose. The Author assumes no liability for direct, indirect,
incidental, special, exemplary, or consequential damages, which may
result from the use of the computer program, even if advised of the
possibility of such damage. There is no warranty against interference
with your enjoyment of the computer program or against infringement.
There is no warranty that my efforts or the computer program will
fulfill any of your particular purposes or needs. This computer
program is provided with all faults, and the entire risk of satisfactory
quality, performance, accuracy, and effort is with the user.

LICENSE: Permission is hereby irrevocably granted to everyone to use,
copy, modify, and distribute this computer program, or portions hereof,
purpose, without payment of any fee, subject to the following
restrictions:

1. The origin of this binary or source code must not be misrepresented.

2. Altered versions must be plainly marked as such and must not be
misrepresented as being the original binary or source.

3. The Copyright notice, disclaimer, and license may not be removed
or altered from any source, binary, or altered source distribution.

 

Fix for RPM-GPG-KEY-CLOUDFLARE-MOD_CLOUDFLARE-1

Updating your software, you may have come upon the error:


Downloading packages:
warning: /var/cache/yum/x86_64/latest/modcloudflare/packages/mod_cloudflare-2016.11.0-1.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 8caccbf8: NOKEY
Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUDFLARE-MOD_CLOUDFLARE-1


The GPG keys listed for the "mod_cloudflare Packages" repository are already installed but they are not correct for this package.
Check that the correct key URLs are configured for this repository.


Failing package is: mod_cloudflare-2016.11.0-1.x86_64
GPG Keys are configured as: file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CLOUDFLARE-MOD_CLOUDFLARE-1

The easy fix for this is to follow the instructions at cloudflare on updating these keys. Just a couple linds of commands to run for most systems. FIX IT!

BitCoin ETF Request for Comment

The United States SEC has made a request for comment before making a decision on the Winklevoss COIN ETF. Specifically, the SEC needs your help to answer the following questions:

1. The proposed fund, if approved, would be the first exchange-traded product available on U.S. markets to hold a digital asset such as bitcoins, which have neither a physical form (unlike commodities) nor an issuer that is currently registered with any regulatory body (unlike securities, futures, or derivatives), and whose fundamental properties and ownership can, by coordination among a majority of its network processing power, be changed (unlike any of the above). Moreover, as the Exchange acknowledges in its proposal, less than three years ago, the bitcoin exchange then responsible for nearly three-quarters of worldwide bitcoin trading lost a substantial amount of its bitcoin holdings through computer hacking or fraud and failed. What are commenters’ views about the current stability, resilience, fairness, and efficiency of the markets on which bitcoins are traded? What are commenters’ views on whether an asset with the novel and unique properties of a bitcoin is an appropriate underlying asset for a product that will be traded on a national securities exchange? What are commenters’ views on the risk of loss via computer hacking posed by such an asset? What are commenters’ views on whether an ETP based on such an asset would be susceptible to manipulation?

2. According to the Exchange, the Gemini Exchange Spot Price is representative of the accurate price of a bitcoin because of the positive price-discovery attributes of the Gemini Exchange marketplace. What are commenters’ views on the manner in which the Trust proposes to value its holdings?

3. According to the Exchange, the Gemini Exchange is a Digital Asset exchange owned and operated by the Custodian and is an affiliate of the Sponsor. What are commenters’ views regarding whether any potential conflict of interest or other issue might arise due to the relationship between entities such as the Sponsor, the Custodian, and the Gemini Exchange?

4. According to several commenters, there is a need for the Exchange to provide additional information regarding “proof of control” auditing, multisig protocols, and insurance with respect to the bitcoins held in custody on behalf of the Trust, in the interest of adequate security and investor confidence in bitcoin control. What are commenters’ views on these recommendations regarding additional security, control, and insurance measures?

5. A commenter notes that the Gemini Exchange has relatively low liquidity and trading volume in bitcoins and that there is a significant risk that the nominal ETP share price “will be manipulated, by relatively small trades that manipulate the bitcoin price at that exchange.” What are commenters’ views on the concerns expressed by this commenter? What are commenters’ views regarding the susceptibility of the price of the Shares to manipulation, considering that the NAV would be based on the spot price of a single bitcoin exchange? What are commenters’ views generally with respect to the liquidity and transparency of the bitcoin market, and thus the suitability of bitcoins as an underlying asset for an ETP?

6. The Exchange asserts that the widespread availability of information regarding Bitcoin, the Trust, and the Shares, combined with the ability of Authorized Participants to create and redeem Baskets each Business Day, thereby utilizing the arbitrage mechanism, will be sufficient for market participants to value and trade the Shares in a manner that will not lead to significant deviations between intraday Best Bid/Best Ask and the Intraday Indicative Value or between the Best Bid/Best Ask and the NAV. In addition, the Exchange asserts that the numerous options for buying and selling bitcoins will both provide Authorized Participants with many options for hedging their positions and provide market participants generally with potential arbitrage opportunities, further strengthening the arbitrage mechanism as it relates to the Shares. What are commenters’ views regarding these statements? Do commenters’ agree or disagree with the assertion that Authorized Participants and other market makers will be able to make efficient and liquid markets in the Shares at prices generally in line with the NAV? What are commenters’ views on whether the relationship between the Gemini Exchange and the Trust’s Sponsor and Custodian might affect the arbitrage mechanism?

Please Send Comments and Answer The SEC’s Questions:
-Use the Commission’s Internet comment form at http://www.sec.gov/rules/sro.shtml
-Send an e-mail to [email protected] Please include File Number SR-BatsBZX-2016-30 on the subject line.
-Send paper comments in triplicate to Secretary, Securities and Exchange Commission,
100 F Street, NE, Washington, DC 20549-1090