Recent searches
Search options
#4d
Diagonal 
section of ðe 4d cartesian product of 2 "I want to be a sea urchin and eat cabbage"(yes, really) tilings
kinda like ðis
Unfortunately we are still too dimensionally, perceptually, & probably intellectually challenged to even try to look at ðe full θing 
#ScreenshotSaturday you can now chop coagulated slime & use it to swap out colors or s p r e a d ð e s l i m e(or eat it if you really want to)
Also you can mine ðe rocks & make walls & some less horrible tools wiθ ðem
#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
𓅱
#screenshotsaturday storage walls 2.0 wiθ a whopping single inventory slot 𓅱
(ðere's a lot of space for giant warehouses of doom in 4d space 𓅱)
#4d cartesian product of 2 of ðese fancy pentagonal tilings + 
2dsections = 
#WIP multi-voxel gummy worms coming in multiple flavors which may or may not affect their stats/size 𓅱
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! 
Forschungsgruppe für #Digital Humanities @UniJena arbeitet im neuen Projekt „3DBigDataSpace“ daran mit, dass #3D-Inhalte in bereits bestehenden Datenpools digital aufbereitet und gespeichert werden können. #Digitalisierung #4D
https://nachrichten.idw-online.de/2025/02/19/das-europaeische-kulturerbe-digital-bewahren
#Funfact you can tile 4d space with ðe cartesian product of any 2 2d tilings(12.6.4 x 12.6.4 here),
Each resulting duoprism shape has a unique color(even if ðey can look like 2 difrnt polygons in ðese 2dsections)
#screenshotsaturday obligatory desert
biome except ðat it forms a smoð gradient wiθ ðe junglyier regions so maybe it will actually be equivalent to like at least 3 or 4 biomes?
Also ICE WALLS‽‽‽‽‽
(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:
https://mastodon.de/@tuxwise/113503228291818865
(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:
https://tuxwise.net/recommended-software/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865
#wip main menu / saving / loading / random seeds(& about too many random parameters
)
(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:
- Encrypt data at rest
- Bootstrap your workplace
- Actively maintain your devices
- Secure your devices
- 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 https://opensource.com/article/21/4/linux-encryption by @seth . If you must have a GUI for creating and mounting vaults, look at #zuluCrypt https://mhogomchungu.github.io/zuluCrypt/ – 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: https://nuetzlich.net/gocryptfs/quickstart/
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865
testing
lightning
traps/weather
& a convenient visual effect system(it can stack any number of ðem using ðe 5th dimension, time(...real time, not turn count, which would be ðe 6th dimension? ig?(if ur new here, yes, ðe game just casually has 4 spatial dimensions 𓅱)))
(23/N) Our fifth, and last, asset classification option:
Public
Assets accessible to, or controlled by, anybody who is aware of them. The existence of such assets is usually easily detectable, or even widely known. Note: "public" refers to potential access or control by the general public, regardless whether there is a legal basis for it.
Public makes a bad default class. Pick Intimate instead.
Start classifying assets
If you haven't done so yet, add a "Classification" column to your asset spreadsheet, and assign each asset to a specific class.
Pick "Intimate" as the default class. Assume that you will act according to the respective classifications, starting today, instead of pondering whether it's "too late", for certain assets.
Some classification suggestions that may look appropriate to you (or not):
For Your Eyes Only (FYEO): Diaries and journals? Private notes?
Intimate: Family photographs? Bank accounts? ToDo lists?
None Of Your Business (NOYB): Your smartphones, tablets, desktops? Medical records? Financial assets? Documents related to legal proceedings?
Shared: Some Personally Identifiable Information #PII (birthdays; place of residence; diploma)? Insurance-related data (lists of valuables; car make and model; flat size)? Travel bookings? Streaming package subscriptions?
Public: Social media or forum posts? Published articles, zines, or books?
When you're finished, consider splitting the spreadsheet in two, and handling the part containing FYEO assets like a FYEO asset, in itself.
Start of this thread:
https://mastodon.de/@tuxwise/113503228291818865