How to attribute Freebase on my site - freebase

Since this page (https://www.freebase.com/policies) doesn't work and since credits data like wikipedia uri and statement, seems to be suddenly disappeared from topic queries (example: https://www.googleapis.com/freebase/v1/topic/m/017n9?filter=/common/topic/description), i would like to know how to credit freebase topics that contain text from wikipedia.
Is it enough to put links to freebase and wikipedia homepages with their respective licenses somewhere in my site or i must link every single topic to it's wikipedia page?
Thanks.

Related

Can I customize look of Google News RSS feed on my website?

I have a doubt regarding the use of Google News RSS Feed. Google News help states this:
Why Google might block an RSS feed In some cases, Google News might
block a feed. That could happen if you are:
Using Google News feeds for profit or to increase traffic to your site
Reformatting news results so they look like your own content
Changing, editing, or creating works based on content from Google News
I am looking to clarify these points:
Can't I customize the look of the feed? I want to have a separate page for news related to content on my website. Will then I violate the second rule if I customize the look of it? For example, I'll display a slideshow on the top along with a listing in the bottom much like FeedWind or Feedgrabber widgets.
I am surely not violating the third one. But everyone displays Google News on their website to sustain traffic right? Isn't the first rule broken by everyone who uses Google news RSS feed on their website?
Can't I customize the look of the feed?
Create an app or script to grab the feed, parse it, decorate it the way you like. Now, you have successfully customized the look.
I want to have a separate page for news related to content on my website. Will then I violate the 2nd rule if I customize the look of it?
A bit critical question. Let me provide you a simple answer: mention at certain corner that it was from google news feed. When google shows you ads, it puts a little AdChoice at a cozy corner by clicking on which you can confirm that that was an ad from google - follow their strategy, give them proper credit.
I am surely not violating the third one. But everyone displays google news on their website to sustain traffic right? Isn't the first rule broken by everyone who uses Google news rss feed on their website?
When you are providing value to others, then people like to act blind and pretend that what they see is not a promotion. For example, free medical camps are not actually done for helping others if they cannot promote them to get prospective patients (clients/customers) or cannot get free media promotion (again free flow of lot of customers) - forget those doctors who are lonely or have no responsibility or for whatever reason serving for free.

When to use the related link relation

The IANA registry contains a official link relation type of "related"
related: Identifies a related resource.
https://www.iana.org/assignments/link-relations/link-relations.xhtml
I have also read the referenced RFC4287.
The value "related" signifies that the IRI in the value of the
href attribute identifies a resource related to the resource
described by the containing element. For example, the feed for a
site that discusses the performance of the search engine at
"http://search.example.com" might contain, as a child of
atom:feed:
<link rel="related" href="http://search.example.com/"/>
An identical link might appear as a child of any atom:entry whose
content contains a discussion of that same search engine.
But that only seemed more confusing to me. Aren't all links related? After all rel = relation.
Can anyone try to clarify this and give valid use cases for rel="related"? Is it just a catch all relation type?
It’s a generic “this link is related to this entry” link relation.
The related link relation serves three use cases:
Link an entry to a related entry from the same publisher. Some content management systems can keyword-match entry archives and find related/suggested/recommended entries.
Link to a related external document. E.g. an entry discussing Facebook’s privacy policy could link to it and a Facebook blog post announcing a policy change. (You can include multiple links with the same relation.) This use cases is intended to enable link-clustering use cases. E.g. grouping entries discussing the same thing/link from different feeds, or rank a  “hot topic” at the top of the feed list (like the Fever feed reader did).
Blogs doing reading-list/daily-digests/link-curations/etc. can link to all the external documents they recommend.
The two last use cases are expressions of the Semantic Web. This was one of the ways we were supposed to get personalized set of trending topics/links/things from our feed subscription. Twitter and Google Now is the global arbitrators of this today.
However, this link relation can also be used by feed readers to display a list of related links from the publisher. The link:title attribute can set the link title to present them to people.

Share On LinkedIn Description field not displayed in new UI

Posts made via the Share on LinkedIn API for users on the new user interface appear on their accounts with at most: a user message/comment, image, title, and link domain. However, the documentation on the Share on LinkedIn API (https://developer.linkedin.com/docs/share-on-linkedin) describes that the request body can also contain a "description" field with text up to 256 characters. When the description and all the post fields are provided explicitly to the API (as in the example in the documentation), the description field does not appear for users on the new UI. The description field did appear for users when they were on the old UI.
The Share on LinkedIn API provides an additional option for sharing by omitting the post details fields (title, image, description), and allowing LinkedIn to generate the post based on the Open Graph data it finds at the link URL. However, the result is the same as above for users on the new UI.
Is this a bug, or is the documentation out-of-date?
These are your only options. Choose one:
Share image.
Share description.
If you try to share both, you will only see an image.
I argued with LinkedIn support about this for two weeks I've also directly contacted many of the developers. They have agreed that this is the logic and this is how it is designed to work. I tested this theory out on Wikipedia (has a description, no image) and GitHub (has both description and image). Results:
Wikipedia: Description ONLY -- Works (but no image)!
GitHub: Image ONLY -- Works (but no description)!
I made test site, with only description, to verify this, and it appears confirmed.
Sure, the Official Microsoft LinkedIn Share Documentation makes no mention whatsoever of this, but once again, reality is in direct conflict with Microsoft's understanding.

creating blogroll by inoreader, feedly or similar ones

In Google reader(R.I.P) we could select some interesting links by a special tag and then make public them and show links on our blogs or websites.
Is there a way to create this by Google reader alternatives like Inoreader or Feedly or AOL reader or etc?
I should probably start by saying that I'm the BDFL of Inoreader, but I feel obliged to answer you. If anyone thinks my answer is inappropriate or that this can be achieved with one of the other mentioned options, feel free to bash me in the comments :)
Yes, you can do that in Inoreader.
Since you are familiar with Google Reader, you shouldn't have much difficulties starting up with it, but if you have, here's a quick guide to get you started.
Depending on what you need to achieve the option you want is accessible via right-click on a folder or a tag:
Then in the dialog that pops up, you will see an Export option. Click it and you will get 3 links - for RSS feed, HTML page (what you need) and a public OPML file (for folders only):
A few notes on folders and tags:
Folders are used to group sources (RSS, social and other feeds) and content inside them is automatically populated from the feeds.
Tags on the other hand are mostly manually populated by you. When you read an article and you find it interesting, you can press "T" or click the label icon at the bottom of article to tag it. This behavior is almost identical in all major RSS readers. Working with tags in Inoreader is covered in detail in this blog post.
Now I said mostly before, because tags can also be automatically populated by Inoreader's Rules. Basically they works like your email filter. You can set up keywords or other conditions and tag articles automatically as they arrive. This feature is covered in this blog post.
Hope this helps!

Retrieving relevant posts from Wordpress blogs

I have a requirement to write a program in Java to retrieve all the posts from all the wordpress sites containing a keyword(s).
This is how I approached the problem. I initially thought I would crawl the wordpress sites looking for the keywords I am interested in. But I realized if there is an endpoint for wordpress search, it makes my job a lot easier. So I have looked around to see if there is any search endpoint to submit queries and get the links for the posts.
All I found is just http://wwww.en.search.wordpress.com. I can still tweak the url and get some links. But
I like to know if there is any better way to handle this problem
The search link I posted is for the users and it might be limiting my search results since I query it through a program
Also I like to retrieve posts from the given date range. I am not sure if this is possible with my approach.
Appreciate any help in this regard. Thank you.
How about this approach:
Assuming you don't need to go back to the history and scrap all the data I would just stick to tags
http://en.wordpress.com/tags/
I would crawl it every day get the most popular tags (by font size) then on each tag get the articles published in the past 24 hours
On each post get all the comments and search for your keywords
Would that work? if not please share more details
Good luck

Resources