I am Rooki Cookie. I am a programmer and i try to help everyone :)

  • 5 Posts
  • 209 Comments
Joined 1 year ago
cake
Cake day: June 22nd, 2023

help-circle










  • Some of the world team That is probably me. I am sorry about it.

    Sublinks should not replace lemmy but add alternatives to the fediverse. We understand it is difficult to maintain such big software especially if there is always that exceptional “big” instance that has special requests for special / specific features. With it we just want to have less “beef” with the lemmy devs, with “big” instance issues.







  • Yes, its their right to do so, you could create a community where you just ban everyone from the community that you dislike. You can do literally anything you want ( except site rule breaking stuff ) with your community. It depends of course on the instances internal policy, if a instance admin wants or should intervene, for personal or just for management reason. )


    1. We are only hostile if you are hostile to us
    2. This was again, sry for this a misscommunication, but to be fair in a legal way, first act then announce it is a common approach.
    3. They just wanted a (indirect) test dummy to test their software on a big scale, and we are sick of it, we are always the first that goes head first into their untested, experimental features, that they probably even didnt started in their test environment and not even mark it as experimental.
    4. The .world “scraper” bot?! is a verificiaton bot for our discord server to reduce trolls, that just uses simple api calls to verify through a dm that it is you and btw, this isnt created by me it is created by someone on the sublinks team.
    5. This will be discussed, so no idea.
    6. Probably, if the users toxicity reduces here, probably yes, we are sorry for that, we hope to improve.

    I am sorry but the FHF / Lemmy instance admins are just humans. And yeah there is a feature now to export your blocks, community subscriptions and we are not blocking you to use it if you are really sick of us.



  • We did our testing, but we didnt scaled it up to be similar size of our main instance. There everything seemed fine, but when we upgraded the real issues have rissen up and were just breaking every setup we had.

    We had some trust that other instances and developers had tested it at least by turning their instance on and report it, but didnt seemed so. Some issues isnt even caused the instance size. Some issues were documentation were just wrong and not noted it was experimental.

    Of course we should have mirrored our big instance, but that would have increased the costs and would be time heavy.