Terms of Service and Privacy Policy update

#18

This isn’t a purely text-based environment, otherwise such a rule-change would not be required. It’s text-focused. I think it was wise for Accipiter to call it “textual” rather than “text-based.” It’s an apt description.

And c’mon, Green, you know me. I’ve been on MUCKs since 97. This isn’t my first rodeo. Even in text, people get squicked and say “eww, I don’t want that around me.” Look how Whitefire banned human children running around from public spaces. At least he didn’t ban them universally, and he lamented about how conservative the young furs were compared to him in his newspost.

Conversely, THIS policy change is a universal ban! It is above mere behavior and goes outside the realm of the simulation, and into the physical server hosting the creatures within that child-dimension. The reality of those inhabiting that dimension are adversely reacted by a change made from “God.” That’s a big deal!

I fully respect the rights of the property owner of a server to dictate what they do or do not want hosted on their machines; and I completely understand Accipiter’s situation; so this isn’t an attack on him.

What I AM driving at, is that I am creating a passionate appeal, pointing out the underlying philosophical principles, as any good critical mind would, to speak on the various facets such a change makes for the community. This platform is in its infancy, and if you don’t have people active enough to speak out about it, how can the one who governs and dictates what happens to so many others make informed decisions about how these policy changes affect them?

In regards to alternative realms, I’m new here. I have given less than 4 days time to the game, and I don’t know off-hand if I can commit to such a venture, but I definitely have interest. Pioneering this sort of thing is of extreme interest to me.

Glancing over the post, however, it still seems like we would be in the same boat as before. It’s all hosted on wolfery.com. So the same server restrictions would apply. Hence the node idea I was throwing out there.

Discussion about hosting model and images
#19

Tbh I thought, when I saw you replying, you were going to say it was you that censored the post. I’m glad it wasn’t. That calmed me down. I have a feeling it was an automatic reaction to my edits. I have that issue where I write something, then I realize there’s more to say, and I revise constantly.

1 Like
#20

I remember when rules were added. Lots of people were slapped, herded off to an empty room or otherwise got a mod warning. Lot of people don’t read forums and aren’t there when Accipiter toasts the server to go read the forums about an update.

When big changes like this are made on other mucks you get a login and immediately presented with modmail. Might I suggest mailing everyone when the new ToS comes? Something that the typical user sees when first logging in to wolfery.com. Even a couple weeks advanced notice to all users would be nice. So that when new ToS rolls out it isn’t immediately met with a bunch of shock and warnings.

4 Likes
#21

The posts were marked by the system automatically because you are a new user and they had multiple links (‘to the same domain’, which I didn’t know it checked but makes sense), which to be fair are usual spammer behavior. Your posts were of course not spam, and I’m unhiding them.

As far as the content goes, I agree with Acci and Maximus.

#22

Who’s Maximus? Don’t see any comments they made on the thread.

#23

Haha, whoops. Maximus is another moderator and I thought they’d replied to this already.

To your fediverse posts however, it is intended for Mucklet to be a service allowing additional realms, though those would likely all have similar rules to this due to the location of hosting.

#24

There are a few important points here that I think are being overlooked.
First and foremost, this policy change is not about what you actually play on Wolfery, be it character concept or scenes. This is a policy change with regards to what images you are allowed to upload as profile pictures, which are stored on Mucklet AB’s servers.

The service owner does not wish to take on the legal burden of hosting images that may be in a legal gray zone, especially as the content is hosted in a country with specific legislation that affects drawn art. This is a matter of following law. Whereas I can understand it makes it more difficult for certain character concepts to present the art they want, it is: 1) Not a prohibition from linking said art, just a ‘No thank you’ to hosting it on Mucklet’s servers. and 2) Not a policy change that affects the ability to play those characters, or play in scenes involving those characters.

Claiming this is a ban on the existence of young-looking characters is disingenuous. It isn’t. You may have art of your clothed young-looking character. You just can’t have suggestive or sexualized images of them on Wolfery’s servers.

3 Likes
#25

If it’s a fediverse, it would be hosted in multiple locations on servers owned by furs other than Accipiter. Different domains, different machines, different countries.

Nodes, like IRC, Usenet, Mastadon, Telegram. Same concept.

#26

I didn’t miss that at all. And I don’t think it’s disingenuous, what I said. What I play influences how I look. How I look will no longer be allowed, therefore it affects how I play.

Just host the images on Inkbunny like Green offered to do. That’ll take care of the issue.

Better for scalability, too, if you ask me. A server geared toward an image library will help the server load.

#27

Allowing externally hosted content to be presented natively in the Mucklet client was discussed. But there are significant security concerns to this, and as I understand it, there’s no core security design in place to handle external content in the system.
It doesn’t mean it’s not possible, but as far as I know, there aren’t any plans for this at present. So don’t rule it out. But in the meantime, looking into alternative hosting for images that do not fit the policy change is the wisest option.

#28

It’s entirely possible to code the Mucklet to where when it asks you the profile pic you want to use, it can point to another domain. They do that all the time in other places.

As for the security aspects, could you describe the issue?

The more likely issue will be when those domains no longer host the image, and the link breaks, but that’s hardly as bad. People just need to update their links. Heck, I’ll imagine most people will just link to existing f-list profile pics.

#29

This reminds me of that one time else-MU I got suspended in an empty room over something entirely off-MUCK, only I was never actually told that, the server administration was so whimsical that their suspension room wasn’t clear it was for administrative suspensions, and one of the standard global exits worked in it, so I thought it was a soft form of idle-purge to move sleepers - since I’d been away for a year and a day - and carried on as usual. Cue a permaban for jailbreaking.

I know this is a bit tangential to the situation described, but it’s a good example of how direct messaging is usually the best policy vs. assumption.

This is kind of a privacy issue and also IB’s content delivery nodes wouldn’t allow it, my suggestion was more a manual “invite people to use some named alternatives and link to them”.

1 Like
#30

I guess I’m trying to understand the security issue that arises, in the difference between displaying a picture in Mucklet, versus creating a text link whose URL opens up a new window and does the same thing.

#31

I’m not the right person to go in depth about Mucklet specifically, that’s Accipiter’s domain. But off the top of the bat - IP logging, XSS attacks, MITM attacks, content spoofing, image library exploits…

Any data you do not have the ability to sanitize yourself before running through more code is a risk. Heck, given that we don’t even have the ability to control content size on external links, it could serve as a DDOS attack.

So yes, any changes that allow externally hosted content is not a matter of ‘just doing it’. It will first and foremost be a decision Accipiter needs to make, and then assess on how to do. In the meantime, what we need to do is comply with that policy, when it goes active.

1 Like
#32

Inkbunny doesn’t allow embedding content into other websites. It’s not a hosting service, I don’t think many would appreciate that either. You’ll have to post links.

#33

This reminds me of that one time I ended up suspended in an empty room over something entirely off-MUCK, only I was never actually told that , the server administration was so whimsical that their suspension room wasn’t clear it was for administrative suspensions, and one of the standard global exits worked in it, so I thought it was a soft form of idle-purge to move sleepers - since I’d been away for a year and a day - and carried on as usual. Cue a permaban for jailbreaking.

I… don’t think this is something that happened on Wolfery?

#34

Host the server where Inkbunny is hosted and have it all under one domain then?

#35

No, that’s why I said MUCK (not specifying which one, it isn’t relevant). Was an example of why quiet/non-specific actions can be bad. I’ve updated to clarify that I wasn’t talking about here.

#36

No, that’s why I said MUCK (not specifying which one, it isn’t relevant).

coughs Whitefire vibes.

image
image939×211 17.8 KB

Oof. I guess I’m out of the conversation for the next three hours.

#37

31 posts were split to a new topic: Discussion about hosting model and images