Axel Hartmann
@axel_hartmann@digitalcourage.social
0
Followers
0
Following
Joined November 20, 2022
??C3:
27, 32, 33, 34, 35, 36
rC3:
2020, 2021
DIVOC:
2021, 2022
other:
froscon, GPN, ...
Posts
Open post
In reply to
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
@axel_hartmann@digitalcourage.social
·
5h ago
@inthehands - but actually it was the product range development (quiet computers that require noisy storage supplements might as well not be quiet) and the constant software rot (media storage and management that became increasingly closed, continuously lost features, and inserted AI slop metadata to my photos) that drove me away from the platform even before that.
0
0
0
0
Open post
In reply to
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
@axel_hartmann@digitalcourage.social
·
3d ago
@WiteWulf @nina_kali_nina wasn't FreeNAS based on FreeBSD - that was rock solid to me for a good decade
1
0
0
0
Open post
In reply to
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
@axel_hartmann@digitalcourage.social
·
Mar 25, 2026
@gmh - which country?
0
2
0
0
Open post
In reply to
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
Axel Hartmann
@axel_hartmann@digitalcourage.social
digitalcourage.social
@axel_hartmann@digitalcourage.social
·
Dec 03, 2025
@robinhouston at those dimensions, do you have to check for computing boundary conditions, processor faults, general six sigma error probabilities etc. ruining the entire run?
0
0
0
0