What is meta? ×
Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 131 Stack Exchange communities.

Ok, so recently reading George's post about a read-only SO for mobile. How hard do you think it'd be to create a read-write front end of SO (nevermind the mobile part)?

Possible problems(and solutions) I can think of:

  • Forward compatibility(ie, every change Jeff makes breaks the frontend)
  • Captchas. This can be solved by detected a captcha and forwarding it to the user
  • Would Jeff like us? I don't believe you are allowed to screenscrape a lot, so would Jeff like us enough to allow us to? (whenever the API is not sufficient, ie, read-only)
share|improve this question
    
Screen scraping is just as bad as it sounds. –  uɐɯsO uɐɥʇɐN May 15 '10 at 1:56
    
Tag this feature-request and who knows...? Maybe something will happen. –  uɐɯsO uɐɥʇɐN May 15 '10 at 3:10

1 Answer 1

up vote 0 down vote accepted

Personally, I would hold off until there is a read/write API (if it even happens at all).

The amount of work to get a read/write version working with no API is HUGE. You have to simulate an openid login and carry around cookies and pretend to be a web browser and so on.

As you said even if you got it working it is almost trivial for the powers that be to break it.

I think there are plenty of opportunities around the read only API. That is where the focus should be.

share|improve this answer
    
Waffles, I'm just curious.. Do you really use MSO but not any of the main trilogy sites? lol –  Earlz May 15 '10 at 1:50
    
I agree here. It seems to me like the best thing to do is wait. After all, as @waffles mentioned, simulating OpenID is no small feat. And I know that - because I once tried (successfully) to implement OpenID on one of my sites. –  uɐɯsO uɐɥʇɐN May 15 '10 at 1:55

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .