Short and easy howto for generating #sourcecode documentation using doxygen to create nice HTML output.
Very useful!
Short and easy howto for generating #sourcecode documentation using doxygen to create nice HTML output.
Very useful!
How much is this "worth" (in money)?
(my) webservers (!) running without reboot for almost 10 years đ đĽł
/WITHOUT/ changing anything.
(only security patches)
Thanks to #Debian's #FOSS-developer best-practice of:
"**fixing a security problem is to make as few changes as possible**"
[quote src=https://www.debian.org/security/faq#oldversion]
And other distros building on top of each other, in collaboration.
I âĽď¸ *stable, professional #OpenSource tech*
#StableIT #Ubuntu #GNU #linux #security #dltp #longterm #bash
Watching the re-indexing of an archival catalog backup of AtoM, I realized:
Indices populated with 18751 documents in 164.84 seconds.
19k Objects?
Thats /nothing/ for a regular #bigDATA tech-tool. This is peanuts.
400.000 Objects?
Millions?! - According to documentation of #ApacheIceberg #ObjectStore #Redis #KeyDB, etc: **easy**
#DLTP & #GLAM: Storing and using those "objects" in key/value annotated filesystems with bigDATA tools:
**FUN!!**
I've mentioned it here already, but I think it's good to keep this way of data-handling/thinking on our radars:
https://datacentricmanifesto.org/
"We have uncovered a root cause of the messy state of Information Architecture in large institutions and on the web today.
It is the prevailing application-centric mindset that gives applications priority over data.
The remedy is to flip this on its head.
**Data is the center of the universe; applications are ephemeral.**"
Zlad: Elektronik Supersonik
What a great example for "lossy" archival master decisions:
My screenshot of the original web-publication was considered "HIGH-QUALITY LARGE MPEG" (9.4 MB)
Found out they've re-uploaded a better-lossy archival copy:
Enjoy:
https://www.youtube.com/watch?v=Re_1HrfOMZ4 𼳠đš đŞ
Getting into mirroring #Artefactual #AtoM between in-house catalog and on-line website, I found this:
https://github.com/artefactual-labs/ansible-atom-replication
"AtoM replication can be used to manage a 2-site AtoM deployment model - one public-facing read only site for public users, with content replicated from an internal read/write edit site for staff, which can be kept behind a firewall."
Proposed this lightning talk for #NoTimeToWait9:
-------------------------------
Long-Term LTO: Stable LTO for "generations"?
What if we could get out of the #LTO-Generations update-race?
[...]
In this short talk, I'll present on how we might actually be able to get proper "Long-Term LTO" support for certain LTO-generations.
-------------------------------
If this sounds interesting to you, let me know! đž đ˝
"Personal Knowledge Graphs: why, what, and where to?"
(Jul 4, 2021)
Ivo Velitchkov
Very interesting. It confirms my observations and research on #AHAlodeck:
It's time we allow ourselves to do-digital-data differently. #GLAM #DLTP #Archiving