Discussion about hosting model and images

Asking for the service to move servers for the sake of hosting risque images is a bit of an ask, do you not think? The core service Mucklet provides is an RP environment. Not an image hosting service that allows content that is questionable or illegal in many countries.

There are services that do this. Mucklet isn’t one of them, and doesn’t seek to be.

2 Likes

It’s a matter of notice and the essentially automatic nature of such image displays. Let’s say you have an IB account, likely required to even view the image. And I know when a character looked at my character. I can make a good guess at what IB user owns what Wolfery character by matching up access IPs. If the URL is there people can make an informed decision and the timing is delayed, use a private window with an alternate throwaway account, etc.

Obviously I have special access to IB and it is unlikely I would actually do that but it’s not really good to allow that possibility for anyone. (This is also why IB uses its own VPSes and machines for content hosting rather than proxy through CloudFlare or the like.)

I suspect the two matters are separate, although one may have prompted re-evaluating the other.

That said, Hetzner’s terms include the following:

This is more specific about certain aspects than e.g. OVH’s equivalent content policy (section 7.2), albeit still subject to interpretation (are they saying all porn is illegal, thus forbidden, or all illegal porn is forbidden?). As always it is the actual enforcement that matters.

I thought Mucklet was already changing servers to Germany, and that’s why the problem is arising in the first place. Legality is completely subjective to the people looking at it. If you go outside your flock, you’re liable to get eaten. That’s just the way the world works.

You can smoke a joint in front of 50,000 people and either be arrested on the spot, or you can be at Burning Man. It’s only illegal if someone cares.

And yeah, that’s why I said… CDN… Images probably shouldn’t be hosted on the core servers anyways for efficiency-sake.

While getting heated about the topic, it is important to keep in mind that just because something is possible does not mean it is advisable to do, and just because another service does something it does not mean it’s a good idea to copy that functionality as is.

What are you suggesting isn’t advisable? Very vague. We talking something purely technical?

I was already typing up what Kelmi clearly meant: “Do it and hope noone notices” is not a winning strategy. I’m not sure if you’re suggesting that at all but you seem to be implying it.

Furthermore the CDN defense is no defense at all. If there is a legal issue they will come to Mucklet AB and you can’t say ‘haha, yeah, images.mucklet.com (or what have you) is actually on a US hoster’. That will be given the dimmest of views legally.

1 Like

When you are the one paying for the service, and your name is on the contract for the server rental, you may choose what hill to take your stance on. That has no bearing on what legal risks Mucklet and its owner is willing to take though.

This is honestly not a point of discussion. The service owner is the final authority on what content they will allow on their servers. That policy has been outlined above.

1 Like

Wasn’t making a defense. Was offering a suggestion.

Correct, and I agree entirely. That’s why I said, federating the nodes out to various parties would be ideal. It’s my understanding this is a FOSS project, correct? Is the server source code licensed under a copy-left license?

It is not. The front-end code is, the back end code is not.

The intent is that you will be able to host your own realms as a service, hosted by Mucklet. To head off the usual follow-up question when people learn that; Wolfery (which is an instance of the mucklet code, a ‘realm’ as it is called) is intended to be free as it is right now permanently.

Huh. But isn’t it based off of Fuzzball Server? That’s GNU GPL 3.0. Mucklet was a fork of MUCK. Hopefully terms of the license isn’t being violated?

There is no Fuzzball code in Mucklet. It is very VERY different under the hood.

…it wasn’t coded nigh on 40 years ago, for starters.

1 Like

I’m sorry, I was always under the impression the intent for this project was an open-source one. Shame. Ohwell. So basically, this is proprietary. Good to know. We might need to update that on Wikifur to make it clear.

Speaking of legalities (which I’m to understand is purely the reason all this is happening), there aren’t any legal infos on Wolfery’s front page… no links to Privacy Policy, ToS, Community Guidelines, etc. If this is a proprietary for-profit venture you might want to look into that!

Privacy Policy

ToS

mucklet-client source, under Apache 2.0

Also what Maximus said.

This is rapidly turning into what smells a lot like witchhunting. I suggest this turns off that path soon.

3 Likes

Yes but it’s not on the website. That’s my point.

We’ve shown you it’s on the website.

Ahh, so you have to be logged out, kay.

The links are in the player settings. If you are a new user you get shown what Maximus has shown you, directly and up front. I will also echo his statement on your tone right now.