Welcome to Wikilivres!

Project:Community Portal/en

Free texts and images.
Jump to: navigation, search

Add a topic

Forums: English · French · Polish · Russian · Spanish

Visit the Community Portal Archives


Bibliowiki hosting

We should have a community-wide discussion about our long-term hosting plan. I am willing to help financially and logistically as I can but note that I am located in the United States and I am an American citizen. First off: do we have any Canadian resident editors here who are interested in this responsibility? Koavf (talk) 07:45, 12 August 2018 (UTC)

I'm not sure why one needs to be a Canadian citizen to host content in Canada. I'm certainly not (Canadian) and it is the easiest thing to deal with VPS cloud providers (there are many operating in Canada). Our current host is SSDNodes.com and we have a great deal with them ($9.99/mo), but they full and cannot provide additional resources. Amazon AWS is offered in Montreal, both EC2 and now LightSail. All of these do require technical knowlege in setting up and securing a server (which is not trivial). Note that there is one Mediawiki-specified host in Canada which offers MediaWiki hosting, though it is not clear the extent of support provided. Should be worth contacting them: https://www.mezzohost.com/webhosting/mediawiki/ --Sysadmin (talk) 04:28, 13 August 2018 (UTC)
Note: Koavf's post was prompted by a message I sent to all donors of Biblio.wiki, as follows:
Hi guys,
On Nov 1st, I'll be shutting down the virtual private server that has https://biblio.wiki hosted on it. After that, I will not be running any servers that will be able to host Biblio.wiki. This means I'm getting out of the Mediawiki hosting business, and that means the Biblio.wiki website will need to find another virtual home (or take over the current account at SSDNodes for hosting) at that point, and also someone to do the maintenance on it.
Unfortunately I don't have any recommendations to make regarding who/where to do the hosting and maintenance. People who have read the technical and policy discussion pages are already familiar with my consideration of the viability of the platform (not good). Unfortunately, those few who are active on the site generally use the functionality that makes it uniquely Mediawiki, especially running bots and the djvu-support.
Right now the site uses 37gb out of a 40gb limit, which is not sustainable. File growth is a major issue on the site as it is currently configured. I've tried to think of various ways around it, but I find I simply don't have the time to try and deal with this properly, and provide the support the project needs to remain healthy. My lack of time is partially due to the fact that at home we have a growing 8 month old child, in addition to our 2 year, 9 month old child.
I started helping out this project about 18 months ago and we did get some level of uptime going for a system which had shut down and all that was available was data backups. It is now time for someone else to take on the opportunity to serve the Biblio.wiki community in this way. I appreciate all the trust and patience you have offered me over the previous 18 months to help out in this technical capacity.
November 1st is a hard deadline, so getting to work and doing a transition/migration earlier than that is wise.
Please use the bibliowiki site to discuss this issue and it will be a community decision on whom will get the technical keys to the kingdom, with all who contributed finanically so far, to have a vote.
- wiith regards, --Sysadmin (talk) 04:32, 13 August 2018 (UTC)
To say the truth I am puzzed what to say... My hands slipped... I am not familiar with servers and hosting. I am pretty good with editing only. I have not idea what to do at the moment. Maybe it would be a good idea to move on a free wiki farm like Miraheze? But it is an American firm... Or transfer our content to wikilivres.ru, as I proposed in previous time. Electron   10:19, 18 August 2018 (UTC)

I am puzzled by the claim that "those few who are active on the site generally use the functionality that makes it uniquely Mediawiki, especially running bots and the djvu-support." I am one of the most active users and have never used either function. All I need is the ability to upload text, ideally with certain formatting capabilities such as bold and italic. Thus I would be quite content not to continue with wiki software. I would have some problems with trying to use wikilivres.ru, as the interface is in Russian. Who owns and operates this site? Does Russian copyright law allow for a 50 year cut-off? --Poetlister

For me Mediawiki is essential. I have to say it: no Mediawiki, no my work... I have no time to learn new type of wiki and change more that 30.000 pages to fit them new type of formatting. Wikilivres.ru is run by Dmitrismirnov. It was not against about our moveing to the site. Main interface every mediawiki can be changed to many languages in yours preferences when you are logged in. I suppose Russian are not as strike to copyright rules as others, so we would abide our previous rules... But if you have better proposition I am not against... Electron   11:49, 19 August 2018 (UTC)
Russia has a Life+70 copyright regime, which would make most content illegal if hosted on wikilivres.ru, unfortunately. If they moved hosting to Belarus that would not be an issue (and Belarus has many hosting options), since that is one of the last remaining countries in Europe with a Life+50 copyright regime. Mezzohost as mentioned above is a Canada-based Mediawiki-specific hosting company. I would think finding out their options would be a good step forward. P.S., note that the Miraheze.org site is hosted in the Netherlands, a Life+70 regime. --Sysadmin (talk) 03:43, 20 August 2018 (UTC)
Also note that Miraheze.org does not have the Proofread extention, which is basically the main impediment to migrating to a different wiki platform (dokuwiki), see: https://meta.miraheze.org/wiki/Extensions --Sysadmin (talk) 03:52, 20 August 2018 (UTC)
Maybe they install it on our request? If it is important for us... See: If you would like to enable other extensions on your wiki that you don't see on this list, please make a task on Phabricator. -> ManageWiki#Extensions Electron   11:21, 20 August 2018 (UTC)
Well, I am not against Belarus... But, well... it is not democratic country and the country of law. Less than Russia, to say the truth... But if there is no better alternative... Electron   11:13, 20 August 2018 (UTC)

That site is not hosted in Belarus. Sysadmin was just saying that if they moved to Belarus we would be OK under the 50-year rule. I am quite happy with Mezzohost.--Poetlister 19:54, 21 August 2018 (UTC)

Looks not bad. They offer price starting at $29/year and a 15% discount for non-profit organizations and community groups. But I haven't found their regular prices... Electron   10:25, 23 August 2018 (UTC)

I've called and written them several times with no response. Koavf (talk) 04:02, 27 August 2018 (UTC)

I made some enquiries via the Wikipediocracy.com website and had the following response from User Dysklyver there. If it is helpful, I can put you in contact. (He tried to create an account here but could not; I told him to e-mail info@biblio.wiki. He also notes that Special:Version is missing. In fact, it is ther ebut can't be seen when logged out.)
I am quite the expert in setting up MediaWiki now, I have done 11 sites and multiple complex installs such as wikibase etc, if you guys need help moving server I am happy to assist. AWS and Google Cloud offer Canadian hosting, the system admins do not need to be Canadian. My recommendation would be to use one of these.
I would not recommend a Mediawiki specific server farm such as Mezzohost - you could use it, but I strongly warn you not to. Without root access you will have problems with extensions and file hosting. Although I joke about maybe hosting my blog in Russia, this is far from ideal and should be avoided, as really should Belarus. Miraheze is not an option currently due to extensions, it is entirely US based and not an option due to copyright. Google Cloud allows for easy drive expansion, AWS is not so good at this, since their pricing and services are comparable I would suggest Google Cloud, this is where I host World Wiki.
Your existing package that costs $9.99 a month is very cheap compared to Google's quoted $28 a month. It could be beneficial to offload image storing to another server and keep your current package.
In conclusion I think the best idea would be to host all the images, divj's etc in a flat file system separate to the server. This is reasonably easy to setup with something like Extension:CloudStorage.
  • I have registered here now, my current thoughts are that there are four clear options:
  1. Remain using the current package and limit the number of files to avoid running out of storage.
  2. Move the wiki to a larger server which would be more expensive.
  3. Move the wiki to a split format where the images are in an expandable cloud storage system and not on the server.
  4. Move the wiki onto someone else's infrastructure.
If that helps. Dysklyver (talk) 16:54, 3 September 2018 (UTC)
Note that AWS just cut their Lightsail VPS prices in half, and they do have Canada locations. This I think is the best approach, except for just keeping the site where it is. While we do have 4 processors and 8gb of ram, I've never seen it go above 4gb of ram so my guess is the other 4gb isn't really accessible. Lightsail is a much better deal than EC2 because it includes several DNS zones, a whole lot of throughput/bandwidth, and storage space. As long as Bibliowiki has the technical skills to keep their own installation up and running, then staying on SSDnodes or moving to Amazon Lightsail seems to me the most viable VPS hosting.
Poetlister's and Dysklyver's thoughts on dealing with images using an external location (as one option) mirror my own, though some clever compression might make that less critical (I've not yet addressed the compression issue, running compression tools against the file system, though it does have promise). It is reassuring that some of the editors have the technical skills needed to keep this project going, which I was not aware of up until now. --Sysadmin (talk) 15:09, 10 September 2018 (UTC)
With the current host, it appears to be possible to upgrade the current server from 40gb to 80gb. However, the new plan is $167.99 annually (payable upon upgrade). This would basically solve the biggest issue which strikes every few months when the server runs out of space. It is also not much more than we pay currently ($14/mo vs. $10/mo). We have maybe $20 or so in the current donations (I have to do the accounting, there were some recent donations), but I think it might be possible to find an external sponsor who could pay effectively $120 for the year for a few links/name recognition as a sponsor. Let me know the thoughts on this. Editor/admin donations barely keep up with current expenses. --Sysadmin (talk) 05:14, 23 September 2018 (UTC)
There are complications with upgrading the host. The virtual server technology for their current offering is different from what we are currently running (OpenVZ vs. KVM), therefore there is no painless upgrade path. It would require backup and restore of files, but also reinstalling the operating system and configuration. We really need someone to step up and take over the role/function/responsibility of Sysadmin, to do this kind of work. --Sysadmin (talk) 07:18, 27 September 2018 (UTC)

I think "a few links/name recognition as a sponsor" is fair enough. I am happy to make a significant donation once the new system is up and running.--Poetlister 19:59, 28 September 2018 (UTC)

As Dysklyver has said already, he is happy to be sysadmin. However, he declines to handle the finance. Really, we need someone in the right country to do that.--Poetlister 16:48, 1 October 2018 (UTC)

Clarification of copyright status and another question

Although I am a Canadian, (from Québec), I know nothing of our Copyrigt laws. I want to upload Lenin, God of the Godless by Ferdinard A. Ossendowski. The book was originally published in 1931 and someone from the USA renewed the Copyright in 1958. Does the book qualify for upload?

Also, I would like to install here my en.Wikisource proofreading tools like Common.css, Common.js and some other .js tools. - I am OK if some won't work, but I don't want to cause a problem.

common.css

common.js

typoscan.js

Thanks in advance for any clarification. Ineuw (talk) 21:45, 22 September 2018 (UTC)

@Ineuw: Copying your preferences is fine. When did the author die? Koavf (talk) 01:00, 23 September 2018 (UTC)

Ferdynand Antoni Ossendowski in 1945. Ineuw (talk) 01:03, 23 September 2018 (UTC)

Do you need the Sysadmin to do anything regarding preferences? I think that this is something each user can do and change as they need individually, let me know if this is otherwise and you need me to do something. --Sysadmin (talk) 05:01, 23 September 2018 (UTC)
Regarding copyright, the standard Canadian law is Life + 50 years, though there are many special exceptions under Canadian law. Generally speaking (if no exception applies) the work you mention is in the Public Domain under Canadian Law. Note that the version you link to is out of an Indian library, where it is life + 60 years. My only question is, why upload the book here if it is already in Archive.org? --Sysadmin (talk) 05:01, 23 September 2018 (UTC)
@Sysadmin: Thanks for asking about my work environment. I have everything necessary. As for uploading Ossendowski's book, is it not the purpose of Biblio.wiki where we can install and proofread books which cannot be uploaded to the Commons/Wikisource because of US Copyright restrictions? Also, the email address selector in Preferences/Notifications leads to a non-existent page. Perhaps my current email address is missing? Ineuw (talk) 03:16, 25 September 2018 (UTC)
@Ineuw: Yes, your purpose to proofread is definitely one we support at Biblio.wiki. For the email functionality, that has not been implemented but definitely needs to be on this Wiki. All the best. --Sysadmin (talk) 04:07, 26 September 2018 (UTC)
Thanks.

It looks like we really need to re-host outside of Canada

  • In that case I vote for Belurussia. I don't see special problems with this country, also I can do all neccessary communication with provider, if needed. They speak Russian and English also will be no problem, I think. — VadimVMog (talk) 05:22, 2 October 2018 (UTC)
  • OK , but could you point out some good provaiders in this country? Electron   10:06, 2 October 2018 (UTC)
  • I'll make a small research, talk with some Belorussians. — VadimVMog (talk) 15:54, 2 October 2018 (UTC) By the way, please remind me what functionality a provider must have? — VadimVMog (talk) 16:18, 2 October 2018 (UTC)
I'll just point out that the country is now usually called Belarus in English. Simon Peter Hughes (talk)
It's because in Soviet times it was Belorussia, now it is Belorus, and I still call it Belorussia out of habit. It's difficult to remember all those renames, please forgive me. I need some information: 1) how much space we need 2) how much traffic our site produces monthly 3) what about wiki-engine? provider must have it? — VadimVMog (talk) 06:01, 3 October 2018 (UTC)
I am not an expert but some information are provaded in the previous topic, especially -> Project:Community_Portal/en#Bibliowiki hosting. What above space: @Sysadmin: says that 80gb will be enough at the moment. Electron   08:57, 3 October 2018 (UTC)
On the second thought, Belarus is not the best choise exactly for me. US can't push Belarus, but Russia can. So it may happen, that Russian content will be the reason for pressure. What other options beside Belarus do we have? Interesting to me look China Cuba, Hong Kong, Indonesia, Iran, Kazakhstan (is more independent than Belarus), Korea, Malaysia(?), Monaco, Mongolia, Philippines, South Africa, Taiwan, Thailand, Vietnam. Don't know much about Egypt. The full list is hereVadimVMog (talk) 05:45, 4 October 2018 (UTC)
indonesia is not an option. In Indonesia, copyright expires 50 years after publication for films and photographs. But for literary works and music, the copyright term is life +70 years. Simon Peter Hughes (talk) 16:13, 5 October 2018 (UTC)
width 400px
For countries which have decent Internet infrastructure and Life+50 there are a few options to consider: Belarus, South Korea, and Hong Kong. While there are many countries in Southeast and East Asia with Life+50, most are not viable because of either a lack of Internet infrastructure/policies and/or local censorship laws and/or practices.
Belarus is the only CIS country in Europe that is Life+50, so they have clearly taken a pro-public domain stance and there are no signs of any changes coming. I agree they are potentially pressurable by Russia, but that hasn't happened yet, including the CIS agreements where everyone else converted to Life+70. The only negatives are that I think VPNs are illegal (which is what I usually use to communicate/manage servers with), and VPS hosting will be more expensive than elsewhere (though still reasonable).
Hong Kong is Life+50 and previously had UK laws, which make them more legally clear, though it is increasingly coming under censorship from China. Personally I think that China is a greater threat to Hong Kong (though they also support Life+50) than Russia is to Belarus.
South Korea is Life+50, and they were never invited to be a part of TPP, though they have many/enough trade agreements with other countries. They are likely the most independent of the three countries listed. In addition, Amazon has AWS Lightsail with a Seoul, South Korea location. This provides an inexpensive VPS hosting option --> 2gb ram/60gb ssd for $10/mo.
Japan is Life+50 but they have a provision for WWII Allies countries where from 8-11 years are tacked on because of the lack of copyright protections during the war. The exact length depends on the country and when they signed onto an agreement, so it is all a bit complex. Treat them as a Life+60 country and that is likely the most accurate assessment (in which case they resemble India in copyright length). Also, Japan was about to cave into Life+70 demands in the TPP agreement (along with MY, NZ, VN) until that provision was pulled from the agreement with the leadership of Canada. --Sysadmin (talk) 05:32, 9 October 2018 (UTC)
Based on research of Sysadmin I would go South Korea. If in a few years the country joins TPP, we can try Belarus. — VadimVMog (talk) 05:27, 12 October 2018 (UTC)
  • Based on the above I have got Jeremy to fire up an instance in Seoul, as November is fast approaching. Currently it is accessible at wikilivres.org. This will allow things to progress since I can the wiki up and people can register however this still leaves the issue of things like the DNS and the issue of actually moving the content over. I can easily move the content with a bot, however this does not retain revision history. xml dumps are better. Dysklyver (talk) 21:01, 22 October 2018 (UTC)
This is great! What do you need me to do? Contact via email: info@biblio.wiki regarding DNS, any admin access to the current system, etc.? Also, if someone needs to deal with the ongoing donations collection and invoice payment. --Sysadmin (talk) 14:18, 25 October 2018 (UTC)

Comment - South Africa would also be a good place to look at (as a fallback, now that we seem to be sorted). pma-50 (unless it's changed?), not as susceptible to us pressure on trade (they're far more involved in african-internal trade), & ther is a significant open-source culture there. the guy who created ubuntu (operating system), mark _? (can't google right now, will fill it in later) is from s.a. Lx 121 (talk) 21:12, 2 November 2018 (UTC)

They do still have a life+50 copyright term, but Amazon does not offer services there yet. Arthur (talk) 18:28, 6 November 2018 (UTC)

Account migration

It looks like my edits, user rights, preferences, etc. have all been reset. Do we anticipate that they will be integrated in December at the .org domain? Koavf (talk) 01:20, 2 November 2018 (UTC)

Ok I should probably explain exactly what is going on;
  1. The wikilivres.org domain is new, however the current plan is to continue using the biblio.wiki domain. Either way both domains will end up aliasing to the same server along with the wikilivres.ca domain. There are no plans as yet to acquire any .kr domains but that is the country tld for South Korea.
  2. The server is not being moved as such, a more accurate description would be that we are building a completely new wiki and then importing the same page content and files. It is not possible to copy server logs, user accounts, passwords, preferences, or watchlists.
  3. This also means anything that was deleted will be effectively hard deleted as part of the move.
  4. I may have to convert a lot of the images to newer file formats, there are some weird files to deal with.
  5. The wiki will have special character support, and potentially support math. If anyone thinks it will be useful I can install Visual Editor. Additionally the wiki will support lua scripts, and several other more modern features that Wikipedia uses, such as per page custom CSS styling and moderation.
  6. The new wiki setup will use Nginx and thus be faster.
  7. There will keep a live backup of the wiki on a seperate server (which hosts other wikis) in case of emergency, the backup will stay up to date by means of a bot. The backup will ensure that the wiki does not get lost.
  8. No bots will be given any deletion powers because this can cause major headaches. You will note that admins cannot delete or protect pages or block people. This is by design.
  9. The wiki will have sendmail and thus support emails.
  10. Editors may potentially be able to have @wikilveres.org or @biblio.wiki email addresses if there is interest in this.
  11. Potentially, anonymous editing could be allowed since unmoderated edits are not seen.
  12. If you haven't already noticed, my email address is dysklyver@linuxmail.org or for (current, not ongoing) hosting queries there is Jeremy at jl22388@ou.ac.uk who will also be hosting the backup going forward. The previous sysadmin will still be involved and is still reachable at info@biblio.wiki
  13. I expect that things will be fully back up and running in about a week, two at the most. By the start of December all technical issues should be resolved.
Arthur (talk) 13:45, 2 November 2018 (UTC)

P.S. I will assign anyone that asks the same user-rights as before and do particularly want to have at least three active crats. Arthur (talk) 13:52, 2 November 2018 (UTC)

Yo, i go away for a while & everything happens? xD glad we are still alive & kicking though! (& did we ever have 3 active 'crats?) Lx 121 (talk) 21:07, 2 November 2018 (UTC)

The list of previous admins and bureaucrat is here: Project:Administrators. If admins cannot delete any pages who will do this? Some texts can be not useful or suitable here (or with bad title) or they even can brake copyrights... And how we will deal with them? Electron (talk) 00:57, 4 November 2018 (UTC)
I will probably have to make a "deleter" user-right to deal with issues that can't be dealt with by blanking or pagemoves. Adminbots are useful but I don't want bots able to delete stuff. Page protection/edit filters/captchas/spamblacklist/blocking are simply not needed in combination with the moderation tool. Sysadmin (talk) 10:16, 4 November 2018 (UTC)

I am happy to become a 'crat. I have plenty of relevant experience.--Poetlister 19:31, 4 November 2018 (UTC)

If you think it would be helpful I can be a bureaucrat as I was in the past. Electron (talk) 12:23, 5 November 2018 (UTC)

  • Ok you are both crats now. For reference the "staff" user-right is functionally similar to a combination of admin/crat and bot. Arthur (talk) 17:32, 6 November 2018 (UTC)

"Awaiting Moderation"

what's with the "awaiting moderation/pending review" thing? o__0 Lx 121 (talk) 21:12, 2 November 2018 (UTC)

It's an anti-spam tool. Anyone can edit but their edits can't been seen until they are approved (via Special:Moderation). Anyone that isn't a vandal can be added to the auto-moderated usergroup and all their edits are automatically approved. It's good because vandalism doesn't need to be reverted, will never affect a page or show up in recentchanges, can be approved hours or even days later, and the system doesn't affect anyone that isn't a vandal. It also means that someone can try and vandalise the wiki it will have no visible effect so they give up pretty fast. Sysadmin (talk) 16:10, 3 November 2018 (UTC)
ok, i get that & i can see its usefulness, but: a) can i be approvced, please? xD [it looks like i have been "approved"? & ty ifso :)] & b) that is going to make more work for the admins (or whoever is going to get the user rights to approve edits). do we really have that much trouble with vandals making edits on existing pages? (as opposed to new page creation?) o__0 & could we exempt talkpages & portal/discussion/whatever -pages from this requirement? because that's going to just clog discussions like crazy, if we ever do get new people coming here... Lx 121 (talk) 02:49, 4 November 2018 (UTC)
I could exempt talk pages from moderation I guess. Moderation does also cover page creation and even stops user account creation showing in recent changes. The issue of course is that if a vandal comes along and over an hour replaces 500 pages with 100k "Lorum ipsum" text (this is a common thing) then no-one logs on for a few days, then hundreds if not thousands of readers will be rather confused. Sysadmin (talk) 10:16, 4 November 2018 (UTC)
There is currently a lot of spammers trying to post ads. I will see if this continues before relaxing the anti-spam filter, in the meantime just give auto-moderated status to anyone that isn't a spambot. It occured to me I could create a draft namespace which isn't moderated and also not indexed like Wikipedia does. Arthur (talk) 17:36, 6 November 2018 (UTC)
  • Moderation is disabled in user and project talk namespaces. New users can't create pages until they are autoconfirmed, after one edit and ten minutes of being registered. Sysadmin (talk) 21:16, 6 November 2018 (UTC)
Comment - on this date (2019-01-01) moderation is NOT disabled (i.e.; is enabled) for pages like 'community portal', 'technical issues', 'current events'. (i am currently waiting to be "approved" for edits on all 3 of those pages) Lx 121 (talk) 20:56, 1 January 2019 (UTC)
AND i just got yet another error message when trying to save. "Sorry! We could not process your edit due to a loss of session data.
You might have been logged out. Please verify that you're still logged in and try again. If it still does not work, try logging out and logging back in, and check that your browser allows cookies from this site."
that has happened on every page i've tried to edit. when i'm coming from another page, & try to make an edit, it always fails on the first attempt, & i have to repeat-save to get it to "take". Lx 121 (talk) 20:56, 1 January 2019 (UTC)

Update

A brief update on how things are going:

  • There are Echo (notifications), Thanks, and Wikilove extensions installed. These will be familiar to people from Wikimedia sites.
  • The site uses Google analytics and Piwik analytics to monitor the number of users on the site at any one time. This tracks basic details like your country, device type, and whether you are using the mobile or desktop site.
  • There is now a working checkuser extension. Admins can view the log at Special:CheckuserLog however since no-one has the checkuser permission that log will hopefully stay empty. (The checkuser extension is switched off at backend now.)

Selected files will be uploaded from the old server, with the following caveats:

  • If the image can plausibly be hosted on commons, it should be hosted on commons.
  • Icons should not be uploaded here, find a new icon on Wikimedia commons if needed. This is an advantage since the icon will be fetched from Wikimedia's faster CDN and also not cut into our data transfer allowance.
  • Uploading a 50mb Djvu file uses slightly over 500mb of server space. There is around 40gb of server space for files. This is potentially enough for 80 works.
  • The new server will not be able to host .mid or .ogg files. I will host these separately on a CDN and enable an interwiki link to make them downloadable. Any file that is not actively displayed by the mediawiki software, for example an epub or kindle ebook of a fully transcribed file, can be hosted in this way.

I will also make the following point clear: Deleting something does not remove it from the server, when deleting an image that should not be on the server please make sure to tell me about it so I can actually remove it from the server.

Arthur (talk) 17:59, 6 November 2018 (UTC)

Fundraiser

There is no obligation to donate, indeed I don't expect anyone to :D

To hide/not see the fundraiser simply add;

.fundraiser { display:none }

To your personal css in your user preferences. Sysadmin (talk) (Jeremy) 12:14, 8 November 2018 (UTC)

If anyone ever wants to consider affiliate links I made Template:Amazon for the purpose. Linking to Amazon is a kind of an advert and I do not advocate using it without good reason. Just saying. Jl22388 (talk) 16:52, 10 November 2018 (UTC)

Uploads

The server can now support single uploads of 50mb. Remember that a 50mb Djvu file will grow to around 500mb with thumbnails. Sysadmin (talk) (Arthur) 14:42, 9 November 2018 (UTC)

Thanks for revival

Have not visited wl/bibliowiki for a long time, and now am happily seeing the new site. Thanks to all who worked and are working on it. K67y (talk) 01:39, 10 November 2018 (UTC)

Unused files

There are a number of unused files I assume were uploaded so they could be used on yet to be created texts, some clarifiction on what these are would be in order. Jl22388 (talk) 12:02, 19 November 2018 (UTC)

Some of them were transfered here from Commons a few years ago because of URAA effect (they were still protected in US but PD in Canada already). But during years some of them stay PD in US now because of their age. I think that there is need to look into them and if there is a copy on Commons of the file it is no sense to keep it here... Electron (talk) 12:32, 19 November 2018 (UTC)
Ok that makes sense. Jl22388 (talk) 12:45, 19 November 2018 (UTC)
There was a period of a few months when instant Commons wasn't working on the old wikilivres.ca site. During that time, I copied a few files from Wikimedia Commons over here, mostly just to put on my user page. Then we changed our web address and instant Commons worked again. I deleted most of the files I copied, giving the reason that they were already on Commons. Then the Big Cheese complained about stuff having been deleted just because it was on another website. I took that as reference to what I'd done and didn't delete any more files. Still, it looks like this file is the only I uploaded that's still here. It's a duplicate of a file from Commons and I would be happy for it to be deleted now. Simon Peter Hughes (talk) 13:32, 20 November 2018 (UTC)
And thanks to my fellow RatWikian for having deleted that duplicate file. Simon Peter Hughes (talk) 03:34, 23 November 2018 (UTC)
Note that some of these files were restored on Commons but they are still copyrited in US, eg. File:AbpCosmoLang.jpg (they are marked with the commons:Template:Not-PD-US-URAA, there) and can be deleted there in any time. So, in my opinion we should keep them in our archive, anyway. Electron (talk) 13:03, 23 November 2018 (UTC)
That would be a good idea. Arthur (talk) 15:45, 23 November 2018 (UTC)

New mirror

For anyone that is interested, I have created a mirror of the Canadian Project Gutenberg. It is hosted at gutenberg.wikilivres.org. Arthur (talk) 11:16, 22 November 2018 (UTC)

Nice! As a (North) American, I'm sad that we had to even resort to this nonsense but at the very least, it's nice to see fellow Indianapolitan Booth Tarkington at the top. Thanks, Arthur. Koavf (talk) 01:47, 29 November 2018 (UTC)

More new extensions

These extensions add parser functions which can be used to control how a page appears in search or when shared on social media. If you need to adjust how a page is described in the Google search snippet, or want to share a page on Facebook and have it display right, these are very useful. Arthur (talk) 13:35, 23 November 2018 (UTC)

Translations made by users

Due to the recent change of the skin and editing interface that caused edits there quite difficult I try to import on Wikilivres some texts in Polish gathered by years on "my wikia site": wiersze.wikia.com (so called Ogród Petenery, the biggest wikia site with Polish literature and poetry) that are suitable here. Next reason to transfer works is that wikia is a commercial site with lots of ads.

When I imported works by Edgar Allan Poe I realized that there are (among others) some translations of his works made by me, see -> Category:Electron PL. We have also others translations in Polish done by others ours users. They all are published on free licences, so it is no problem with the compatibility with our license policy but...

...I have a question: should we gather such works or not? If you do not agree, of course I will delete them. And will try not upload such works in the future...

But in my opinion it's better to have a "free" (even imperfect) translation done by users than not have any. It always allows readers who do not understand the language of the original text to know what a given work is about. Electron (talk) 01:13, 25 November 2018 (UTC)

This is a translation done by a user. Of course we should have them. Why ever not? Simon Peter Hughes (talk) 03:26, 25 November 2018 (UTC)
Translations by users are good. Basically what matters is that it is has free license and since they do that is not a problem. Within reason you could import the entire Ogród Petenery site without any problems. Arthur (talk) 10:03, 25 November 2018 (UTC)
OK. So I will import our articles gradually. Electron (talk) 15:27, 25 November 2018 (UTC)
It is possible for me or Jeremy to import large xml files from the server command line if needed. The server seems to timeout if the import file is larger than about ~4mb. Arthur (talk) 16:56, 25 November 2018 (UTC)
It depends. I have problem with upload if the file is larger then ca 7-8 MB... A larger file I must divide into smoller parts. Electron (talk) 12:02, 29 November 2018 (UTC)

Russia

Over the last month or so, https://wikilivres.ru has been redirected to agiosignatios.gr which I think is the website for Greek Church? Not clear. Anyway the http still works, the https redirects. The previous site is in part on archive.org however the Wikitext is not archived there. Therefore, because I am worried about the stability of that site, I am going to consider importing some works from there. What do you think? Arthur (talk) 10:43, 25 November 2018 (UTC)

Why not?... The more we have texts the interesting our site is for readers on the world. But their articles should be chacked with our licence policy. They might published some works that are not fit to it. Electron (talk) 15:51, 25 November 2018 (UTC)
But it seems that wikilivres.ru is still working at the address http://wikilivres.ru Strange :) Electron (talk) 16:07, 25 November 2018 (UTC)
I have had a look, and the works they host are split between public domain works which we can host, and CC-BY-NC-ND which I believe we can't. I have made a start on transferring the public domain works. They use a whole different category and template system which I plan to convert but otherwise it seems fine. Arthur (talk) 16:53, 25 November 2018 (UTC)
OK. It is a good way to increase our archive in a quick way. Electron (talk) 02:07, 26 November 2018 (UTC)
This is a long conversation that we've had a couple of times about hosting non-free CC works. The entire reason .ru exists is because we got rid of NC/ND works. :/ Koavf (talk) 01:45, 29 November 2018 (UTC)
So, think mainly about PD works gathered there. What about CC NC/ND: they not entirely free but can be used freely if the only purpose of a reader is to read them. But of course we should not do anything that was set in our discussions. 12:13, 29 November 2018 (UTC)
As far as I can tell the tl;dr of the NC-ND issue is that NC-ND works can't be reused as freely. However it occurs to me that I can simply mirror the site on a subdomain. Problem solved. Arthur (talk) 16:29, 1 December 2018 (UTC)
See File:BD-propagande-2 en.jpg for the issues with NC. Koavf (talk) 03:09, 2 December 2018 (UTC)

Biblio.wiki not redirecting

https://wikilivres.ca/ still redirects properly. Koavf (talk) 01:45, 29 November 2018 (UTC)

This is deliberate and related to some server stuff still being sorted out. Just use wikilivres.org for the moment. Arthur (talk) 16:25, 1 December 2018 (UTC)
Btw. Now, it redirects stright to https://classics.io/ - a commercial site. To say the truth it is not fair, because as I now bibli.owiki address was paid from our money... Electron (talk) 12:29, 20 December 2018 (UTC)
Yes, I don't know what the plan is here but there are surely some incoming links to the old address that need to be redirected. Please resolve this. Koavf (talk) 20:24, 25 December 2018 (UTC)

Main pages in some other languages need updating

Can somebody please update the Chinese, Czech and Russian main pages? References to Bibliowiki need to be changed to ones to Wikilivres, references to Canada need to be changed to ones to South Korea and a link to the Esperanto Ĉefpaĝo. Needs to be added. I have updated the Esperanto, French and Spanish main pages and I seem to have managed to update the German one too. Simon Peter Hughes (talk) 03:30, 3 December 2018 (UTC)

For Заглавная страница in Russian and Hlavní strana in Czech - done. Electron (talk) 12:38, 3 December 2018 (UTC)
@Electron: Thanks a lot! Simon Peter Hughes (talk) 14:42, 3 December 2018 (UTC)

Change to special page

I think this requires access to LocalSettings.php, so I can't do it myself: can someone please amend the confirm email page to say to check spam (that's where it went just now when I confirmed my email address)? Thanks. Koavf (talk) 04:40, 3 December 2018 (UTC)

You should be able to change the text of any special page or system prompt via the system messages interface at Special:AllMessages. Try one of these, and create the corresponding mediawiki page with the replacement text. You could be looking for Mediawiki:confirmemail_oncreate but I am not 100% sure.
I can't promise results, but I may be to configure DNS records to properly authenticate the email server and then it might not be treated as spam. Jl22388 (talk) 16:28, 3 December 2018 (UTC)
@Jl22388: It was in fact MediaWiki:Confirmemail oncreate. Thanks a lot! Koavf (talk) 08:13, 9 December 2018 (UTC)

Image broken in template

The thumbnail is broken in Template:PD-Canada. Not sure if this is a known issue being looked into, or if it affects more than just this template, but thought people should know about it. Beleg Tâl (talk) 19:28, 3 December 2018 (UTC)

Ok. Thanks for the info. I've changed the link from the png file to svg version. I've observed that there is sometimes problems with the png file thumbnails. Electron (talk) 20:00, 5 December 2018 (UTC)

Celebrating Public Domain Day

Merry Christmas to all. We have Project:1968 deaths, therefore now in the Public Domain, ready to go in a week. Does anyone have any plans on what to upload? Koavf (talk) 20:26, 25 December 2018 (UTC)

Not as yet, but I believe I will find something soon enough Now it's 2019. Arthur (talk) 00:07, 1 January 2019 (UTC)
Well on reflection, and looking at the people available, the highlights to me are:
There could be more, but then this seems plenty to me, already! Arthur (talk) 18:05, 1 January 2019 (UTC)

Pages that have language about "Canada"

Can we collaborate on a checklist of pages mentioning Canada that need to be converted to South Korea? Please note that we don't need to remove all historical references to this site being Canadian. Please add to the below and then use <del></del> when it's done. Thanks. Koavf (talk) 19:33, 4 January 2019 (UTC)

Problems with copyright

I just received this email:

Hello,

I just found that South Korea extended general copyright to life + 70 years till year end in 2011, formerly life + 50 years till year end. Will this affect hosting it in South Korea after moving out of Canada?

Former administrator Jusjih

Of course this is not something I knew about, and hard to deal with fully because I don't actually speak Korean.

According to Copyright litigation in South Korea - overview by Angela Kim, Seoung Soo Lee and Hyung Ji Kim, Kim & Chang the following is the situation:

As a general rule, an author's economic rights subsist for the lifetime of the author plus a post-mortem term. This term has been extended from 50 years to 70 years, effective 1 July 2013, for works that were still protected at that date.

The latest relevant law is not translated, and is Copyright Act (Act No. 432 of January 28, 1957, as amended up to Act No. 14634 of March 21, 2017). Using Google Translate produces mostly gibberish.

Our policy page: Help:Public domain is based on the 1995 version of this same copyright act (the most up to date official English translation that could be found). It seems that this was significantly changed around 2011, but this was not apparent from anything I had previously read.


This means that anything in the public domain as life+50 before 2014 will still be public domain in South Korea, but that from 2014 onwards works are instead life+70, the same as the US.

It follows that we should probably copy the site to a server in another country, because otherwise the site would be limited in new works, being slowly ported to Wikisource over the next 15 years.

Ideally we should get our site moved as soon as possible to avoid disruption, any country is an option provided it has a provider of hosting services. Thoughts are welcome.

Arthur (talk) 13:57, 10 January 2019 (UTC)

Oh, no! Not again! Well, I suppose it's Belarus here we come! Simon Peter Hughes (talk) 14:10, 10 January 2019 (UTC)
Ideally this goes smoother than last time. Jl22388 (talk) 14:27, 10 January 2019 (UTC)
Belarus should be considered. It is Europe, any way... But what about New Zealand? Sems it has "life + 50" also, see -> wikisource:en:Help:Public domain... Electron (talk) 14:35, 10 January 2019 (UTC)
I will just point out that the copyright extension was eventually left out of the successor to TPP, but wikipedia:Copyright law of New Zealand has not been updated with that information yet. Jl22388 (talk) 14:44, 10 January 2019 (UTC)
I got the email. I suggest checking the New Zealand law because―for example―the Wikisource page suggests the Seychelles are life+25, when the Seychelles has been life+50 since 2014. Frayae (talk) 14:59, 10 January 2019 (UTC)
Tho Belarus is in Europe and I find it unlikely that anyone cares that much about this site to kick down some doors and confiscate servers, I am pretty wary of having something hosted in some autocrat's playground. Koavf (talk) 07:37, 13 January 2019 (UTC)
Also Europe is having a big copyright shakeup right now, so their law may change soon. Arthur (talk) 13:06, 13 January 2019 (UTC)
___________

Just from a practical point of view, Wikimedia New Zealand is sort of a thing, almost everyone on this site speaks English which is the official language of New Zealand and all their laws/news. I don't know any Wikimedia presence in Belarus, and the number of users here who speak Belarusian/Russian is a bit more limited. Arthur (talk) 15:16, 10 January 2019 (UTC)

Right, now find a hosting provider. None of the main hosts I have existing relationships with host in New Zealand. openhost and sitehost are both options. Jl22388 (talk) 15:41, 10 January 2019 (UTC)
Openhost is cheaper, and they offer better bandwidth costs, and we can use the flexi plan. Arthur (talk) 19:10, 11 January 2019 (UTC)