|The following section is preserved as an archive. Please do not modify it. The result was Move already started, so...
Earlier this year there was discussion and a vote about many changes, some of which ended up being implemented, while others weren't. For example, we voted to consolidate the sites, although due to technical reasons this hasn't fully been carried out yet. One of the proposals which got more votes than most other things have for a long time was ToaMeiko's proposal for a new host for Brickipedia. Even though the votes were overwhelmingly in favor of the proposal, it wasn't implemented and now, in December 2016, Brickipedia is hosted on the same server it was hosted back in March 2016 when Meiko's proposal was created. It goes without saying that obviously the problems that were present in March are still present in November.
As such, I would like to propose the following: let's move Brickipedia into ShoutWiki.
- Better performance. Site slowness, occasional timeouts, database errors, error 502/504 etc. are all too common and they're things that really shouldn't be happening at all. Needless to say that this is directly linked to the current server's insufficient resources.
- Financial aspect of things. As pointed out by Meiko in the March discussion, the current hosting costs quite a bit but doesn't provide sufficient return for the money.
- Long-term stability. ShoutWiki has been around for a long time and isn't going anywhere.
- More and better support. ShoutWiki's staff consists of MediaWiki professionals who have been working on the software for a long time. (Full disclaimer: I'm a member of ShoutWiki's Customer Support Team and over the years I have written numerous extensions and skins for ShoutWiki.) I'm also a sysadmin on Brickipedia and based on my experience over the past year or so, I can say for sure that ShoutWiki has more manpower on the technical front, which enables us to focus less on the operational side of things (i.e. "Is the site up? Why is the site so slow?" etc.) and more on improving Brickipedia via new content, new features and other cool things!
- And more features. Currently Brickipedia's running on MediaWiki 1.26.2, released in November 2015 which reached its end-of-life this November, on PHP 5.4.45 and due to the PHP version, it's not possible to upgrade Brickipedia to a newer version of MediaWiki without upgrading PHP, which is a prime example of an issue that's not going to happen on ShoutWiki. ShoutWiki runs MediaWiki 1.28, the current latest stable version of MediaWiki with many custom features to protect against spammers and the like.
- Security. ShoutWiki takes security very seriously, whether we're talking about something that is used on ShoutWiki or not. The recent security incident regarding the public exposure of database backups of sites hosted on Brickimedia's server underlines the importance of proper procedures to ensure the security of users' private information stored by Brickipedia.
- URLs — like Sir Tim Berners-Lee said, "cool URIs don't change", and they don't have to change in this case either (provided that the owner of the domain agrees, of course). ShoutWiki has plenty of sites using their own, non-ShoutWiki domain names.
- User accounts and wiki content can be imported easily enough. (Okay, so user accounts are always slightly tricky, but there is a script for migrating users between databases, so it should definitely be doable, though!)
- All the features you've come to love, from social tools to the Refreshed skin and beyond, they'll all be there!
Please leave any questions you may have in this section and I'll be more than happy to answer them! --Jack Phoenix (talk) 19:29, 21 December 2016 (UTC)
- By my understanding, what you're proposing is simply changing hosts? We can keep everything the way it is (unless people want it to change), but just be hosted on a different server? Also, will this move have an effect on our LUG support? I seem to recall someone mentioning we couldn't get it on wikia because we were technically part of a larger group that wasn't LEGO related (or something like that, someone with more understanding of the program please chime in here)
BrikkyyTalk 08:28, 22 December 2016 (UTC)
- I think you'd have to explain what you mean as "keep everything the way it is" and be a little less... completely vague, in your question. As for the LUG support, that's not something anyone from ShoutWiki can comment on. --Lewis Cawte (talk) 17:24, 22 December 2016 (UTC)
- Well, no, not everything will stay exactly the same. One of the reasons for the move is to get rid of things like the "out of memory" errors preventing edits and whatnot that multiple users — myself included — reported in early December. --Jack Phoenix (talk) 16:02, 23 December 2016 (UTC)
- Will look into the LUG support situation. --ToaMeiko (talk) 05:41, 24 December 2016 (UTC)
- Heard back from Kim and he says he doesn't see a change in hosting effecting our LUG support status, as we'll retain our domain and identity and control over that. --ToaMeiko (talk) 00:20, 11 January 2017 (UTC)
- How long would the move take? Soupperson1 Friends are Forever! <3
- The following answers are purely as a representative of ShoutWiki and do not in anyway reflect my opinions or views on Brickimedia or this topic -
- I've not been asked to assess this. In theory, not very long. The relevant databases can be imported in a matter of minutes. We'd then need to create the relevant settings files (various bits of copy and paste), as well as add some aliases to a couple of files to handle the web address. The more complicated part comes when we have to deal with merging the user database and any conflicts there. We've also got the image import to contend with, and work out how we're going to deal with all the images. In fact, that last thing is probably the thing that will require the most discussion a move happens - assuming it is supported. While I've not discussed this with anyone else on staff at ShoutWiki, I will on this rank occasion pull rank and say I'm not happy maintaining the current shared image setup. We may be able to do it as more of an InstantCommons style deal, but I will not have forced centralised uploads. --Lewis Cawte (talk) 17:24, 22 December 2016 (UTC)
- What's the setup on ShoutWiki like compared to Wikia? ie, is there any chance we're going to get new skins/"features" forced on us at any time? Also, what happens with ads- will the number/placement of ads change? NovaHawk 12:52, 22 December 2016 (UTC)
- The following answers are purely as a representative of ShoutWiki and do not in anyway reflect my opinions or views on Brickimedia or this topic -
- With regards to new skins and features. All wikis get a choice in their skin. We don't have any plans to force wikis to change their skins, I can't say with 100% certainty that we won't have to disable a skin in future for some reason or another. When it comes to features, we often enable extensions globally that apply to all wikis. These are often behind the scenes, staff or anti-spam tools, and very rarely features that affect editors or day to day users.
- Ads is a question I can offer less certainty on. There's an open task on our Phabricator for doing a review of our placements. What I do know is that we're ditching a few of the smaller, poorer (or non-performant) units because nobody really likes looking at ads. Saying that, our placements and styles vary between skins - we don't inject ads in to the content area and I'm fairly certain in saying we never will. We don't (knowingly) have any rollover or page-fill ads (or whatever the appropriate term is) on our site. As Refreshed is not a skin we currently offer - we'd have to convert it to use our ad serving extensions, however, we'd probably look at the current placements and work from those. --Lewis Cawte (talk) 17:12, 22 December 2016 (UTC)
- As a developer, I'd say that skins are quite stable these days. A much more likely scenario is that we'd have to disable a malfunctioning extension (*cough*I'm looking at you, MultiUpload*cough*).
- We already offer a lot of MediaWiki extensions and we plan on making more available, but it is not our intention to force these changes on any wiki. They will however be available should the community ever choose to enable some of them. Security is, of course, an exception — should a security issue be discovered with an extension, a skin or even MediaWiki core, we will review the report and act accordingly to protect ShoutWiki users, even if it would mean temporarily disabling the offending piece of code.
- Regarding ads and the Refreshed skin, the following Phabricator tasks on ShoutWiki Phabricator may be of interest: T89 and T99. --Jack Phoenix (talk) 16:02, 23 December 2016 (UTC)
- What level of access do current Brickipedia admins/sysadmins have in influencing development and features? I get that ShoutWiki is all about letting sites do whatever but I'd like to know what our restrictions would be. In addition, will our site be able to generate revenue to be able to sustain itself when it comes to non-hosting-related expenses? e.g. shipping contest prizes, review sets, sending members to events, etc? Or will ShoutWiki take any and all revenue the site generates in ads? It's been evident over the past few years that a donation-based funding system is not enough to sustain the website's expenses alone, so if we take away our ad revenue, that's not gonna work out. --ToaMeiko (talk) 05:45, 24 December 2016 (UTC)
- Access - the same as everyone else. In fact, that's wrong - you're already getting some special privilege with the amount of third-party code ShoutWiki supports for your wiki. You want anything else, well then there's Phabricator or osTicket. If we're really getting enough revenue to do those things already, then we've got the wrong priorities. But, I'm doubting the ad revenue even justifies the hosting costs at this point. I'll just refer you to NovaHawk's point. If you want an official answer from ShoutWiki, this isn't it. This is as someone who spent a fair bit of time as a sysadmin in the early days of this project. --Lewis Cawte (talk) 10:11, 24 December 2016 (UTC)
- Have you browsed through the help pages and other documentation on ShoutWiki Hub already? That should give you a nice overview of things. Additionally you might want to sign up (it's quick and free!) and try creating a new wiki. :)
- The question of features and their management is a good one, no matter where and how you're hosting your wiki. MediaWiki is highly extensible and you can do almost anything with it (it doesn't yet make your coffee for you, but for almost everything else, there's an extension!). The sad fact is that not all extensions are equal. The extensions used on Wikimedia sites are guaranteed to be mostly stable and functional with the given MediaWiki version (i.e. the REL1_28 branch version of, say, the Interwiki extension is pretty much guaranteed to work with MediaWiki 1.28); the same is true for certain other extensions, such as many of those that I maintain, which includes extensions used on ShoutWiki sites as well as social tools.
Then there are the other extensions that don't exactly fall into any of those categories. Their stability is questionable. Some — like MultiUpload — provide a highly desired feature, yet the extension keeps breaking like just about between each major MediaWiki release, and the fact it has no active maintainer doesn't help either. These kind of features are the ones you'd really want to avoid at all costs, if possible, because they make life a lot harder for you — whether you're running your own MW instance or not. Likewise, security is another important aspect to consider. The more unaudited third-party extensions you have installed, the bigger the risk, especially if you're not fluent in PHP and thus capable of reviewing the extensions on your own. The popular Tabber extension, currently installed on Brickipedia and several other MediaWiki wikis (even though it's somewhat unnecessary to install a separate extension for that because the same functionality can be achieved with a bit of CSS and JS without requiring any PHP for that) had a cross-site scripting (XSS) vulnerability for years until a new maintainer stepped up. But a new maintainer taking over an abandoned extension is a pretty rare occurrence, sadly. On a setup like ShoutWiki's, the importance of security is paramount, and that's why we need to review requested extensions and that's why we reserve the right to reject extension requests. --Jack Phoenix (talk) 17:15, 24 December 2016 (UTC)
How and where is ShoutWiki's servers hosted? Is it a single location? Or are there multiples based on geolocation? How powerful are the servers and how much resources can be allocated for an individual website? Do all ShoutWiki sites share resources or are the allocated individually à la VPS? What's the network infrastructure powering the servers? What kind of bandwidth can an individual website on ShoutWiki expect? Are the servers powered by backup generators in the case of a power outage? Uninterrupted power supplies in the event of power blips? --ToaMeiko (talk) 19:10, 24 December 2016 (UTC)
- Lcawte is more qualified to speak on the specifics, but I'll gladly shed some light on the matters I know about. It's not a VPS-like setup, because honestly I can't see how such a setup would scale. We host over 8000 wikis on the same codebase. Bandwidth has never been an issue and I don't see it becoming an issue anytime soon, as we have plenty of that. --Jack Phoenix (talk) 19:16, 27 December 2016 (UTC)
Could being a part of ShoutWiki increase our page views in anyway? e.g. increasing Google search results, etc.
BrikkyyTalk 02:07, 27 December 2016 (UTC)
- I think there's definitely the potential for that, yes. However I'm going to hold off on promising anything, because search engine optimization itself is a form of art — or (dark) magic, depending on how you look at it. One part of the problem is that "search" still largely means "Google", despite Bing and some other (smaller) alternatives. Google certainly seems to favor bigger hosts over smaller ones, hence why many moved wikis are struggling — honestly, you'd be surprised how many people use search engines to access sites they frequently visit (such as Gmail, YouTube, etc.) despite these sites having easily memorizable URLs. What we can do as editors is to keep creating quality content and promoting it via social media and co-operation with other LEGO fan sites, and thus get our name and URL out there, so that people will associate Brickipedia with good quality content, stability, etc. --Jack Phoenix (talk) 19:16, 27 December 2016 (UTC)
- Would it still be possible to make phab:T145302 possible if Brickimedia moves to be hosted on ShoutWiki? I'm guessing this task would be closed and transition into sw-phab:T131? SamanthaNguyen (talk) 22:56, 4 January 2017 (UTC)
- So I was
stalking CJC looking at some ShoutWiki wikis the other day and noticed that Wikisimpsons has an Answers site. I was just wondering if that was also hosted on ShoutWiki, and if so, if we'd be able to set up an Answers site of our own after the move? NovaHawk 02:13, 27 February 2017 (UTC)
- The wiki is not hosted by shoutwiki as the staff and intern groups are not present in Special:ListGroupRights. 2600:1000:B036:7339:F552:9135:EE56:BD95 02:39, 27 February 2017 (UTC)
Stuff from Ajr
I've put a comment in the oppose section below, as I personally don't think moving to ShoutWiki will help us much. That said, I'll do everything I can to make it happen (transferring domain name, etc) in the event that it does. Just a few of my own thoughts:
- The Brickimedia domain is doing OK. We're doing pretty well in search results, though still behind lego.wikia. But we keep picking up!
- If we had more people that could help out with social media, we could do better.
- If we further consolidated to get rid of Meta, that would be good too. Just have the one domain name, make it easier.
- We're doing fine financially! Sorry for not posting regular updates, but this year has recouped almost all of the money I've put into the site with no signs of slowing down. We've been getting payouts every month for the past five months, and are in the black by over $500 this year. No need to worry about that, and I can pump more into hosting and such. NBP - as I've said before, if you want a refund on your donation, just ask. I'm not paying interest though!! :P
- The usual apologies for not being around much :-(
Anyway, happy to answer any questions. Like I said in my comment below, if we want more community, I think Wikia is the place for that. It's always cool being on our own, but that requires a dedicated tech community that I'm not sure we have consistently (no offence intended). Ajraddatz (talk) 07:17, 29 December 2016 (UTC)
- I can help out with social media if you guys like. I don't do that much editing, it would be nice to help out in some way.
BrikkyyTalk 08:00, 29 December 2016 (UTC)
- I don't think our Facebook is updated very consistently. Twitter is (or at least was) a little better. I don't know who you'd talk to about getting access, but I'd be okay if you had it. (Also, thanks Ajr.) Berrybrick (talk) 15:00, 29 December 2016 (UTC)
- If anyone would like to help contribute to the Facebook, send me a friend request  and let me know who you are either in a Facebook message or on my talk page here and I'll give you access to the Facebook page. As for Twitter, just email me and I'll set you up with the login. Obviously use common sense when acting on our social media channels. Prior marketing experience is preferred but it's pretty simple to get the hang of. Just posting regular content with links to our site as often as possible will help not only the social media but our wiki as well grow. --ToaMeiko (talk) 18:21, 29 December 2016 (UTC)
- Hi Ajr, thanks for your comments on this! Some thoughts on your thoughts:
- The bigger the site, the better the visibility on search engines. It's nothing new, really. Big sites (like, top 500 or so) also tend to have contact people inside Google etc. whom they can directly get in touch with in the case of problems, whereas the rest of us will have to stick to using contact forms and whatnot. Sucks, but nothing much we can do about that expect to improve our content, get the word out there and have people link to us, using our sitename.
- Social media is big, so having a few people manage the Bricki(p|m)edia accounts would definitely be awesome!
- Meta (and the closed-but-stil-existing Customs and Ideas) is going to be closed eventually, but it's not exactly the easiest technical task to do.
- It's great to hear that the site isn't on the verge of bankruptcy! Even better is to hear that you're willing to invest more funds into the site. That being said, I don't think it should be necessary. The site should be doing well (from a financial point of view, that is) should an important contributor or contributors leave the site or disappear etc. for whatever reason(s). I'm not suggesting that you would do that, but over the years I've seen circumstances change rapidly and people come and go. We need Brickipedia to be here in 2026...2036...2046...you get the idea. Likewise, I can claim that in 2026 I'm still going to be around, editing Brickipedia, writing MediaWiki extensions and skins as I don't see myself quitting either of those anytime soon, but I can't know for sure. What if I get hit by a bus tomorrow? Life's full of surprises, both good and bad ones, and that's the reason why being prepared is essential.
- As for your comment about community, editors and Wikia, I must admit that — along with your oppose vote — I find it very surprising, to say the least. In early March you though it'd be "worth trying for a month" to move to a different server. I'm not exactly a math major or anything, but that proposal didn't exactly seem to be quite as thought-out as this is — 3-9 sentences is considerably shorter and more vague than this proposal — and that was something you as well as several other community members had no problem with.
But suggesting moving back to Wikia, even as a joke...oh boy, where do I start? I guess I should start by saying that this isn't an official answer on behalf of ShoutWiki and I'm only trying to represent myself, a Brickipedia administrator, a MediaWiki developer and someone who's been involved with wikis for over a decade here. A major argument against moving "back" to Wikia would be that we'd lose users instead of gaining any. See, Wikia likes to ban people (and later disable their accounts) based on accusations and implications rather than facts. I for one am rather fond of my ability to make edits to Brickipedia and despite the outcome of this discussion, or any other discussion for that matter, that's one thing I'd like to keep as-is; and I suspect the same is true for many other users of the site as well.
ShoutWiki's technological innovations, many of which I have authored or co-authored and which I maintain, are stable, well-written (note that this does not mean "bug-free" because bug-free software is impossible to create as people make mistakes) and used by many MediaWiki sites around the world, from Brickipedia to considerably smaller wikis, from ShoutWiki to various smaller wiki farms. ShoutWiki runs the latest stable version of MediaWiki, unlike many other sites running MediaWiki — including Wikia, wikiHow and even Brickipedia. --Jack Phoenix (talk) 18:27, 29 December 2016 (UTC)
- Brickia (or Brifandom powered by Wikia now I guess) has 164 accounts that have edited in the last 30 days. We have... 30. That's clearly where the community is, and I think I still have enough name recognition over at Wikia to give our community some favourable conditions of re-entry. It's certainly not a joke, anyway, though I do understand that people here don't like Wikia. Ajraddatz (talk) 19:42, 29 December 2016 (UTC)
- I'm pretty sure half of our 30 are globally banned at Wikia :P Many users decided to burn the bridges when we left... CJC95 (talk) 21:26, 30 December 2016 (UTC)
- The only users I know who aren't globalled are Sam, Ajr, Lcawte, CJC, and Cook879. The rest of us have been hammered. 9_9 The Princess Cave~ 20:50, 16 January 2017 (UTC)
- I'm reasonably sure I could get the global blocks lifted if we went back. If people want, I could investigate this further. Ajraddatz (talk) 10:09, 21 January 2017 (UTC)
- Can you get that in writing from someone at Wikia with the authority to make such decisions? Let's just say that I'm not very confident in a site where the paid staff like to ban longtime users on a whim and later on disable their accounts for no good reason. --Jack Phoenix (talk) 20:40, 21 January 2017 (UTC)
- This needs to be investigated before, not after. (Also agreed with Jack - this issue needs to be forwarded to the appropriate Wikia staff as well as discussed with) SamanthaNguyen (talk)
- Before we start begging for promises from the totally professional sounding "Fandom", shouldn't we see if there are even remotely enough users who would want to go back there? At least a quick poll. Definitely needs to be investigated if we're seriously considering this (but come on... we're not actually seriously considering this are we?) NovaHawk 22:43, 21 January 2017 (UTC)
- No, I'm not actually interested in going back to brickia (no way!) - That step you asked about should definitely happen before; somehow I completely forgot about, sorry. :P (I'm betting though that even if there was enough users, and the investigation happens to globally ublock everyone, that Brickians probably wouldn't be welcoming to let us integrate back in) SamanthaNguyen (talk) 00:39, 22 January 2017 (UTC)
- (edit conflict with Sam, who seems to have had similar thoughts) Yeah... I mean, I know a lot of the hate people had for Wikia at the time of the fork was overdone, but a move back is a tough pill to swallow. The name change to fandom, though perhaps superficially important, doesn't garner much respect. I don't know if the ads have exactly improved. Getting users here to try and warm up to wikia again would be difficult. And then there's the functionality... But one big thing I wonder about is how would we integrate with the community that's currently in charge of Brickia? I.e. Who from whichever site would get to still be admin, how policy/style/feature changes done since the move at both sites be reconciled, etc. Also, forget about Brickia being unpopular with the users here -- would Brickia even want to do a merge themselves? Any thoughts on this? 18.104.22.168 00:42, 22 January 2017 (UTC)
- Meant unblock (my response accidentally said globally block instead of globally unblock), just fixed that typo :) But yes, I agree with you anon. Ads are kinda crap, but I guess you can look at their most recent blog http://community.wikia.com/wiki/User_blog:Tedgill/Making_Ads_Better:_How_We're_Going_to_Do_It and judge for yourself (as well as others). Going back to Wikia means losing extensions too. We've already spent a lot of time to move away from Wikia, I don't feel like going back. I honestly bet Brickians wouldn't want to do a merge, so answering the previous questions is most likely a waste. (I'll think about them anyways, in case if the answer is actually a yes, but I still have doubts) SamanthaNguyen (talk) 01:28, 22 January 2017 (UTC)
- CJC95 (talk) 12:06, 22 December 2016 (UTC)
- Lachlan (talk) 13:34, 22 December 2016 (UTC) As long as we are still on the Refreshed skin and the adverts stay reasonable I think you should go for it
# We will need to find out how moving will affect our relationship with TLG before we move and contact them beforehand if it does change something. However I still think a reliable server and not having to worry about funding is better than free gifts from TLG- although they're definitely appreciated and it's a really great program LEGO has going, our site seems to be seriously underutilising anything we get anyway. NovaHawk 23:22, 22 December 2016 (UTC)
- @NovaHawk: But how active is our reviews section without LUG support? From my recollection it wasn't very successful. The biggest issue preventing us from getting more sets to users is shipping them across the country or internationally when we barely generate enough revenue to pay for that. Several users have paid out of pocket for that, but that shouldn't be necessary, especially since that severely limits which users can receive sets. Part of my proposal months ago to move hosting was to cut down on hosting-related expenses, but that didn't mean to cut down on income as well. Therefore, unless ShoutWiki can present how our community can generate income while being hosted on their platform, I don't think this is a good idea. Finances has been the biggest struggle this site has had from the beginning, and yes, while moving to ShoutWiki will reduce one area of expenses, if it prevents us from creating income to support any other areas of expenses our community has or might have, that's not a good financial decision in my opinion. --ToaMeiko (talk) 19:00, 24 December 2016 (UTC)
- While I definitely appreciate the support from LEGO, I'd argue that there are other obstacles to writing a review. Namely that it takes quite a bit of time to put together a good, interesting review, to take the pictures needed and postprocess them (cropping, adjusting the lightning, etc.) and finally submit it. I've bought some sets earlier this year that I've been wanting to review, but alas, unlike ordinary page edits or such, it's far more time-consuming to write a review.
While I don't know about the specifics of LUG support, it would certainly seem odd, to say the very least, if the site were to lose its LUG status over changing the host. The technical platform and its specifics should (IMHO) be irrelevant to LEGO — it's the content and the community behind it that matters.
We should keep Brickipedia's core mission in mind: to be a comprehensive LEGO encyclopedia. Editors need stability and safety in order to be able to make Brickipedia an even better LEGO resource; constant out-of-memory errors and inadequate technical resources aren't exactly helping the matter. --Jack Phoenix (talk) 19:16, 27 December 2016 (UTC)
- @ToaMeiko: (sorry for the late reply, haven't been able to get online for long enough to properly read this in the last few days): Well, since September 24 we've had 4 reviews, 3 of them due to LUG support (I'm using September 24 here because there seems to be a bug in the RC- I'm asking for the 500 most recent edits in the last 200,000 days and it's not going back any further). So, while LUG support does make up 75% of our recent reviews, I wouldn't exactly call 4 reviews in 3 months active or successful anyway. But as far as finances go- aren't we still losing money? So basically as far as I can tell, if we stay, Ajraddatz and other donors are paying out money but we have potential to make money if we miraculously get a stack of extra viewers. But if we move, we don't have the potential to be losing any money but worst case scenario, we don't have potential to make any money either. So I'm not exactly seeing any drawbacks here. But I have no idea how finances have been going over the last year or so, we could now be making money for all I know. Plus I'm terrible at finance and could be completely wrong about this whole thing :D NovaHawk 12:49, 28 December 2016 (UTC). edit: please ignore the financial comments, looks like it was wrong. NovaHawk 07:10, 29 December 2016 (UTC)
- If there's an updated version of this it could help this discussion.
BrikkyyTalk 06:55, 29 December 2016 (UTC)
- Sounds good. --CPPLAYER90210 T ~ C 23:44, 22 December 2016 (UTC)
- Per NovaHawk - I would advise contacting TLG before making any agreements/changes. I support provided the content that is imported which is the property of Brickimedia under the CC-BY-SA (not TLG content) still remains under the same license. Don't want everyone's hard work to be forfeited and un-credited by sources which like to duplicate the content of Brickimedia. SKP4472 (Admin) 14:50, 23 December 2016 (UTC)
- Changing content license is up to the community, and it is not something that can be done on a whim, as it basically requires consent from all parties who participated in the generation of the content. Therefore I don't forsee a license change happening anytime soon, if ever (with the exception of possibly migrating from the current CC-BY-SA 3.0 to CC-BY-SA 4.0, which some wikis — including Wikimedia wikis like Wikipedia, etc. — are considering). --Jack Phoenix (talk) 16:02, 23 December 2016 (UTC)
- Per Nova. Berrybrick (talk) 19:30, 23 December 2016 (UTC)
Originally support, but some interesting questions have been asked which made me switch to neutral -I know that this proposal was made with good intentions, and the idea is good as well, although I think I need some time to think about it just a little more. Alright, so maybe we won't get LUG support, but I agree with Nova - this opportunity I believe will help us much better in the long run. SamanthaNguyen (talk) 19:32, 21 December 2016 (UTC)
- We'd be better off on ShoutWiki than on our own, TBH. Rocko | The Princess Cave~
- As our LUG support will not be affected, I support moving to ShoutWiki. ShoutWiki is clearly more stable than what we are attempting to run here, and frankly I would like to be able to use the site again as it is dysfunctional. It would also be nice to keep our current domain name, since we've been using the name for almost four years now. LCF (talk!) 21:36, 25 January 2017 (UTC)
- Sure. Look like the site is still broken, we don't have a team of people willing/able to fix server issues here (see the typical Lcawte post below). I've cancelled the server payments, so we've got a month to work out the move off. Ajraddatz (talk) 05:19, 29 January 2017 (UTC)
#Waiting for more info.
BrikkyyTalk 04:59, 26 December 2016 (UTC) # If we can get a more reliable server and still stay independent, I'd be happier with that. I was under the impression we were losing a stack of money every month. Definitely oppose going back to Wikia though. As for search results- has anyone typed in an item number of a 2016/2017 set followed by "lego" into lately? We seem to be at the top as far as I can tell :S NovaHawk 07:10, 29 December 2016 (UTC)
- Latenightguy (talk) 00:50, 22 January 2017 (UTC)
- There does seem to be potential benefits from this move to ShoutWiki, but I believe that we need to make more people recognise and familiar with Brickimedia. (Currently the other Brickipedia seems to come before Brickimedia in google searches =/) Changing servers again might make them even more confused. Omega X (talk) 07:57, 22 January 2017 (UTC)
- Really? Whenever I Google search for any late 2016/2017 sets, we actually come up third (after Brickset and Bricklink). Maybe that's just me though :S Also, as far as I know, changing servers shouldn't have an impact on readers, apart from some possible changes to ad placements that Lcawte's mentioned. Our URL and pretty much everything else will appear the same (anyone feel free to correct me if I'm wrong) NovaHawk 09:46, 22 January 2017 (UTC)
- My apologies, just tried searching for Jestro's Headquaters and we are indeed third =P But when i tried searching for something more generic like lego 2017, the other one came first =/...if it depends on how frequent users visit a page we should have the edge here, the other one is pretty much dead =P Regarding the
- @Omega X: Everything the user will see will stay the same basically (which includes our URL), ads will be slightly different. Have you seen Brickipedia:Forum#Proposal to move domain to brickipedia.com as well as buy it yet btw? You should vote when you get the chance ;-) SamanthaNguyen (talk) 13:03, 22 January 2017 (UTC)
- Ahh I see..thanks for the enlightenment! Regarding the other proposal, I was not aware of it, but I have voted (you could probably guess what stand I took) =p
# I don't even care anymore. Images for the second wave Batman Movie sets are out- what can we do? Nothing. Nuremberg starts in about 24 hours, big chance for more viewers with new info/possibly images- what can we do? Still nothing. Wikia totally won't be gaining a lead on our search rankings for second-wave 2017 sets. Still think it's pretty stupid to not even consider other options (if going with ShoutWiki means we can't make money, it means we can't ship any stuff we receive from TLG to other people for contests/reviews and if the bid for the new domain fails we can't make a higher offer) but whatever. I'm over it. NovaHawk 23:31, 30 January 2017 (UTC)
- Despite there being potential upsides to this, I don't see it being worth the time and effort required to handle this kind of task. Brickimedia is far from a perfect wikifarm/host, but (no offense to ShoutWiki developers) I don't think ShoutWiki would be much better for us. If we want a perfect wikifarm/host, Wikia will be the closest we could get, and we didn't like that several years ago, hence why we're here. Being here gives us the ability to control so much more. So while our backend and server might not be perfect and does have its issues, being here allows us to fix that. Yes, ShoutWiki is probably less buggy. So moving there would solve some problems. But it would also make us lose some independence I'm afraid. With the time and effort it would take for our sysadmins to pack everything up here and move it to ShoutWiki, we could dedicate that time and effort to fixing some of our own bugs instead, which allows us to retain our independence. Why do I care so much about our independence when we're good friends with the guys at ShoutWiki you're probably wondering... Mostly from a financial standpoint which I believe I explained my stance on earlier in this page. Right now we not only have independent hosting but we also are independently funded. Thanks to Ajraddatz recent update to our financial reports, it's been shown that 2016 was our first profitable year. If you're wondering why I care so much about profitability when Brickimedia is and has been from the beginning a self-claimed non-profit organization, it's all about opportunity. With profitability, our opportunities are much greater than they've been in years past, such as when we were on Wikia and when we were unprofitable in our first several years of Brickimedia. Back then, despite our necessary expenses covered (hosting), we didn't have opportunity for much more and no opportunity for significant growth. Now that we're showing profitability, our opportunities here are greater. We have the ability now to offer activities to our community at no cost to members. Activities such as free review sets, contests, etc. Previously, shipping expenses for sets and prizes has either been paid out of pocket by myself or by the recipient, and this shouldn't be necessary. Our community should not be an expense to its members. Now that we have profits that can fund these activities, the opportunities are greater. We also have more ability to fund our operations. We could expand our server resources if that's still a concern to the community, or we could budget in marketing funds so that we can start utilizing paid advertising to reach new audiences and hopefully grow our user base. All of this and more is possible as of this year, and as we go on, I'm sure only more and more opportunities will be created each year. Moving to ShoutWiki though, we'll lose our self-funding. We'll go back to the state we were at for many years and not too long ago where merely our basic expenses (hosting, domain) were covered. In essence, I believe moving to ShoutWiki would be one step forward and a few steps back for us. --ToaMeiko (talk) 05:48, 24 December 2016 (UTC)
- Okay, I'll bite. Why do you consider Wikia the best wiki host? Is there a reason besides its fairly high Alexa ranking and user base? (I should note that while generally speaking "the more the merrier" is true, it takes time to turn newbies into productive contributors. Sometimes a senior contributor is easily worth ten newbies.)
"Independence" is such an abstract concept. One could relatively reasonably argue that if and when you're not running your own colo (and/or even the power plant for it!) you're not being "independent". Or maybe you are, but your servers are using Intel's backdoored CPUs...
All I'm trying to say is that "independence" is actually always somewhat of a trade-off. MediaWiki is free and open source software and there are a lot of "independent" wikis out there that use MW, but not all of them do a good job at it. Keeping MediaWiki updated, secure and spam-free isn't trivial; not doing that turns your site into a spambot magnet which is then used to relay even more spam. "With great power comes great responsibility", and sometimes outsourcing (parts of) that responsibility is sensible.
Relatedly, given my non-trivial involvement in all kinds of sysadmin matters on Brickipedia, especially from March 2016 onwards, I think I'm qualified to make some kinds of time estimates with regards to this proposal, and I'll say that fixing actual code bugs is a lot harder. Moving some databases and a bunch of files across servers is tedious, but very much doable. So no, it won't be the kind of resource hog you're afraid it'd be.
I hope that, whatever the outcome of this discussion is, more attention is given to the technical side of things. Rather than shelling out big bucks on ads, I'd rather see us focus on security, stability and upgradability. If we cannot keep our users' data secure in the first place, is there any point in advertising the site? With the increasing prevalence of security breaches — think of Yahoo!, for example — it's safe to say that this is a very real risk and one we're not able to outsource to anyone else (because we're independent, which also translates to "fix everything on your own if you want it fixed", which is actually a rather tricky thing to pull off with such a small team). --Jack Phoenix (talk) 00:56, 19 January 2017 (UTC)
- I agree with ashley. Wikia is far from being the perfect host, and this is coming from a girl who thinks her ban from Wikia is well-justified (the "joke" I cracked wasn't funny...). --The Princess Cave~ 22:49, 19 January 2017 (UTC)
I'm pretty much totally removed from the day-to-day here, but I would like to say a few things. First, the ad revenue generated by the site is currently enough to sustain our hosting and even upgrade if we so want. I'll release more info at the start of 2017, but we're doing pretty well in that regard, to the point that I think I've recouped all of the initial value I pumped in. My goal here is still not to make money, so if we want better servers or whatever I can pay for it. That said, I've still been watching the site, and the community isn't growing much. If anything, it's staying the same. I think that if we want to improve that, the place to go is back to Wikia. They have the search results and the infrastructure. It's the people that make these communities worth building, and I doubt we'll get more of that on ShoutWiki. All this said, it's nothing personal against ShoutWiki - I just don't see benefit in moving from one small host to another. Also, apologies for not spending more time here, but the interest has really gone I'm afraid. Glad to still pay for hosting though, because the site still has nostalgia value if people like using it. Ajraddatz (talk) 07:03, 29 December 2016 (UTC)
- See Brickipedia:Financial reports. It's gonna start messing with my taxes if this keeps up! Ajraddatz (talk) 07:12, 29 December 2016 (UTC)
- Per Meiko really. It kind of seems like people are jumping to "support" before it can all be laid out. Also, from what's been mentioned, it seems like moving to ShoutWiki could be a bit of a struggle. Additionally, if we're doing fine on the financial side of things it doesn't seem like a bad idea to simply upgrade to something that won't be so troublesome.
BrikkyyTalk 08:00, 29 December 2016 (UTC)
- Also, now that the possibility of moving to brickipedia.com is a reality, I'd rather see us do that over this. I know we could do both, but I think changing domains and using some of the money we have for a better host would be the best choice.
BrikkyyTalk 03:43, 11 January 2017 (UTC)
- Based on my decade of experience with (MediaWiki) wikis and almost a decade's worth of development experience, I doubt it would be as much of a struggle as you think it would. Database errors on page views, let alone edits, are quite a struggle too and they don't really help with page views and defintely don't impress brand new users who have never been to Brickipedia before. --Jack Phoenix (talk) 18:27, 29 December 2016 (UTC)
# This isn't an oppose against the move itself so much as thinking we need to step back and consider all our options, then take it to a vote when everything's been discussed (now that it appears that we have options since it turns out we've got money). Eg, would upgrading to a better server that we can afford fix all our errors? Is it possible to upgrade our version of PHP and how hard would that be for our sysadmins? (with what little experience I have with PHP, I do know it's not just as simple as hitting an "upgrade" button or anything like that). Is there anything we can do to improve our security? Again, I'm not closed off to the idea of moving to ShoutWiki, but I am just a bit worried about us getting locked into a wikifarm again then finding out later that we could have been doing better on our own. NovaHawk 01:24, 31 December 2016 (UTC)
- While I don't oppose your oppose (it's actually fairly sensible), I'll answer your points fairly quickly. Upgrading the server would fix some of the performance issues you've been having - depending on what the server "upgrade" is... your cache is still going to be terrible running through CloudFlare imo. Upgrading PHP (or even to HHVM) would be a lot easier if we were running on a decent Linux distro, not this garbage, ageing Debian. This could be fixed if the server moves to a new provider (RamNode tends to be garbage in most respects based on previous experience) Security is improved by having competent, active people on the "sysadmin" "team" who think before they do stupid things like symlinking the backups dir to the web root. In addition to that, staying up to date with the latest software releases - such as, but not limited to, OS and it's core software (tick), PHP & MySQL (tick) and MediaWiki + extensions (tick!). If people didn't realise, you got a tick for stuff not at the most supported release at Brickimedia. --Lewis Cawte (talk) 10:06, 31 December 2016 (UTC)
- Oppose Just from looking I can see that some of the extensions and skins that we use are not installed on shoutwiki. 2600:1000:B018:21DC:19E3:F7CC:A8A2:7A93 23:30, 18 January 2017 (UTC)
- Thank you for your concern. I'd like to note that there's a difference between "enabled by default for all wikis" and "enabled only on request". (The relevant help page has a bit more info about this.) --Jack Phoenix (talk) 00:56, 19 January 2017 (UTC)
- @Jack Phoenix: I did look at that page. I also looked at the skins page. 2600:1000:B031:202:2C96:ADC2:4508:1414 01:20, 19 January 2017 (UTC)
- Do IP addresses get a vote? It's been a while, but last time I was active here, you had to be a registered user... --Lewis Cawte (talk) 10:06, 19 January 2017 (UTC)
- They aren't so I striked their vote --The Princess Cave~ 22:49, 19 January 2017 (UTC)
- I know you had to be a registered user to vote for things like RFRs but I don't think there was anything relating to community discussions. Personally I have no issue allowing anons to vote on community things. If someone else remembers our rules please chime in
BrikkyyTalk 00:16, 20 January 2017 (UTC)
- I don't remember either, I do remember a forum a couple of years back about relaxing some of our requirements for voting on stuff. I don't know if that extended to allowing IPs and I can't find the forum. And like Brikkyy I can't remember if there was anything against IPs voting on stuff in the forums in the first place. However, striking votes has always typically been an admin's job so shouldn't be struck out by anyone. @Rock-O-Jello: if you can find a place where IP voting was discussed and point it out, that'd be great :) (and @any other admins reading- feel free to strike if you do remember) NovaHawk 02:01, 20 January 2017 (UTC)
- As far as I know there was never anything against that. --ToaMeiko (talk) 16:37, 20 January 2017 (UTC)
- I don't believe there was any either, and even if there was, it seems pretty silly (IMO) to restrict IPs from getting a say in a community matter (but I'm more than willing to discuss that with others too) SamanthaNguyen (talk) 21:51, 20 January 2017 (UTC)
- Well, one issue with IPs voting is that, technically, users could be getting in multiple votes without anyone knowing, unless checkusering occurs, right? Not that I think there's much of a trust issue in the community right now, but this is something to perhaps consider. 22.214.171.124 01:34, 21 January 2017 (UTC)
- Touché, but at the same time, it's important to consider wp:WP:AGF as well. In the event when there is evident or suspicion of voting fraud however, it can always be investigated if necessary. --ToaMeiko (talk) 03:05, 21 January 2017 (UTC)
- That's the main reason. Is there any particular reason IPs aren't signing up for a user account? As we know, in most parts of the world, ISPs do not assign IPs statically, so many people can have edits across a whole range of IPs, which may have been used before. --Lewis Cawte (talk) 11:19, 21 January 2017 (UTC)
- I'm not opposed to unregistered users commenting on things, but it does seem a bit suspicious, to say the very least, when their first edit is an oppose vote on an important community discussion. Also I'm not sure if an anon's vote should be considered as important as that of a registered user; if they want to seriously participate in this community, creating an account is quick and free.
That being said, I disagree with this anon's oppose vote — as a MediaWiki developer, as a ShoutWiki developer and as a Brickipedia system administrator. Extensions and skins are simply not going to be an issue, plain and simple. I'm aware that some of the related documentation is a bit outdated, but to my knowledge, all of our major extensions are either already offered on ShoutWiki (SMW, social tools, etc.) or can be made available at request. --Jack Phoenix (talk) 20:40, 21 January 2017 (UTC)
We are in a decent position, financially at least, and one of the biggest concerns appears to be that the community is not growing. If that is the case, I feel that a greater social media campaign would benefit us (Yes, I realize that it has failed before, though it still is a valid solution). If we can continue to do things 'our way', why should we stop? Latenightguy (talk) 03:27, 19 January 2017 (UTC)
- Who said anything about "stopping doing things 'our way'"? The way I see it, this proposal is more technical than anything else in nature. I'm not sure why you'd want to oppose what is undeniably a clear improvement over the status quo (not being able to submit edits due to OOM errors, etc.). --Jack Phoenix (talk) 20:40, 21 January 2017 (UTC)
- Honestly, I wrote that just to make it seem as if I were justified. I am completely for the move of Brickipedia to an improved server. I have experienced these issues and at this point, if this is the result, I would not oppose it. Latenightguy (talk) 00:50, 22 January 2017 (UTC)
Oppose: I can understand how moving to ShoutWiki could help us financially, but I also believe that our LUG status is helping us out at the moment. I certainly don't want to move back to Wikia either, as was pointed out that most of our users have burned the bridges and are globally blocked there, myself included (I myself have two concurrent permanent global blocks there). LCF (talk!) 21:28, 22 January 2017 (UTC)Moved back to support
- Meiko's already confirmed that our LUG status will not be affected if we move to ShoutWiki NovaHawk 22:42, 22 January 2017 (UTC)
- Right, I must have overlooked that. In that case, I suppose I will move back to support. LCF (talk!) 21:31, 25 January 2017 (UTC)
- I know, I've jumped around a lot, sorry for that. And I know this isn't going to make much difference. But to me with the financial situation, this move is just plain dumb. We're going from making $550+ a year to losing $10 a year. Not to mention giving up our independence- if we don't like ShoutWiki, we're not really going to be able to move off again, we'll be stuck there. With the money we're making we could upgrade our servers to make things run, and if noone on the technical team wants to do anything anymore because we don't move, surely someone somewhere would take $300 to look after our site (I know it's not much, but just think about all the people who do this for free). We could ship stuff we get from TLG to people (without making any money, that isn't going to happen). If our bid for brickipedia.com doesn't go through, we could continue to make more money and take another shot at it some other time. But if we move, we're locked into permanently losing $10 a year with no way out. NovaHawk 21:43, 9 February 2017 (UTC)
- The issue right now is more on my side. I'm able/willing to pay for the hosting, but I can't handle the technical side of the site. Right now, the issue isn't RAM-based - we're currently running at a fraction of our capacity. Something else is wrong, and I have no idea what, and we don't have enough engaged technically-minded people to help out. The ShoutWiki folks obviously have no incentive to try and fix the site here. I agree that it's quite ridiculous that they are unwilling to pay for the domain name. Finally, the poor site performance is having a very strong and negative impact on our finances - we're on track to make under $30 this month because of it. Ajraddatz (talk) 22:37, 9 February 2017 (UTC)
- I haven't been able to uninstall SMW (Composer, a package manager, along with the SMW family of extensions, is quite an ass to work with); If I was able to figure out how to I would've done it a while ago but I already tried and no luck so far. For the record, Composer isn't the traditional way to install things and it should be through LocalSettings by setting a
wfLoadExtension (and its' respective alternate,
wfLoadExtensions( array(...) );, but SMW has to be installed/uninstalled through Composer (for whatever reasons). SamanthaNguyen (talk) 00:30, 10 February 2017 (UTC)
- But we've had semantic mediawiki for years without issue. Why does it randomly break mid-January? That's the crux of the issue here; we don't have the human capital to figure out what is wrong and fix it. Ajraddatz (talk) 00:54, 10 February 2017 (UTC)
- Now I know it's not a memory thing, I did a 30 second Google search. It looks like the big problem is caused by SMW not having the permissions to CREATE TEMPORARY TABLES and DROP- is there any chance either of you could check that SMW still has permission to do these? NovaHawk 01:18, 10 February 2017 (UTC)
- @Ajraddatz: @SamanthaNguyen: ^ NovaHawk 23:32, 11 February 2017 (UTC)
- By default, SMW will give permission for both of these query actions. SMW still has permission to do this, otherwise, this would be in LocalSettings.php (which isn't in currently):
$smwgQSubcategoryDepth = 0;
$smwgQSubpropertyDepth = 0;
$smwgQFeatures = SMW_ANY_QUERY & ~SMW_DISJUNCTION_QUERY;
$smwgQConceptFeatures = SMW_ANY_QUERY & ~SMW_DISJUNCTION_QUERY & ~SMW_CONCEPT_QUERY;
- SamanthaNguyen (talk) 15:44, 12 February 2017 (UTC)
- Thanks for checking anyway :) The only other thing I've come across with for people having the same problem is that the buffer size might need to be increased: ,  NovaHawk 00:59, 13 February 2017 (UTC)
- I know my opinion doesn't count for much, considering that I haven't been active around here in quite literally, years, but nonetheless, I think that staying independant is the way to go. No matter the problems, it is still better to stick with a known bad solution, than to opt for a potentially worse unknown one. Just my 0.01c. LK901 00:02, 5 April 2017 (UTC)
Let's close this and make it happen
Per title. Obviously the site isn't working right now, which seems super convenient that it stops working as soon as this proposal is made. But whatever. Just make it happen. Ajraddatz (talk) 19:07, 5 February 2017 (UTC)
- So the proposal happened when it did because Jack decided to propose it at that point. Although I've not looked, I've worked with Jack long enough to trust that nothing's been changed on the backend. Not sure what killed the site when it did, but it could be a combination of many things.
- As to making this happen - you mentioned you've already cancelled the server? When's the renewal date? What time limit are we working to? I could do with access to the DNS (login, transfer, or set us as your nameserver, I don't mind, they all work) to help make the switch when it's time to go live. We've already got root access to the server, so that much is sorted and we should be able to move you guys over as soon as our server upgrade finishes. --Lewis Cawte (talk) 10:56, 6 February 2017 (UTC)
Will ShoutWiki be taking over financial responsibility for our current domain? Will they get us brickipedia.com as well? And has the GBC community been involved in any of this discussion? Because they're going to need to be moved as well. --ToaMeiko (talk) 18:14, 6 February 2017 (UTC)
- As a company, no, we won't be taking over responsibility for the $10 USD/year renewal fee for your domain. If Ajr wants to transfer the domain, I might offer to take it on personally. I've always been open to sniping brickipedia.com/org, I've always been open to that, but as an individual. I'm certainly not going to appease whoever is squatting those domains by paying the stupid prices they want. And if you've not noticed, the discussions so far are something along the lines of (and this is a rather crass simplification) -
- Ajr: Well, we've got no ops volunteers. I'm out, server's cancelled, get moving to ShoutWiki.
- Ajr: (a few days later) Let's go!
- Me (Lcawte): What's our timeline.
- That's all the discussion as of this point. If you think there's anything in particular that GBC needs to comment on, feel free to go and notify them to join the great discussion we're currently having here. It's not like we're just going to leave them on this server and watch it expire... --Lewis Cawte (talk) 23:20, 6 February 2017 (UTC)
- We have the domain for another year as of today, and we have the server til the end of the month. So there's your timeline I guess. Ajraddatz (talk) 23:55, 6 February 2017 (UTC)
- So the server expires on the 28th of February? Ok, well I guess I can leave Jack to do any prep, and we'll work on the move when I get back from Switzerland on the 21st. I'll probably get a more firm timeline out tomorrow as I've got the day off. --Lewis Cawte (talk) 11:52, 8 February 2017 (UTC)
- So ShoutWiki, a "big" wikifarm company that claims they're going to have extensive enough resources for us to never see an error again, and vigorously argues for us to move there, and leave us without any hosting expenses, can't afford to take over the $10/yr renewal fee for our domain? Nice, 10/10 --ToaMeiko (talk) 00:07, 7 February 2017 (UTC)
- George, it seems the more you comment, the less I want to do nice things both in a personal or "official" capacity for Bricki(m|p)edia. We host 8300 sites. Sure, we can afford a $10/year domain. We can't currently afford $83,000/year in domain fees. Which is why we only offer the option to use your own domain. --Lewis Cawte (talk) 19:11, 9 February 2017 (UTC)
- How many of those sites moved onto ShoutWiki and can be making more than $100 in ad revenue a month? Even Wikia was willing to take over the domain names of some sites. Ajraddatz (talk) 21:17, 9 February 2017 (UTC)
- Brickipedia is proven to generate ad revenue. So by you acquiring us, you're acquiring a financial asset. And you're saying that you can't take some of the money you'll be making off of us and use it to carry our domain over? And if we stop maintaining our domain, our currently-strong search rankings will diminish since it'll take Google quite a while to find our new domain (and when they do, their anti-plagiarism algorithms will likely interpret the ShoutWiki site as a mirror of en.brickimedia.org and as a result rank it low in searches), and you'll start to lose ad revenue off of our site. If you want to maintain the revenue our site generates, you'd want to keep our domain. It's common sense. --ToaMeiko (talk) 03:44, 10 February 2017 (UTC)
- ^ Err... if we can't make any money if we're on ShoutWiki, how exactly are we meant to maintain a domain? NovaHawk 00:59, 7 February 2017 (UTC)
- Couldn't we just move to Lego.shoutwiki.com ? --The Princess Cave~ 02:24, 10 February 2017 (UTC)
- That sounds like a horrible idea and the LEGO Group generally doesn't appreciate (and sometimes issues cease and desists for) websites using "lego" in their name. We couldn't really do anything about it at Wikia, but now we own our own domain. It's just rather silly that we'd be giving away our monthly earnings to ShoutWiki without them covering our domain name. --ToaMeiko (talk) 03:44, 10 February 2017 (UTC)
- ShoutWiki posts ads to pay for the hosting, I think. --The Princess Cave~ 18:28, 8 February 2017 (UTC)
- They profit off of them, their ads do more than pay for hosting. --ToaMeiko (talk) 03:44, 10 February 2017 (UTC)
ShoutWiki's back up again, we can move now, right? --The Princess Cave~ 18:28, 8 February 2017 (UTC)
@ToaMeiko:: Do you have contact with the guys at GBC? Their DNS will need updating as well if they want to continue to use their domain. --Lewis Cawte (talk) 12:00, 26 February 2017 (UTC)
- http://greatballcontraption.com/wiki/User:ALittleSlow is the owner of that domain. 2600:1000:B02B:1E80:BC67:A5EB:FA20:2279 18:50, 26 February 2017 (UTC)
- Ajr will probably have their email address, I personally don't have their contact info outside of the wiki. Perhaps try Special:EmailUser/ALittleSlow --ToaMeiko (talk) 18:05, 28 February 2017 (UTC)
- @CJC95: @Lachlan: @CPplayer90210: @SKP4472: @Berrybrick: @Edward Nigma: Hey guys, haven't seen you around in a month or so. Just wondering if you would mind possibly restating your support- circumstances surrounding this potential move may seem somewhat different to when you originally voted. Please note I'm not trying to change your minds or anything. I'm just a little on edge that we somehow seem to already be moving forward on such a huge decision even though the vote is 9/4 (well... Ajr just seems to want it over with, it could be interpreted as 8/5)- even something as relatively inconsequential as admin votes require a higher ratio of support. I'd just be a lot more at ease knowing that you are all actually supporting whilst knowing the facts that have come to light after you voted. Thanks. NovaHawk 23:32, 11 February 2017 (UTC)
- I've been following the discussion, and I've changed my vote several times. Perhaps it would be a good idea to restate my support, but I haven't seen anything that might make me think twice (again). LCF (talk!) 06:03, 12 February 2017 (UTC)
- No that's totally fine, again sorry for even asking this, I know it could seem like I'm asking you to change your vote or something NovaHawk 07:51, 12 February 2017 (UTC)
- I'll re-read the thread either today or tomorrow [its only luck that I saw this, as the ping didn't seem to work]. CJC95 (talk) 16:51, 12 February 2017 (UTC)
- definitely tomorrow nova. Sorry. CJC 126.96.36.199 22:45, 14 February 2017 (UTC)
- I really don't know. Sorry. (Also, ping didn't work. What CJC said there.) Berrybrick (talk) 02:36, 14 February 2017 (UTC)
- Well, I don't feel like there is much to add from me in terms of actual useful discussion.
- Its clear that the current set up has issues (half the reason I stopped paying attention to this discussion is when I came to check it wouldn't load).
- Its clear that while in an ideal world we could fix those issues here, we don't have the resources/people to do so effectively.
- There is no denying our sysadmin team is for practical purposes identical to ShoutWiki's.
- There is a weird tension (well, its fairly clear where its coming from I think) above which I feel has perhaps driven the discussion into a more vitriolic one than it should have been.
- Ajr has clearly set this in motion no matter what I comment here.
- Finally, I find it hard to judge this clearly, because my ties to ShoutWiki are both familial and development related.
- So I guess my position is unchanged? I wish I could say I felt strongly either way, but I don't really. Sorry Nova (and anyone else who cares, but as with most things around here its probably only Nova who really cares.) CJC95 (talk) 22:45, 15 February 2017 (UTC)
- Nope, all good, it's just that there has been a lot of discussion lately and wanted to make sure everyone who's been away for a while knows what's going on, that's all :) NovaHawk 02:04, 16 February 2017 (UTC)
Sorry I just dip in and out here so I guess my opinion shouldn't have as much weight as those that edit all the time. My strongest feelings are: whatever happens I would like to see the domain name kept, whether it be brickimedia.com or .org as it immediately makes this website more visible than the Wikia version. Secondly if the ShoutWiki move didn't happen and Bricki moved back to Wikia, I will not be editing here again. Sorry but my experiences of being an admin on, and subsequently forking, a Wikia wiki mean I will never support the company.
The fact that ShoutWiki can't pay for the domain name is annoying. I don't know anything about the finances here but surely Brickipedia makes more in advertising than the £10 a year or whatever it costs to keep a domain. There is also the issue of if Bricki decides to leave ShoutWiki in the future, would ShoutWiki sell back the domain name? I know Uncyclopedia got screwed over by Wikia who refused to sell them back the domain name.
Ultimately I think we can all agree the service would be better if it were hosted on ShoutWiki. So I guess it comes down to whether someone is willing to pay for the Bricki domain out of their pocket, since ShoutWiki have made it clear they have no interest in acquiring the domain. Sorry I know what I've just written isn't a vote either way. Count me as neutral but keep in mind what I said above. Lachlan (talk) 09:18, 17 February 2017 (UTC)
- I mean, I did mention that I need DNS access to make the move happen - and I said a transfer of the domain to me would make it work. So I have indeed said, as an individual person I will take on the cost of the domain. --Lewis Cawte (talk) 21:03, 17 February 2017 (UTC)
- that's cool, so when are we moving? The Princess Cave~ 23:24, 8 March 2017 (UTC)
- You can follow progress reports Here. We'll be releasing more details in due course. We're testing the scripts to migrate Bricki users over and making tweaks where nessesary. Note a full test is still pending and waiting on myself not being at work and Jack being free from Uni commitments at the same time for at least a couple of hours which isn't particularly easy this week. We've also been working on getting the email working here on Bricki again because we need to send out some details to users via email. The linked page will be in the Sitenotice when we've got a more confirmed timeline (which'll be when testing is done so we can set things in stone) --Lewis Cawte (talk) 09:40, 9 March 2017 (UTC)