#Twitter & #WordPress RSS in #Mediawiki (#Wikieducator) #vmvwiki #vmvdlt

1 Comment

Using RSS to put a WordPress or Twitter feed into Mediawiki (wikieducator)

Thanks

I must thank my friend & colleague Steph Day for working behind the scenes into finding Amit  Agarwal’s connection between Twitter and MediaWiki via Google Drive Developer, and proving it could be done.

WordPress

The RSS extension in MediaWiki allows you to feed from the WordPress RSS feed. Add the following to your MediaWiki page (but replace my WordPress blog with yours)

<rss>https://virtualmv.wordpress.com/feed/</rss>
<rss>https://virtualmv.wordpress.com/feed/|short|date|max=5</rss>

Instructions

The following parameters are supported:

  • charset=… The charset used by the feed. iconv is used to convert this.
  • short Do not show the description text for each news item.
  • date Shows date/time stamp for each news item.
  • max=x Shows x most recent headlines.
  • highlight= term1 term2 The terms separated by a space are highlighted.
  • filter= term1 term2 Show only RSS items containing at least one of the terms.
  • filterout= term1 term2 Do not show any RSS items containing any terms
  • reverse Display the RSS items in reverse order

See complete article at http://www.mediawiki.org/wiki/Extension:RSS

Twitter

This is much more complicated since  in 2013 Twitter changed the way it allowed developers to access the Twitter Stream. An RSS feed unfortunately is not available, instead a JSON file is generated. However, using a bit of “magic” by creating a Google App allows you to convert the JSON file into an RSS feed which can then be accessed in MediaWiki.

Instructions

 from  Digital Inspiration created the bridging program that performs the magic and has generously shared the instructions at http://www.labnol.org/internet/twitter-rss-feeds/27931/

Examples of an RSS feed generated

You should replace the value of ‘q’ parameter in the URLs as per requirement.

Following Amit’s instructions I found one area that needed a little further explanation: For Step 2.  Configure your Google Script:

If you want to get a wrapper for your feed refer to the Sample page/instruction links at the start of this post.

Some Notes:

  • Don’t expect the RSS Feed to show older Tweets particularly for Search. After activating the gApp you may need to add a Tweet for it to appear in the panel.
  • Twitter Search does not necessarily return all the relevant Tweets in the Search. So in my classes I have had a lot of students post with my #vmvwiki hashtag and they have not shown up in the panel.  Unfortunately this is what Twitter have done and in 2013 this killed the student use of Twitter as a viable communication tool for Social Media in the classroom.

.. now to see if I can create an RSS Feed for a Facebook Group 🙂

 

2013 Feb: YahooXtra’s email hacking

Leave a comment

YahooXtra: What actually happened? 

A WordPress vulnerability caused this…

http://www.iitp.org.nz/newsletter/article/414?utm_source=email 

and another

http://arstechnica.com/security/2013/01/how-yahoo-allowed-hackers-to-hijack-my-neighbors-e-mail-account/ 

 

 

.. and looks like my Backup blog has suffered a hack again too. Getting to the stage I'll switch it off and use a different Blog system.

Domain Name cloaking using frames

3 Comments

Learn't something the other day. We have a wordpress web site on hostable.com and the Domain Name is with Freeparking.

We have been having trouble with the url displaying in the browser. So you get "http://mydomain.com/&quot; no matter what page is displayed – this is pretty useless if you want to bookmark a page.

Lots of web searching revealed that Freeparking cloak your site in a 100% frame – which is VERY bad form as search engines tend to ignore any frame based sites (we couldn't figure out why the site rated so poorley).

So the actual page HTML looks like

<frameset rows="100%,*">

<frame name="top" src="http://xxxx.12345.a.hostable.me/wordpress/&quot; noresize="noresize" frameborder="0" scrolling="auto" />
<noframes> 
   <body>
   <p><i>This document uses a frameset.</i></p>    
   <p><a href="http://xxxx.12345.a.hostable.me/wordpress/">Click Here</a> to view the page.</p>
   </body>
</noframes>
</frameset>

Ok.. so off to Freeparking Help desk .. and their response

 

Subject: [WebFarm/Freeparking #1400011] URL Redirection – xxxx.co.nz

 Hi ,  There's no good answer to that unfortunately. Cloaked wont show much in the way of filenames, or anything else, as you mentioned. You can really only cloak it or not cloak it.  — Regards, Chris

So the choice is either show xxxx.co.nz on all pages or  forget the domain and wind up with urls like http://xxxx.12345.a.hostable.me/wordpress/be-involved/ .. so whats the point of the domain name???

There does not appear to be away around this apart from:

  1. Host the site with freeparking or
  2. register the domain name with someone else (though check if they also do cloaking the same way – I have been told godaddy does the same)

Any ideas welcome….

13-Aug: Suggestion from Inga – does require certain conditions to be met before this will work.  http://www.thesitewizard.com/apache/frame-blocking-anti-clickjacking.shtml

 

WordPress hacking: Bat Boy and Mr. DJh

1 Comment

Grr!@###$

What a damn nuisance  looks like there is a way to hack your WordPress web site. My research shows it as The Bat Boy or in my case Mr. DJh (see below)

Bat Boy Hack on WordPress

It does 2 things

  1. Changes your admin login & email account in the users table and (this means you can't log in as admin)
  2. Changes index.php code for the theme (which is what shows on the page)

Anyway this is how to fix it:

http://www.youtube.com/watch?v=ESp_rceZ_gw

UNFORTUNATELY, in my case the admin user was unchanged (but I still can't log in) but one of the index.php files in the template was changed (you can see by the edit date on the server) though cleverly in code: starts like

? echo(stripslashes(base64_decode('PGh0bWw+ ….. 

Renaming the folder killed the site so the hack is in there somewhere and this was the only program with a different date that I could find.

At this stage I can either find the index.php file (which is pretty old) or reinstall WordPress and import the main blog (which I will probably do as it was only my backup anyway). 

I am guessing a flaw was found in one of the versions of WordPress and subsequently fixed by the WordPress people, however (as in my case) this was my backup blog and was quite old – so probably had the flaw still, and so wide open for the hack. My more recent one was left alone (so far) – this one. Can anyone confirm this???

So the Moral is "Keep up with updates" – yes I should know that!!!!