HN user
It has actually improved a lot since then. The UI has had changes, search is better, it has quote posts now. More usability enhancements are under active development.
They pivoted from pure BEV to bet their future on Hydrogen FCEV trucks. They were a flop and that's what sunk them IMO.
They're aware of the problem.
https://www.reddit.com/r/duckduckgo/comments/1cynfft/duckduc...
It's not stalled.
Ok it's not growing at the crazy rate that hit when news of the Musk twitter takeover broke. That's not a bad thing as the infrastructure couldn't sustain it, but it is growing.
I'm following @mastodonusercount@mastodon.social and it reports a consistent steady growth in the number of user accounts. As of 48 mins ago ..
12,811,208 accounts
+594 in the last hour
+2,367 in the last day
+195,778 in the last week.
.. and it's quite typical to have just over 200k new accounts a week.
Then there was the news that on the 17th April 2023 the number of monthly posts across the Fediverse crossed one billion for the first time.
Personally my timelines are a hive of activity, far more than I can possibly keep up with.
It doesn't look or feel stalled to me.
My biggest anxiety with hardware-backed security is what happens if someone breaks into my house and steals my laptop and phone. Today I would buy a new laptop, login to Bitwarden using my strong memorised master password and carry on. If everything about me is linked to hardware-backed passkeys then my digital life walks out the door with the thief.
I live in Northern Ireland (also part of the UK) and we're very well served here too. I switched from copper to fibre about a month back. Could have gone 1Gb but chose a cheaper 500Gb DOWN / 75Mb UP package (no data limits) as I didn't think I'd notice the difference. Speed tests show I get very close to both. Very happy.
And? If you don't trust TLS then I assume you don't trust web banking, or purchasing anything over the internet for that matter. Might as well give up on technology and go find yourself a nice quiet pastoral life.
Like most of your replies, the UK is the same. Its everywhere here.
Oh that looks cool. Will investigate this. Thanks.
ChromeOS runs Debian in an LXD container. You can install desktop apps in it (e.g. using Flatpak) and they appear as launchable icons on the ChromeOS desktop. Being LXD you're not just limited to one container either. I have additional multiple containers with Ubuntu and AlmaLinux on my Chromebook and can use other LXD features to snapshot and publish them as required. This is far from being "useless".
Maybe there was some content on mastodon.social they didn't like. As they don't integrate with ActivityPub they can't block individual users so perhaps they chose to block the whole domain instead.
It's not like they're cutting off the whole Fediverse. There are hundreds (thousands?) of mastadon instances and none of the others will be affected by this.
"cotton bags should be used 131 times"
And? Most of the reusable bags in my house are 3-5 years old. We even have a couple that we brought with us when we moved home 11 years ago. Using them hundreds of times is the whole point.
I've never understood how links can fall victim to copyright. A link is just a signpost instructing your browser where to go next. There is no copying involved, anywhere. Subjugating links with copyright law is morphing reality into fantasy.
Depends what you want to do. If you're happy for changes to dribble in over time then size your puppetmaster pool to how many hosts you want to be able to run puppet simultaneously and stagger client execution to avoid a stampeding herd. Accept that sometimes there will be individual failures due to load and clients will just have to wait till the next time.
Alternatively, in real life, many teams have Change Management to consider and Maintenance windows. If there's a need to update thousands of systems on a saturday morning then expect teams to start puppet runs manually. You'd better have a seriously big pool of puppetmasters ready and waiting to manage the load, and don't forget Puppet DB, that has to be scaled up too to avoid lock ups. Even then, if teams start too many puppet runs at once, you'll get flattened.
We ended up scrapping all the puppetmasters in individual DCs and consolidating them in an AWS EC2 Autoscaling group. The number of puppetmasters started at 70 and just went up. That came with problems of its own. e.g. ensuring that all puppetmasters share the same copy of role versions at the same time. Being able to spin up new puppetmasters fast enough to meet spikes in demand. Various other corner case tuning issues.
It's taken a dedicated team years to get to grips with puppet, tame it and master it. Very glad I'm not involved in that any more.
How secure is E2EE anyway when, like WhatsApp, it's implemented such that you blindly trust a 3rd party to distribute the public keys and instruct your client who it should be encrypting and sending your messages to? How do you know your mobile app isn't also sending encrypted copies of your messages to a ghost user you have no visibility of? A ghost user that could be WhatsApp, law enforcement or anyone.
They have a point. We used to use Hipchat until Atlassian retired it. We took a good look at Slack, negotiating over the price. In the end the decision was made to use Teams as we were already paying for Office, so effectively it was free. It's very difficult to argue against a value proposition like that.
There used to be a lot more information in binaries in general. These days everything is stripped. Giving my age away here :)
I'll happily bet against you, but I'll let Sabine Hossenfelder explain why. https://youtu.be/LJ4W1g-6JiY
There will probably be booster shots later to protect against variants like this. In the meantime, Lambda is not getting a foothold where Delta is common. The more transmissible Delta variant appears to be squeezing it out.
Understand. Did some quick tests myself and see what you mean.
Here's a version that doesn't use "here string" and so doesn't create temporary files.
#!/bin/bash
shopt -s lastpipe
string="Los Angeles, London, Belfast, New York"
echo "${string/, /,}" | readarray -d, -t arrayA
echo ${arrayA[0]}
echo ${arrayA[1]}
It's the read/readarray builtin that's creating the tmpfiles and that's not great, but the string substitution doesn't. My point was there's no need to call out to another program to do something that bash is capable of doing itself.
If you have newlines present then process the data a line at a time, as you would if reading from a file. This is nowhere near as difficult or cumbersome as you're making out.
The long rebuttal from bgoldst fails to answer the question of how to solve this "in bash" when he introduces additional commands like tr(1) and sed(1). You should avoid using additional programs to perform actions where bash builtins can do the job. The extra overhead and impact on runtime of context switching to load in a new program is non-trivial if you have to loop over it thousands of times. It's better to normalize the string data for use with 'read' using builtin string substitution.
$ string="Los Angeles, London, Belfast, New York"
$ IFS="," read -r -a array <<< "${string/, /,}"
$ echo ${array[0]}
Los Angeles
$ echo ${array[1]}
London
Don't have the free time today to read the rest of it unfortunately.
AlmaLinux are also publishing Errata. That's not something we enjoyed with CentOS and I don't think Rocky have any plans to do this currently.
I tried this recently for the first time using Elements and have struggled with it. There's no message threading, so it's very hard to discover the history and flow of a subject when it's embedded in a larger conversation. I'll keep an eye on this and check back from time to time, but right now it's not for me.
Linux on Chromebooks is Debian buster running in an LXD container. Being LXD there's no reason why you're limited to just one container either. I don't like to mess around with the default "penguin" container too much so I've added more. I've currently added centos7, centos8, ubuntu and another debian container. Plus you can take LXD snapshots, rollback, publish images etc.
Hint: Add a Ubuntu container and install LXD, then copy the lxc binary to your "penguin" container and setup a trust between it at the Chrome OS "termina" hypervisor. Then you can manage all your containers from the default linux install.
I have a Pixelbook Go with 8GB of ram and a 128GB drive.
If you need history then still put them on a web server and increment the filenames. Storing large files in a git repo is a misappropriation of the tool. It wasn't designed for that use case.
I switched from Samsung to Pixel for the same reasons. Samsung's additional bloatware and their penchant for installing new things I didn't ask for drove me nuts.
Ok, so now I'm confused about what Magnetic field lines are. Many years ago I asked a friend who had a physics degree what Magnetic field lines were made of and gave him an example of those generated by earth propagating through the vacuum of space. His answer involved an interaction between virtual particles and the electromagnetic field. But that doesn't fit with this description of virtual particles.
In the article Strassler says: "A 'virtual particle', generally, is a disturbance in a field that will never be found on its own, but instead is something that is caused by the presence of other particles, often of other fields."
So if a virtual particle (disturbance) can only exist in the presence of another particle, what other particles are involved in the generation of magnetic field lines? I didn't think there were any.
Similar situation to yourself except we already have some Ubuntu as well. Decision is yet to be made. Ubuntu is a viable alternative and just as capable as CentOS if not more so these days. Snap is there in case what you're looking for isn't already available in a repo, but it's not mandatory to use it. One of the nice things you get with Ubuntu is LXD System Containers. Think half way house between application containers (docker) and full fat VMs. Super impressed with how lightweight and flexible they are (snapshot, cluster, publish, migrate, etc).
If you're really paranoid about getting burned by a proprietary business decision again in the future have you thought about Debian? Providing your hardware is supported it's also a solid choice. It can also optionally run snap and LXD Containers (via snap currently).