@cwebber @jfred @vagrantc you could have another minimal kernel + initramfs that decrypts /boot and then loads guix's kernel with kexec (something like u-root, except u-root doesn't support LUKS (but if disk space isn't an issue you could probably include a cryptsetup binary with u-root if you wanted to use that))

@kemona_halftau @nyanpasu64 what’s the lowest common bio length limit to be accepted from remote instances? akkoma’s default seems to be 5000 (and the same limit is used for both local and remote, which I did not know when I set mine to 65535), and your bio is only 3029 characters (in HTML, according to select length(bio) from users where ap_id = 'https://sharkey.skydevs.me/users/afjv12aww6ae01kq';)

@kemona_halftau @nyanpasu64 (convince your instance admin to) increase the limit?

@mjg59 some people fetch Debian repos over Tor specifically to avoid this

good night

@seabass @neil I think reply controls of the kind that’s actually implementable without changing how every implementation does replies (that is, just reject them locally) are already partially possible on Pleroma/Akkoma using MRF (the Message Rewrite Facility). Rejecting replies to a certain user is certainly possible with an MRF filter, the only thing missing is a way for the user to specify this per-post.

@mossfet I am

@seabass @neil Reply controls would require changing how replies work to make them all go via the original poster's server. Currently they go directly to mentioned users (and the replier's followers), and the original poster's server can't do anything about that except reject them locally. This would also allow for fixing follower-only replies (so they go to the original poster's followers rather than to the replier's followers, which results in people seeing random fragments of conversations if they follow only some parties) and making replies federate to all users who see the original post without the need to backfill via non-standard c2s protocols (like fedifetcher does), but good luck getting everyone to implement that.

As for how Mastodon's quote controls work: they kind-of don't. I'm on Akkoma, which has had quote posts long before Mastodon and does not implement Mastodon's quote controls. Nothing prevents me (and nothing can prevent me) from quoting a quote-restricted Mastodon post, although it will (probably, I haven't tested) only appear as an ordinary post with a link to the quoted post on Mastodon, and I think also won't show up under the original post on Mastodon servers (but will on other Akkoma servers and every implementation that doesn't implement Mastodon's quote controls).

@famfo matrix.to was a mistake, but no-one uses matrix URIs unfortunately

@famfo there's another cloudflare outage?

@foone I’m not sure if there’s a better way that doesn’t involve exec:

import sys
for module in sys.modules.keys():
    exec("import " + module)

@paco @RickiTarr are you allowed to name the bank (so I can avoid it)?

@kemona_halftau @frawst akkoma can generate a pack.json from a zip file by itself, but in this case the filenames differ from the shortcodes (like A_BlobCat_Approach.png is :ablobcat_approach:, rather than :A_BlobCat_Approach:) so it needs to read the meta.json to get the correct shortcodes. I attached neocat's pack.json as an example

@kemona_halftau @frawst do you know if there's any existing software to convert the meta.json (*key's format) into pack.json (*oma's format)?

@domi I wish GRUB actually was default. It's only default for UEFI (which I do not use), otherwise it installs syslinux (which I then always replace with GRUB because I use GRUB as a coreboot payload)

@Baa regdomain should prevent this from being possible and limit the power to either 20 dBm (2.4GHz and most of 5GHz), 26 dBm (DFS channels), or 23 dBm (indoor-only channels)

(I'm not sure why OpenWrt is showing only 255 dBm, for me it only goes up to the legal limit for the channel)