0.50 $/kWh is a normal price in Europe now

My household of 7 averages 900 watts year-round.

We’re not suggesting moving away from the HTTPS protocol. Gmail and other web email apps, as well as Word Online etc. still use HTTPS to communicate with their backend infrastructure. They are just registered in your browser as apps that can handle the mailto:// or ms-word:// URL schema. This registering most likely happens automatically when you have visited a page that supports the schema so fediverse:// links would continue working for Fediverse users - they’d see a prompt to open the link with their home instance’s web app (its web interface like the default web UI) or a dedicated web app they are already using like Voyager. What would need to change is just a minor thing: browsers would need to offer the default web UI of target instance as fallback: for example, even if you haven’t visited any Fediverse site yet, the link fediverse://lemmy.example.com/post/1337 will show “lemmy.example.com web interface” in the “Open with…” option list, redirecting to https://lemmy.example.com/post/1337.

The disadvantage is, Reddit and other platforms will never add support for [fediverse hyperlink](fediverse://example.com/post/1337) Markdown syntax, or even start blocking it (they can already block known Fediverse domains but there would be backlash if they did).

You wouldn’t need browser extensions to open links on your instance

App maintainers wouldn’t need to maintain lists of instances to correctly signal “I can open this” to the OS

So if your Mastodon instance just sprung up, you can just give someone a link like fediverse://masto.darkthough.ts/post/1337 and it will auto-open using the app and instance account of their choosing.

Look up what a URL schema is. Examples include https (obviously handled by your browser), ftp, mailto, ms-word etc. The mailto one is most well-known for letting you choose between in-browser (Gmail etc.) and native (Thunderbird, Outlook etc.) options on desktop and mobile. There does not need to be a formal protocol and port, it’s just a way to signal support for a kind of content via URL.

It could continue running on HTTP(S). Did you know browsers and OSs can handle different URL schemas than the ones they natively open (http, https, file, data)? Ever saw a mailto, magnet, ms-word etc. URL schema? They can be opened with an in-browser or native app of your choice, and this has worked for years. Yes, clients would need to be patched for support but that’s easy. I would only add “instance’s native UI” as a fallback for people coming from outside the fediverse.

I agree. As long as anonymous voting doesn’t cause obvious trolling/spam issues, it should be preferred.

One of the reasons I’ve always found Facebook off-putting and never used it (even before learning about the shady practices) are the very visible votes. I tend to overanalyse any reaction and would judge people based on their votes on my posts, even if I consciously tried to avoid it. Similarly, I imagine some other people would do the same and I’d feel like I’m under surveillance.