Jonas Smedegaard

As I understand it, the intention is for the pacage to automatically load needed other packages, so seems there is a bug here. A workaround is to manually load `hyperref`...

Another workaround is to avoid use of hyperxmp (read the documentation for details on when that might be suitable), like this: ```LaTeX \documentclass[english]{article} \usepackage[ type={CC}, modifier={by}, version={4.0}, hyperxmp=false, ]{doclicense} \begin{document}...

Thanks for the confirmation - I'll simply skip that test, then. By the way, in case you care: I am packaging this crate officially for Debian - [Develpers' dashboard](https://tracker.debian.org/pkg/rust-fast-srgb8) and...

I sure will

> The log says i686-unknown-linux-gnu tho, which should have SSE2 on everywhere Debian architecture `i386` [does *not* include `SSE2](https://wiki.debian.org/ArchitectureSpecificsMemo#i386-1). > If you know, did this test fail on more targets...

CRDTs are certainly exciting - and Rust implementations of YJS is emerging, which looks promising (but I have only glanced - not sure how reliable it is for production yet)...

Let me try elaborate what it really is that I propose, as I realize that it might not at all be obvious from my terse post above. You consider using...

What makes sense to me is to distinguish multiple kinds of remote data handling: * `referenced` - exists only externally (maybe *cached* locally for speed but by definition a cache...

I disagree: I think only a cloned resource should be renamed and tracked as a separate issue - a resource that is mirrored is still the same, including subject. I.e....

I imagine the Atomic Server would only cache at first, and if at a later refresh of the cache the resource had gone then flag it as needing action. One...