• 5 Posts
  • 22 Comments
Joined 2 months ago
cake
Cake day: April 2nd, 2025

help-circle


  • As Lemmy is federated but not fully decentralised, continuation of communities hosted on a dead instance is not currently possible. (Compare this to Matrix, where a room can carry on even if its original homeserver dies, so long as at least one other homeserver participates in it.)

    So that is indeed still a problem here, although not as severe, because I think the posts in those communities will still be available on instances that participated in them. Such communities would be forever frozen, though; carrying on from where they left off would require migrating to (or creating) communities on still-running instances.

    Lemmy does allow you to export your own data and import it into another instance. That includes settings, subscriptions, and links to saved posts/comments. So I guess maybe you could save your own posts, export your data, and import it elsewhere to keep links to what you wrote on the dying instance. I have not tested this to be sure.


  • I haven’t been following Reddit events since I left a couple years ago, but if there have been recent ban waves for bad behaviour, it wouldn’t surprise me to see corresponding upticks in it here.

    I wish more of us spoke up against rudeness, confidently incorrect ignorance, combativeness, tribalism, brigading, and other such stuff when it rears its head here. If all of us participated in moderation, I suspect it would be more effective and make our mods’ lives easier.





  • The sad reality is that while there are a lot of great people on Lemmy, there are also some who use the platform to attack others, stir up conflict, or actively try to undermine the project. Admins are volunteers who deal with the latter group on a constant basis, this takes a mental toll. Please understand why our admins chose to step down, and be kind to the admins on whatever instance you decide to join.












  • https://pubs.acs.org/doi/10.1021/acs.est.4c11265#_i24

    4.4. PFAS in Beer and Drinking Water Occurrence

    Beers selected based on their brewery location’s proximity to known elevated levels of PFAS in drinking water had 15 times the odds of having one or more detection of PFAS compared to larger-scale U.S. or international beers selected based on consumer popularity without known PFAS sources in municipal water. The PFSAs and PFOA had the highest detection rates and were also among the most frequently detected chemicals in drinking water across the United States in recent studies. (26,28,55,67) The substitution of long-chain PFSAs with short-chain PFSAs (PFBS) has also been observed with high detection rates in recent drinking water studies as well as beers we analyzed. (26,28,55,61)

    North Carolina beers, particularly those within the Cape Fear River Basin, generally had detections of more PFAS species than Michigan or California beers, which reflects the variety of PFAS sources in NC. (68) The two beers with the largest number of different PFAS detected were both located in the upper regions of the Cape Fear River Basin in Chatham and Alamance counties, where larger variability in the types of PFAS as well as higher concentrations of PFAS have been observed in surface waters in the Haw River. (14,68) HFPO–DA was detected in both beer and raw water from a drinking water treatment plant (DWTP) in the lower region of the Cape Fear River Basin. (14) The DWTP at which HFPO–DA was detected pulls in water from the Cape Fear River downstream from a fluorochemical manufacturing plant that produces the chemical. (14,69)

    Similarities between PFAS in drinking water and beer were also observed in Michigan, where Kalamazoo County had the highest reported average PFOA concentration from the state-reported drinking water of all counties in the three states. The beer brewed in this county also had the highest measured PFOA concentration of all of the beers in the study. The correlations between ∑PFAS, PFOA, and PFBS levels in beers were linked to local drinking water contamination.

    Approximately 18% of breweries operating in the United States are located within zip codes served by public water supplies with detectable PFAS in drinking water as reported by UCMR5 (as of July 2024; Figures 6 and S2). We found that international beers were less likely to have detectable PFAS or PFAS at higher levels, which may reflect the lack of or lower levels of PFAS in drinking water in these regions. The first study of PFAS in tap water in Latin America found that PFAS were not generally associated with any drinking water source in Guatemala City, the region’s largest city, which lacked PFAS manufacturing industries; rather, PFAS occurrence in tap water was instead associated with plastic water storage tank usage. (70)

    Figure 6. U.S. Map showing total PFAS (ppt; color scale) in zip codes served by public drinking water supplies reported by UCMR5 (July 2024) and locations of currently operating breweries (light blue circles). See Figure S2 for additional maps zoomed into several regions.