Would this be easy to implement soon? If not maybe (at least) to have redirects as fallback?

Not yet. They only discussed it last year.

I am inserting Wikimedia to Commons, as I would love to see this becomes also more generic later to include (ideally) other Commons media servers like https://commons.miraheze.org or once WikiTide Commons are available.

Consider adopting https://forum.wikibase.world as possible platform for managing FAQs.

IMHO better methodology would be to rename this to something like:
Documentation for Wikibase Cloud [was: Session @2023 Hackathon]
rather then for each event that wants to do something related to this open and close new task and create pile of half finished tasks...No?

@Jan-Bart I think this was your art ;-) I have no access to change it.

As (digital sustainability concerned) I am mostly for doing essential based on need, it would be good to generate just .svg and smallest (really just for business card) .png for shortURL requests that are pages, not diffs, media or queries...no?

@Aklapper IMHO your aggressively push your point of view as the norm. There is no reason WMF needs to do things the same way always.
There is also no reason why WMF should self-host Phabricator as a given and not self-host communication platform that could (at least) bridge others (like Mattermost can to both IRC as basic standard and Telegram as the most popular) ... Lack of following standards and establishing at least guidance is what caused this situation. Anyway we are not the same, our needs are also different and it is OK to have different tools, but lowest standards and inter-operational bridges need to exist. Currently they are mostly exceptions, not as a rule.
Not everyting needs to start and end with 'hacker' cynicism and/or jokes.

I think there should be more then one option here and both WM Chat needs update and Federated chat should be an option (each has benefits and shortcomings) serving different needs and focuses.

@Aklapper if you do this so that task can be found rest assured both @Andrerodriguex and I have it in mind, it is just not perfect time to deal with this in the week before event in the task. Thank you for your understanding.

@Aklapper I would have gladly if I had the skill and time...instead I was passing on link to few to consider stepping in.

@Aklapper you were not consulting me if I would take the task, while you warn others not to do that. Double standards?

We can close it in few weeks...not done just yet.

Upgrade is even more needed + also bridges to existing global Telegram groups.
*(Brasil has blocked Telegram service)

@Aklapper is this not something that should be resolved in the system, so that people can only assign themselves? *(with possible exception of WMF staff where professional sub-ordination is assumed rather then voluntarism)

Is this deprecated task?

@MF-Warburg I was not asking only for myself but for all...
Either way IMHO your _assumption_ on Incubator should not be considered adequate neither content nor communication wise to new user. Also projects with that amount of content and history in Incubator should not be blocked based on subjective hunch. No?

@MF-Warburg please do not close the bug without informing us on reason.
We should be learning from each other and not experiencing suppression.
This is especially relevant for new and minority users.
Thank you very much! Have a wonderful day.

@jhsoby thank you for reply. I hope that (internal) technical requirement and consistency will not force Wy HBS (wider spectrum) to fallback to SH (historic spectrum with Serbian and Croatian standards of pre-breakdown of Yugoslavia) as we do write it and want to accommodate widest spectrum possible (including new standards and local non-standard language use). It is essential for this project to try to have bottom up approach to language (politics) and not just perpetuate top-down language antagonisms in the region. I hope this is clear and acceptable, if not lets have a conversation on this now and not wait for the stress and shock as we try to leave the incubator. OK?

Is this something that could be resolved soon?

Thank you! Will add few more subscribers who might be still interested from initial task.

Not sure if (only) T329535 related but linking to it.

It has been more than 3 months since this bug report was made and I tried to get feedback on my proposal and send reminders 5 times by email to get any feedback in past months. Initially I thought that it is a matter of the winter season slowing down for holidays, but now I see other issues are addressed and this is not. Is this issue a hot potato or something else is an issue? (I know language politics is hard to navigate with South Slavic languages, but ignoring it deteriorates our trust and commitment)

Nice! I renamed it and moved just to be conforming to WikiSPORE model of all Content being in some namespace *(TechR: is good for Tech Reviews and Research for example)

If your notes are fastly expanding, consider using tabular sheet for overview and sorting, not just text pages.
Please keep me in Cc: with communication you do on this as we could also help with sorting priorities and focuses.

I modified description a bit to make more explicit order of scale, focus on FLOSS, CC-licences and good-enough (range of solutions, not just single best). Feel free to revert/correct.

Great! I added few more details and will share it to others for more input.

Great! I made some markup updates with interlinking on Blogpost 1 EN you can integrate in PT and ES versions + adopt for future, and Blogpost 2 should maybe link also to Wikipedia for both FLOSS and Open Source *(as the Meta page seems to be just a 2015-2016 draft that was just once touched in 2022).

@Andrerodriguex I was adding few more aspects maybe worth tracking here
https://meta.wikimedia.org/wiki/Talk:WikiProject_remote_event_participation/End_user_minimum_tech_requirements ...and invited few more folx to give us inputs.

((@valerio.bozzolan it just worked for me but with strange (?intentional) delay of few seconds))

Sorry to say this as a critical feedback to @LDickinsonWMF (maybe you are not in a resource managment position) but how can a cost of WMF's US based staff doing stealth : exploration and constantly reviewing situation... compare to cost of any WMF contractor just setting up mirroring of a Mastodon account for WMF tweets? (even if it does not get huge amount of shares, it would at least help advance the situation) Hope you can consider this in early 2023 at least for the benefit of (high and low) key contributors to Wikimedia ;-)

I would love to use it in early 2023 for MediaWiki Blogs which seems to be best created with Cargo.

Item done...will close.

This work was corrected. Item done...will close.

This work was corrected. Item done...will close.

@awight
#1 Are you sure Wikimedia(ns) use(s) region in consistent way?
#2 Same as above + this is something where we need proper Ontologist no? ;-)

I know this is not popular way but it is technologically sane and somewhat minimalist approach to connect the two in persistent chat of Wikimedia Chat *(Mattermost instance) or the non-persistent but AV enhanced Wikimedia Meet *(jisti instance).

To elaborate on possible #cheapUIimplementation (for tech resource use) with pre-rendered images of 'typical' timeline waveforms:
#1 make a spectrum of relatively few (lets say 8 to 20) 'typical' timeline waveforms
#2 render them and assign to pages that were rendered at least once in 6 months by using AI
#3 ask for feedback and evaluate if this is useful to enable across wider set of pages/projects