Originally Posted by rmerren (Post 894348)

Whatever permissions you deny, will cause facebook to stop sending that information. For example, if you deny the user_checkins permission, then facebook will not tell the app about any checkins you have. If every third post in your statuses is a checkin, they simply won't be returned in a query. In general, denying the user_* permissions just makes that type of object not be returned in a query.

The pubish_* permissions are, as expected, the ability of the app to publish that type of object on your behalf. If you deny the publish_checkins permission and never try to do a checkin, you will not notice the difference. If you do try to publish a checkin without the permission, you should get an error that (I think) the app will show to you. (I am only slightly uncertain because I do check the returned info for these types of errors, but facebook doesn't really give great error messages for everything.)

In any case, you can deny the permission for either reading or writing checkins and the app will work fine. Feel free to try it...you are certainly thinking of things that I didn't consider, you won't break anything by trying, and I (and I'm sure others here) will appreciate hearing the results of your testing.

Also: if you are interested in seeing what the backend does with your permissions, you can check out the source code at Gitorious. It is always stressful to cede permissions on facebook because you don't know what will be done with your data. But the great thing about open source (and platforms like Maemo that encourage it) is that even if you can't read the source code yourself you can be reasonably assured that someone else would spot nefarious code.

Originally Posted by sup (Post 906340)

Hi, nice application, but I found out today it does not handle well my localization. I am Czech, we have some funny characters like ěščřžýáíéú - using ˇ - hacek/caron and ´ - acute accent. Effing handles these fine, but there is also special characet "ů" - which Effing handles as "ú". I have the character straight on my keyboard. It is not that grave since the language is well understandable even without these special characters, but it would be nice if it worked.

I will be happy to provide any other information (or should I file a bug?).

Originally Posted by rohanhole (Post 906757)

Please Please We need n900 ICON !!!

Originally Posted by rmerren (Post 906837)

If it were any other nationality, I would tell you to buzz off, but since Prague has the coolest town clock in Europe, I will check it out. :D

I had problems with international characters early on, but that was an issue of encoding the text for sending it to facebook via http post. So a few questions for you:

• [1]When you type these characters into the app, do you see them onscreen properly as you type them?
  [2]When you use these characters directly in Facebook, do they work properly?
  [3]Does a status entered on Facebook that shows up properly on facebook show up properly in the current statuses list of the N900 app?
  [4]Can you identify the specific unicode values of these characters? Look at this page to help: http://en.wikipedia.org/wiki/List_of_Unicode_characters

The last is the most important...if you can give me the character values that work and don't work I can do some testing directly.

There are lots of possibilities for where this encoding is going wrong, so if I can isolate the layer where this is happening (in QML, QML to C++ transfer, QT C++ code, encoding for HTTP transport, HTTP Transport, in Facebook, when viewed in facebook, when rendered in the upper box in QML, etc.) I can better figure out how to resolve it.

Originally Posted by elie-7 (Post 906858)

is this app awesome or what, fastest updating status way i know, yes i know it could be faster (via an effing widget ?? ;) ) .
just a question, whats the future of this app ? is there any new features ? don't get me wrong it does what its suppose to do great (position doesn't work with me :( maybe becasue my country isn't supported) .