yashsingh1/xdaforums huggingface dataset:
[Windows Mobile Software Development] Agent Zach:
lol, okay smartass. :P

After replacing the Util & dlls on the device, it SEEMED to work [showed the "Loading" at the bottom again]

But still nothing. And I hard reset my device prior this time, in case of conflicts...

Maybe my Fuze is just garbage. :P
[Windows Mobile Software Development] mkucuksari:
According to me "ITEM-1" seems to be the best solution :)
[Windows Mobile Software Development] Agent Zach:
I left my device on the Auth page for literally 6 hours... nothing loaded...

I've lost hope. :P And everytime I close the Auth page, I get the FacebookUtil.exe error that's been listed in previous posts..

EDIT::

Think I may have found a solution... still in progress... [Got an Internet Explorer Error saying that the page couldn't be displayed... but I was unknowingly in Airplane mode...]

Will report with update..

{{Still waiting.....}}

** Just realized that I should have added the the "Not loaded" page to my Favorites... Would've made it a guaranteed success if I would've opened it, as a favorite, in Internet Explorer Mobile...
[Windows Mobile Software Development] madindehead:
@ meltwater

I don't understand why the authorisation doesn't work. As nothing seems to have changed your own end currently, it must be Facebook.

As for language files, I'm not seeing any change even using the new files sadly :(
[Windows Mobile Software Development] meltwater:
I take it you are having issues with the sense part of the language translation? If so, then disable sense, delete manilafull.xml and reset sense. If that doesn't work try changing your regional settings to something else, reset and put back (until I did this, my sense was working fine with the original files - probably since I had been using different iterations during development and it had cached it somewhere).
[Windows Mobile Software Development] madindehead:
@ meltwater

My authorisation did actually work this morning. I used the Desktop setting. Will try that with Sense. Does that mean I should no longer being seeing the IDS menu items and should see the real thing yes?

Will try that in a bit. Off out for now, so will sort it either when I'm out, or later on.
[Windows Mobile Software Development] meltwater:
OK that's great, glad it worked.

This authorisation thing is bugging me now, either it works or it doesn't (that's kinda how software works!), after all if the url isn't right (it's the same for all modes except the "type=popup/desktop/wap/touch" bit) it would not work at all. So unless there is something I'm missing with the WebBrowser control which needs to be initialised or something, it can only be facebook.

Also not sure if its using any proxy setting if present.

Will try to find some info on the "Feedback-Based Allocations" stuff, it doesn't make any sense what they've written, but if it's a anti-piracy measure where apps have to gain use over-time before it is trusted enough to be allowed greater access then that's a whole heap of problem (on release the tab will be requesting hundreds of authorisations...). Humm, it might be a control on how many requests to add the application can be sent via users (the trouble is most of the documentation is for apps within facebook, and the remaining stuff is for java, android and iphone, wm is forgotten already it seems).

Language:

If you have draftD loaded in your windows dir and named correctly (and set to that region) then Sense should use that file for the translations, just have to force it sometimes to read it!

I think I will try a mix of 1 and 2, since there is no reason to allow a user to select an invalid file and may as well check it when it's selected. It still won't be able to check it for sense working, but it's probably a help. Will also make sure the correct locale is tried on the first run (I might also see if I can add an item on the drop down to "select devices detected locale" so there is an option to allow it to always detect it).

webBrowser control:

http://support.microsoft.com/kb/975281

Ok, so there is a hot fix for the webBrowser, which explains the no-scrolling issue I have. Will try updating my CFW version (currently 3.5.7283.0 found via \windows\cgacutil.exe) will see what effect that makes. I love M$ for making life easy (can't even find a cab to get anything newer!).

This is the problem without the updated Compact Framework (Agent Zach's framework is newer). Note: I got around the scollbar issue by un-docking the control and making it big. Still doesn't solve the authorisation issue though...

OK, hitting brick-walls here with this. Although the authorisation is only to update your status, it's the key to the rest of the API, so need to fix it somehow.

Ahhhh, the more I read on this, the less I want to know, the webBrowser control is seriously messed up! You get different behaviour on each WM version and the workarounds are insane & incomplete.

this.webFbAuth.Navigate(new Uri(authUrl)); <--how bloody difficult is that to get right!

UPDATE: Url works fine within Opera on the device, and in IE so must be the webBrowser control. Also works fine within the Emulator (normal windows mobile 6) - which also has right-click and loading bar where my device doesn't. Will focus on the other issues for now and come back to it (when I'm less annoyed by it...).
[Windows Mobile Software Development] mike2nl:
So it is friday and this means i have reached my weekend. No work today, juhuu. What i am was thinking is when i look to meltwater...

It is nteresting for you that i make a cab file of the actually version to test this again?

Possible some news that i can use for that?

What do you say meltwater?
[Windows Mobile Software Development] madindehead:
@ meltwater

I'm sure people will appreciate all your extra work :) I should be able to check later what versions of those things I have :)
[Windows Mobile Software Development] Agent Zach:
I, of course, appreciate all of the time you put into the extra work to guarantee complete functionality..

As I, being the one who kinda' spotted the issues, feel decently responsible for the loss of "free-time" for meltwater.

Though, me listing the issue is, of course, part of Beta Testing.

The new tab may work for thousands of users, yet may fail for thousands more.

If you wish to halt "fix" progress, as everything else seemed to work flawlessly, I completely understand.

I did a hard reset a few hours ago and lost the tab, but I hard reset due to another Sense Issue I have been experiencing with the Photo's & Videos tab, not the Facebook Tab.
[Windows Mobile Software Development] Captain_Throwback:
Did someone say CAB?

I made one for myself, to test it, so I can post it here, if you want :).
[Windows Mobile Software Development] zjxpot:
Sure, I would also like to test it:D
[Windows Mobile Software Development] mike2nl:
Hi Captain,

yes i was it. I am busy with that. Two cabs done and testet. I hope the 4rd and 4th test are going ok. Then it can be out of the door, hoppa...
[Windows Mobile Software Development] Captain_Throwback:
In that case, I will allow you to post what you have. I only have 1 CAB, and it seems to work fine (it does still require you to manually run MoonNah's FixStartManila, but it's included in the CAB). Since it sounds like you've been working hard on it, I don't want to post mine if yours is going to be more complete.
[Windows Mobile Software Development] mike2nl:
@Captain_Throwback:

ok then i will post it later on the day with a password on rar. This i wll post in privat message (PM). Now we have a child party, sorry..stress in high concentration, uff :eek:
[Windows Mobile Software Development] meltwater:
I know that is what the beta testing is for (and suspected it might cause issues), just not enjoying the microsoft development experience this week.

Will try not to stress about it and look at it fresh in a few days and think up some new options. Will keep trying it until it works.
[Windows Mobile Software Development] madindehead:
No problem meltwater. Just take your time on this release. At the end of the day, we want you to have the drive to continue to develop the tab past this stage. Hopefully once most of the hard work is out of the way, future releases will be easier.

I look forward to testing the new release, whenever that may be. But don't feel rushed.
[Windows Mobile Software Development] newdecember:
any user that is able to haveall the functionality that you have stated will be more than appreciative of all the time taken to get it completely right

i for one will be one of them :D

so if it is troubling you my best advice would be to maybe take a few hours (or days) away from it and come back with fresh eyes... and you may even take one look and find the problem straight away...

it helps me when i am recording/mixing songs
[Windows Mobile Software Development] Agent Zach:
For the possible Solutions, numbers 3 and 4 seem to be the best choices. 3 may be an easier approach.
[Windows Mobile Software Development] meltwater:
Yep I think I'm fighting a losing battle trying to fix the WebBrowser control. I've posted on the facebook forum about the client_id hopefully they can tell me if it's a problem.

Had another thought...adding 5.
[Windows Mobile Software Development] Agent Zach:
I think 5 is the big winner, but would you NEED to disable Cut/Copy/Paste?
[Windows Mobile Software Development] meltwater:
If using either 3 or 5, it's out of my hands by then (no way to protect that initial url), since it's using an external browser (hence why I can forget about the WebBrowser control issues). Catch22.

For next beta test, might try 3 & 5, but dependent on testing out the client_id aspect.

Just depends on what damage you can do with a client_id.

If you can simply take that id and pretend to be that application you can do a lot of damage and the client_id will be linked to the authors profile and the user would have trusted the author's application.
[Windows Mobile Software Development] Agent Zach:
But in that sense of the Client_id, it is the users responsibility to maintain and secure their device(s), whether through common sense or software.

And I'm sure the average user won't be tampering with such queries. Especially if they want the Tab & Features to work as they were intended to. :)
[Windows Mobile Software Development] meltwater:
Yep but we all type in user names and passwords to random apps without thinking what else could it use those details for. DroppedBox Client, 3rd party web-browsers, ummm facebook apps.

Got to admit though, huge security hole on facebook's part if

a) it's easy to see the client_ids (for all I know, it could be within the links to the application on facebook anyway)

b) the documentation is right about the User Agent Flow (there is a chance it requires a specific callback url defined in the application settings [that would fix it], but the documentation uses the default one (for cases where you don't use a specific callback) so hard to tell).

Anyway testing tonight should tell me one way or another. May not be a show stopper anyway (as you say, not many would be bothered about abusing it), but at least I would know in advance the risk.

EDIT:

a) Ok had chance to check it and the client_id is dead easy to get from within facebook, so not much point trying to protect it.

b) I was right (you can generate access for any facebook application [[[REMOVED]]]

So the security aspect is academic, apparently (nice to see facebook apply the same care to security as they do with privacy).

Will have a go at working on solutions 3 & 5 and see how it goes.

OK, the security aspect is NOT academic, I think I've discovered a very serious fault in facebook security!
[Windows Mobile Software Development] Agent Zach:
I think you should inform Facebook of their fault, for the sake of all of us. :P

And take your time with the fixe(s) m8. I'm in no hurry, and I'm sure the others aren't either. :)
[Windows Mobile Software Development] meltwater:
Posted it on the facebook dev forum, and managed to find a valid email via the privacy email.

No-one seems too bothered so far, I just said on the fbdev forum I'll post the full instructions in a weeks time if it's not been fixed. Hopefully that'll spur them into action. For now, revoke permissions on any apps you don't use (worth doing anyway), and if you are really worried make sure you don't keep it logged in. Anyway, since there is no Graph-API for windows mobile yet that I know of (except my own in-development one) it's a lot of work for someone to abuse it on our devices.

It'll probably take an evenings work to do the implementation and try out the solution, the other stuff is done anyway. I'm avoiding using the aforementioned authorisation method, although it's simpler, facebook may need to break it to fix the problem (personally I don't see the need for it).

Will find a night to do the changes.
[Windows Mobile Software Development] madindehead:
Have to agree with this. Like I said before, we don't want you burning yourself out developing this mod.
[Windows Mobile Software Development] meltwater:
No problem. Just got the initial test code ready for the authorisation, will test and then if it works, clean up the interface so it is easy to use. Hopefully we can test three possible methods in the next beta and then determine what we want to keep/use:

Previous internal webBrowser control - still interested to see if this works once the permissions have been granted.

Pre-Authorise - Use external browser to initially accept permissions (so app should then be able to fetch granted permissions without requiring a browser)

Provide Access Code - Use external browser to supply temporary Access Code, which when pasted back into the settings page is then exchanged internally for the required Access_Token.

This should still provide a secure way (with exception of the Facebook issue already reported to Fb) to Authorise the application. Note, the Access Code that the user can obtain in 2 & 3 is of no use except for the linked application, the granted permissions and the related user account to exchange for a genuine Access_Token, so is acceptable for it to be exposed to the user.

Also, I've found where I can revoke permissions from my fb account, so it should be easier to test now.
[Windows Mobile Software Development] madindehead:
Excellent meltwater. I look forward to it! PM away when you are ready ^^
[Windows Mobile Software Development] Agent Zach:
So rather than Facebook, themselves, fixing the issue, you basically found a work-around that is still secure?

Awesome!
[Windows Mobile Software Development] meltwater:
Unfortunately not, but that is a problem for most apps until they change it.

Nope can't secure mine, like I hoped, unfortunately. Plus Fb have got back to me and don't see the issue yet.
[Windows Mobile Software Development] madindehead:
That's always worrying when a company can't see the problem they have created. Facebook has always been a bit dodgy with privacy etc :(

I wanted to add something about your new language files by the way meltwater. I have been using the tab on and off for checking things, and I have noticed, that the left soft key that says "Update Now" sometimes says the correct text ("Update Now") and sometimes says IDS_Update_(whatever it is exactly). Sense seems to like messing around with the language file, it's very strange.

I know you are busy working on other bits currently with the security, but I just thought I would mention it :)
[Windows Mobile Software Development] meltwater:
Sounds like sense isn't quite reading the full file or something, it tends to do that when it finds a matching name in another file (i.e. weather tab), it'll be IDS_UPDATE_NOW which is the text it looks for. I've found it is very sensitive to the file format white space, I only edit them in Programmers Notepad now since Visual Studio was causing issues.

I've got the paste code method working so far, doesn't use the webBrowser control so fingers crossed that'll solve one issue. Still working on the pre-auth method, which would be the smoother option if I can get it working.

Will see what happens with fb, the dev forum appear to understand there may be an issue, I've PM'd one of the mods the full steps, so hopefully it'll be dealt with (I half expect without comment on fb part - wouldn't be the pr they need after the last few weeks/months of privacy issues).

Google Buzz anyone? Oh hangon, they nicked my MAC address and SSID, captured my wifi packets and took pictures of my home.....perhaps not.

VERY busy this week, sorry for the delay but beta2 will come soon. Thanks so far.
[Windows Mobile Software Development] madindehead:
No problem meltwater.

You thinking beta 2 will be out next week?
[Windows Mobile Software Development] romualdrichard:
French translation

Hi,

Here is the French translation.

Let me know if I can try out the beta to see if all the messages are ok.
[Windows Mobile Software Development] meltwater:
Yep, I'm aiming for end of this week, but if not beginning of next week.

If beta2 goes well, can release a version for the language translations and then proper release. :)

Thanks for the translation, will check it out when I get chance.
[Windows Mobile Software Development] Captain_Throwback:
XDA Facebook App?

Hey meltwater,

I just came across this thread: http://xdaforums.com/showthread.php?t=630992

There's a team of people working on coding a new WinMo Facebook app. I don't know if they're aware of the security issue you discovered, or if they might have some info that would help you with your development, but I thought I'd mention it here if you weren't already aware of it.

Keep up the good work!
[Windows Mobile Software Development] meltwater:
Nope hadn't spotted it before, contacted them to see how they are getting on etc.

Only got a few bits to do on the beta2 now, I could only implement 1 of the alternative authorisation solutions, but hopefully that will be enough, just making sure it's as clear as possible on how to do it (there are a few issues with the sense look n feel SDK which will still need to be resolved too - but won't worry about that for this beta fingers crossed the SDK will be updated).
[Windows Mobile Software Development] mike2nl:
sorry for no response the last 7 days. I was away in austria for motion control lessons and support for other people with highspeed network problems (400us response).

But now i am back after the 1000KM on the highway (BTO - roll on down the highway). I hope my head will be free tonight, so i can read all the new postings here, uff.
[Windows Mobile Software Development] meltwater:
Glad you had a good trip.

Look sharp everyone, beta2 hopefully will be PM'd out tomorrow fingers crossed. I'll also be able to explain my serious lack of time too.
[Windows Mobile Software Development] sharkie405:
:D Glad to hear it's coming together. Can't wait for the release!
[Windows Mobile Software Development] meltwater:
Ok beta2, is zipped up and ready to go! Will PM in the morning, time for bed and sleep, plus will allow me to write proper release info etc.

NOTE: Still only CLOSED beta, but a step closer to proper release.
[Windows Mobile Software Development] Agent Zach:
Glad to hear, and can't wait! :)
[Windows Mobile Software Development] mkucuksari:
Feedback For Beat4_040710

Hi meltwater,

First of all congratulation with your a new baby in the family :) I have just installed BETA4 version. Please find my quick response related with your changelog

It is working now :) But did not notice any difference between selecting and diselecting

"No Facebook Authorisation" pop-menu is a new item, I guess. Like it, very good idea. This new message successfull canceled from "Facebook Api Setting>Disable Prompt for Authorisation" item

a-Firstlly I select and use "Internal Authorisation" method. Without any problem it is authorized :) (Pict-1)

But I have also noticed that you were not able to fix Log-on web page resize problem. :o

Althgouh I have successfull authorized and "Update Now" Left-Soft key is working, "Link to Facebook" info still stay at Facebook tap asking authorization which is a problem I guess and with Right-Soft Key only opens "Setting" menu :o (Pict-2).

After I re-logon from Facebook tab by using "Link to Facebook", I get the correct menu options at Right-Soft" Key

b-Then after removing the authorized method without any problem, I select "Use Default Browser & Paste Code" method.When I click "Open Browser" button, my default webbrower "Opera-10" is opened (Pict-3) that suprised me:). You find a way to send URL to OPERA-10 that I have never seen before :D .

Somehow COPY&PASTE did not work for me, can not copy the whole adres. I guess it will be very difficult to copy correct whole adress from Opera-10.

So According to me, "Use Internal Authorisation" method must be default :)

But

I will ask you to use URL Adress sending method at "Facebook On-line". For now it only opens "OPERA-10" without connecting to "m.facebook.com".

That is a general problem of using "OPERA-10", I guess :)

With a pop-up message, it works great without any problem

I have Diamond with VGA screen. Please look at Pict-4 I guess it is fixed now

"Default system's language setting" (en-us) works perfect.I also make a test by changing Language setting to UK (en-gb). It works without any problem. When I try to change the language to other like germany it warns me to have "...._manil" file, which is again perfect.

Could not test, not sure what was the original problem.

PS Each time when I return back to "Facebook Tab", I see "Process cursor", seems to be something is running at back. It was same at previous Beta Version. Not sure ,if it is problem or not, just want to share.

I hope I am clear enough with my poor english, sorry for that :o
[Windows Mobile Software Development] meltwater:
Thanks for the fast test! Great detail too.

No it changes the items available within the other sub-sections.

Yep that's the reason for the other method, the webBrowse control it uses it kinda broken in wm6 onwards in several ways, worse on wm6.5.1. Hence why it's not a solution for all.

Yeah that could get confusing, will have to make it clear to people, the tab needs to be authorised via HTC settings, and the extras are authorised via my app (this is why it's optional). I did think about stealing the htc apps permissions and using them but I HOPE facebook will fix that hole.

I've found, long press on the bar gives copy option which gives you the whole address, alternatively you can grab the last bit which includes the "code=xxxx...xxx", the util will extract the correct part automatically.

Not had that problem, I've found the desktop url has needed to be changed (it auto-detects and defaults back to mobile). I may have forgotten to check the default links in the registry file, I'll look them up and post them, may fix your problem.

Yep thought it was more obvious it had been done correctly that way.

Yep that's perfect.

Good good.

When an item was hidden or show, due to another item changing, it wasn't updated on the display until the page was scrolled.

I'll see if I can spot this, may just be the tab reloading the pictures and fb icon overlay.

No problems at all, very clear and very good info. Thanks for taking the time to try it.
[Windows Mobile Software Development] madindehead:
Seems to be working well meltwater :)

The authorisation works well. Language file works properly (using en-gb). Advanced settings stay saved properly. Everything else seems smooth so far. Will need to test more, but that will happen with daily use, as I don't have time today to sit and test every function sadly :p