kogasa

joined 2 years ago
[–] [email protected] 1 points 11 months ago (1 children)

Ah, maybe we're looking at different teas though. Bear in mind you can/should steep a lot of them several times.

[–] [email protected] 1 points 11 months ago (3 children)

I have bought from Yunnan Sourcing in the past and recommend em. There is some expensive tea for sure but tons of affordable ones.

If you don't mind venturing to r*eddit, r/tea has a vendor list that is very helpful

[–] [email protected] 1 points 11 months ago

What's wrong with mssql besides licensing? It's fast

[–] [email protected] 1 points 11 months ago (8 children)

You can buy it from Chinese farmers on the internet and it's not even expensive

[–] [email protected] 9 points 11 months ago* (last edited 11 months ago)

All cloud providers will support budget notifications. That doesn't do much good when you shoot past the budget in a short timespan. I set a Google cloud budget of $20/month and enabled a Tensorboard instance, which had no observable indication that it cost anything except the base cost of the VM, and got notified that I was $280 over budget the next day. Apparently there was an upfront $300/month/user fee for Tensorboard. (Several months later they changed the pricing model to $10 GiB/month with no user fee.)

[–] [email protected] 16 points 11 months ago

Obfuscation is meaningless. It's public info or it's not. In this case it's necessarily public

[–] [email protected] 14 points 11 months ago (6 children)

Not really a substantial opinion, but I have little hope that replacing a fairly well established Rust codebase with a brand new Java one will do much in terms of increasing contribution.

[–] [email protected] 14 points 11 months ago

It could still be rust. Code is always the easy part. Design and organization and funding are hard

[–] [email protected] 24 points 11 months ago (14 children)

Not sure I understand. How could there possibly be a solution? Isn't this an inherent problem with federation? You can't un-share information

[–] [email protected] 5 points 11 months ago

It's what happens when content is url encoded and not decoded again later. It's easy to do by accident because you can't tell if a string is already url encoded in any general way, so the processes responsible for sending and receiving need to agree on how/when to encode and decode (i.e. they both have the power to break it for the other)

[–] [email protected] 1 points 11 months ago

No, no. It's perfectly safe I assure you.

[–] [email protected] 6 points 11 months ago

Don't play it on hard mode fyi, it's absurdly hard

view more: ‹ prev next ›