mathstodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance for maths people. We have LaTeX rendering in the web interface!

Server stats:

2.8K
active users

#4d

2 posts2 participants0 posts today

#ScreenshotSaturday #WIP new biome(?) - yellow/green/cyan slime marshes

Movement between yellow & cyan slime, or green & non-slime is not allowed(ðis also applies to your inventory because of course it does 𓅱)

Also you can't technicly see cyan/yellow by default, just r/g/b, but even if you don't have any lenses you can red/blue-shift your vision by soaking in ðe right slime😳𓅱

Das Projekt #4D – 4 Dimensions of Digital and Didactic Development stärkt das digitale Lehren und Lernen an der Universität Freiburg auf mehreren Ebenen. Seit 2021 widmen sich Teilprojekte verschiedenen Aspekten der Lehre – von der Weiterentwicklung der Lernplattform #ILIAS über #Qualifizierungsangebote für Studierende und Lehrende bis hin zu frei zugänglichen Lehr-Lern-Ressourcen.

Gefördert wird das Projekt bis Ende 2025 von der Stiftung Innovation in der Hochschullehre.

Die #Digitalisierungsstrategie der #UniFreiburg definiert vier zentrale Dimensionen der #Lehrentwicklung, die im Projektnamen verankert sind: Studierende, Lehrende, Organisation und gesellschaftlicher Kontext. Damit umfasst das Projekt eine breite Palette an Einsatzbereichen und Zielgruppen. Oder, wie Projektkoordinator Dr. Christian Kny es ausdrückt: „Die meisten, die an der Universität Freiburg arbeiten, profitieren von den Ergebnissen – oft ohne es zu merken.“
uni-freiburg.de/digitale-trans

Hoy es #28F, el día en las andaluzas y los andaluces conmemoramos el referéndum con el que accedimos a la autonomía. Pero para muchas personas, entre las que me incluyo, el verdadero Día Nacional de Andalucía es el 4 de Diciembre.

En aquella fecha de 1977 dos millones de personas salieron a las calles de las ocho capitales de Andalucía para reclamar nuestros derechos como pueblo. Sin #4D ni hay 28F ni se entiende el actual modelo autonómico español.

En cualquier caso ¡Viva Andalucía Libre! 😊

Continued thread

(26/N)

3. Actively maintain your devices

1] Package managers are no longer the only source of software for systems. Look into a one-stop upgrading tool like Topgrade that takes care of this, and also handles, e.g., updates of #Flatpak applications.

2] Use unattended / automatic upgrades on #Linux distributions that have a non-rolling release model. Restrict them to security upgrades, only: You want your devices to stay secure, but reduce the risk of things breaking while you are not available for resolving any issues. @fedora has listed the pros and cons of unattended upgrades.

You can find helpful howtos on the web for many distros:
Debian, Fedora, Linux Mint, openSUSE, Ubuntu, …

If you can’t find one, as a last resort, look up the parent distribution of yours and continue your search there.

3] Finally, collect notes how you resolved maintenance issues. Include research results, like helpful links. Copy & paste the history of terminal commands used in the process. Integrate these into your regular note-taking system. Don’t lose the knowledge you have acquired.

Start of this thread:
mastodon.de/@tuxwise/113503228

GitHubGitHub - topgrade-rs/topgrade: Upgrade all the thingsUpgrade all the things. Contribute to topgrade-rs/topgrade development by creating an account on GitHub.
Continued thread

(25/N)

2. Bootstrap your workplace

Remove all software packages that you haven't used, ever or since a long time. Whenever you (re)install #Linux on a device, pick the most minimal version of the installer (usually the smallest download for your processor architecture, sometimes still a CD .iso image).

(Re)add only what you need, and when you need it: Wait for it, don't speculate. Our #WFH / #office-centric list of recommended software:

tuxwise.net/recommended-softwa

Start of this thread:
mastodon.de/@tuxwise/113503228

tuxwiseRecommended software - tuxwiseRecommended software - If you could recommend one, and only one software for this job, what would it be? Deliberately one option, only.
Continued thread

(24/N) There are some best practices that will make it easier to answer threat modeling question #3, "What are you going to do about it?". These will help you protect a wide range of assets by taking care of your devices, so let's look at them first:

  1. Encrypt data at rest
  2. Bootstrap your workplace
  3. Actively maintain your devices
  4. Secure your devices
  5. Prepare for repair

1. Encrypt data at rest

What can you achieve with intermediate knowledge, without fully descending into the rat hole?

⚠️ Caveat: this is best done when setting up #Linux on a new device. Modifying an existing installation on your own IMHO isn't advisable if you're not a seasoned user. If you still decide to venture into it, make SURE you have backed up all your assets, before following "howtos on the internet". You have been warned.

Likening your device to a medieval city:

1) Full-Disk Encryption (FDE) is like locking the "city gate". Most popular Linux distributions offer FDE during the installation process. FDE is also your last line of defense when your device gets stolen, or your disk fails and cannot be safely wiped before disposing of it. Use FDE. (Yes, technically, "Full" is not absolutely accurate. We'll leave it at that.)

2) Within your "city", there will likely be at least two "houses": the home of the admin account, and your personal home. Using FDE alone, the "doors" of these homes won't have any locks of their own. Possibly not a big deal with respect to the administrative account, but admins being able to access any of your non-public assets, even when you're not logged in, is probably not what you want.

While the specific steps depend on your preferred Linux distro, a "portable" solution is to create a separate, encrypted disk partition, and have it mounted as your user home directory, when you log in. That solution is based on cryptsetup and the pam_mount module, a nice tutorial example is:

3) Within your "house", you may wish to have a locked "chest", e.g. for your #FYEO assets. There's essentially two options: a) a single, encrypted container file that acts as a "#vault" for your asset files; or b) an encrypted overlay file system that maintains an openly visible directory hosting your encrypted assets, including directory structures, in the background; and allows you to mount a decrypted counterpart, for working on your assets.

a) A "vault", being a single file, is easy to copy and carry around, on arbitrary storage media, e.g. USB sticks. It doesn't reveal too much about its contents, but resizing it takes a little effort. Also, you can't "incrementally backup" content changes, just copy the whole, changed vault.

A nice tutorial for creating and using a vault using plain, standard cryptsetup is opensource.com/article/21/4/li by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt mhogomchungu.github.io/zuluCry – IMHO the app is still in need of a little polish, though.

b) An encrypted overlay file system allows for incrementally backing up changed assets, but exposes considerable metadata (rough file sizes, directory structures, modification dates).

The most widely used package for this is probably #gocryptfs. Its "HowTo" is literally a one-pager: nuetzlich.net/gocryptfs/quicks

Start of this thread:
mastodon.de/@tuxwise/113503228

Cobertos · LUKS Encryption for my Linux Mint user directory • Cobertos BlogI just setup a new OS and decided I would put /home/cobertos on a separate partition and that I should full disk encrypt it. In my last Linux Mint install, I ...