Permanently Deleted
Yep that was after make clean :). Running a 12-core Ryzen 9 that's a few years old and 64GB RAM; using 24 threads does speed it up quite a lot.
Edit: to be sure, I completely removed the source directory and re-emerged gentoo-sources and got similar results
Great idea to use GPT for that! Been wanting to trim mine down for a while; will give it a shot.
With a decent CPU the kernel compiles pretty fast. I'm using a default configuration with modules disabled (compiled in) and various settings enabled/optimized for my hardware, and this is what I get:
make -j24
real 2m16.357s
user 38m36.133s
sys 4m26.449s
An extension would be cool! I'm currently trying to do something similar, in some sense; I've patched my instance to filter out DB results from public queries so that only my posts and comments are visible (unless I am logged in).
The only thing I’m not sure about yet is if it’s possible - if I create a Post on an instance that’s not my home, who is hosting the data? Do I only send ActivityPub Create Post with the data and the instance then saves it, or do I create the post on my own instance, send an ID, and if someone requests the Post data on the instance I posted to, it will be requested from mine?
I believe it might be possible, but I'm not sure. It seems that the protocol itself is mostly geared for synchronizing data and distributing updates. From my limited understanding, servers follow users or communities on other servers, which inform those servers that updates should be sent to the requesting inbox. These updates are then used to build up a local copy of the remote page. In the case of a remote community, users interact with their local copy and notify the remote community of those changes.
For example, I am viewing a local copy of this post that I received from lemmyml, and my reply to your comment will be stored locally. My server will notify lemmyml of this comment (including its contents), and lemmyml will notify my inbox if anyone interacts with it (because I am a follower).
It seems that at least some of this syncing might not be necessary... a lightweight frontend could rely on the API of each site it connects with to build up the activities it sends. However, this would probably cause some unnecessary traffic, as such a follower would both receive updates and query the API. Also it would probably break some things, such as ap_id (see the multicolored fedilink icon, which points the original copy of the content on my instance).
Absolutely! I haven't had any problems setting up dependencies for various projects and have only needed overlays a few times. Sometimes USE flags can be tricky but most things are pretty well documented
Encourages hardware-based optimization and kernel specialization
Out-of-box security configurations supported by the organization (SELinux, hardening)
Excellent package and dependency management with a wide variety of up-to-date software
fl0w.cc- single user; the domain is meant to be part of my username :)
I usually use new comments which works pretty well for me but it's not perfect and doesn't take scores into account. I'm sure the hot and active algorithms will evolve over time, will be testing them out as well
Thanks! This works pretty well for now, until a more integrated solution comes along. I made a slight modification, since the original script only works when you're at the community level. This version redirects community URLs as before, but also redirects any non-matching URLs to the search form of your home instance. It seems to work pretty well for posts. Comments and user profiles have some issues- searching comments works as long as the user is commenting on their own instance, and searching profiles works as long as the user is registered with that instance.
Edit: It actually does seem to work well for comments; I was using the B/W chain link icon rather than the multicolored fedilink icon. Also, I added another regex to fix profiles, so this should now work with anything that is searchable from your instance.
javascript:((inst = "lemmy.world") => { const l = location; const m = l.href.match(/(?:.*)\/c\/(.*(?=\/)|.*$)/i); if (m) { l.href = `https://${inst}/c/${m[1]}@${l.host.toString()}`; } else if (l.host !== inst) { const m = l.href.match(/(?:.*)\/u\/([^@]*(?=\/)|[^@]*$)/i); if (m) { l.href = `https://${inst}/u/${m[1]}@${l.host.toString()}`; } else { const q = new URLSearchParams(); const m = l.href.match(/(?:.*)\/u\/([^@]+)@(.+(?=\/)|.+$)/i); if (m) { q.append('q', `https://${m[2]}/u/${m[1]}`); } else { q.append('q', l.href); } l.href = `https://${inst}/search?${q.toString()}`; } } })()
I'm not using an immutable distro, but I am daily driving a KVM-based Gentoo setup where most of my VMs use transient (immutable) storage and iSCSI where persistence is required.
I'd say that immutability has a ton of benefits for security and reliability, but it's important to be able to customize things when needed. I'm not sure an immutable distro would offer much in the way of customization though.
In my case I am generally unable to harm my system without meaning to, and I'm able to test new configurations without issue. I have lost data before when accidentally saving to a transient disk, but this is something I could fix with better scripting.
I'd say that in general, incremental backups are a better solution if you're only looking to avoid messing up the system. But immutability is a good option if you like containers or have some other way to configure things before locking them down.
Haha. Yeah it takes time to learn how to do even the most basic things with it. Just how I would approach the situation
I'm sure there's a better solution, but SELinux is an option. It can be difficult to customize, but it's capable of locking down the system entirely. You could theoretically block all actions taken by the user except for a select few mozilla_t actions and others necessary for login.
I was able to get it running from source on Gentoo (without docker). Building from source is an option but you need to manage the dependencies and daemons yourself. This is my first comment! Good luck with your setup
GPT-4 in NeoVim. Definitely has taken the place of StackOverflow for me in most cases, but I still go there for especially difficult problems.
Would rather run something on my own hardware, but I'm waiting for other models to catch up