As we say in Germany:

Sackdoof, feige und verklemmt
ist Erdoğan, der Präsident.
(...)
 Ja, Erdoğan ist voll und ganz
ein Präsident mit kleinem Schwanz. 

https://lyricstranslate.com/de/jan-böhmermann-schmähkritik-lyrics.html

I assume, you are asking how to allow remote (as in outside of your network) access. There are multiple options to achieve this goal:

1. Local reverse proxy and port forwarding: You essentially poke a hole through your firewall to expose your Jellyfin to the internet. Only works if you got a static IP and your router allows it.
2. VPN: Sometimes your router has a VPN option built in. Otherwise Tailscale is a simple option. Requires some setup on the playback device. Not recommended if your users are using a lot of non-Android smart TVs
3. Tunneling to remote reverse proxy: generally the recommended option. Pangolin and netbird are two providers of such services. Your users connect to their servers and then they are automatically redirected to your server. Both services are also open source, so you can selfhost that part of the setup as well, if you want (that’s what I do)

Because the important factor is being in the European Broadcasting Area. This area is bigger than the European sub-continent and includes all countries with Mediterranean coastline and some countries to the east of Israel. Wikipedia has this helpful map:

dark green: Countries which have participated in the Contest at least once.

yellow: Countries which are eligible to participate, but have not (yet) done so.

light green: Countries which have competed in the contest as a part of another country, but never as a sovereignty.

red: Countries which were supposed to compete in the contest but withdrew right before the final.

https://commons.wikimedia.org/wiki/File:EurovisionParticipants.svg

As you can see Marokko competed one time, Tunesia and Lebanon had had at one time real plans to compete and Jordan and Irak are also eligible but opt to not participate.

Australia on the other hand isn’t eligible at all but requires a special invitation from the EBU which they have received every year for the last ten years and are likely to receive until the contest collapses.

It’s really interesting watching discussions about the trolley problem in abstract vs the problem in praxis. Because the thought experiment is about inaction (letting the runaway train crash into the group of people) on one hand and harm reduction (switching tracks) on the other.

The thing that I find fascinating is that with the thought experiment (basically) everyone says the answer is clear: switch tracks. But in the applied scenario of voting picking the lesser evil somehow stains your hands more than not voting.

OK, so CryEngine and it’s open source descendant O3DE already exists

Two of the three parties have set up their own Mastodon instances years ago (grüne.social and social.linksfraktion.de respectively).

The Left is also present at @dielinke@mastodon.social

And even high ranking SPD politicians are active on the Fediverse (@eskensaskia@mastodon.social for example)

They are going to be present on closed platforms, because like it or not (and for the record I don’t) that’s where a large part of voters is, but the Fediverse plays an active part in their social media strategies.

I’m fairly sure it can, but that’s default behaviour over there, similar to how Mastodon and X/Twitter work.

She’s posting from Friendica. Ignore the @mention, that’s just how that platform works

Orion isn’t Chromium based. It’s based on WebKit. Chromium uses a WebKit-fork called Blink, that’s diverged quite a bit from its origins

What do you mean “planned successor”?

https://en.wikipedia.org/wiki/D_(programming_language)

Link works for me.

This client won’t work on your Pixel because Sailfish hasn’t been ported to that device.

That being said Voyager is usable as a web app and !thunder_app@lemmy.world is written in flutter so you should be able to built it for arm-Linux and use it on Postmarket OS.

Sure, technically it’s a replacement for a bunch of services. But from a institutional perspective you wouldn’t use Signal in the first place, just like you wouldn’t use WhatsApp. You want closed (as in no open participation not as closed source) systems where only employees can send messages in the first place. Traditionally you would use Slack or MS Teams for that.

That doesn’t mean that your employees wouldn’t use WhatsApp or Signal anyway and having a convenient alternative might curb that use.

1. A lot of the solutions are based on standards that already include E2E. The French and German platforms for example are just rebranded Matrix.
2. the platforms are not intended for civilian communication. The video is a bit misleading when it talks about WhatsApp alternatives. A more accurate description would be “Slack alternative”: A communications platform for government workers to message each other, so that potentially sensitive data isn’t stored on 3rd party servers.

The right man in the wrong place can make all the difference in the world.

You might want to keep an eye on Plasma Bigscreen, KDEs UI for TVs. Combine it with Waydoid and you get a system that allows you to sideload anything you want.

https://plasma-bigscreen.org/de/

https://wiki.postmarketos.org/wiki/Plasma_Bigscreen

CDU-Geführt

Nice to see (some of) my taxes going to improving the Fediverse.

The Sovereign Tech Agency (previously Sovereign Tech Fund) is an organisation set up by the German government to fund critical open source projects. Mastodon receiving funds therefore means that the German government considers the Fediverse critical infrastructure.

Nice to see that my translations made it into the latest update. One thing I noticed while translating: I couldn’t properly translate time related strings into German without running into grammar issues. The correct translation for “5 min ago” would be “vor 5 Min”. The number moves from the beginning into the center of the string, which isn’t possible in your current setup.

Now for some more general feedback: I have been thinking about how to structure the UI of the app. Currently you’re just throwing every menu option into the pulley menu. That means this one menu contains both navigation items and actions for the current view which I generally consider suboptimal UX. I’m sure this is just temporary while you are working on features and you have ideas how to restructure the central navigation. But I want to give one option of how you could possibly restructure the UI to clean up the UX nonetheless. I’m aware that this is a big change to the app, so see it as merely an impulse.

SFOS has generally speaking two forms of main navigation menu: The menu page, which is what quickddit for example uses, and tabs. I have chosen the latter option for this concept:

The pulley would contain the options to change the feed between subscription, local and all, as well as the already existing options to refresh. But all options should relate to the feed.

The search tab could double as the list of your subscribed to communities:

As soon as you tap on the search field the list would disappear and make way for the search results.

Again just a couple of ideas of how to guide the user a bit more.

Unless we’re talking about German ICE: https://en.wikipedia.org/wiki/Intercity_Express

Qt (Sailfish Silica), C++ & Rust