
Want to know how much website downtime costs, and the impact it can have on your business?
Find out everything you need to know in our new uptime monitoring whitepaper 2021



Researchers at the Fraunhofer Institute in Germany have come up with a novel way of fighting eBook piracy with a trick that pays homage to more old-fashioned techniques for protecting copyright works.
The project “Secure Documents by Individual Marking”, or SiDim, is a type of digital rights management (“DRM”) which takes the original eBook and slightly alters the text for each copy of the book sold, so that each copy is ever so slightly different – and unique.
The project which has secured back from the German government, as well as the media and publishing industry, doesn’t use technical measures to try and block copies being reproduced. Instead because each book is unique with its own fingerprint or DNA, should that book later turn up on a file-sharing site for example, the copyright owner can immediately tell who the book, which is being shared, was sold to. The theory is that people will simply not upload and share their books for fear of being caught.
SiDim will change words within the book – for instance it may change the word “little” for “small” or “not visible” to “invisible”, perhaps the punctuation may be slightly changed or the grammar and construction of the sentence altered.
How authors will in practice react to this remains to be seen. For some authors even subtly changing the words, punctuation or construction of sentences could be a step too far. Even if it doesn’t dramatically change the book, they may feel that this is altering their artistic work.
Researchers, keenly aware that attempting to stop copying by technological means simply becomes an arms race, have realised that the better approach is simply to allow copying, but make it clear that if you do copy without permission you’re likely to get caught.
These copyright-traps, or copyright Easter-Eggs, are similar to those often used by cartographers to “trap” anyone who copies their map. A “trap-street” for example is a made-up street name, which does not exist – or perhaps is depicted on the map differently to how it should be, so that if the map is copied by a third party its immediately obvious where it’s been copied from.
There are many examples of copyright Easter-Eggs including on Google Maps – just one example being Moat Lane, Finchley, London N3 in the UK which does not actually exist. These are not confined to maps though – dictionary compilers also use them. The New Oxford American Dictionary — includes an entry for the fictitious word “esquivalence.”
So do these copyright traps work? Absolutely, the use of “esquivalience” – which fittingly was said to mean “the wilful avoidance of one’s official responsibilities” was enough to entrap Dictionary.com.
Main Image – The “town” of Argelton appears in the middle of a field in Lancashire, UK on Google Maps but does not exist. The clue is in the name – “Not Real G”
Share this

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
4 min read How AI Is Shifting Software Engineering’s Primary Constraint For most of the history of software engineering, the primary constraint was production. Code was expensive, skilled engineers were scarce, and shipping features required concentrated human effort. Velocity was limited by how fast people could reason, implement, test, and deploy. That constraint shaped everything from team size,
5 min read Autonomous Code, Trust Boundaries, and Why Governance Now Matters More Than Ever In Part 1, we looked at how AI has reduced the cost of building monitoring tools. Then in Part 2, we explored the operational and economic burden of owning them. Now we need to talk about something deeper. Because the real shift isn’t
Find out everything you need to know in our new uptime monitoring whitepaper 2021