• 0 Posts
  • 20 Comments
Joined 5 months ago
cake
Cake day: February 15th, 2025

help-circle
    • People buy njalla domain.
    • Start to do illegal stuff on domain.
    • Njalla gets legal complaint.
    • Since njalla doesnt know your personal info, all they can do is shut down the domain
    • People cry that they were “scammed” by njalla for “no reason”
    • Sometimes in these kind of posts, when you pry long enough they admit to doing something illegal (which they think is fine, like pirated media sharing).

    I have my personal website domain and some selfhosted stuff on subdomains on a njalla for over 5 years. Never had any issues cause none of what I do is illegal.













  • Sounds like you are in head over heels.

    Pterodactyl has a discord, why don’t you go there for dedicated support?

    Regardless of where you ask - if you want help you should provide detailed information. Tell exactly what commands you entered, from start to finish, not skipping anything and provide the outputs that you’ve gotten, especially the errors.




  • I just tested it on my instance. You can create a public share by setting the mode to “Write”, which is accessible without logging in as a user (but with optional password).

    It works, but one does not see any files, not even the ones you uploaded yourself. So for example if you updated the file and need to re-upload it, there is no way for you to delete the previous one.

    You can also create a shared “virtual folder” that is seen by multiple users, and then you have fine grained control on a user basis (Users > burgermenu > edit > ACLs > Per directory permissions) there you can mix and match from a list of ~15 permissions. To upload anything to that virtual folder, you’ll have to properly log in as a user.

    Hope either one of the ways works for you. Cheers




  • the protocol is text only, to embed media, you need to host it on the regular ( Centralized ) internet

    except we already figured out how to encode images (or any file) as text when E-Mail was created. That is how images in E-Mails, attachment or embedded, are done. I can easily imagine a userJS script that will render them in the browser, but even if not you just copy the text and decode.

    if a community is badly moderated, the user will never see it, it wont be recommended to him. the user can visit bad communities directly just like you can visit a bad website directly, but it’s not recommended to you so it’s safe to use.

    Ah… so you’re guaranteed to have a dark CSAM subculture on there at some point.

    being p2p, seedit is not private, so it can’t really be used for illegal activity

    As if that has ever stopped anybody. See all the people that got caught for sharing it on the clearnet. Or on Signal, Telegram or similar, where you have to enter your phone number, which is personally tied to you.


    All in all - Great way to adress the concerns, by admitting they are in fact possible. “Hurray crypto” or whatever.