• 0 Posts
  • 30 Comments
Joined 17 days ago
cake
Cake day: April 10th, 2025

help-circle



  • @DigDoug @sparkle_matrix_x0x I have differing partition schemes on different machines depending upon their function. On my workstation I have four partitions, a root partition which is on SSD and all the system binaries and files reside there, a /home partition which is on rotary media because speed is less critical space more so, and a backup drive which keeps compressed copies of the /home and /root partitions. On my servers mostly everything is RAID and it’s much more complex and varies according to the function of a particular server.



  • In addition to Mastodon and Pixelfed, I have a Friendica, Hubzilla, Yacy, and Nextcloud.

    Federated Services

    Federated Services are services which many instances form a network to provide a greater whole than the sum of their parts, each participant in the Fediverse is an “instance”. A message or other item made available on one instance is visible and available on other instances.

    We make these services available to all people who do not abuse it in order to promote the values of Free Speech, and those of the United States Constitution First Amendment. A free republic is not possible without free speech and commercial mainstream media do not provide it. We also get some advertisement benefit from hosting these, it is our hope that people who see how fast and responsible our services are will decide to do hosting or use other paid services here.

    There are numerous federated services available, we offer Macrobloging platform Friendica, Hubzilla; Microbloging services Mastodon, Misskey, a federated search engine, Yacy, and a federated cloud service, Nextcloud.

    Macrobloging services are message systems that allow long form posts similar in format to Facebook. These allow for works of fiction, poetry, technical papers, news items, short stories, and more. These formats are most useful for discussion of social issues.

    Microbloging services allow only short form posts similar in format to Twitter. While you can link to larger articles elsewhere, you have a relatively short character limit and so can not post them directly.

    Censorship, is handled much different on the fediverse than on mainstream media like Twitter or Facebook. On the fediverse, each individual instance is responsible for content available on that instance, but does not censor the rest of the network. Thus if you find the rules of one instance too constraining you can move to another.

    Federated search engines are analogous to federated message systems in that each instance chooses what portion of the internet it wants to crawl. When you enter a search term, the local instance queries all of the federated instances, collates and sorts the results and presents them to you. As with messages, each instance can have it’s own censorship policies but no one instance can censor the entire network.

    Given the wild-west nature of the fediverse, it is probably not suitable for children under 14, and you’re guaranteed to find some material that will offend virtually everyone. With federated search engines, material that is inappropriate will usually be flagged sensitive or nsfw (not safe for work) so as long as you don’t expand material marked as such, you can avoid this sort of material. There are occasionally people who violate these rules, we do our best to remove such individuals none the less some will get through.

    We offer the following federated services:

    Friendica.Eskimo.Com
    Friendica is a decentralized long format macrobloging message network. It is similar in format to facebook however there is no centralized censorship. Also, it is able to federate with all other federated message systems which use ActivityPub protocol and also we have extensions that allow it to speak to several other networks via other protocols.

    Hubzilla.Eskimo.Com
    Hubzilla is similar in message format to Friendica in that it allows long posts. However, it specializes in it’s ability to provide connectivity to multiple protocols and so we include it in our mix of federated services primarily for the better connectivity it offers. Hubzilla provides a great deal of interoperability between many networks though ActivityPub is still it’s primary protocol. Hubzilla gives you a greater degree of control over privacy than some of the other networks. You can create private channels that are served between hubzilla instances and other compatible instances.

    Mastodon.Eskimo.Com
    Mastodon is first and foremost an alternative to Twitter. While Twitter has Tweets, Mastodon has Toots. The format is very similar. Mastodon toots have a limit of 500 characters. Similar to the short limit of Twitter. This is why this platform is referred to as a Microbloging format. Mastodon interacts with other ActivityPub instances however when a long form blog post from another instance arrives, you are only shown a short portion with a link to follow to see the full post on the originating site.

    NextCloud.Eskimo.Com
    If you are a customer of Eskimo North, your login credentials will work without a domain extension to access Nextcloud. If you are not a customer you can apply for a Nextcloud account using your choice of login and password, in this case the login should include your originating network. Some features require an Eskimo North shell account to take full advantage of.

    Pixelfed.Eskimo.Com
    Pixelfed is a federated pixel gallery. A place where you can share your photos to the widest audience possible, and you can view what others have shared. Instance is new as of April 6th, 2025.

    Yacy.Eskimo.Com
    Yacy is a federated search engine. There are several thousand instances on the Internet. Each instances crawls whatever portion of the web the administrator requested. It is also possible for the administrator of a site with relatively few resources to request a larger site to do crawls on their behalf. Unfortunately, it does not provide a method for an end user to initiate a crawl, but if you send e-mail to support@eskimo.com and request a crawl, we will initiate a crawl on your behalf.

    If you enjoy these services, please consider supporting us by taking advantage of our paid services: https://www.eskimo.com/






  • I’ve had Windows and Linux installed on the SAME drive for decades and don’t have this issue. Install Windows first because it WILL fuck up the EFI boot partition, that’s inevitable because Windows sucks, then install Linux, use the manual partition option and simply select the existing EFI System partition for the EFI and DO NOT mark format, Linux will then install and leave the Windows boot loader in the EFI partition undisturbed.

    Linux WILL overwrite the boot block to start grub instead of the Windows boot loader, but most Linux distros will automatically add a chain boot loader entry to the grub menu to allow you to boot Windows, at least Debian and Redhat derived distros will do this, probably a more manual process in Arch derived distros.

    If it does become necessary to install Whendoze after Linux, you can use boot-repair to automatically fix the EFI System partition Windows fucked up or you can boot off of a flash drive, and fix it manually.



  • One of the things you run into with audio production software is that in order to maintain accuracy with respect to phasing between channels, they require very accurate timing, this usually comes at the expense of very high interrupt rates and context switching and under the best of circumstances this is hardware intensive, more so with older processors that don’t have single instructions for storing the entire register set or restoring the entire register set to the stack with one instruction as many modern CPUs do. So hate to say it but you may need to upgrade to something less geriatric. You might also try a real-time kernel, it might allow the application to keep things sync’d up with less hardware interrupts though it will rely more on software interrupts do do the same. Unfortunately, I have found that while I can get the performance I require on my six year old processor using a realtime kernel, it has come with a sacrifice of stability, that is to say real time on my hardware at least has not been terribly stable.






  • @marauding_gibberish142 I personally find the Intel ME a useful feature, it’s nice for example to be able to upgrade BIOS without a CPU and/or memory, this has allowed me for example to upgrade the BIOS to a version needed for a newer CPU on a board with a BIOS that didn’t initially support it without needing the older CPU to perform the upgrade. And from a security standpoint, if you do not enable and configure the network stack, and you don’t have a DHCP server available to it for it do so on it’s own, I really don’t see what it can do that is harmful.


  • @jeena I grant you that is true, but under Linux, the kernel talks to the hardware directly after boot, not through BIOS calls. About the only time you would talk to the BIOS after boot is for sleep/suspend, or in rare cases such as the server my friendica instance runs on, for temp/CPU speed control because Linux kernel has issues properly using the MSR on the i9-10980xe, oddly it does not seem to have the same issue on the i9-10900x which is a ten core CPU in the same family, so I am forced to depend upon ACPI since talking to the hardware directly in this specific case is problematic. If you were running Windows or if you had weird hardware that is somewhat broken under Linux like mine, I can see the need, or if a laptop and you wanted sleep/suspend functionality. But for what you describe it isn’t clear the benefits. And there are some risks like it probably isn’t going to do the extensive memory training of a more advanced UEFI bios like American Megatrends, so your memory access may not be as efficient as it could be, and you’re more limited in hardware selection.