Monitoring
Status Pages
Pricing
Self destructing messages are seemingly becoming all the rage at the moment – SnapChat with it’s self-destructing pics; Wickr with its self-destructing SMS, videos and PDFs and Efemr with its self-destructing tweets – to name just a few recent arrivals. And now email. Telecoms giant AT&T has had a patent published recently which paves the way for emails which have a short life and then self-destruct.
The patent explains a system whereby the sender can set rules on how the email can be viewed – for instance can it be forwarded on? If so, to whom? The email sender can also set a date and time after which the email becomes unreadable. And that all important self-destruct means you can remotely destroy a message you’ve sent. From a security point of view this is far preferable to the current alternative of recalling an email – an exercise which often fails even if the person you’ve sent the email to hasn’t even yet read the email.
AT&T’s email system won’t work with all email. The person you’re sending the email to would also have to have the right AT&T software installed as well.
The system is unlikely to be adopted widely for day-to-day sending of personal emails, but in business where there is a need to have full control over sensitive data, having full control over where emails are sent (and being notified when emails are treated outside rules) is hugely important.
However as ever there’s an Achilles heel to this product. A good old fashioned screen-grab would still work. With this in mind perhaps the danger is that AT&T’s system could give businesses a false sense of security.
James Barnes, StatusCake.com
Share this
7 min read A website may be standing and still be in trouble. It may answer a request, return a cheerful 200 OK, and yet load slowly enough that visitors begin to lose patience. Its certificate may be nearing expiry. Its domain records may have changed. A server may be filling its disk in the background, patient and
6 min read StatusCake tells you that something might be broken. Hermes can check whether it really looks broken, decide who should hear about it, send the email, and keep the record for tomorrow morning’s summary.
3 min read The allure of OpenClaw is undeniable. You deploy a highly autonomous, self-hosted AI agent, give it access to your repositories and inboxes, and watch it reason through complex workflows while you sleep. It is the dream of the ultimate 10x developer tool realized. But as any veteran DevOps engineer will tell you: running an LLM-backed
7 min read There are cloud outages, and then there are us-east-1 outages. That distinction matters because failures in AWS’s Northern Virginia region rarely feel like ordinary regional incidents. They tend instead to expose something larger and more uncomfortable: too much of the modern internet still behaves as though one place is an acceptable concentration point for infrastructure,
7 min read Artificial intelligence is making software easier to produce. That much is already obvious. Code that once took hours to scaffold can now be drafted in minutes. Boilerplate, integration logic, tests, refactors and small internal tools can be generated with startling speed. In some cases, even substantial pieces of implementation can be assembled quickly enough to
10 min read Whilst AI has compressed the visible stages of software delivery; requirements, validation, review and release discipline have not disappeared. They have been pushed into automation, runtime and governance. The real risk is not that the lifecycle is dead, but that organisations start acting as if accountability died with it. There is a now-familiar story about
Find out everything you need to know in our new uptime monitoring whitepaper 2021
