#akkoma — Public Fediverse posts

Are you able to explain what the “shorts” are that you’re referring to? I’m not familiar with the term in this context.

Regarding #Lemmy, if you’re #selfhosting, you can use a Linux “bash” script to block much of Lemmy at the firewall level. I.e. you don’t necessarily need to configure or modify your #Fediverse server. Details on request.

That said, #Pleroma and #Akkoma permit partial blocks of much of Lemmy at the config-file level as well. The firewall approach might be preferable as it blocks Lemmy more completely.

#askfedi

Are you able to explain what the “shorts” are that you’re referring to? I’m not familiar with the term in this context.

Regarding #Lemmy, if you’re #selfhosting, you can use a Linux “bash” script to block much of Lemmy at the firewall level. I.e. you don’t necessarily need to configure or modify your #Fediverse server. Details on request.

That said, #Pleroma and #Akkoma permit partial blocks of much of Lemmy at the config-file level as well. The firewall approach might be preferable as it blocks Lemmy more completely.

#askfedi

Are you able to explain what the “shorts” are that you’re referring to? I’m not familiar with the term in this context.

Regarding #Lemmy, if you’re #selfhosting, you can use a Linux “bash” script to block much of Lemmy at the firewall level. I.e. you don’t necessarily need to configure or modify your #Fediverse server. Details on request.

That said, #Pleroma and #Akkoma permit partial blocks of much of Lemmy at the config-file level as well. The firewall approach might be preferable as it blocks Lemmy more completely.

#askfedi

Are you able to explain what the “shorts” are that you’re referring to? I’m not familiar with the term in this context.

Regarding #Lemmy, if you’re #selfhosting, you can use a Linux “bash” script to block much of Lemmy at the firewall level. I.e. you don’t necessarily need to configure or modify your #Fediverse server. Details on request.

That said, #Pleroma and #Akkoma permit partial blocks of much of Lemmy at the config-file level as well. The firewall approach might be preferable as it blocks Lemmy more completely.

#askfedi

Are you able to explain what the “shorts” are that you’re referring to? I’m not familiar with the term in this context.

Regarding #Lemmy, if you’re #selfhosting, you can use a Linux “bash” script to block much of Lemmy at the firewall level. I.e. you don’t necessarily need to configure or modify your #Fediverse server. Details on request.

That said, #Pleroma and #Akkoma permit partial blocks of much of Lemmy at the config-file level as well. The firewall approach might be preferable as it blocks Lemmy more completely.

#askfedi

#akkoma - does someone know what could cause my simple default OTP setup to just fuck up signed fetch? default nginx, as per tutorial. no major changes. i don't know what to check...

(KeyError) key :data not found in: nil
{:fetch, {:error, :not_found}}
:fetch, {:error, :forbidden}}

#akkoma - does someone know what could cause my simple default OTP setup to just fuck up signed fetch? default nginx, as per tutorial. no major changes. i don't know what to check...

(KeyError) key :data not found in: nil
{:fetch, {:error, :not_found}}
:fetch, {:error, :forbidden}}

#akkoma - does someone know what could cause my simple default OTP setup to just fuck up signed fetch? default nginx, as per tutorial. no major changes. i don't know what to check...

(KeyError) key :data not found in: nil
{:fetch, {:error, :not_found}}
:fetch, {:error, :forbidden}}

#akkoma - does someone know what could cause my simple default OTP setup to just fuck up signed fetch? default nginx, as per tutorial. no major changes. i don't know what to check...

(KeyError) key :data not found in: nil
{:fetch, {:error, :not_found}}
:fetch, {:error, :forbidden}}

#akkoma - does someone know what could cause my simple default OTP setup to just fuck up signed fetch? default nginx, as per tutorial. no major changes. i don't know what to check...

(KeyError) key :data not found in: nil
{:fetch, {:error, :not_found}}
:fetch, {:error, :forbidden}}

#pleroma and #akkoma by default present a “mrf transparency” panel on their /about page that lists every instance that it they won’t federate with (or that they moderate in any way).

this list of moderated instances is typically the longest panel on the page, and is packed with names like nazis.social and die.<slur>.net.

it doesn’t make a good first impression.

so instead of doing things the Right Way™ and changing the code to not create this panel, one of the static html pages for mtl.rocks that gets copied onto every page includes a stylesheet that simply sets display:none on that panel.

i’m a Hacker. i hacked pleroma

#pleroma and #akkoma by default present a “mrf transparency” panel on their /about page that lists every instance that it they won’t federate with (or that they moderate in any way).

this list of moderated instances is typically the longest panel on the page, and is packed with names like nazis.social and die.<slur>.net.

it doesn’t make a good first impression.

so instead of doing things the Right Way™ and changing the code to not create this panel, one of the static html pages for mtl.rocks that gets copied onto every page includes a stylesheet that simply sets display:none on that panel.

i’m a Hacker. i hacked pleroma

#pleroma and #akkoma by default present a “mrf transparency” panel on their /about page that lists every instance that it they won’t federate with (or that they moderate in any way).

this list of moderated instances is typically the longest panel on the page, and is packed with names like nazis.social and die.<slur>.net.

it doesn’t make a good first impression.

so instead of doing things the Right Way™ and changing the code to not create this panel, one of the static html pages for mtl.rocks that gets copied onto every page includes a stylesheet that simply sets display:none on that panel.

i’m a Hacker. i hacked pleroma