Thanks for all the work you put in. Now, how do we federate the status page so we end up needing a status page for the federation of the status of the instance? :)
There are uses for 'blockchain' based systems, for instance git uses what is effectively a blockchain to store commits. The big difference is, rather than using proof-of-work or proof-of-funds to maintain consistently, if you break the upstream repository 'Mad' Dave over there, who is trying to push his changes before the weekend will beat you with an Ethernet cable until you regret your ways.
It's likely operating the other way around. You've been being conditioned to think "I need to apply cream, I don't want dry skin" by the ads, posts and other media you've been targeted with. It was probably quite subtle to start with, but you'll have been getting related ads for a while and ignoring them. It's dark patterns all the way.
I'm not an expert, but there's a good overview of the process here: Nat Geo. You can de-paywall it at the usual places. They describe it more as "an organised broth full of chunky bits" as some organs don't break down.
It's a fascinating process either way.
As with so many problems, this one can be solved with a suitably large cannon. Why you'd want to fire cups of water into the stratosphere is left as an exercise for the interested reader.
Ha! Fair enough. I suppose that would make it even less appealing.
I tried that once. Came down in the morning to find it had vanished from my driveway. My main consolation is they would have ended up upside-down in a ditch if they tried to corner too fast.
There are multiple copies of your files; the obvious one is your 'working copy', which is just the files on your machine that you work on. The second copy is in your local object store (in the .git directory). Git stores the committed data and it's metadata there. Then there's the remote copy on your git server if you push your commits to one.
Git uses the difference between the data in your 'working copy' and your object store to work out what you've changed and so needs commiting.
That's the thing, 'cloud' is just another tool in your toolbox. It's the right tool for some workloads and the wrong one for others. The fact they've shifted the work to their own servers and kept the ops team suggests it was the wrong sort of workload to be in the cloud in the first place.
For a while there was an obsession with moving everything to the cloud, and that was always going to be an expensive mistake in a number of different ways. Hopefully, as the hype dies down more nuanced decisions will be made. There's a whole gamut of options between all in the cloud and all in the data centre, and when people jump straight from one end to the other I'm put in mind of Hamlet's quote "There are more things in heaven and earth, Horatio, / Than are dreamt of in your philosophy." Understand your workload, understand your business' future plans and their needs, and then make a plan, considering all the tools at your disposal.
That's the thing, 'cloud' is just another tool in your toolbox. It's the right tool for some workloads and the wrong one for others. The fact they've shifted the work to their own servers and kept the ops team suggests it was the wrong sort of workload to be in the cloud in the first place.
For a while there was an obsession with moving everything to the cloud, and that was always going to be an expensive mistake in a number of different ways. Hopefully, as the hype dies down more nuanced decisions will be made. There's a whole gamut of options between all in the cloud and all in the data centre, and when people jump straight from one end to the other I'm put in mind of Hamlet's quote "There are more things in heaven and earth, Horatio, / Than are dreamt of in your philosophy." Understand your workload, understand your business' future plans and their needs, and then make a plan, considering all the tools at your disposal.
I've been trying to work out if, by cutting a helix around the bagel, you can create a mobius type sandwich with two, interlinked parts.
Moving in to higher dimensional bagel cutting is probably the sort of thing you can really make one's brain hurt.
I like the way you think. That also leaves open the possibly of the yandwich, which is cut into three equal segments in the same way as the opening post, and the xyandwich when you combine the x and y options.
What do we call it if it is also cut and filled in the conventional bagel plane?
It currently depends on which client you're using. The devs are working on building it into the server side, but at least 'connect for lemmy' on android allows you to block instances yourself.
Connect for Lemmy has that and seems pretty stable.
Thank you for a calm and well expressed post, especially in light of how some of the things you read must have affected you. Hexbearians serm to be a complicated bunch, and while there do seem to be some who just want to troll, and more who sometimes just want to let off steam, I've also seen some well thought out arguments there too. In general, if their mods can get the more egregious problems under control, and they're not making too much work for the mod team here, I'm in favour of keeping them federated. I may not agree with them, but they should still be heard.
Nah, the top set are just gaps between the tentacles. You'd be pretty grumpy too if you spent endless aeons looking at the world through your face tentacles because you couldn't find a scrunchy to hold them back.
For something like that i'd take a parameter like this (repeated as necessary):
--custom-repo=<name>=<synctype>+<url>for example:
--custom-repo=custom=git+https://github.com/matcha/custom