home.social

#wikidata — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #wikidata, aggregated by home.social.

  1. Back by unpopular demand!
    Week 42, 2026: Top album languages found on @wikidata right now.

    For the complete list, see w.wiki/6TNS

    📊 #Wikidata 🎶🎵 #ExMusica

  2. 2026 維基數據跨領域論壇,全球 Wikidata 週年慶臺灣響應活動,首次移師高雄,即刻開放報名!

    四位第一線社群工作者分享四種不同的角度,共同討論「社群如何面對資料」;地方書庫數位轉型、藝術檔案開放、林業歷史地圖、政府資料整理,四場議程全數聚焦在本次維基數據跨領域論壇。

    活動資訊
    2026 維基數據跨領域論壇
    時間:2026 年 10 月 24 日(六)13:00–18:00 (UTC+8)
    地點:Le Phare 共享空間 | 新左營館 / 高雄市左營區站前北路 1 號環球購物中心 4 樓
    免費報名:wikidatatw.kktix.cc/events/wik
    與 Civic Tech Day @高雄 同日舉行,歡迎一起來!

    #維基數據跨領域論壇
    #wikidata #維基數據 #維基資料 #活動 #event
    #WikidataBirthday
    #高雄市 #左營區

  3. Wikimedia Foundation is transitioning from Blazegraph to QLever for the engine of Query Service.
    uses Sophox, and according to @mxn (following a recent reply on OSM wiki about "green" keys) Sophox has issues with data items, making it kinda degraded and broken.

    From what I understand by looking at Sophox's github, it uses Blazegraph which stopped being maintained since 2020, one of the reasons Wikidata goes to QLever. QLever is maintained by the Algorithms and Data Structures Group of the University of Freiburg, which also maintains osm2rdf. Sophox uses osm2rdf.

    Where I'm going with this? I'm not sure yet, random thought, trying to understand which is actively used since both are being mentioned in OSM wiki, and if Sophox should upgrade to QLever aswell, or just drop it completely (since github shows no maintenance lately) and stay with QLever only (as being offered via qlever.dev/osm-planet )

  4. 現在想要編輯 Wikidata 也可以在行動裝置上面進行,Wikidata 行動裝置編輯介面完整版正式開放所有社群夥伴試用!

    即日起只要在偏好設定的測試功能中,開啟「在行動裝置上編輯維基數據項目」就能夠率先體驗到 Wikidata 的行動裝置介面,再也不用等到用電腦或是還要拿筆電出來改資料了!

    若體驗中遇到任何問題,歡迎到錯誤回報頁面發起討論,讓開發團隊看到問題所在。

    行動裝置編輯錯誤回報:wikidata.org/wiki/Wikidata_tal

    #Wikidata #維基數據 #維基資料
    #行動裝置

Share on Mastodon

Enter the server where you have an account.