Mauve 👁💜 @mauve@mastodon.mauve.moe

I know it should be "because privacy first", and I do take it into account, but Google killing off services/products left and right for whatever reason is my main reason for not wanting to subscribe some of the stuff. https://arstechnica.com/gadgets/2023/08/google-kills-two-year-pixel-pass-subscription-after-just-22-months/

If you aren’t sure about what we add:

- an escrow system for commission deposits so both parties feel like they can trust each other more
- a shop/studio system where you can specify your offerings, with support for limited slots that are automatically managed as you accept commissions
- a discovery system where potential clients can find you
- automatic sales tax/VAT connection and remitting so you know you’re compliant
- for US artists, we even generate 1099s for you with your earnings!

Curious about #Banchan but have questions, no matter how basic, about how it works and what we can do to massively improve your commission management experience? Are you overwhelmed by how you get started? Reach out to us wherever it’s most convenient for you and we’ll help you out!

There should be a rule that any media company that pulls that shit of canning completed work for the tax write-off has to make it public domain.

I mean, if they're saying for tax purposes it's worthless then they're not out anything by releasing it free and under Creative Commons, right? Right?? 🤨

@foone the frustrating thing is that everything should be able to work together but as I understand it everything has an API and needs a library to interact with it.

Watching lgr videos and hearing about how smart devices used to be whether or not they had a computer inside them you just sent them a certain number and they would do a thing.

now you need a library and authentication and then the library isn't maintained, so a change in one of the 8 million libraries it depends on breaks it...

The reason for difference between two is in the WHATWG spec: https://url.spec.whatwg.org/#url-representation

There are "special schemes" (http(s), ftp, ws(s)) for which hostname gets actually parsed, but for the rest - everything after the "protocol" part will go into the pathname (including two “//" slashes). This is wild!

You likely don't have to worry about it, but in Electron apps this can easily result in a bug. Here's my fix for proxy-agent npm module https://github.com/TooTallNate/proxy-agents/pull/242

free software? aye comrade, and food should be free as well! and housing, and the hospital, and the library and post office too. ah, but why are these things not gratis? that is a dangerous question, isn’t it? why when there is more food than even all of us could eat, is there poverty all around us? do not limit your query to the business of software, comrade, for the villains of this play have a far greater span than your meager discipline.

Many people seem still unaware of just how bad Chrome Sync is for your privacy. By default, Chrome will sync all your data – including e.g. your passwords, bookmarks, browsing history and open tabs. And by default, Chrome will not encrypt any of this data. All of it will be accessible by Google, by anyone who subpoenas Google to turn up your data and whoever else managed to get access to these servers.

If you want this data encrypted before it is first uploaded, you need to click “Settings” instead of confirming sync, then expand “Encryption options” and set up a sync passphrase. The default option “Encrypt synced passwords with your Google Account” is essentially a disguised “We can access all your data but we promise not to look. Don’t you trust us?”

Except that they will look of course. Apparently, they now started censoring your synced bookmarks: https://strangeobject.space/@silvermoon82/110969122337810598

The only positive aspect here: Chrome Sync used to be a lot worse. It used to enable automatically when you signed into Chrome. It used to encrypt only passwords and none of the other data even if you set up a passphrase. It used to warn you when setting a passphrase because Google’s web services would no longer be able to access your passwords. It used to upload data without encryption first, only allowing to enable encryption after the fact. And its encryption used to be horribly broken. I wrote about that five years ago: https://palant.info/2018/03/13/can-chrome-sync-or-firefox-sync-be-trusted-with-sensitive-data/#chrome-sync

But even now, Chrome Sync requires you to take action in order to get privacy. Because Google knows that you won’t. Compare that to Firefox Sync which has always been encrypting all data by default. I criticized the implementation here as well, but that was really a minor issue compared to the mess which is Chrome Sync.

#Google #GoogleChrome #privacy