90
Kitchenowl creator has been flagged without warning making all of their repositories return 404, while in their settings all of the repositories still look normal with public visibility. (lemmy.ml)
submitted 7 months ago by to c/selfhosted@lemmy.world
12 comments fedilink hide all child comments
 

cross-posted from: https://lemmy.ml/post/45529149

Here is the message where he found out what happened:

I didn't receive any information about it but when creating a support ticket I was told my account has been flagged and I had to do some extra verification. I've created a support ticket now and will keep you posted. I'll believe it's nothing major though, I use 2FA everywhere, the last commit on all repos is what I expect, and all sessions and usages look fine

Absolutely fuck Github and Microslop, they can just vanish your projects without notice whenever they want with barely any justification for it, and then take their sweet time to fix it too.

you are viewing a single comment's thread
view the rest of the comments
[–] 8 points 7 months ago* (last edited 7 months ago) (2 children)

The scraping/bandwidth abuse problem can easily be worked around.

But there still are actual good reasons to not host a public forge.

For example, as long as pull requests are allowed (which is required for actual contributors), anyone can abuse the PR feature to fork your repository, then start pushing random shit into their fork (since the fork is an actual separate git repository).

Bad actors can do it on github all they want, it's not my storage, not my server used to host potentially illegal content.

Self-hosting public services where you are the only authenticated user and sole publisher of content is easy (using your public forge as a mirror with account creation disabled is fine), hosting other's people content is another can of worms. Think twice before you do that.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 7 months ago (1 child)

    The scraping/bandwidth abuse problem can easily be worked around.

    how?

    anubis does not protect the APIs, and it cannot protect against bot traffic coming from many different residential proxies

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 7 months ago

    It can protect APIs as much as any other URL. Or more simply you could disallow any unauthenticated API access in gitea or at the reverse proxy level?

    cannot protect against bot traffic coming from many different residential proxies

    It can block anything that doesn't pass the proof-of-work/JS challenge. Most bots don't interpret JS.

  • permalink
  • fedilink
  • source
  • parent