The specified file temporary://file8QieVT could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
The specified file temporary://fileWOSK0p could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
The specified file temporary://fileeSFyfW could not be copied, because the destination directory is not properly configured. This may be caused by a problem with file or directory permissions. More information is available in the system log.
This is a bot which searches the Twitter public timeline for mentions of IPv6. Any URLs mentioned in those tweets whose hosts do not have an AAAA record (i.e. do not have IPv6 support) are clearly meant to be ironic, for why would anyone be commenting on IPv6 if they've not tried to deploy it yet? Your irony is @IPv6fail's invitation to jokingly lament the lack of support for a decade-old networking protocol by the content provider in question.
Here is how I routed myself a block of IPv6 to my laptop, wherever I am in the world! Note that I deliberately route myself an entire /64, but only allow a /128 through tinc (to reduce the amount of junk I might drown in). It should be relatively trivial to swap addresses if necessary in future.
The IPv6 Internet is not immune to breakage and so it seems prudent right now to ensure good connectivity to the big providers. Faelix takes IPv6 transit from TINet, but the possibility of a free 6-in-4 tunnel to Hurricane Electric as a backup path is too good to pass up.
