Talk:Wikis World

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search

Terms of service[edit]

Happy to see we're with Masto.host. When I launched a read-only instance with them, I used very simple but explicit terms of service to start with, maybe they're useful:

You accept to release under Creative Commons Zero any original work you publish through this instance. For content mirrored or federated from other fediverse instances and websites, refer to the responsibilities and rights of the respective sources. Please refer to the MastoHost privacy policy. No personal data is processed by us other than what is performed by MastoHost to run this service.

(With CC-0 to be replaced by CC-BY-SA-3.0 as discussed.) When you start accepting new users it will be necessary to also discuss conduct and maybe reuse some part of the default privacy policy, but it needs some adapting. Nemo 04:40, 12 October 2022 (UTC)Reply[reply]

Oh, I see you already have everything (?) in /about/more even if /terms is just the default. Nemo 04:47, 12 October 2022 (UTC)Reply[reply]
Yeah, I just copied what mastodon.technology has. I think leaving the default privacy policy in place is fine for now. Legoktm (talk) 00:23, 13 October 2022 (UTC)Reply[reply]
What I don't like about the default privacy policy is that it's impermissibly vague, so it doesn't actually serve as a valid privacy policy. In particular, the part where it says "if this server is hosted in EU" etc. needs to be changed. It's definitely hosted in EU and serves EU users. Nemo 05:16, 14 October 2022 (UTC)Reply[reply]
Good point. I switched /terms to just link to /about/more and updated the Privacy policy text with some of your wording. How does it read now? Legoktm (talk) 06:06, 15 October 2022 (UTC)Reply[reply]
Good. Most instances other than mamot and friends aren't very strict about this, but I think it's a good idea to state who is the data controller, or rather how to reach them: probably it's enough to say that it's wikisworld@legoktm. Other than that, the masto.host page, despite being written from the perspective of the data processor, contains pretty much everything you might need to know about privacy in Mastodon. Nemo 05:53, 16 October 2022 (UTC)Reply[reply]

Rapid growth of new users[edit]

We are currently at 23 users with 3 invites outstanding. There are at least 4 more people who've requested invites that I haven't replied to yet. Our current "Planet" masto.host plan is rated for 20 active users. The next tier ("Star") is for 100 active users. Wikis World has been a bit slow and sluggish today, but I think that's probably because masto.host has seen 10x growth in the past week and is struggling to keep up.

My current thinking is that we're probably fine to keep handing out invites until we get to 30-35 users, at which point we should upgrade to the next plan (and hopefully by then masto.host has stabilized too). Some amount of currently active users will probably go inactive, so we're probably going to stay close to the "20 active users" anyways. Certainly we weren't expecting this level of rapid growth, but since it's happening we should try to capitalize on it and get more people into the fediverse. Legoktm (talk) 07:07, 8 November 2022 (UTC)Reply[reply]

FYI: If there is further growth, I don't mind pitching in for the cost. Even though I'm not on the server right now, I do support it as a mission and I'll likely either move there at some point, or will fork my account into two different accounts. —TheDJ (talkcontribs) 12:05, 8 November 2022 (UTC)Reply[reply]
@TheDJ that is generous and I think many other people and some affiliates would follow that.
WMF should have flexible discretion funds *(not just funding protocol option) for this kind of situations. -- Zblace (talk) 08:58, 22 December 2022 (UTC)Reply[reply]
They have grants for this, but I think that ppl of that server would prefer to manage it completely standalone from the WMF. —TheDJ (talkcontribs) 09:32, 22 December 2022 (UTC)Reply[reply]
Yeah...I think it's important the server continues to be operated in a bottom-up manner by individuals who are passionate about it, rather than an organization that appears to not care about this stuff :(. At the same time, it certainly feels weird to ask individuals to donate/contribute financially for this when the cost would be pretty negligible for the WMF.
Anyways, I was/am hoping more people will comment in #Finding a legal home below, which is somewhat related to this and would influence what direction we go in. Legoktm (talk) 09:48, 23 December 2022 (UTC)Reply[reply]

Finding a legal home[edit]

If you haven't read https://denise.dreamwidth.org/91757.html yet, please do, it is a good overview of the legal stuff we want/need to take care of in the long term.

I see 3 primary options: 1) join up with an existing Wikimedia affiliate/WMF 2) join up with a more generic open/free non-profit like Open Collective 3) register our own LLC/non-profit.

Obviously #3 is the most work and therefore my least preferred solution. For #2 I know @Nemo bis has been exploring Open Collective.

Do people have thoughts, comments, suggestions? One other thing to consider is whether we want said legal home to be in the US or EU. Our data is currently in the EU but there are backups in the US (because of me).

Legoktm (talk) 08:30, 16 December 2022 (UTC)Reply[reply]

@Legoktm Open Collective sounds good if none of the WM Affiliates wants to proactively pick it up. --Zblace (talk) 08:53, 22 December 2022 (UTC)Reply[reply]

Correction needed?[edit]

The FAQ currently includes, Anyone can view all posts from users on our instance (the "local timeline"). Shouldn't that read "view all 'public' or 'unlisted' posts"? Surely the 'private' and 'direct' posts (I'm using the terminology in spec/models/account_statuses_filter_spec.rb here) cannot be viewed by non-followers or by non-mentioned (@) people, respectively? I don't know if you hacked the code to prevent private and direct posts... Boud (talk) 00:27, 21 December 2022 (UTC)Reply[reply]

@Boud: correct, it's just public posts, which I've clarified (please edit if it's still not clear). And for what it's worth, we're running normal Mastodon, with all the standard features including DMs. Legoktm (talk) 01:18, 22 December 2022 (UTC)Reply[reply]
Yes, it's clearer now. Boud (talk) 01:55, 22 December 2022 (UTC)Reply[reply]

Consider dropping the advertisement for Microsoft[edit]

Given the tyranny of convenience attitude that seems to be the spirit of active Mastodon developers, Wikis World sysadmins (not me :)) might want to consider shifting away from Microsoft (scroll down to View source code at the bottom left (desktop browser) of the /about page) to a community git forge, e.g. see [1], which points to https://framagit.org/framasoft/framapiaf . Even if most issues will have to be posted at Microsoft until there's a community shift (in order to have a chance of being handled) - just as some communities are still on the birdsite because the mass of people are still there - it would be good to at least point to community-hosted forks. I understand the time/effort costs of migration, but the attitude seems to be "we don't even want to open up or stimulate any discussion about how to migrate off Microsoft servers; if you're not an influential developer of Mastodon, then you'll just have to wait to see if and when we decide to migrate the system." Or wait a few more days to see if there any more constructive reactions...?

A patch or fork that edits line 21 of mastodon/spec/views/about/show.html.haml_spec.rb and lines 94 and 95 of mastodon/spec/presenters/instance_presenter_spec.rb , either with a new hardwired value or a value read from the host itself might make sense.

Independently, switching from joinmastodon.org to fediverse.party would be less trivial to change: grep -r "joinmastodon" mastodon/|wc gives 50 lines in a bunch of different files, all having this string (and w:John Mastodon might get upset ;)). Boud (talk) 02:34, 22 December 2022 (UTC)Reply[reply]

I'm sympathetic to your request, but unless these links are customizable in the UI somewhere, we don't currently have the technical means to implement this. Our hosting provider doesn't support any modifications to the Mastodon software. Legoktm (talk) 02:43, 22 December 2022 (UTC)Reply[reply]
The three lines with in show.html.haml_spec.rb and instance_presenter_spec.rb look hardwired to me. Boud (talk) 03:25, 22 December 2022 (UTC)Reply[reply]

Visual branding start[edit]

Instance looks super bare (default) and I wonder if WMF can recognize the effort and dedicate someone professionally for a few hours to part time in this so that it can go in direction to be green lighted for use of communal Wikimedia branding (not WMF logo) maybe with 'legacy' colors and develop own custom visuals? I know this is painful topic with WMF so I think going just colors and own visuals for start would be good...am I correct @QuimGil? -- Zblace (talk) 09:02, 22 December 2022 (UTC)Reply[reply]

More design resources and customization would be nice! One note is that we can only tweak things with CSS right now.
I would also like to clarify that this server is explicitly not a "Wikimedia Mastodon instance", it's open to anyone interested in wikis, broadly defined, hence "wiki enthusiasts". We already have a few accounts for non-Wikimedia wiki projects. Legoktm (talk) 07:54, 23 December 2022 (UTC)Reply[reply]