Some posts inserted using Blogger API not displayed on main page - api

I am using Blogger API to insert posts. Go through the following blog to understand the problem:
Link: https://post-testing123.blogspot.com/
In this blog I have 7 posts:
5 posts with title of format 'Title #no'- are created with API request.
2 posts with title of format 'Manual #no'- are created manually.
Manual posts were created before API posts.
In this blog, I have set the number of posts to be displayed on the main page to 3.
So, on main page 3 out of 5 posts created with API are visible.
On clicking on Older, only the 2 manual posts are displayed and the 2 API posts left are not displayed.
In archives all 7 posts are displayed.
And if I set the number of posts to be displayed on the main page to a large number like 30.
Then, all 7 posts are displayed correctly.
I have tried changing the theme but it doesn't work.

I found the reason for this, it is a bug in Blogger.
It occurs when two or more posts have same timestamp (Same minute, not same seconds or milliseconds).
So, when you post using API (especially using Google Apps Script), a lot of your posts are likely to have the same the timestamp.
Something similar is stated here:
https://support.google.com/blogger/thread/2238679?hl=en&authuser=0
Hope it helps.

Related

Google suddenly stopped indexing my posts after I changed the categories

Why suddenly Google stopped indexing my posts? I started posting regularly in October. And the site got Adsense approval. I just changed the categories and front design. Some posts were in the top results but they lost ranks too. Domain age 2 yrs.
All of my posts got indexed after I submitted request. But after changing the category structure new posts are not indexing. But when I run live test search console says, "the post is ready to index" and no error sign shows up.
If it’s for the category change then how can I fix that?
I repeatedly submitted imdexing requests after running the live url test. I also submitted a new site map on the search console. But no luck. Google indexed no new post.

Tracking readership of a PDF document

Background. As some of you know I Publish a business deals listings magazine in PDF format. I am after Google Analytics/Matomo style tracking of readership of the PDF. (I use Matomo for my websites and prefer it over google)
Where I want to get to for example is User one spent 3 seconds on Page 1 skipped page 2, read pages 3-10 left.
User 2 read pages 20-30 and spent an average of 5 seconds on each page. Etc Etc,
Is there a way to do this or is it even possible?
I already know if the magazine has been downloaded and where and when and have this data.
Many thanks

Change in number of geotagged Instagram posts

I have written an app which uses the Instagram API to retrieve geotagged posts containing "#sunset" and related tags. On March 22 - 23 2016, the number of posts being collected dropped dramatically. Has anyone else observed this behavior, or do you have any suggestions for what I should look for? Is it possible there has been a change to Instagram's privacy policy that leads to fewer geotagged posts? I do not think it is due to a change in my code (I have not changed the code, and I am actually collecting the posts using two different methods, both of which display this pattern). Nor do I think it is due to my API key suddenly becoming invalid (the key seems to work).
UPDATE: I discovered other people have been having similar problems. See here:
Instagram API /tags/{tag-name}/media/recent changed behaviour
Instagram /v1/tags/{tag-name}/media/recent endpoint doesn't return min_tag_id in pagination block
UPDATE 2: it appears that both the Python + Ruby Instagram clients were deprecated on the same day, March 22, right before everyone started having this problem: https://github.com/facebookarchive/instagram-ruby-gem/commits/master, https://github.com/facebookarchive/python-instagram/commits/master

How Facebook organize posts in news feed page

I have always wondered how Facebook organize posts in news feed page. Facebook doesn't use date and time to organize posts in news feed page. This is obvious when some posts acquire many likes or comments. These posts, in spite they may be older posts, will be displayed first.
let's suppose a simple database table for posts :
Post_Id
Post_Owner_Id
Post_Text
Post_Image
Post_Date
So what field (or fields) that must be added to organize posts like the one in Facebook ?
The algorithm for how Facebook sorts the newsfeed isn't public from what I've heard, but what the algorithm looks for isn't completely.
Have a look at these articles for a slight idea on what they do and why.
Bufferapp - Decoding the Facebook newsfeed
Forbes - Facebook Changes News Feed Algorithm To Prioritize Content From Friends Over Pages
Everything You Need To Know About Facebook’s News Feed Algorithm
So if you are wanting to recreate their algorithm, you could get a very rough imitation by sorting based on date rounded to the closest week, second by the type of post it is (message, page, etc) then perhaps the number of likes it got.
Which means you would need number of likes and the Post_Type attributes.
You would also need to have it sort them based on friend status (direct or friends-of-friends) and whether or not the post comes from someone verified such as a celebrity.
There is so much to it.

/me/home doesn't return all the posts

I've noticed that me/home in the Graph API doesn't return posts by certain users. I've tried this in my app as well as just using Graph Explorer. It returns most posts, consistently fails to include posts by certain friends. I don't think this is a caching issue, because I've tried over a period of one day with same results. It's not random either. It's the same handful of posts that are always missing.
I checked the posts in question and don't see anything special. And it's happening with newer posts also.
Do I need to add any special parameters to my request ?
Users, in their Facebook privacy preferences, can configure what data 3rd party applications can see about themselves.
What you are seeing is that certain users have made their activities not viewable to your application.