I think you're making a mistake by offering this for free.
The kind of people who care enough about their web experience to install a new browser are the kind of people who won't mind parting with a few £$€ to do so.
To be profitable, free apps must target the broader market, but this is a relatively niche product. I don't think you'll get enough IAP fast enough to be sustainable.
Because the average user doesn't even know what a web browser is, they just open up "the internet" on their phone. They are not going to change something that they're not even aware of. It's also demonstrably true that the average user doesn't know or care about privacy enough to make this choice anyway. You don't have the resources to change either of these things.
So, disregard the average user. Market this as a paid product which offers a superior web browsing experience for the technology connoisseur and the privacy concious. These people, on average, have a lot more money, are easier to sell this product to, and don't mind paying.
Another reason to just charge money for this is that this provides assurances about your income stream which should mean that you are less likely to consider anti-user practises in order to generate income at some point in future.
Apathy is probably your biggest enemy. Look at the struggles Firefox and Opera went to even with the random browser choice stuff in Windows in Europe, which made no significant difference to their market share.
Yahoo’s implementation of this (Sign In Seals) works with a Flash (LSO) Cookie. So, they remember your username (and your personalized picture / seal) by inspecting the Flash cookie. I remember the first time I tried it—and being impressed—but then wondering how the fuck they did it. Then being less impressed when I realized that it doesn’t work after clearing your Flash cookies (or if you have Flash turned off).
Suppose that to log in to friendface, you enter your username, then it shows you the cartoon elephant that you selected beforehand, and you enter your password.
When fake-friendface wants to phish you, they get your username, then they give that username to friendface and receive your cartoon elephant in exchange. They show you the cartoon elephant, and you decide that this must be friendface.
How does friendface show your cartoon elephant before you enter your username? (hint: it won't)
The way this works looking at banking websites is that the user enters a username. Then they get some secret image + description that they previously wrote and can enter their password.
Most of the banking websites that do this also remember information about your browser and IP. If it's a new computer, you're required to verify the computer before they show you the image.
It is a simple man-in-the-middle attack. The proxy will forward the username and echo back whatever it receives from the bank.
The reason it might work in this case is because the assumption is that people will only verify the browser bar when they first arrive on the page, and not when they have been "tab nabbed" like this
Plus, the secret image assumes I actually remember which image I select for every page. Given that none have the same collection of images, I'm likely to have only a vague notion of which one I picked at account creation.
to accurately determine the current machine's external IP address, as the one reported by the operating system may be inaccurate (doesn't take into account NAT, proxies, firewalls etc)
I think code blocks don't track indentation. A code block is just a bunch of lines beginning with 4 spaces (or blank lines) and the rest (when >4 spaces) are treated as leading spaces.
Markdown has outgrown Gruber's stewardship, "ambiguity is a feature" is not an opinion I can get behind. Calling this something other than markdown would be more confusing for end users. It is markdown, standardised.
"I don't like his position so he should lose his ownership". Lovely.
My problem with the name "Standard Markdown" is I don't think it's going to be clear enough, I think people will think it's the same thing as Markdown (which it's not), under the theory that "non-standard" would have an obviously different name such as "Lisp Markdown" or "Japanese Markdown".
If they had used a word other than "Markdown" I wouldn't have a single problem, I would cheer them on.
I don't see a real benefit in this name to anyone, but I see serious downsides.
> "I don't like his position so he should lose his ownership"
That's certainly an unbiased translation :rolls eyes:. If you want to have a good-faith debate, you should avoid tendentious re-writes of your interlocutor's arguments.
> "ambiguity is a feature" is not an opinion I can get behind
You clearly don't like his position.
Be he has explicitly chosen not to make a specification, he's had years and numerous requests. From what I've seen/heard John Gruber likes that it isn't formalized with a spec.
So if a group of people, especially a large group with 10s of millions of users (at a minimum) decides to write a spec and name it "Markdown" over Gruber's wishes it sounds like trying to take ownership from him.
My phrase was glib, but I don't think it's that far off from many of the comments expressed here.
He owns an ambiguous text formatting system? He didn't invent the notion of simple ASCII-character based formatting, and he didn't write a spec. Plus this spec explicitly deviates from his implementation, so it's not the same obviously.
The reasons that he didn't write a spec after requests is very likely post-hoc rationalisation, behind the simple reason that writing a spec is not a fun task.
Can't over emphasise the importance of a good IDE for this kind of thing, even if you're a hardened vim or emacs zealot. A tool like IntelliJ IDEA makes navigating new/large codebases a million times easier.
With Vim and Emacs you can get this if you have a plugin that autogenerates a ctags/etags file. Then (in Vim) just <C-]> to an identifiers definition and <C-o> back.
The kind of people who care enough about their web experience to install a new browser are the kind of people who won't mind parting with a few £$€ to do so.
To be profitable, free apps must target the broader market, but this is a relatively niche product. I don't think you'll get enough IAP fast enough to be sustainable.