Jump to content

Talk:0.0.0.0

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia
This is an old revision of this page, as edited by 154.222.5.207 (talk) at 20:00, 19 June 2024 (20000). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

20000

Comments

Zero of 4294967295.

Note that much of this article is copied verbatim from this ServerFault answer. — Preceding unsigned comment added by 208.84.159.226 (talk) 21:46, 6 May 2015 (UTC)[reply]

Zero of 4294967295. — Preceding unsigned comment added by 68.184.30.29 (talk) 12:21, 12 March 2013 (UTC)[reply]

"0000:0000:0000:0000:0000:0000:0000:0000" listed at Redirects for discussion

An editor has asked for a discussion to address the redirect 0000:0000:0000:0000:0000:0000:0000:0000. Please participate in the redirect discussion if you wish to do so. NASCARfan0548  22:56, 28 April 2020 (UTC)[reply]

Ref RFC

@Dandorid: Please check your recent edit. There is a reference at the end of "A way to explicitly specify that the target is unavailable." For me, clicking the ref (currently [7]) does nothing. It should jump to and highlight ref 7. Johnuniq (talk) 08:23, 6 February 2024 (UTC)[reply]

@Dandorid and Johnuniq: The same problem occurs with references [4], [5] and [6] at Template:Ref RFC/doc, and, after some experimentation, references [1] and [2] at User:John of Reading/X3 (permalink), so this is a general problem, not a problem with the edit made to this article. -- John of Reading (talk) 09:18, 6 February 2024 (UTC)[reply]
Thanks for the detail. I assumed there was something off. Dandorid is also the creator of {{Ref RFC}} so they are the right person to debug. I hoped to avoid looking at it myself but had a quick peek and see that it requires a hand-built database of every used RFC, for example Template:Ref RFC/db/46. Yikes. Johnuniq (talk) 09:32, 6 February 2024 (UTC)[reply]
Yikes, maybe... I am happy to pursue an alternative if you have one. The {{Ref RFC}} template generates a <ref name='rfc9999'>...</ref> code, but when page numbers and/or quotes are requested the template reverts to an empty <ref>...</ref>, since multiple references to the same RFC have different content. Using option 'rp' instead of 'p' generates a {{Rp}} within the <ref>, but quotes cannot be taken out that way.
For now the issue is fixed by manually specifying <ref></ref> around a {{Ref RFC|ref=no}}. — DandoriD (talk) 12:33, 6 February 2024 (UTC)[reply]

Aisl001007

https://en.m.wikipedia.org/wiki/9.9.9.9 43.224.39.177 (talk) 14:05, 12 May 2024 (UTC)[reply]