Timeline for Thoughts on the future of Stack Exchange site customisation
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17 at 15:18 | comment | added | OrangeDog | The domain/cookie issue is that security policy for cookies is isolated to domains. SE has a single unified login - you use the same one across all sites. But, unless you do non-trivial custom configuration, cookies set on e.g. stackoverflow.com will not be sent to meta.stackexchange.com, nor to e.g. askubuntu.com. However, it is very easy to get everything with a common domain suffix to share a cookie. | |
| Jun 3 at 2:50 | comment | added | V2Blast StaffMod | "Any particular reason why challenges with domain names is mentioned?" – I assume it's just because that reason is a notable one why additional sites aren't likely to have custom domains; it's a factor they need to consider whenever a site has a custom domain. | |
| Jun 2 at 19:41 | history | edited | starballMod | CC BY-SA 4.0 | added 127 characters in body |
| Jun 2 at 18:41 | history | edited | starballMod | CC BY-SA 4.0 | added 69 characters in body |
| Jun 2 at 17:39 | comment | added | user400654 | as far as taht last bullet... i could see a world where, if the company was no longer called "Stack Overflow", the community that is stack overflow would be more capable of such changes (though... the more active a given site is maybe the more involved such a change should be) | |
| Jun 2 at 17:06 | history | answered | starballMod | CC BY-SA 4.0 |