|
|
| Line 12: |
Line 12: |
| From [[RayKing]]: Ben shut off that extension because it was somehow being abused and we were seeing problems on ICANNWiki which shares the same server (these are the only 2 sites on this server). I'm cc'ing Jonah (ICANNWiki) and Ben now, having just read the thread in your e-mail to see if there's a resolution to both issues. ~~ [[MarkDilley]] | | From [[RayKing]]: Ben shut off that extension because it was somehow being abused and we were seeing problems on ICANNWiki which shares the same server (these are the only 2 sites on this server). I'm cc'ing Jonah (ICANNWiki) and Ben now, having just read the thread in your e-mail to see if there's a resolution to both issues. ~~ [[MarkDilley]] |
| : From [[Emufarmers]]: I've added a robots.txt file telling bots not to crawl the dynamically generated pages; it looks like in this case it was probably a well-intentioned spider. I've re-enabled Semantic MediaWiki for now, though I can't guarantee that I won't have to disable it again. | | : From [[Emufarmers]]: I've added a robots.txt file telling bots not to crawl the dynamically generated pages; it looks like in this case it was probably a well-intentioned spider. I've re-enabled Semantic MediaWiki for now, though I can't guarantee that I won't have to disable it again. |
|
| |
| ==== 06 April 2014 - why https? ====
| |
| https://WikiIndex.org fails for me, is this a browser issue or a configuration issue with the website? ~~ [[MarkDilley]]
| |
| :'''Failing''' I also have a failure to connect. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 15:58, 29 June 2014 (UTC)
| |
| ::Why the need for a secure https configuration? And you can't just put https infront of a standard url,.and expect it to load, without correctly configuring the server to accept https page access. --[[User:Hoof Hearted|Sean, aka <small>Hoof Hearted</small>]] • <sub>[[:Category:Active administrators of this wiki|Admin]] / [[WikiIndex:Bureaucrats|'Crat]]</sub> • <small>[[User talk:Hoof Hearted|talk2HH]]</small> 23:33, 5 July 2014 (UTC)
| |
|
| |
| ::: That's right. As well could You rename a picture.bmp into a picture-jpeg and expect it to become compressed ;-)
| |
| ::: But back to the original question: It seams not to be important to have secure connection, because the content of a Wiki that is even IP-edited would not be in anyway private, rather the opposite, very, very public ;-) But for those who log on, they have to send a password which is unprotected and could be read out during login. And than look at admins whose passwords would be read out and anybody could mess around as they please.... --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 13:40, 29 July 2014 (UTC)
| |
|
| |
| :::: Thanks for the responses, at minimum, can it be redirected if anyone happens upon it? I would rather it didn't just fail. ~~ [[MarkDilley]]
| |
|
| |
| I presume you mean can anyone else 'hijack' or steal <code>https://WikiIndex.org</code>? The answer to that is NO. "WikiIndex.org" is the domain name, and that is the important bit – providing the domain name registration doesn't expire (and I get the feeling from Ray's other interests, that is likely to be zero), you can't let anyone else take the domain name over. Furthermore, the "WikiIndex.org" domain can be configured in a number of related ways – in addition to our current "www.WikiIndex.org", you can also have "m.WikiIndex.org" (typically for mobile-configured displays), "ftp.WikiIndex.org" (file transfer protocol), and I'm sure I've missed a couple of others.
| |
|
| |
| The "http" vs "https" can be applied to any of the above – but the "https" means in laymans terms a 'secure' communication method. In order to have an "https" site, you need an 'SSL' (secure socket layer) certificate (often regulated by the likes of VeriSign, Comodo, and many others). The secure "https" is typically used on internet trading sites (which take payment via Visa, MasterCard, Amex, PayPal, etc), banking, insurance and other commerce sites. As [[User:Manorainjan|Manorainjan]] states above, there is no real need to have a secure connection on a wiki. If a password is compromised (which is honestly very doubtful), simply reset your password! [[User:Hoof Hearted|Sean, aka <small>Hoof Hearted</small>]] • <sub>[[:Category:Active administrators of this wiki|Admin]] / [[WikiIndex:Bureaucrats|'Crat]]</sub> • <small>[[User talk:Hoof Hearted|talk2HH]]</small> 21:52, 30 July 2014 (UTC)
| |
| :'''Security on a wiki''' While wikis generally aren't as privacy-centered as (e.g.) banking, there are definitely times when added security is important. If a dissident journalist were dumping documents to [[Wikileaks]] (which is no longer a wiki) or [[Wikinews]], he would certainly want greater security. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 23:17, 30 July 2014 (UTC)
| |
|
| |
| :: I did not mean to say that there is no need for a secure connection on a Wiki. I mean, "it looks like" there would be no need. But actually there is a need, because many people do logins. And every login procedure wherever should be secured. German end English Wikipedia connect via https by default. Wherever there is a SPAM or vandalism risk, there You need to have security as well to counteract it. Here and there I was reading about SPAMers, imposters and the like also here on WikiIndex. You need to have secure login at least for admins. And when the capability is installed, there is no reason whatsoever not to make it available for all. --[[User:Manorainjan|Manorainjan]] ([[User talk:Manorainjan|talk]]) 00:05, 31 July 2014 (UTC)
| |
| :::'''Agreed''' If you login, make it secure. [[User:Koavf|Koavf]] ([[User talk:Koavf|talk]]) 00:08, 31 July 2014 (UTC)
| |
|
| |
|
| ==== 24 February 2014 Domain Name ==== | | ==== 24 February 2014 Domain Name ==== |