Something went wrong with BRPS server!

[Leniel Macaferi]

Hi,

I'm getting this error: Something went wrong with BRPS server!

My blog: http://www.leniel.net/2007/12/first-post.html

Looking with Firebug I can see this:

"NetworkError: 500 Internal Server Error - http://brps.appspot.com/get?blog=4926735770070291800&post=1208315199370579484&key=1d44a6fb&callback=jQuery1640166422942570303_1338525447963&_=1338525478333"

Hope you get it working again...

Thanks,

Leniel

[Leniel Macaferi]

Well... if you click the link http://brps.appspot.com.get?... you'll see this message at the end of the page:

verQuotaError: The API call datastore_v3.Get() required more quota than is available.

Looks like there are a lot of people using this awesome blogger plugin/extension.

Is there any way to overcome this right now?

[Yu-Jie Lin]

Thanks for reporting.

I checked the log, there was near 3 hours outage due to out of quota
for database read operations. (Between 9 hours and 6 hours ago)

Unfortunately, if you want to stay with /get (the old client script),
there is nothing I can do. Google App Engine requires minimum spending
US$2.10 per week for enabling billing, and I am not going to spend my
own money for that.

I suggest you to move onto gas.js:

http://brps.appspot.com/install
http://code.google.com/p/brps/wiki/ClientGasJs

gas.js is more powerful is a way of speaking.

Yu-Jie Lin

[Leniel Macaferi]

Hey Yu-Jie Lin,

Thanks... correct. You should not spend your money. :)

Does gas.js offers the same features of the old /get client script? Will I have to tweak something to get the same behavior?

Thanks,

Leniel

[Yu-Jie Lin]

Yes.
No, basically. not tweaking, but changing the names.

Please read:

http://code.google.com/p/brps/wiki/ClientGasJs

> --
> You received this message because you are subscribed to the Google Groups
> "Blogger Related Posts Service" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/blogger-related-posts-service/-/4Ue5gU_NCp8J.
>
> To post to this group, send email to
> blogger-relate...@googlegroups.com.
> To unsubscribe from this group, send email to
> blogger-related-post...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/blogger-related-posts-service?hl=en.

[Leniel Macaferi]

Great Lin... just got it working after doing the renaming. The only thing I think now is that it's not as precise as the old script. The old script showed the matching value and from what I could remember the matching of posts by labels was better! Nonetheless it's working as expected and it's a pretty good add-on for any Blogger user.

It's trimming the posts' titles and placing ... Is there any way of changing this?

Once again, thank you very much for your support!

Leniel

[Yu-Jie Lin]

It's nothing about accuracy, in fact, if have to speak of it, it may
be more accurate. It uses Google Search to perform the searching, so
if you label lazily, the result might be better than you get from old
script. Blogger label searching requires perfect match, by searching
using Google, you don't need to have perfect match, for instance the
plural form and singular form would match. Moreover, it is not only
searching within labels, but the entire page, that's said, the post
content is searched.

Anyway, there is some drawbacks, of course.

About the trimming, you need to adjust the regular expression, I am
sure this is not a big problem for you since you have Firebug
installed, I assume that you know JavaScript. I am not sure about what
you mean about placing issue.

> --
> You received this message because you are subscribed to the Google Groups
> "Blogger Related Posts Service" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/blogger-related-posts-service/-/IFmNrjXFT68J.

[Yu-Jie Lin]

Oh... the trimming, now I see. I will need to look at the result of
API call. I may not be able to do anything for that if returned entry
title is already trimmed. I don't recall gas.js trims, it's been long
time since I touched that script.

[Yu-Jie Lin]

Okay, there is nothing I can do about this, the returned data looks like:

{"GsearchResultClass":"GwebSearch","unescapedUrl":"http://www.leniel.net/2009/10/finding-missing-numbers-in-list-csharp.html","url":"http://www.leniel.net/2009/10/finding-missing-numbers-in-list-csharp.html","visibleUrl":"www.leniel.net","cacheUrl":"http://www.google.com/search?q=cache:AiYd7bli1GAJ:www.leniel.net","title":"Leniel
Macaferi's blog: Finding missing numbers in a list using LINQ
<b>...</b>","titleNoFormatting":"Leniel Macaferi&#39;s blog: Finding
missing numbers in a list using LINQ ...","content":"Oct 12, 2009
<b>...</b> Sort(); // <b>First</b> number of the list var firstNumber
= list. <b>...</b> Of course, this solution assumes that the list
you use already contains the <b>first</b> and last <b>...</b>"}

It's already been trimmed.

[Yu-Jie Lin]

By the way, BRPS is an open source project, so you can actually run
your own if you like the old script.

I have thought about make it more easier for people to run its own
BRPS, one normal blog is hardly able to consume entire free quota of
GAE unless it's super popular. Unfortunately, the current BRPS source
code may require user having little knowledge of Python and GAE in
order to deploy on their own.

I may also add post preview feature, but only if it's possible for
regular use to deploy on their own.

Do you have such knowledge and/or are willing to help out?

[Leniel Macaferi]

Sure... it'd something I'd like to setup for my own! What's needed in order to make a copy of the script and setup it just for my use?

Programming languages in general are no problem to me! Google App Engine is easy to get going...

Let's move together and make it available for everyone do a private deploy! :)

I'm waiting your instructions...

On Friday, June 1, 2012 4:47:12 AM UTC-3, Yu-Jie Lin wrote:

By the way, BRPS is an open source project, so you can actually run
your own if you like the old script.

I have thought about make it more easier for people to run its own
BRPS, one normal blog is hardly able to consume entire free quota of
GAE unless it's super popular. Unfortunately, the current BRPS source
code may require user having little knowledge of Python and GAE in
order to deploy on their own.

I may also add post preview feature, but only if it's possible for
regular use to deploy on their own.

Do you have such knowledge and/or are willing to help out?

[Yu-Jie Lin]

Actually, I don't know what exactly needs to be changed. I think some
domain name/url change in script is all needed.

The code can be viewed here:

http://code.google.com/p/brps/source/browse/

What's the OS you are working with normally?

I am thinking it can be more like someone (who already has the
knowledge or is willing to read a page of instruction) runs their own
BRPS and shares with their fellow bloggers, which might be a better
direction for next BRPS.

Anyway, this might take time, because I need to think what has be done
for next BRPS and what new feature can be implemented. I will also
write a post to see if there are more people want to join. And create
a new thread here for further discussions.

Basically, I only need people to try to set up BRPS and write the
instructions, and point out the difficulties, so I can make it easier.

> --
> You received this message because you are subscribed to the Google Groups
> "Blogger Related Posts Service" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/blogger-related-posts-service/-/nn6E3hBtl00J.

[Yu-Jie Lin]

I just add a new wiki page:

  http://code.google.com/p/brps/wiki/RunningYourOwnBRPS

Let me know if there is any unclear instruction.

I am guessing, this is as far as I would do at this stage after thinking about it. Really don't want to spend time to write more stuff when there is not many users. Not many users involve in discussion, at least. BRPS probably has served 1 million related list a month, gas.js served 840K the last 30 days, but I barely see any feedback, actually no feedback at all.

So I change my mind, will not create a new thread or write a blog post, and probably won't change any code of BRPS.

[Leniel Macaferi]

Dear Lin,

You have good Python coding skills... :D I cloned your repo in Google Code and downloaded GAE SDK and Python 2.7.3. I managed to get the web app running locally through Google App Launcher. Went through some walls but managed to get everything working as expected.

I think I'll write a blog post showing how one can work on a open source Python project using GAE SDK on Windows. I'm working on Windows 7. Of course I'll use your project as a great example! :)

I'll get back here when I finish the configuration as per your WIKI page... I did the modifications you mention in the wiki. Now it's just a matter of deploying the app to my GAE app spot. I'll do it tomorrow because I have had enough installations and code for today!

[Leniel Macaferi]

By the way: I tried the LinkWithin widget for Blogger http://www.linkwithin.com/learn

You can see it working here: http://www.leniel.net/2007/12/first-post.html

See the the image thumbnails? They're great. This is something that can be implemented in BRPS. The post preview you mentioned is other great feature that could be turned on/off...

LinkWithin is not as good as BRPS. The accuracy/matching is not that good... BRPS is fair enough. If it doesn't see something related to a post (looking at the labels/tags) it won't show nothing: "No posts found". This is better in my opinion. I don't like to see posts that have nothing to do with the post the user is reading at the moment.

Let's keep evolving the BRPS... and no, it doesn't SUCK as you wrote at the project home page. It ROCKS! :o)

[Yu-Jie Lin]

Actually, LinkWithin is not only widget, I have seen a couple more.

To add thumbnail preview to BRPS isn't hard, the preview image link
has already been returned via API, just BRPS currently didn't store
it. That probably only take 10-minute coding for storing it and an
hour or two to update client script, most likely to adjust the layout.

The issue I have is I don't know how many people want it, certainly
not me. In fact, I have planned to let BRPS dies quietly when Google
Search API shuts down, it will be sometime in 2013. When I first
release BRPS, I was still hoping Blogger would soon have official
gadget for us, so I can retire BRPS, but it never happens, I am
guessing they are reluctant because those related content providers,
if Blogger releases official gadget, that might damage those
providers' business.

To be honest, BRPS is never accurate enough for me, the best way to
have related posts is to manually mention in post as it should be in
the first place. Related posts is just a lazy way for me to, uhm, be
lazy.

> --
> You received this message because you are subscribed to the Google Groups
> "Blogger Related Posts Service" group.
> To view this discussion on the web visit

> https://groups.google.com/d/msg/blogger-related-posts-service/-/Ma-sFnjM1sIJ.