Author Topic: Neat WP Plugin  (Read 3786 times)

Brad

  • Inner Core
  • Hero Member
  • *
  • Posts: 4154
  • What, me worry?
    • View Profile
Neat WP Plugin
« on: July 18, 2018, 11:05:50 AM »
Unfortunately it's out of date.
https://wordpress.org/plugins/i-dont-endorse-google/

It automatically nofollows any link to any Google entity.   :D

martinibuster

  • Inner Core
  • Full Member
  • *
  • Posts: 180
    • View Profile
    • Email
Re: Neat WP Plugin
« Reply #1 on: July 21, 2018, 02:43:23 AM »
Heh. I suspected it was created by a disgruntled web worker.

Quote
I manage lots of big website and for all of them I received Absurd “Unnatural Link warning” even if I never made link building and I received those links only for real merit.

 :o


« Last Edit: July 21, 2018, 02:52:42 AM by martinibuster »

Brad

  • Inner Core
  • Hero Member
  • *
  • Posts: 4154
  • What, me worry?
    • View Profile
Re: Neat WP Plugin
« Reply #2 on: July 21, 2018, 10:51:19 AM »
Yeah.  Not that it matters, but I like that somebody served Google some of their own medicine.  Heck if it was up to date I'd install it.

aaron

  • Inner Core
  • Full Member
  • *
  • Posts: 229
    • View Profile
Re: Neat WP Plugin
« Reply #3 on: July 21, 2018, 06:39:34 PM »
The way of serving Google some of their own medicine there would perhaps some sort of security warning overlay that reminds them their Chrome browser is operated by the largest & most profitable data mining company in the history of the world & there are alternatives like Brave, Firefox, Opera, etc. :)

Brad

  • Inner Core
  • Hero Member
  • *
  • Posts: 4154
  • What, me worry?
    • View Profile
Re: Neat WP Plugin
« Reply #4 on: July 22, 2018, 10:21:27 AM »
Yeah, it would be fun to see browser wars again.


Rooftop

  • Inner Core
  • Hero Member
  • *
  • Posts: 1915
    • View Profile
Re: Neat WP Plugin
« Reply #5 on: July 26, 2018, 09:18:04 AM »
Yeah, it would be fun to see browser wars again.

Fun is a strong word

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 9292
    • View Profile
Re: Neat WP Plugin
« Reply #6 on: July 26, 2018, 02:32:26 PM »
It would be really easy to bring up to date.

There's almost no code there. It's just one file, mostly comments and arrays of Google URLs and properties. Not much room for security issues. Other than the README, the entire plugin is this file:
https://plugins.trac.wordpress.org/browser/i-dont-endorse-google/tags/1.0.2/nofollow-google.php

There are no settings, no user input, no admin interface, no database calls, no Javascript. This has pretty much no security risk. The only downside of being out of date is some URLs might be wrong.
« Last Edit: July 26, 2018, 02:34:03 PM by ergophobe »

ergophobe

  • Inner Core
  • Hero Member
  • *
  • Posts: 9292
    • View Profile
Re: Neat WP Plugin
« Reply #7 on: July 26, 2018, 02:43:17 PM »
Fun is a strong word

Thanks for reposting - I was  trying to find your original post yesterday to forward to a friend.

rcjordan

  • I'm consulting the authorities on the subject
  • Global Moderator
  • Hero Member
  • *****
  • Posts: 16340
  • Debbie says...
    • View Profile
Re: Neat WP Plugin
« Reply #8 on: July 26, 2018, 03:20:28 PM »
.

Brad

  • Inner Core
  • Hero Member
  • *
  • Posts: 4154
  • What, me worry?
    • View Profile
Re: Neat WP Plugin
« Reply #9 on: July 26, 2018, 04:46:09 PM »
It would be really easy to bring up to date.

There's almost no code there. It's just one file, mostly comments and arrays of Google URLs and properties. Not much room for security issues. Other than the README, the entire plugin is this file:
https://plugins.trac.wordpress.org/browser/i-dont-endorse-google/tags/1.0.2/nofollow-google.php

There are no settings, no user input, no admin interface, no database calls, no Javascript. This has pretty much no security risk. The only downside of being out of date is some URLs might be wrong.

Thanks ergo.  I might install it for fun and adventure.  I just wrote a post about hosted analytics for blogs and for Google Analytics I linked into the Wikipedia article rather than the service URL.  Not my usual practice but what the heck.