Many thanks Laurence for the quick reply!

To clarify, i had not expected sitelinks to work (other than perhaps between different wb.c instances) but though it best to check (since the edit function is enabled) before we try to work around that by the use of a property. Thanks also for the sparql pointers around this.

I opened a ticket for enabling Extension:Interwiki (I did it in the github repo, but it's unclear to me what the relation is between that repo and the wb.c Phabricator board.) Afterwards I however found that interwiki links are enabled, the abbreviations are just not the shortened ones we might be used to from Wikimedia-wikis. See api.php?action=query&format=json&meta=siteinfo&siprop=interwikimap for the list. So with the `wikidata` as the interwiki prefix I could import the needed templates.

Re licensing (thanks for the pointer to the github issue). In the short term I'll guess we'll just override the system messages.

Cheers,
André
André Costa | Chief Operating Officer, Wikimedia Sverige | Andre.Costa@wikimedia.se | +46 (0)733-964574

Stöd fri kunskap, bli medlem i Wikimedia Sverige.
Läs mer på blimedlem.wikimedia.se


Den tors 13 okt. 2022 kl 04:04 skrev Laurence Parry <greenreaper@hotmail.com>:
Hi André (and Alicia),

With respect to your sitelinks question, I fear this may require some work on the development team's side, even to work partially. The sites table must be configured via maintenance scripts per https://mediawiki.org/wiki/Wikibase/Installation/Advanced_configuration#Enabling_sitelinks and there is no access to them from Wikibase.cloud. Similarly sitelink groups are part of code config. On the SPARQL side of things it may be possible to query Wikidata's sitelinks through code like https://opendata.stackexchange.com/a/7690/26857 and https://tinyurl.com/y5kvpxnx (by Andra), but I'm not sure this is useful to you.

There is also no way to inform the target wiki even if the config could be changed, as it is not a local SQL database (this at least might be expected, as WB.C is separate from Wikimedia). The areas of Direct Access and Wikidata Bridge are ones where Wikibase still seems relatively closely coupled to a local installation, complicating standalone hosting; perhaps some magic could be done with foreign data wrappers?

As you say, it'd be good to have interwiki support as well. There are extensions that allow easy editing of the interwiki table, and I think doing so would be sufficient to enable links separately, but they're not currently installed on Wikibase.cloud. To work around external link icons I enclosed links to other wikis in <div class="plainlinks">. A more general CSS override might also be possible (but not JS, yet, as that is not enabled currently).

Licensing issues were raised on https://github.com/wbstack/mediawiki/issues/124 but as far as I can see have not yet been addressed. I put license notifications on https://furry.wikibase.cloud/wiki/Project:About and https://furry.wikibase.cloud/wiki/Project:Copyrights on the grounds that the first is linked from all pages and the second from the edit page for regular pages, however this is not ideal. The specific message you highlighted can also be edited, e.g. https://furry.wikibase.cloud/wiki/MediaWiki:Wikibase-shortcopyrightwarning (note: Wikimedia currently uses CC-BY-SA 3.0, not 4.0; the latter isn't back-compatible, as it grants more rights). You may need to set MediaWiki:Wikibase-shortcopyrightwarning/sv and perhaps other language variants. Entity schemas have a separate message, MediaWiki:Entityschema-newschema-copyright.

There was a detailed discussion of licensing issues on the WBStack/Wikibase.cloud Telegram group on August 18, 2021, if you can access that (if not, poke me at @WikiNorn and I can invite you, though I'm not entirely sure the history will be accessible even then).

Hopefully WMDE can chime in if they have plans to resolve any of the issues you raised, or conversely if they see some of them as out of scope, at least in the mid-term.

Best regards,
--
Laurence 'GreenReaper' Parry - greenreaper.co.uk
Wikibase Community User Group / WikiFur.com