Sorry about "Yet Another Vulnerability Patch" hiccup. We are now running 2.5.2 github.com/tootsuite/mastodon/

Sorry about that hiccup. Needed to update our instance to 2.5.1 which fixes a vulnerability problem. github.com/tootsuite/mastodon/

sorry for that hiccup but we are now running Mastodon 2.5.0

kayiwa boosted

I was trying to access a particular website in the wayback machine, but it looks like it's completely broken because it's React-based and some of the key JavaScript wasn't archived. As a result, the site doesn't load at all - it's an entirely blank page.

Starting to worry about how many pages are going to end up like this. JS-free fallbacks aren't just about people who turn JS off in their browsers!

kayiwa boosted
kayiwa boosted

Ha, it's funny when white people assume Black folks can't speak another language.

Yeah, I see you.

kayiwa boosted

Well, here's my Mastodon timeline, inside Emacs, on a DEC VT420.

The latest update was done during non-maintenance hours 0700 - 0800 (Eastern) because of the critical vulnerabilities.

kayiwa boosted

my inaugural post may as well be a job: Digital Initiatives Projects Librarian careers.ualberta.ca/Competitio

We had a temporary service interruption to upgrade this instance to 2.4.4.

keybase.io/kayiwa
BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkMAxdLK jxOeJPWkZAK7x6C i45mW8uoVYgq3Dx 4Vg84Btyj3QRkjb avwQHqQRihANnEq sEkMr50Qy19drqO k1Uj8l35hNkPyMW zu8TL7jtbinDhu3 fy9LRI5zOmmYfDs IYOMvglkSMzvP66 5iKLpqh2OsqmAwL OHdeUNVQGFljinV ldnQOJngfQDDznO 1RnRZE0YJOA9I4E lLZ3ovADQIaEEXH TC. END KEYBASE SALTPACK SIGNED MESSAGE.

Sadly, word is out and spammers are creating accounts. I've disabled open/free registration. Will spend time trying to find a way (pointers welcome) make people prove the are humans. (that sounds weird.)

kayiwa boosted

Mastodon is an open source decentralised alternative to Twitter! I've made a Mapstodon #OpenStreetMap instance!
#sotm

The following local accounts have been reported as spam/bots and disabled @tsumaida @borikin and @neruhon until I hear from them. I'm easy to find on the interwebs

kayiwa boosted

4. When possible, archivists should apply traditional archival practices such as appraisal, collection development, and donor relations to social media and web materials. It is hard work adapting these concepts to the collection of social media content, but they matter now, more than ever.

kayiwa boosted

3. Archivists should follow social media platforms’ terms of service only where they are congruent with the values of the communities they are attempting to document. What is legal is not always ethical, and what is ethical is not always legal. Context, agency and (again) positionality matter.

kayiwa boosted

2. Documentation efforts must go beyond what can be collected without permission from the web and social media. Social media collected with the consent of content creators can form a part of richer documentation efforts that include the collection of oral histories, photographs, correspondence, and more. Simply telling the story of what happens in social media is not enough, but it can be a beginning.

kayiwa boosted

1. Archivists must engage and work with the communities they wish to document on the web. Archives are often powerful institutions. Attention to the positionality of the archive vis-à-vis content creators, particularly in the case of protest, is a prime consideration that can guide efforts at preservation and access.

kayiwa boosted

The Documenting the Now project (which I've been lucky to be a part of) published its ethics white paper today about archiving social media in times of protest.

news.docnow.io/documenting-the

The findings in short are:

kayiwa boosted

wallabag - an open source alternative to Pocket, Readability, Instapaper or Pinboard for saving web articles #wallabag wallabag.org

Show more
code4lib.social

code4lib.social is one server in the network