Archive for March, 2020

WordPress Built-in Feeds

By default, WordPress comes with various feeds. They are generated by template tag for bloginfo() for each type of feed and are typically listed in the sidebar and/or footer of most WordPress Themes. They look like this:

URL for RDF/RSS 1.0 feed

<?php bloginfo('rdf_url'); ?>

URL for RSS 0.92 feed

<?php bloginfo('rss_url'); ?>

URL for RSS 2.0 feed

<?php bloginfo('rss2_url'); ?>

URL for Atom feed

<?php bloginfo('atom_url'); ?>

URL for comments RSS 2.0 feed

<?php bloginfo('comments_rss2_url'); ?>

The first four feeds display recent updates and changes to your site’s content for the different feedreaders. Of these, the RSS feeds are the most well known. The last feed example is used by RSS 2.0 feedreaders and does not show your site’s content. It only shows the comments made on your site.

To track the comments on a specific post, the post_comments_feed_link() template tag is used on single post pages like this:

<?php post_comments_feed_link('RSS 2.0'); ?>

Finding Your Feed URL

There are times when you want to tell someone your site’s feed address or URL, or you need it to submit it to search engines and directories, many of which now accept feed URL submissions. There are four possible URLs for each of your feeds. Any of these will work.

http://example.com/?feed=rss
http://example.com/?feed=rss2
http://example.com/?feed=rdf
http://example.com/?feed=atom

If you are using custom permalinks, you should be able to reach them through this usage:

http://example.com/feed/
http://example.com/feed/rss/
http://example.com/feed/rss2/
http://example.com/feed/rdf/
http://example.com/feed/atom/

So if you are like me and are always playing with operating systems and computers, you probably get tired of removing ssh known_hosts entries so you can get past the:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is…….

First delete your ~/.ssh/known_hosts file

Then:

a) To disable for all users put the entry below in the global SSH configuration file ‘/etc/ssh/ssh_config’

b) To disable for one user, put the entry below in the configuration file in the user’s folder ‘~/.ssh/config’

To disable key checking for all machines in the 192.168.0.0/24 submit enter:

Host 192.168.0.*
   StrictHostKeyChecking no
   UserKnownHostsFile=/dev/null