1,249 karma · joined October 14, 2019
> When registering a new publication and its references at Crossref, a publisher may sneak extra undue references in the metadata sent in addition to the ones originally present. Then, digital libraries (e.g., SpringerLink) and bibliometric platforms (e.g., Dimensions) harvest these metadata, undue citations included. These sneaked references are processed and counted even if they are not present in the original publication.
The three journals in this particular case are all published by Technoscience Academy, an OA publisher operating out of India (not one of the well-known ones). I would think twice as an author before I submitted to any journal from this publisher, lest my paper is abused for manipulations like this (although I'm not sure if it has any journals worth submitting to anyway).
NB (because I got confused first): This is not really about Hindawi. Hindawi published the (trash) article that these fake citations were pumping up, but the pumping-up happened using Technoscience Academy journals.
An exchange program with Manchester, though? That must have been late in the 80s?
- large academic population and high general education
- a tradition of collecting banned and bootlegged content, particularly Western (samizdat, magnitizdat)
- lack of resources to get things legally (e.g. university subscriptions)
- a culture of hacking and tinkering (the best known book scanning middleware, like ScanTailor and ScanKromsator and various djvu tools, comes from Russian hobbyist programmers).
Also applies to adjacent countries like Ukraine.
We could go that way, but it would be a serious change of rules and create its own perverse incentives.
The best example is perhaps the polynomial ring R[x][y], which consists of polynomials in the variable y over the ring of polynomials in the variable x over the real numbers. Any algebraist would tell you that it is obviously just the two-variable polynomial ring R[x, y] in disguise, because you can factor out all the y-powers and then the coefficients will be polynomials in x. But the rings are very much not the same at the level of implementation, and every time you use their "equality" (canonical isomorphy), you need to keep the actual conversion map (the isomorphism) in the back of your mind.
Stacks is not finished, however -- still a lot of "Proof. Omitted.". From what I understand, the goal is to fill them all in (otherwise there would be references to the literature in their stead), but ultimately it is still mostly a one-person project (see https://github.com/stacks/stacks-project/graphs/contributors ).
I once filled in one of those missing proofs, only to see Johan replace it by a much better one that I would never have thought of. And this was (for him) a technical lemma, not one of the crown jewels of the project. His dedication to the project is truly incomparable to anything except Bourbaki and Serre. And the usefulness of the work extends far beyond algebraic stacks, just like Bourbaki is much more than a textbook on Lie algebras.
> Marsalek's grandfather, [Hans Maršálek](https://en.wikipedia.org/wiki/Hans_Mar%C5%A1%C3%A1lek), was a member of the Austrian resistance and later a suspected spy for the Soviet Union.
And following the link to Hans Maršálek's page:
> He was long suspected of being a Soviet asset. Recently uncovered documents indicate that are grounds to believe he was responsible for helping the Soviets kidnap at least four people and illegally render them to Moscow for torture and interrogation.
While I am not surprised that a socialist persecuted under the Nazis would join Soviet efforts, this is some useful backstory in understanding why Marsalek the younger apparently had no reserves in collaborating with the KGB.
Ehm, this is not what happened. In 2006 Rhapsody became Rhapsody of Fire to avoid some trademark dispute. Then they split around 2009, though the main chunk is still called Rhapsody of Fire whereas the spinoff is called Luca Turilli's Rhapsody.
I have not been following the development of mathjax, pandoc, etc. carefully, so I'm wondering: Have the main issues been solved? By these I mean
(1) support for most popular packages,
(2) automatically breaking long outputs into small pages that don't overheat my laptop or crash my browser and yet reference each other properly,
(3) printability (without lines broken in half, senseless overflows and the likes) or cross-compilability with a regular PDF compiler?
I know the ar5iv project is getting closer and closer to (1) and (3), but is that available to regular users?