#globalstage — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #globalstage, aggregated by home.social.
-
Kansas City Royals’ Bobby Witt Jr. Makes Summer Olympics Decision https://www.rawchili.com/mlb/585662/ #2028Olympics #Baseball #BobbyWitt #BobbyWittJr #FoulTerritory #GlobalStage #Kansas #KansasCity #KansasCityRoyals #KansasCity #KansasCityRoyals #MLB #MLBPlayers #royals #SummerOlympics
-
Thursday, January 15, 2026
From Venezuela to Iran, Trump shows "how weak Russia really is," ex-US envoy says -- How can foreign defense manufacturers benefit from Ukraine’s Defense City regime? -- New type of Russian Shahed-type drone shot down -- Republican congressman blasts Trump's Greenland invasion talk as "one of the dumbest things" that could wreck NATO ... and morehttps://activitypub.writeworks.uk/2026/01/thursday-january-15-2026/
-
Thursday, January 15, 2026
From Venezuela to Iran, Trump shows "how weak Russia really is," ex-US envoy says -- How can foreign defense manufacturers benefit from Ukraine’s Defense City regime? -- New type of Russian Shahed-type drone shot down -- Republican congressman blasts Trump's Greenland invasion talk as "one of the dumbest things" that could wreck NATO ... and morehttps://activitypub.writeworks.uk/2026/01/thursday-january-15-2026/
-
Why are there still so many posts from both individual posters and entire instances where translation is neither offered nor allowed (http 403 or 503)
Certainly if #Mastodon wants to compete as #SocialMedia on a #GlobalStage translations into the reader's stated Interface Language should be mandatory, unless explicitly prohibited on an individual poster-by-poster basis
What gives?
As it is now, I #Mute and #Block posters who will not let me translate their posts into a language I can read
Why do I want to give up my very finite screen space to posts I'll never be able to read?
I don't, and I won't
I'm on an instance currently running v4.3.7
-
Why are there still so many posts from both individual posters and entire instances where translation is neither offered nor allowed (http 403 or 503)
Certainly if #Mastodon wants to compete as #SocialMedia on a #GlobalStage translations into the reader's stated Interface Language should be mandatory, unless explicitly prohibited on an individual poster-by-poster basis
What gives?
As it is now, I #Mute and #Block posters who will not let me translate their posts into a language I can read
Why do I want to give up my very finite screen space to posts I'll never be able to read?
I don't, and I won't
I'm on an instance currently running v4.3.7