Talk:Nesdev Wiki/current: Difference between revisions

From NESdev Wiki
Jump to navigationJump to search
(→‎Anonymous editing: All these IPs are in the same /30 as the webserver.)
Line 16: Line 16:
::And through 4G LTE on a cellphone. Why do I have the same IP address each time? Reverse proxy much? --[[Special:Contributions/69.20.131.234|69.20.131.234]] 17:30, 10 November 2016 (MST)
::And through 4G LTE on a cellphone. Why do I have the same IP address each time? Reverse proxy much? --[[Special:Contributions/69.20.131.234|69.20.131.234]] 17:30, 10 November 2016 (MST)
:::That must be it. This plus an edit from work are all in the same /30 as the result of <code>nslookup wiki.nesdev.org</code>. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 17:32, 10 November 2016 (MST)
:::That must be it. This plus an edit from work are all in the same /30 as the result of <code>nslookup wiki.nesdev.org</code>. --[[User:Tepples|Tepples]] ([[User talk:Tepples|talk]]) 17:32, 10 November 2016 (MST)
== Protocol relative linking? ==
Noticed this edit by lidnariq: [//wiki.nesdev.org/w/index.php?title=GTROM&curid=1857&diff=16180&oldid=16179 diff]
I understand the value of using "protocol relative" links to the forum, which omit the http: or https: prefix, so that the user's choice remains continuous (though it's more of a roulette situation coming here from the forums). However, I don't understand why we'd want to do this for links to anywhere else. Shouldn't we just link to whichever the "default" form of link is for the external site? AFAIK most websites with https don't really want users to use http anyway? NESDev seems like a very unusual case for treating them as interchangeable. - [[User:Rainwarrior|Rainwarrior]] ([[User talk:Rainwarrior|talk]]) 13:19, 19 January 2019 (MST)

Revision as of 20:19, 19 January 2019

Layout test pages

If you have any example of layout for the wiki that you would like to share, please make a link to your examples here.

Would be nice if the http://nesdev.org/ main page made it clearer that all the up-to-date stuff is on the wiki. It's just two links and fairly easy to miss. -Ulfalizer (talk) 09:32, 12 April 2013 (MDT)

Anonymous editing

Why are non-registered users allowed to edit talk pages ? Bregalad (talk) 09:23, 27 March 2014 (MDT)

As a means of reporting technical problems with registration to registered users, for one. Almost all automated vandalism gets reverted within twenty-four hours anyway. And because some drive-by edits have in fact been constructive. --Tepples (talk) 18:29, 27 March 2014 (MDT)
It also makes spambots less likely to skip immediately to the sign-up page. Instead, they try to post on whatever pages anonymous visitors can post on, where the ABUSE filter picks up on behavior patterns in the bot software. Looking at all the $#!+ that doesn't get through helps me figure out how to stop even those spambots that bother to register. --Tepples (talk) 19:54, 16 July 2014 (MDT)

I am editing through my router --69.20.131.234 17:24, 10 November 2016 (MST)

And through my neighbor's router on the same ISP --69.20.131.234 17:27, 10 November 2016 (MST)
And through 4G LTE on a cellphone. Why do I have the same IP address each time? Reverse proxy much? --69.20.131.234 17:30, 10 November 2016 (MST)
That must be it. This plus an edit from work are all in the same /30 as the result of nslookup wiki.nesdev.org. --Tepples (talk) 17:32, 10 November 2016 (MST)

Protocol relative linking?

Noticed this edit by lidnariq: diff

I understand the value of using "protocol relative" links to the forum, which omit the http: or https: prefix, so that the user's choice remains continuous (though it's more of a roulette situation coming here from the forums). However, I don't understand why we'd want to do this for links to anywhere else. Shouldn't we just link to whichever the "default" form of link is for the external site? AFAIK most websites with https don't really want users to use http anyway? NESDev seems like a very unusual case for treating them as interchangeable. - Rainwarrior (talk) 13:19, 19 January 2019 (MST)