Timeline for Is the use of "utf8=✓" preferable to "utf8=true"?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 16 at 8:10 | comment | added | stickynotememo | @Gary I can't image possibly being a millionaire because of an off-hand comment on stackexchange 12 years ago. You're insanely lucky. | |
| S Jan 6, 2020 at 18:44 | history | suggested | Sazzad Hissain Khan | Added related tags for the post | |
| Jan 5, 2020 at 15:12 | review | Suggested edits | |||
| S Jan 6, 2020 at 18:44 | |||||
| Sep 18, 2018 at 10:30 | comment | added | Kyralessa | @GaryRowe So did you ever get any donations off that link? | |
| Nov 18, 2013 at 19:58 | history | protected | CommunityBot | ||
| Oct 22, 2012 at 17:47 | comment | added | Gary | Off topic, but OK. Here's my personal donation Bitcoin URI: bitcoin:1KzTSfqjF2iKCduwz59nv2uqh1W2JsTxZH?amount=0.5&label=Agile%20Stack. Notice that the scheme is essentially a URN with query parameters, but it hands off to a protocol handler. This kind of URI could probably benefit from the “utf8=✓” workaround as well. | |
| Oct 22, 2012 at 12:59 | comment | added | hakre | Give examples of these URLs or didn't happen. | |
| Oct 19, 2012 at 8:29 | comment | added | Gary | I disagree. There are schemes out there that look like URNs and that take query parameters - such as Bitcoin. URIs are not confined to browsers. See en.wikipedia.org/wiki/URI_scheme. This question may also address the general case where character encoding is required when a browser accesses a protocol handler. | |
| Oct 19, 2012 at 2:22 | review | Close votes | |||
| Oct 19, 2012 at 2:27 | |||||
| Oct 13, 2012 at 15:52 | vote | accept | Gary | ||
| Oct 13, 2012 at 15:01 | history | tweeted | twitter.com/#!/StackProgrammer/status/257133980393017344 | ||
| Oct 13, 2012 at 12:45 | answer | added | Gareth | timeline score: 827 | |
| Oct 13, 2012 at 11:57 | history | asked | Gary | CC BY-SA 3.0 |