Fwd: Yahoo to reuse email addresses - re: Identifier persistence

[Melvin Carvalho]

This is quite an interesting point.  Perhaps webfinger records could have a created date field...

---------- Forwarded message ----------
From: Tim Berners-Lee <ti...@w3.org>
Date: 20 June 2013 23:53
Subject: Yahoo to reuse email addresses - re: Identifier persistence
To: TAG List <www...@w3.org>


As email addresses become increasingly the grounding point for identity
on the net, interesting to ask whether we should be expecting some
standards of persistence ...  or should we be always quoting them with a date?

Timbl


> """Yahoo tells security critics to chillax regarding its email recycling program
>
> So much for trying to be nice. Yahoo’s latest bid to lift itself from the tech also-ran swamp with an email recycling initiative has been criticized for potential security threats to dormant users. To try and calm down the pitchfork-wielding crowd, the company has released a statement describing various security measures that will be taken to insure past users’ data and security—but they may not cover all the bases."""
>
> http://www.techhive.com/article/2042508/yahoo-tells-security-critics-to-chillax-regarding-its-email-recycling-program.html

[Melvin Carvalho]

On 21 June 2013 04:07, Peter Saint-Andre <stp...@stpeter.im> wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Yes, interesting.

But wouldn't the same be true of, say, HTTP URIs or any other URIs?

Yes, absolutely!

Tim wrote a note about this called "Cool URIs dont change"

http://www.w3.org/Provider/Style/URI

"The creation date of the document - the date the URI is issued - is one thing which will not change. It is very useful for separating requests which use a new system from those which use an old system. That is one thing with which it is good to start a URI. If a document is in any way dated, even though it will be of interest for generations, then the date is a good starter."

Ideally URIs should remain persistent.  But sometimes they are not in practice, of course.

 

On 6/20/13 4:48 PM, Melvin Carvalho wrote:
> This is quite an interesting point.  Perhaps webfinger records
> could have a created date field...
>

> ---------- Forwarded message ---------- From: *Tim Berners-Lee*
> <ti...@w3.org <mailto:ti...@w3.org>> Date: 20 June 2013 23:53

> Subject: Yahoo to reuse email addresses - re: Identifier

> persistence To: TAG List <www...@w3.org <mailto:www...@w3.org>>

>
>
> As email addresses become increasingly the grounding point for
> identity on the net, interesting to ask whether we should be
> expecting some standards of persistence ...  or should we be always
> quoting them with a date?
>
> Timbl
>
>
>> """Yahoo tells security critics to chillax regarding its email
> recycling program
>>
>> So much for trying to be nice. Yahoo’s latest bid to lift itself
>> from
> the tech also-ran swamp with an email recycling initiative has
> been criticized for potential security threats to dormant users. To
> try and calm down the pitchfork-wielding crowd, the company has
> released a statement describing various security measures that will
> be taken to insure past users’ data and security—but they may not
> cover all the bases."""
>>
>>
> http://www.techhive.com/article/2042508/yahoo-tells-security-critics-to-chillax-regarding-its-email-recycling-program.html
>

>  --
>
> --- You received this message because you are subscribed to the
> Google Groups "WebFinger" group. To unsubscribe from this group and
> stop receiving emails from it, send an email to
> webfinger+...@googlegroups.com. For more options, visit
> https://groups.google.com/groups/opt_out.
>
>


- --
Peter Saint-Andre
https://stpeter.im/


-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJRw7VuAAoJEOoGpJErxa2pBXEP/0ImE5zDUFRNEaXoLdbTlkaC
XSBtZs8D9AxSEif5Shde8kyieQqNniOW69qqkRR7xT50GUIn1vrBHPCXaB+3eG/3
hKl3sh7ddzjA8FQL36j6Nq+no6Ilg7nZ5RswRIIA95Nu3kUFR/Axy5wztb1wsAYq
gJUVddHPZw3m5IGwtN7vITBWCyfDI4+dZ6o1bawi7wBKAJKvDo332twqWdOWUe7O
7eN6S49egrRKSKYHCUkqd9YSAqBqj+IyjfYM2b29JK6GPx1NYoOhlzfHNzCrKeyo
MxYbAl/cO3MBK7lidMChnJDF02tP9wB5OgdVc5UUhIjJBXNqHx20n5blvcj8g1b6
fccnxYyPx28mzotUh0Sg/Tv0JPBfvhd8zhEKYfqVsk0gbvnxLhry7LH+uAmhsVP+
gerPxMLHQBi7qcmsGciBMVMdROViZtzxs4rEadZk3blfWSQNeuUruugIwl1Pel8c
IXI2nljPbJtcgEFaS3m6sw4+QtFXe+8wXiS3buG65Lhq7/h/tCoPFTpJMEKsycVl
POR5WAZvm2tIuUaBQnDfveiubAKsJywzW+/AunkwVknKL6i+vEvWklrv/eRql60B
bECq1KS0ElMsI0A2aJ4RDnvhHfA85oWbvMWX21bPgXeX9bHtTI6fEgjrJ8YFQyeM
3VhiHBzRVzU7PL/uOGVF
=lHmq
-----END PGP SIGNATURE-----

[Paul E. Jones]

Melvin,

 

Records had them in early drafts (the “expires” field), but that was removed since HTTP has headers that serve the same purpose.

 

Paul

 

--