With #renewables, even just domestic solar panels and privately installed batteries we can get domestic electricity mostly for free in a few years in many developed regions of the world. The electricity companies will do everything to make that impossible. But their claims of a grid that can't cope only shows their centralised approach that favours big consumers is failing ;)
But it can be done. Communities can buy back or create themselves the power lines needed for domestic use. They can build communal power storage units that decouple (hyper)local grids from the Big Grid. It needs an #OpenStandard to control input and output to that local grid. Which is being worked on. Clean electricity can power private homes very soon. For free.
There should be an open, universal standard/specification like USB, WiFi or Bluetooth, but for wireless data transfer (basically AirDrop, but for everyone).
It's only an #OpenStandard if you can choose between at least two #OpenSource implementations of which one is not produced by a member of the SSO (Standard Setting Organisation). And yes, it is OK if more implementations exist that can even be proprietary, as long as interoperability is a given.
One thing I miss from the golden age of #Facebook, when pretty much everyone was on it and kept their #profile up to date, was that it was easy to find how to message someone. When I wanted to contact someone who I hadn't talk to in a while, I just used Facebook. I didn't had to worry that I had a wrong or outdated email address. I could see their profile to make sure it's the right person, and that they had been active recently so my message wouldn't get lost in the void. It was reassuring.
This system should be an open standard, so that all existing contact book apps could implement it. Kinda like an updated version of CardDAV (https://en.wikipedia.org/wiki/CardDAV).
And ideally, all of that would be end-to-end encrypted, so that only your friends get to see your personal data. The host where you store your profile and your friends hosts should not be able to read your contact info!
A kinda weird question. If you were to write an #OpenStandard, just the standard document itself: Under what license would you put it to make sure it is irrevocably available for free to anyone but also making sure it cannot be altered by downstream recipients? 1/n
(For background: One of Thunderbird's core principles is the use and promotion of open standards - this focus is a rejection of our world of closed platforms and services that can’t communicate with each other. Our upcoming marketing efforts will really lean into this, and we want a long-term hashtag to accompany it.)
Today's question for a resilient #Fediverse is whether various different initiatives are willing to collaborate and cross-pollinate, while keeping their independence.
There's great opportunity to increase the cohesion of the #GrassrootsFedi#ActivityPub developer community and creating strong joins:
@danjac@smallcircles@w3c@fedidevs@Codeberg@dansup@EC_NGI@EC_DIGIT It's what I've been saying since many years without being heard :( Every #OpenStandard MUST consist of the Standard, an Open Source reference implementation and an open source validator to test interoperability against. All three MUST be maintained by the Standard Setting Organisation. Without this it isn't an Open Standard.