@markstos interesting.

• I'm pretty shure this is something for @antidiskriminierung to look into and get @BNetzA to ask #Google why they surpress comms like that per default with neither opt-in nor legitimate interest…

Even tho I doubt #Google's #GoogleWorkspaces can comply with #GDPR & #BDSG at all...

There are just so many "where and when do I build? rest? persist? resist? bring fists?" choices.

On the 6 month scale; I don't see switching the org where 100% of it's revenue flows through a Ruby on Rails app as particularly beneficial.

The other cooperative is already bringing 2/3rds of it's revenue off of services running on #Python, But that's running on top of #GoogleCloud, which is... you know... Google.

And then they're *both* in #GoogleWorkspaces and #Heroku which are... #Salesforce and #aws

Across both, we're probably spending ~$400k/yr in cloud services.

And we currently spend $0 on Ruby on Rails stuff.

So from a time/talent/treasure tradeoff perspective, there are bigger fish to fry.

I would love to get us onto a #CoopCloud infrastructure provider that uses green VPSes, but that is also a N Quarter Project, and there are higher-benefit-to-client-and-community-and-colleagues ways to spend that time and the treasure it costs to equitably buy that time from the crewmates who provide it.