4 ms·
The only place I've seen these used are universities (eg each professor gets a webspace) and other small companies and organizations. I think it's relatively sa
by Wowfunhappy 7y ago
The only place I've seen these used are universities (eg each professor gets a webspace) and other small companies and organizations. I think it's relatively safe to assume Alice isn't going to attack Bob—if she did want to, she has better ways to do so.
Now, if someone knows of a host selling ~username spaces to members of the public, that's a different story.
- tinus_hn 7y agoFor Bob to trust Alice not to do something dumb like installing something and never updating it is another matter though.
- kccqzy 7y agoIn most of the places where you get the ~username sites the users themselves have non-root UNIX accounts and they can't really install things on their own. (Well they can install it in their own home folder but that's it; won't affect other people.) Even the web server is centrally managed and the user only provides static HTML.
- tinus_hn 7y ago> won’t affect other people Except what the article is about; because all sites are on the same domain and origin all sites security affects all other sites security. A page on one site has the right to manipulate all pages on another site. > Even the web server is centrally managed and the user only provides static HTML In other news php has suddenly ceased to exist and javascript is no longer a thing. Sorry, handwaving the problem away does not work.
- Polylactic_acid 7y agoWhen I see ~username I know I'm about to load a page with some cream tiled background. These days every user just gets their own subdomain like username.usersites.com
- op00to 7y agoHeh. I use two userdir websites for work.
- ccmcarey 7y agoNPM does this, noticed yesterday when creating an account. And wow, that website is absolutely terribly written.
- lieuwex 7y agoWhat? npm doesn't provide site hosting of any kind. Apart from just using the ~ convention this is not relevant at all.