HVTA [cnttbachkhoa]

Recently, I've tried to share a URL on Facebook. They displayed (No Title) on status box without any further information. I checked my site and found that I cannot even click on the like button at the end of each post. I'm gonna report this problem to Facebook. But how?

All parameters (extracted by UltraEdit32)

--------------------------------
- Activate-on-launch
- Allow-sandbox-debugging
- Always-enable-dev-tools
- App
- Automation-channel
- Bookmark-menu
- Assert-test
- Crash-test
- Browser-subprocess-path
- Chrome-frame
- Country
- Debug-print
- Diagnostics
- Disable-winsta
- Disable-audio
- Disable-byte-range-support
- Disable-custom-jumplist
- Disable-databases
- Disable-desktop-notifications
- Disable-dev-tools
- Disable-extensions
- Disable-hang-monitor
- Disable-ipv6
- Disable-images
- Disable-javascript
- Disable-java
- Disable-logging
- Disable-metrics
- Disable-new-tab-first-run
- Disable-plugins
- Disable-popup-blocking
- Disable-prompt-on-repost
- Disable-shared-workers
- Disable-site-specific-quirks
- Disable-sync
- Disable-web-resources
- Disable-web-security
- Disable-web-sockets
- Disable-xss-auditor
- Disk-cache-dir
- Disk-cache-size
- Dns-log-details
- Dns-prefetch-disable
- Dom-automation
- Dump-histograms-on-exit
- Enable-application-cache
- Enable-benchmarking
- Enable-experimental-extension-apis
- Enable-webgl
- Enable-extension-timeline-api
- Enable-extension-toolstrips
- Enable-fastback
- Enable-file-cookies
- Disable-local-storage
- Enable-logging
- Enable-monitor-profile
- Enable-native-web-workers
- Enable-new-autofill
- Disable-remote-fonts
- Enable-renderer-accessibility
- Enable-seccomp-sandbox
- Enable-session-storage
- Enable-stats-table
- Enable-sync
- Enable-tabtastic2
- Enable-udd-profiles
- Enable-watchdog
- Experimental-spellchecker-features
- Explicitly-allowed-ports
- Extension
- Extensions-update-frequency
- File-descriptor-limit
- First-run
- Force-fieldtest
- Hide-icons
- Homepage
- Import
- In-process-plugins
- Incognito
- Internal-nacl
- Js-flags
- Load-extension
- Load-plugin
- Log-filter-prefix
- Log-plugin-messages
- Log-level
- Make-default-browser
- Media-cache-size
- Memory-profile
- Message-loop-histogrammer
- Metrics-recording-only
- Nacl
- New-tab-page
- No-default-browser-check
- No-events
- No-first-run
- No-js-randomness
- No-proxy-server
- No-sandbox
- Omnibox-popup-count
- Pack-extension
- Pack-extension-key
- Parent-profile
- Pinned-tab-count
- Playback-mode
- Plugin-data-dir
- Plugin-launcher
- Plugin-path
- Plugin
- Plugin-startup-dialog
- Print
- Privacy-blacklist
- Process-per-site
- Process-per-tab
- Profile-import
- Proxy-auto-detect
- Proxy-bypass-list
- Proxy-pac-url
- Proxy-server
- Purge-memory-button
- Record-mode
- Remote-shell-port
- Renderer-assert-test
- Renderer-cmd-prefix
- Renderer-crash-test
- Renderer
- Renderer-startup-dialog
- Restore-last-session
- Safe-plugins
- Enable-sdch
- Search-in-omnibox-hint
- Show-icons
- Show-extensions-on-top
- Silent-dump-on-dcheck
- Simple-data-source
- Single-process
- Start-maximized
- Sync-url
- Syncer-thread-timed-stop
- Tab-count-to-load-on-session-restore
- Test-name
- Test-sandbox
- Testing-channel
- Thumbnail-store
- Trusted-plugins
- Try-chrome-again
- Uninstall
- Use-flip
- Testing-fixed-server
- Use-lf-heap
- User-agent
- User-data-dir
- User-scripts-dir
- Utility-cmd-prefix
- Utility
- Utility-allowed-dir
- Wait-for-debugger-children
- Web-worker-process-per-core
- Web-worker-share-processes
- Winhttp-proxy-resolver
- Wininet-ftp
- Worker
- Worker-startup-dialog
- Zygote-cmd-prefix
- Zygote
- Kiosk
--------------------------------

Some interesting ones:

- Disable-images (Disable Images Display:: do not show pictures)
- Disable-javascript (Disable Javascript:: turn off JavaScript)
- Disable-java (Disable Java Applet:: turn off Java Applet)
- Disable-audio (Disable Audio / Sounds in html:: Music Sound off site)
- Kiosk (Full-Screen acted like a KIOSK:: F11 full screen is not adjusted)
- User-data-dir (Assign User History / Bookmark:: bookmarks and history browsing history specified directory)
- User-agent = "XXXX" (Assign User-Agent:: Specifies the user-agent)
- Crash-test (Simulate an Exception:: Analog Chrome crashes)
- Disable-plugins (Close all PlugIns:: Close all Plug-Ins)
- No-sandbox (No Sandbox features:: solve some open problems)
- No-default-browser-check (Disable Default-Chrome-Browser Check:: turn off start the default browser check)
- Experimental-spellchecker-features (Enable Chrome Spell-Check like Firefox:: Open experimental spelling)
- First-run (Simulate First Run with Welcom Msg)
- Start-maximized (Maximized on Start:: open maximized, and not the same as F11)
- Incognito (Incognito Private Mode:: Seamless Windows)
- Disable-popup-blocking (turn off pop-up blocking, no blocking off one by one)
- Disk-cache-dir = "X: /" (Google Chrome Assign Disk Cache Dir specify the temporary files cache directory)

NOTE:
Close & Shutdown all Google Chrome instances beofre launched in command line

Note:
First close all Chrome windows, new parameters to take effect

I've just recognized today. When logged in to Bluehost's control panel, DNS Zone Manager, I can see an option to add an AAAA record. They also merged MX records with A and CNAME (before I had to go through different components to see A, CNAME and MX records)

That's pretty great, as my network supports IPv6 now. Will try sometimes to make sure it works.

3 years ago, I used co.cc domain to create my blog. Started with personal feeling, involved with CCNA module test and other IT stuffs. It went very well. In recent month, Alexa ranking is about 400K.

Of course, anyone can get a free co.cc domain, so spammers use it a lot to spam and build rank. As a result, Google has banned co.cc domain recently

Now I have to build my blog from beginning. Very big lesson.

Google has been the king of the internet world. There are many policies which google has framed to fight against spams. In order to effectively and more powerfully fight against spams, Google now has taken an initiative to block all of the Co.cc sub domains from its search index. These domains have been widely used by many people especially spammers to exploit people’s resources.

People start a website with CO.CC copy & paste same contents and make the website as junk to get a Google page rank. This started attracting so many spammers.

Google Blocked Co.CC Domains from Search Index

This is what Matt Cutts said about Co.cc

    “First, a definition: a ‘freehost’ is a domain that will let anyone register a site on that domain. There’s lots and lots of high-quality freehosts out there (wordpress.com comes to mind),”

    “We absolutely do try to be granular, but I wanted to mention that if we see a very large fraction of sites on a specific freehost be spammy or low-quality, we do reserve the right to take action on the freehost as a whole”

The following are some of the reasons which lead to removal of Co.cc domains from search result index.

    Giving free subdomains like real domain names.

    Co.cc sub domain sites made a mess with google search results with copied content and spamming the net

    Many autoblog sites runs with free co.cc domains.

    In the last few years, these domains are widely used by many users for spamming.

Now what you should do, if you are the one of the user who was using Co.cc domains

    Quickly remove the co.cc subdomain from your blog address and change to blogspot domain name

    Submit your blogspot url and sitemap to google using google webmasters tools