An ex-Google, ex-Apple, leadership chatbot focused on improving outcomes with data and cat memes, hustling 24/7.
thatsnothowyoudoit
joined 1 year ago
2 years plus source code and working oss backends or 10 years (and still source code).
2 years will just ensure endless forced upgrade cycles IMO.
Shawshank Redemption.
The Big Lebowski.
Also Star Trek 2.
So many great ones though.
Write to LanguageTool. They’re OSS in name only at the moment. I self-host their server, but the client is only usable on desktop and limited to web browsers without their paid version.
I’ve long been asking to be a customer, but to use their self-hosted server for privacy.
I think there’s a small but growing market for folks that want a quality grammar and spell check but don’t want data sent to the cloud.
If I could connect iOS to my LT server that’d be so rad.
Haroun and the Sea of Stories
All the Muderbot series
Old Man’s War series
There sadly isn’t a viable one at the same level of functionality.
Edit: some random other comment appeared here. Fixed.
Agreed. Companies should be required by law to release source code, build guides, documentation and service architecture for services or apps that are required by hardware they sold.
While there are bigger fish to fry at the moment, socially speaking, the problem is only going to get worse if legislators don’t step in.
Building off the other reply - it’s the standard UX/UI design tool these days. Name a popular SaaS tool - their design / product team likely uses Figma.
They were recently in the news after their acquisition by Adobe fell through.
They also recently release a competitor to Google slides/powerpoint.
Pros:
- you run a home lab
Cons:
- you run a home lab
Thanks for the reply. Makes sense. I haven’t had any jobs recently that would push us there.
CC is also priced low enough we can sign back up for a month if we need it.
One feature set of CC I’ll miss is the libraries functionality working across all the apps. Someone on the team needs a client asset in any app ? (AE/ID/PS/AI) There it is.
Easy to block that - though not with pihole exclusively.
We use another tool at our network edge to block all 53/853 traffic and redirect all port 53 traffic to our internal DNS resolver (works much like pihole).
Then we also block all DoH.
Only two devices have failed using this strategy: Chromecast - which refuses to work if it can’t access googles DNS. And Philips Hue bridges. Both lie and say “internet offline”. Every other device - even some of the questionable ones on a special VLAN for devices we don’t trust - work just fine and fall back to the router-specified DNS.