Time |
Nickname |
Message |
00:00
🔗
|
ranma |
can webpages be coded in a way that the archive.org capture of it isn't what renders when you visit it at a later time? |
00:00
🔗
|
ranma |
for example, A Major Cellular Carrier advertised a shiny new feature |
00:01
🔗
|
ranma |
and i'm pretty sure archive.org captured the page around the time said feature was mentioned |
00:02
🔗
|
ranma |
but i visit the time/date website capture around the time of the new feature being advertised, and it no longer shows up |
00:13
🔗
|
|
kyan has quit IRC (Remote host closed the connection) |
00:39
🔗
|
xmc |
probably |
00:39
🔗
|
xmc |
but i doubt they would do that explicitly? |
00:39
🔗
|
xmc |
look at the source code for it |
01:01
🔗
|
Frogging |
I want to say that certain uses of Javascript could cause that but I'd be guessing |
01:03
🔗
|
yipdw |
ranma: what is the Shiny New Feature |
01:03
🔗
|
yipdw |
simplest explanation is that the date isn't close enough to the date of introduction |
01:19
🔗
|
|
jbenet___ has joined #internetarchive |
01:22
🔗
|
DFJustin |
could be geography, if the feature was only offered to IPs in certain areas |
01:56
🔗
|
|
Coderjoe_ has joined #internetarchive |
01:57
🔗
|
|
Coderjoe has quit IRC (Read error: Operation timed out) |
01:58
🔗
|
|
Coderjoe_ has quit IRC (Read error: Connection reset by peer) |
02:15
🔗
|
|
Coderjoe has joined #internetarchive |
02:24
🔗
|
|
jbenet___ has quit IRC (Connection closed) |
02:40
🔗
|
|
jbenet___ has joined #internetarchive |
05:36
🔗
|
|
Ctrl-S___ has quit IRC (Ping timeout: 260 seconds) |
05:41
🔗
|
|
matieu has quit IRC (Read error: Connection reset by peer) |
05:55
🔗
|
|
matieu has joined #internetarchive |
07:43
🔗
|
|
Stiletto has quit IRC (Ping timeout: 260 seconds) |
11:29
🔗
|
|
Stiletto has joined #internetarchive |
16:58
🔗
|
|
Stilett0 has joined #internetarchive |
17:02
🔗
|
|
Stiletto has quit IRC (Ping timeout: 244 seconds) |
20:18
🔗
|
|
Stilett0 has quit IRC (Read error: Operation timed out) |