Lady @Lady@cat.family

@Satsuma i could understand it if it was like “the author got tired of spelling Avignon and wanted a slightly spicier heading”

@Satsuma okay nvm that is weird then

@Satsuma wait do you mean to say they are *exclusively* calling it the Babylonian Captivity?!

@Satsuma in my experience people who work regularly in given fields (the sort who might be writing textbooks) often get desensitized to the political nature of the terms they use, and such language usually only gets dropped after someone writes a scathing enough critique in a peer‐reviewed journal that enough of them read

maybe this is overly cynical of me

@Satsuma (my point here just being that it appears to be a metaphor with long historical precedent and it’s possible (?) they simply didn’t think too hard about it?)

@Satsuma per Wikipedia, « The period has been called the "Babylonian captivity" of the popes. When and where this term originated is uncertain although it may have sprung from Petrarch, who in a letter to a friend (1340–1353) written during his stay at Avignon, described Avignon of that time as the "Babylon of the west", referring to the worldly practices of the church hierarchy.[26] The nickname is polemical, in referring to the claim by critics that the prosperity of the church at that time was accompanied by a profound compromise of the papacy's spiritual integrity, especially in the alleged subordination of the powers of the Church to the ambitions of the French kings. As noted, the "captivity" of the popes at Avignon lasted about the same amount of time as the exile of the Jews in Babylon, making the analogy convenient and rhetorically potent. The Avignon papacy has been and is often today depicted as being totally dependent on the French kings, and sometimes as even being treacherous to its spiritual role and its heritage in Rome. »

@Satsuma i don’t think i’ve ever really seen someone take a stance in support of it

@Claire how are we defining “trending”?

got tired of not being able to just drop a link to e·g https://go.KIBI.family/Fortune/?/Tendencies/vividly_remembered_promises in chat

finally added permalinking to my ./Fortune/: https://github.com/marrus-sh/marrus-sh.github.io/commit/5404bf743ce2756cae57473a7f82c062318d08aa

chrome: what if we simply removed “View Source”?

me, designing webpages under the assumption that people interested in more information will attempt to view the underlying source:

when the meta tags give the canonical URL for the author 😌

this post explains better than i can the principles regarding the #GLAM-adjacent and Linked Data–related work i have done over the past few years, down to why i publish my webpages as RDF/XML+XSLT instead of using a static site generator

« We need to develop the practice of thinking about our tools as layers of components where those components that can be shared are simple enough for someone at a different instituion, someone who is just as busy and distracted as you are, to quickly understand what something does or doesn't do.

The emphasis here is on quickly because the reality is that other people will be looking at whatever you've shared over lunch or on the train going home. The emphasis needs to be on quickly because the ultimate goal is to have something that can be understood with sufficient ease that it can be filed away to be remembered at some later date when there is a need to address a specific problem. If the goal is to build a common kit of parts that can be re-used across the cultural heritage sector the first step is to make awareness of those tools, and their conceptual boundaries, a practical and tangible reality. »

« Everything I've described so far has been built using the same raw materials that we've made available for you to do something with. This introduces a non-zero cost in the build process for the public-facing museum efforts but we believe it's worth the cost.

First of all we want other people to build new interfaces and new services, new "experiences" even, on top of our collection so this is a way to keep ourselves honest. If we can't build something with this stuff why should we imagine you will?

Second, we want to ensure that the data we release and the manner in which it is published, is actually robust and flexible enough to engender a variety of interfaces and uses because we need that variety. It is important to the museum because I don't believe there is, or should be, only one master narrative in to the collection. »

« I am not suggesting that we return to the web of the mid-1990s with its grey backgrounds and blue and purple links. I am suggesting however that we ensure that web is our guaranteed failure scenario, should it ever be necessary, and that we layer everything on top of it.

This is as much about safe-guarding against other people's browser decisions as it is giving the cultural heritage sector the freedom to engage with the walled gardens of platform vendors, without that participation turning in to a black hole from which it is impossible to escape. »