Recent searches

No recent searches

Search options

Only available when logged in.
eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Administered by:

Server stats:

209
active users

eupolicy.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#c4l24

0 posts0 participants0 posts today
Mike Giarlo<p>Dear <a href="https://code4lib.social/tags/library" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>library</span></a> technology community, we need to talk about @OCLC. <a href="https://code4lib.social/tags/libraries" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>libraries</span></a> <a href="https://code4lib.social/tags/code4lib" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>code4lib</span></a> <a href="https://code4lib.social/tags/c4l24" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>c4l24</span></a></p>
Ed Summers<p>This talk by Christina Cutler at <a href="https://social.coop/tags/c4l24" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>c4l24</span></a> was pretty great about the accessibility of PDFs, and the importance of allowing supplementary files to be submitted to institutional repositories and preprint servers:</p><p><a href="https://www.youtube.com/live/B0fG0j949GM?feature=shared&amp;t=7442" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/live/B0fG0j949GM?f</span><span class="invisible">eature=shared&amp;t=7442</span></a></p><p>I learned that arXiv (sorta) recently started generating HTML views of TeX &amp; LaTeX in order to improve accessibility over PDF: <a href="https://info.arxiv.org/about/accessible_HTML.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">info.arxiv.org/about/accessibl</span><span class="invisible">e_HTML.html</span></a></p>
anelki<p>I will say, and I'm sure this will come up at <a href="https://tilde.zone/tags/LPF24" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LPF24</span></a> tomorrow and Thursday:</p><p>for all we talk about "open infrastructure," many libraries are adopting tools/platforms that on the technical side are over-engineered, require substantial computing power, and often, considerable attention from people with technical expertise.</p><p>To say nothing of the fact that to load a single page, you are asking your users (who aren't using the latest MacBook Pros on 1+ gbit connections like many developers or first-world librarians, especially in the US/Canada) to load tons of webfonts and JavaScript, asking them to do all sorts of stuff in order to access an ostensibly open textbook.</p><p>The result of the first part is that our 'open' infrastructure becomes highly centralized, we surrender privacy protections that we (hopefully!!) have for things we host/manage ourselves, and we risk locking ourselves into a vendor/client relationship. Just like with Elsevier/Springer/et al. And lol, what happens in 5-6 years when you can't afford whatever they're charging? Or when the company that you pay for hosting realizes that maintaining this complicated code monster isn't worth the effort?</p><p>The result of the second part is that we make it actively harder for people who aren't at ARL Libraries, who don't have lots of resources, who have a hard time accessing sites because the only internet connection outside of campus is their phone?</p><p>Compare this to something like <span class="h-card" translate="no"><a href="https://mastodon.social/@PublicKnowledgeProject" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>PublicKnowledgeProject</span></a></span>'s Open Journal System which is a drastically simpler application based on 20+ year old technology that is rock solid.* That is easy to maintain. That is easy to understand. That is secure. Serving pages that are lightweight and easily accessible. </p><p>Not based on the popular programming language of the week. Not based on whatever the latest trend is. </p><p>Built on technology that very simply: <strong>JUST WORKS.</strong> </p><p>...and yes, we can make it have a slide carousel on the front page. </p><p>*technical: it's a (BSD/Linux/Mac/Windows)/Apache/MariaDB/PHP stack</p><p><a href="https://tilde.zone/tags/PKPSprint" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PKPSprint</span></a> <a href="https://tilde.zone/tags/LPF24" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LPF24</span></a> <a href="https://tilde.zone/tags/C4L24" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C4L24</span></a></p>
robincamille<p>I'm at Code4Lib 2024 in Ann Arbor on an incredibly beautiful day! I'm so excited for a week of nerding out with fellow library technologists. </p><p><a href="https://code4lib.social/tags/code4lib" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>code4lib</span></a> <a href="https://code4lib.social/tags/C4L24" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>C4L24</span></a></p>
TrendingLive feeds
About