Computers and the internet gave you freedom. Trusted Computing would take your freedom.
Learn why: https://vimeo.com/5168045
What??? Whoever wrote this sounds like he has 0 understanding of how it works. There is no “more privacy-friendly version” that could be developed, the models are already out and you can run the entire model 100% locally. That’s as privacy-friendly as it gets.
Unfortunately it is you who have 0 understanding of it. Read my comment below. Tldr: good luck to have the hardware
im not an expert at criticism, but I think its fair from their part.
I mean, can you remind me what are the hardware requirements to run deepseek locally?
oh, you need a high-end graphics card with at least 8 GB VRAM for that*? for the highly distilled variants! for more complete ones you need multiple such graphics card interconnected! how do you even do that with more than 2 cards on a consumer motherboard??
how many do you think have access to such a system, I mean even 1 high-end gpu with just 8 GB VRAM, considering that more and more people only have a smartphone nowadays, but also that these are very expensive even for gamers?
and as you will read in the 2nd referenced article below, memory size is not the only factor: the distill requiring only 1 GB VRAM still requires a high-end gpu for the model to be usable.
so my point is that when talking about deepseek, you can’t ignore how they operate their online service, as most people will only be able to try that.
I understand that recently it’s very trendy, and cool to shit on Proton, but they have a very strong point here.
why is it important, and where is it used, though? on windows you cant make symlinks without admin rights by default, and steam usually does not need admin rights to install a game
hmm I see. and why do you want that? balancing storage usage between backup sites? one of them is too little for the whole pool?
for now I don’t have a better idea, sorry. maybe this is the second best time to think up a structure for the datasets, and move everything into it.
but if the reason is the latter, one backup site cant hold the whole pool, you may need to reorganize it again in the future. and that’s not an easy thing, because now you’ll have the same data (files of the same category) scattered around the FS tree even locally. maybe you could ease that with something like mergerfs, and having it write each file to the dataset with lower storage usage.
if you are ready to reorganize, think about what kinds (and subkinds) of files will you be likely to store in a larger amount, like media/video, media/image, and don’t forget to take advantage of per-dataset storage settings, like for compression, recordsize, maybe caching. not everything needs its own custom recordsize, but for contiguously read files a higher value might be better, also if its not too often accessed and want better compression ratio as compression (and checksumming!) happens per records. video is sometimes compressible, or rather some larger data blob inside the container
the reason might be is that freetube can only proxy your usage over a server when using invidious, otherwise it needs to connect to youtube directly, making it possible for them to track you by IP (and by logged in users using yt from the same IP)
what is your goal with this?
do you still want to keep all the data in a single pool?
if so, you could make datasets in the pool, and move the top directories into the datasets. datasets are basically dirs that can have special settings on how they are handled
ninja edit: now that I think about it, moving across datasets probably makes that data to be resent.
it would be easier to give advice by knowing why do you want to do this
in my opinion its only better with an alternative frontend, if it works well enough. because it cannot add any more datapoints than instagram could, but a good lightweight frontend will add much less, because I won’t need to worry about my mouse movements and page scrolling pace being recorded. uBO and such wont be able to protect against that
that’s ok if you want to publish content. but frontends are for a different purpose: you were never able to use them for that, they are for viewing instagram content
did you try pixelfed? It’s basically a selfhostable, federated instagram
btw, my university (EU) teaches blender
privacy, and preservation
it deals with items of different materials and different kinds of dirtyness. drying is done wildly differently too, and some dishwaser detergent has stuff to help faster drying
I run all of these or their equivalents in docker containers and have up to date versions of them. to me it makes management easy and the system clean from random files at random places. just one example: fortunately it does not need babysitting but i2p keeps its files in a very disorganized way inside the container, and I would never want to install it directly to the system (maybe unless the system would be dedicated to that)
why do you think that?
for what kind of software? also, do you maybe also have exact features on your mimd?
I’m quite sure Debian’s server-related packages are kept patched against security issues in a timely manner
well yeah actually it depends on how they are rotated. if they are “hanging” with the connectors facing the bottom/top, it does not make the box big in the dimensions I imagined
Absolutely. I think having this in mind would probably also solve the outdated packages problem. the docker based services won’t depend on it, and unless OP wants it to be a full blown desktop system too, the older packages shouldn’t get in the way
can you give examples of what you need more recent versions of?
it is certainly that. but recently its become very trendy to hate Proton, so its just easier to do that instead of thinking. I’m really disappointed in this community