beta.fyle.uk banned by Glitch

[Jack5079]

[nbitzz]

The most likely reason is a DMCA. Even if pfile was big it couldn't have been hogging bandwidth that much; it had to have been a DMCA

[Jack5079]

We need to add an abuse email

[Jack5079]

Also make sure HTML can't work like https://fyle.uk/mee6 because that could get us banned for phishing

[nbitzz]

We should look into hosting options for monofile's main instance, even if it's not banned yet. Also ban copyrighted content

[nbitzz]

Also make sure HTML can't work like https://fyle.uk/mee6 because that could get us banned for phishing

maybe through a comma-separated env var like

DISALLOW=text/html

[nbitzz]

Next steps:

• Consider if beta.fyle.uk should even return at all
• Find a new host for the monofiles
  • Oracle, maybe
  • Vultr may be coming out with purchasable bandwidth soon, if it's cheap enough maybe just go Vultr

[WaviestBalloon]

What's holding you back from not migrating away from Glitch?

[nbitzz]

What's holding you back from not migrating away from Glitch?

icdont know

[WaviestBalloon]

icdont know

You should totally migrate :3

[nbitzz]

icdont know

You should totally migrate :3

Yeah we should

[Jack5079]

I think what actually happened was someone posted the link to fedi which caused every instance to fetch a 400 mb file which caused the bandwidth to skyrocket which caused glitch to ban us

[Jack5079]

But doesn't monofile 2.0 serve a embed on /:fileId now

[WaviestBalloon]

every instance to fetch a 400 mb file

400 MB? Do you have any logs to check this?

[nbitzz]

But doesn't monofile 2.0 serve a embed on /:fileId now

No

[Jack5079]

every instance to fetch a 400 mb file

400 MB? Do you have any logs to check this?

We know because someone posted a TV episode hosted on monofile to Mastodon and beta.fyle.uk got banned the same day

[nbitzz]

it was a /download though