It is important to stop the introduction of these chemicals and microplastics into our environment. That should be the number one goal - to stop it at it's source instead of dealing with it after the fact. Depending on how the filtration systems scale, not everyone would be able to benefit - and certainly not wildlife which is affected.
In the meantime, it may be effective to remove these chemicals from your body through regular blood and plasma donation[0]. Although not entirely altruistic, I doubt those in need of emergency blood are asking if it contains PFASs. In the end it helps you and those in need.
I have also recently switched to stainless steel cookware and picked up a LifeStraw home water filter[1] that claims to reduce these chemicals in your drinking water.
If the goal is security, then there is more to it than just using a memory safe language. Otherwise the result of this, possibly unwittingly, seems performative.
I have been using Brave Search for a year now. It has been great. It provides relevant results and I love how Brave AI floats a summarizer to the top with cited and hyperlinked material when applicable.
Very rarely I will need to hit the Find Elsewhere 'Google' button. This is usually done for niche technical searches where Google prioritizes some forums dedicated to the topic like Reddit or Stack Overflow. I _could_ re-search with the site operator, but after scrolling down with the Google escape hatch there, the flow just seems more natural.
Just as an aside, I have also been experimenting with SearX searches. The experience isn't as streamlined as Brave Search, but I can incorporate Brave Search into my results. I find the value proposition interesting for SearX, but implementation still lacking.
If this isn't standardized in an organization it should be. Otherwise, it's the same repetitive questions, the same finger pointing, and the same miscommunication. If these are the requirements needed to put a service into production, then make it explicit. As the developer, of course I own the service, but (usually) don't have the access. Standardized as requirements, both teams can work together to produce, monitor, and troubleshoot production services smoothly. Then nobody is surprised when it is release day, and asked these questions with an impatient PM whom has already publicly set expectations.
I love Firefox. I use Firefox on Android with UBO. However, I wish they allowed about:config tweaks and user.js so we can have full control of our browser on mobile. To adjust about:config I'm forced to use Firefox Beta on Android.
I think going forward to be consistent with Firefox's values, the user should be allowed to turn off telemetry etc via about:config and I hope they make this available in the future.
I like the new UI. As with all major UI changes there will be some backlash. People become set in their ways of old UI/UX, accustomed to the training and ease of use. Users will have to adapt. And that takes effort. People hate forced effort.
I am very happy now that the android UI matches the web. I have been waiting for this for sometime, and the disconnect prior was disorienting.
I use this on my daily driver every day and is a great option to the "standard" systemd-logind or elogind. I think of it as a shining example of sourcehut's core values.
Mostly because of the philosophy of the software's author. This was the selling point for me. It is incredibly small scoped by design, easy to understand, and is very explicit in it's actions. It is not as "user friendly" as other inits, though the author is currently working on making it more accessible. It practices separation of mechanism and policy, it attempts to do less than more, and it know when to stop and not introduce scope creep. All by design. I won't ever have to worry about it becoming a system layer and reaching into my network stack, or making policy decisions for me.
I'm sure other available init systems have their selling points - but to be honest, after reading s6's reasoning and design goals I was sold. I'm happy to report that after a year and a half I'm pleased with the decision.
I have long been an advocate against systemd for the typical reasons (overreaching responsibilities, lock-in, lack of choice, software assumption "it will be there", complexity, driven by large corporate interests [see lock-in], being modeled after launched, etc etc). I feel like the chickens are coming home to roost.
That said, if one wants to use it, then use it. However, there are alternatives which I would love to see receive more adoption. I've been extremely happy with my Artix [1] system running s6 [2] init.
I'm not sure of any distros that have default s6, but Artix[1] allows you to pick your init/service manager. It is what I used and I am very happy with it.
I'm glad to hear it. I find s6 extremely stable. I've learned to come around on execline and have been converting bash scripts to it when I have the thought. The idea of it makes sense (to not load a heavy shell when kicking off a service and chain loading programs for small footprint).
I _think_ I did something similar to what you mention, though I'm not familiar with guix. Analogous to systems, what I _did_ like about systemd was the user level service management. So I essentially kick off a user privileged supervision tree for my session with s6 with its own scandir and service db when launching X. It is not under the root supervision tree but lives side by side at this moment since 1) I wasn't aware of s6-usertree-maker at the time and 2) i wanted any user to be able to kick off user privileged services without root intervention (e.g. setting up usertree-maker)
I used systemd for a time, and after looking into all the documentation I found it hard to understand and it's scope overreaching. It doesn't stand by the unix philosophy of mechanism not policy and is prescriptive in it's inplementation. As another comment stated, the politics behind how it was pushed never sat right with me and I believe it is leading the Linux community to vendor lock in.
I have been using s6 on Artix and find it a great init system and service manager with a clear cut design goal of knowing where to stop. It does what it is supposed to do and no more - by design. It doesn't have the user friendly interface of systemctl but that is being currently worked on. If one is looking for an alternative to systemd, I think it is an excellent option to consider.
Yes. I introduced this with great success at my company. Every day a member of the dev team would post their standup to a dedicated slack channel.
It accomplished a number of things: people could make their own hours as long as they post sometime within 24 hours it didn't matter, it was persistent so people can search history (what was everyone doing on Friday), and commentable so those who need to get involved can start a thread on the post and schedule a meeting if need be for sync communication to follow up. It accomplishes everything of an in person standup, but is more efficient and respects people's time.
I've been reading about the tech behind bitcoin and I find it interesting yet have been skeptical due to some perceived flaws. I've been concerned about the market externality due to the amount of energy it takes to mine blocks. What are some alt coins worth exploring?
I'm not sure I understand what you are stating here. The universe does in fact exist. When _your_ brain ceases to exist the universe will still be here, and my brain's interpretation of that universe is my consciousness.
In the meantime, it may be effective to remove these chemicals from your body through regular blood and plasma donation[0]. Although not entirely altruistic, I doubt those in need of emergency blood are asking if it contains PFASs. In the end it helps you and those in need.
I have also recently switched to stainless steel cookware and picked up a LifeStraw home water filter[1] that claims to reduce these chemicals in your drinking water.
[0] https://www.ncbi.nlm.nih.gov/pmc/articles/PMC8994130/ [1] https://lifestraw.com/products/lifestraw-home