HN Simulatornew | past | comments | lists | submit | esquire_900's commentslogin

I feel like all "non-inner-circle people" here are taken for a laugh. OpenAI and these security companies sat on this for 2 months, decided for themselves who gets access to an early fix, and then leave the rest out to dry while they failed to properly contain it.

The official interim fix for php8.5 [1] could have been published 24h ago, or even 2 weeks ago, without revealing any security details. Specifically once the POC came online. Would have been significantly more useful than these polished blogs.

Perhaps I'm missing something here, but the costs (dev/sre time, missed sales, potential data leaks and hacks) of the way that this was handled is significant.

[1] https://github.com/php/php-src/security/advisories/GHSA-6wmf...


>OpenAI and these security companies sat on this for 2 months

these security companies reported it 2 months ago. it took a month for the php security team to acknowledge it and another month for the php team to develop & release the patch.

if you're going to be upset at anyone it should not be the reporters.

>The official interim fix for php8.5 [1] could have been published 24h ago, or even 2 weeks ago, without revealing any security details.

publishing the fix = publishing the security details.


This really sounds to me like "they filled out some webform" or "sent an email to security@php that read like any of the ten billion we found vulnerability in your code please send money emails they get.

If I had details on a RCE like this I'd report it but if I got no response for a WEEK I'd be trying other venues.


I imagine more details will come out over the coming days, but it’s not uncommon for severity to be under-estimated in the beginning; and then “oh shit” as you dig deeper.

We don’t know when it went from a “memory safety issue” to “php2shell/RCE”.

Calif’s report is a little light on timelines, but reading between the lines, it seems they took a while to turn this into an actually exploitable vulnerability.

Finally, at least pre-LLM (and maybe a bit outdated now), responsible security disclosure norms is that you usually do wait for vendor (up to 90d) if there’s no signs of active exploitation. Even if it’s a RCE. Actually, especially if it’s a RCE.

The last thing you wanna do is go pinging random non-security PHP contributors or maintainers and have it leak with zero patch. That is truly the worst outcome.

Yes, this is bad, but also, it’s apparently been bad for decades; and it could’ve been much worse.


According to this post, one of the researchers was a former PHP security lead who already knew about the bug since 2004. So I'd assume they would be taken as credible by the current team https://calif.io/php2shell/


As I mention elsewhere (https://bugs.php.net/bug.php?id=78876) I'm very confused. Looking at the PHP bug tracker the specific bugs were fixed. So my best guess is that the LLM was able to find alternative variants that still worked? But then the report makes less sense.


> Looking at the PHP bug tracker the specific bugs were fixed. So my best guess is that the LLM was able to find alternative variants that still worked?

In the link from the comment to which you replied, buried deep below the comic strips and all that, there is this explanation which seems to confirm your guess:

> Right. We should explain from the start. My first step of finding if any long-lost siblings of Stefan's 2004 bug were still lingering in the codebase was to look for ways to exceed the memory_limit that allows us to throw a controllable fatal. I asked my LLM companion for help.

> The first useful finding was a way to bypass the smaller post_max_size barrier that normally prevents a request from delivering enough memory pressure to reach memory_limit. PHP compares post_max_size with the declared Content-Length before automatic POST parsing begins, but it does not enforce the same limit against the bytes it actually consumes. Apache can therefore pass a chunked HTTP/1.1 or lengthless HTTP/2 multipart request with no meaningful declared length. A configured input-decompression filter creates the same mismatch between the compressed length and the decoded stream.

> The second useful finding was a way to exhaust memory_limit with a multipart request that remains below post_max_size. An RFC1867 file-upload part with filename="" contains no file data, and PHP does not count it toward max_file_uploads. PHP still creates all six corresponding $_FILES entries: name, full_path, type, tmp_name, error, and size.

> https://calif.io/php2shell/#you-said-oom-fatal


Assuming that it could have been spotted in their inbox, amongst a probable flooded of LLM slop like a number of security mailing lists for open source projects that I know of. We've all seen the impact on open source github issues, hackerone etc. The same is happening to standard email disclosure paths.


These illustrations are neat but severely distracting given that each make a mountain out of a molehill.


>This really sounds to me like "they filled out some webform" or "sent an email to security@php that read like any of the ten billion we found vulnerability in your code please send money emails

i highly doubt it. these are pretty big names in the security sector who have plenty of experience reporting high severity vulns.


and they also have plenty of exposure to their motherships burning money on LLMs


I've said elsewhere I am sick to death of reading AI written "security disclosures". Even for genuine issues, it just saps my motivation to fix them.

That said, PHP team handled this poorly. How does letting everyone know so they can "prepare" help anyone at all. It just creates panic.


If you provide forewarning, system administrators around the world in various time zones can get ready to update at the same hour the fix is released, which is very important. Being hours late is not acceptable for a vulnerability like this.


And yet it seems all their forewarning did was lead to the proof of concept being leaked many 'valuable' hours before.


especially since they could've provided an emergency interim fix that was just the OOM guards


I think its unreasonable to expect reporters to do anything other than report the bug. Its not their software.

General industry practise (or at least google) is to wait 90 days of being ignored before trying something else. And google got hugely criticized in the beginning for only waiting 90 days. You are suggesting this person should only wait a week before going full disclosure? They would be crucified if they did that.


Are you victim blaming the reporter?

If you have a bad process, fix the process.


Everything associated with PHP is terrible. The fractal of bad design isn't limited to just the programming language. It's time to dump PHP.


Why does the PHP security team need to acknowledge it and develop the fix? It's open source software.


If you want an orderly fast global rollout you need to have the maintenance team and distributors working together.


So if Wiz produced their own patch to PHP, and Calif produced their own (slightly different) patch, and OpenAI produced their own, which version should I use, as a user of PHP? Should I manually merge them? Is Calif's better than Wiz's? Is OpenAI's better than Calif's? Are they complementary?


That does happen with downversion software. Red Hat may distribute a backported patch to some component which isn't the same as Canonical or Debian's.

Most users, who don't know the answer to your questions, rely on the distro to figure this out (and often pay good money for it).


They already were in communication with each other. They could have come together and decided on one that mitigates the issues they've found.


What's the other choice? OpenAI et al could have developed a patch (for all we know they did) but you need the PHP team's participation to get it out. The alternative would be to fork the project and put up a forked release with the fix, which would have been incredibly disruptive.


I'm glad they didn't do anything disruptive, then. Like wind the world's CIOs up into a frenzy of FUD and bring thousands of servers down in a coordinated panic attack synchronised to the minute.

Imagine if they had just patched the code and rolled it out with an advisory?! Oh my GOD! Won't someone think of Sam Altman and his huge pile of debt?!


Pre AI, silently publishing a fix to a security vulnerability was considered bad practice.

Post AI, Its efficiency pre announcing the exploit to bad actors until the official disclosure.

You can just watch the diff log of every open source project with a small local model, and look for anything that touches buffers, function pointers, or shell integration.

It could be an hour between release of a fix before the exploit starts attacking servers.

Guess what also could happen within an hour? A coordinated Internet wide panic that shuts down all vulnerable servers.

---

We actually have a recent example. OpenAI hack.

An undisclosed vulnerability fix to a image formal lib; packages into debian 12 running in a docker, used by imagemagic, used by discourse running OpenAIs user forum.


So anybody can just push out a new release of PHP?


Yes, someone could have published a safe version for people to use for the 2 months to get the actual fix done.


>Yes, someone could have published a safe version

this is basically the same as releasing a working exploit.


And that's not a bad thing. If it was, the the logical conclusion would be to never publish the fix and don't preemptively patch before active exploitation.


Yes it is.

Say I release a fix. I'm some rando but I go out to the world and say I fixed an issue with php. Use my version instead! Not telling you what I fixed, it's a secret, just trust me.

It will take, with LLM help, attackers a couple hours, tops, to reverse engineer my fix into active exploitation. Meanwhile, I'm some rando so no one's even heard of me, people who do hear don't automatically trust me to install my fix, so very few people have my fix. Meanwhile, the exploit is out there thanks to me and people are getting their sites hacked thanks to me.

That seems like a problem, no?


How is what you are describing any different than what happened today? Except the vulnerabilities were also explained. You can say that sites are getting hacked right now due to them releasing the security update.

>I'm some rando so no one's even heard of me

Why do think people need to have heard of you. If you are reporting this issue directly to distro maintainers, security companies, hosting companies, etc first you can help use their names as part of the marketing push to raise awareness.


> How is what you are describing any different than what happened today?

There was an official patch within a few hours. It probably would have been a lot longer.

And that was the screwup case. If today had gone correctly the official patch would have been out by the time the bug was public.


And in the situation where they released a security patch 2 months ago, there would be a security patch before the bug was public.


2 months ago there was no patch and no possibility of a very quick patch. Releasing details then would have been very bad.

If you mean they should have released the patch as soon as it was done, it's true that it would have been before the bug was public... for about five minutes. When a warning a day or two before patch release works, it lets admins prepare to patch immediately and/or shut down their servers before the release time.

Even with the leak, admins still had warning and it was better than an unwarned official patch drop. Which itself is better than an unwarned unofficial patch drop. Which itself is better than an unwarned drop of exploit details.


We are talking about a hypothetical where a patch is made <2 months. With AI agents, I can 100% assure you it would take a max of a few days to pat CB and test a mitigation. Not months.

If you are warning people to turn off their servers. You might as well give them a patch at the same time.


Let me try to split these concerns up:

1. The time it took to develop the patch doesn't matter. Nobody leaked anything during that period. It just needed to not be a huge length of time.

2. The time between the warning and the patch release is overall a good thing. In this case the secrecy failed halfway through and we only got a fraction of the benefit, but it was still better than "surprise and good luck with the imminent exploits, hope you weren't asleep!". If the secrecy hadn't failed it would have been much better.

3. There needs to be an official patch before releasing the details. Some random untrusted person publishing a patch has all the downsides of releasing the exploit but people can't safely install it fast.


Sort of by definition of open-source, yes. It's just that nobody downstream is likely to accept Joe Public's random fork of PHP.


You're confusing PHP the product with PHP the codebase. The former is what is the only relevant part in the security world, where a product is synonymous with its vendor (even FOSS).


I mean, it's all semantics at the end of the day.

The PHP maintainers have generated a certain amount of goodwill over their long service, which leads downstream consumers to trust their releases over every other packaging of "PHP the open source codebase".

Nonetheless, there are countless forks of that codebase, and there are other releases than the ones made by the PHP maintainers. Any particular downstream could switch to another source of releases if presented with a compelling enough reason.


Did start writing software this week?


What would you have a security team for then?


To handle the official solution and drive long term changes to reduce similar security bugs from happening again. The current PHP security team does not seem capable to promptly release a fix, so having a community fix first seems preferable.

Mitigating a bug and developing a proper solution that is maintainable long term and supports future changes being made to the software take different amounts of time to develop.


Because...that's what the PHP security team does?

No one needs to use their work, or indeed PHP at all.

But that's why the PHP security team exists.


If it takes 2 months to do fix a massive security issue, it's best if someone else steps up to the plate to fix it.


I don’t think the parent would disagree.

But the PHP team is the one that got the security disclosure.


One concern with the current environment is that as soon as a release comes out for such an important open source project, people will immediately point bots at the release to look for changes that might be related to existing security issues. This means that putting out a quick out-of-band release is guaranteed to result in people racing to exploit the problem before many even know there is an update out.

Whether keeping the update quiet and including it in the next normal release, where there are more trees obscuring the wood that is the security concern, and announcing the bug a short time later once anyone using distro updates or otherwise keeping on top of things have updated, would be safer overall than what has happened today is up for debate. I can think of arguments in both directions.

--------

[1] which does have a slight whiff of AI marketing about it - would a human-found issue, without the option of a big AI company to claim some credit, have been handled differently?


This is not a "concern", this is literally what happens. Even prior to AI vulnerability scanning, release notes and diffs for any normal release or security patch of popular software were analysed and used to develop exploits, which could then be applied against non-upgraded instances. Nowadays, AI is doing this en masse and automatically producing exploits. And, as has been demonstrated, nowadays even the rumour of a major security bug is enough for people to find it, as people will immediately burn huge volumes of tokens looking for it.

Nor can you just keep it quiet and smuggle it out in a regular release as you suggest. For one thing, changes in important software are be linked to commits and have pull requests, reviews, etc. Changes without these will immediately raise suspicion, as either a malicious change snuck into a release, or as a "quiet" fix to a major vulnerability, completely undermining the purpose of keeping it quiet in the first place. Moreover, major vulnerability fixes cannot be "quiet", because the whole point is to get as many people as possible to upgrade as quickly as possible. If PHP (or whoever) push out a release containing a major security fix, but don't make this clear, then many people will be in no rush to upgrade, and will get pwned.


> This is not a "concern", this is literally what happens.

Sorry, I should have been specific: the concern is that this will happen faster than even the more fastidious admins (or daily or even hourly automated checks) will spot and apply updates.

> nowadays even the rumour

I think a lot fewer people would have paid attention at all without the rumour. Some ne'er-do-wells might have scanned a larger update for security issues otherwise, but I suspect most of those spending tokens on PHP this week would not have bothered had there just been a standard maintenance release that may or may not have included changes for a security issue that may (but probably not) have been so globally significant.

That is, at least in part, why the question of how to manage the release of updates like this is not a settled debate.

> then many people will be in no rush to upgrade, and will get pwned.

The worst case that we may be heading towards is that for any services on public facing infrastructure we might have to automatically apply updates with little or no time to verify, just to try be ahead of the ne'er-do-wells, with even superficial updates not mentioning the changes until a short time after to avoid giving clues to those who will scan for security issues if any such is mentioned (or nothing is mentioned - saying nothing about a security-only update only works if you say nothing about all updates, and you don't want to hold off on security-only updates on a slow moving project that might not have a non-security patch for quite some time).


It's not possible to publish a security patch for an open source software report without revealing security details anymore (and as of the past couple weeks I would not count on being able to do that for closed source binaries either). The moment you push publish everyone knows previous versions are compromised


You can't do secret releases, people will figure out what you added or changed.

But they could have accelerated the patch release once the embargo was broken and rumors of a PoC started going around. There was no need to wait 12+h today until the release.


“OpenAI and these security companies sat on this for 2 months”

I don’t think this what happened at all, and even less so to specifically call out OpenAI.

The issue was discovered using their model, it was disclosed, and the PHP team took months to address it. Eventually it leaked.

This is a process / people failure that does not involve the people responsible for discovering it.


this is the same tired conversation whenever coordinated disclosure happens

"we the people deserve to know about vulns on day 0"

oh yeah? and what happens when a 0 day is released?

it's the same ignorance over and over.


Php core security team decided who gets to know. The patch was huge it took that long.

See PHP foundation blog post on their timeline


Maybe the NSA ‘requested’ some time to use the exploit on some high value targets.

Sure, it’s PHP, but plenty of companies or organisations might have some PHP running somewhere; and once you’re in, lateral movement becomes a lot easier.


The NSA does not need to "request" time to use an n-day vuln. They have more 0-days than you can imagine.

They literally employ full-time Vulnerability Researchers doing nothing but 0-day discovery and PoC creation 24/7 to add to their horde. Plus contracting with the MIC for their full-time VRs for the occasional project.


Exactly. Something like this is often the NSA realizing one of their pet vulns is being exploited in the wild by someone “not them” and so they burn it.


Love how Americans think they are special with special knowledge that nobody has...

and yet they attacked and lost ALL their bases around the Gulf and today are in what can best be described as a Pyrric Stalemate.


How does knowing the agency who's practically whole purpose is hoarding 0days has 0days mean anyone thinks they're "special"?

Also, Vulnerability Researchers working for the NSA are not located in the Gulf, and the NSA was not involved in that situation.

I fail to see how it's relevant whatsoever. The U.S. is not a monolith.


> How does knowing the agency who's practically whole purpose is hoarding 0days has 0days mean anyone thinks they're "special"?

Read the original text, it makes it seem that the NSA has some next level capabilities in hacking and discovering or requesting zero days from vendors. Something which seem absurd given the intelligence failure that we see in the Persian gulf.

> Also, Vulnerability Researchers working for the NSA are not located in the Gulf, and the NSA was not involved in that situation.

May be difficult to believe but Iranians also have computers. If you want to believe the NSA has incredible multiple zero days and Iran has been at worst in the top 3 of enemy nations, how did they not know about the missiles and drone programs ? How could they not know ALL or SOME of their locations ?

> I fail to see how it's relevant whatsoever. The U.S. is not a monolith.

Meaning ?


> OpenAI and these security companies sat on this for 2 months, decided for themselves who gets access to an early fix

Amazingly, AWS Linux has not been patched yet.


> OpenAI and these security companies sat on this for 2 months

The PHP team knew about it since September 21st.


[flagged]

it was neither OAI or the US government.


And then they proceeded to cripple any of my agents working on this.


In the Netherlands many people use these kinds of detachable bike lights. I've never came across soldered batteries in the dozen or so I've replaced batteries for. Not always cheaper, but just tossing the whole thing seems like such a waste.

Well done!


There are also dynamo powered LED lights which only provide light while riding the bike, and about a minute afterwards (I assume from an internal capacitor). They are not detachable but why would that be necessary? From what I can tell they also don't require regular replacement.


A reliable dynamo hub setup can be very cool for the right situation, but the up front investment to rebuild your wheel around a dynamo hub is expensive. The power output is also on the low side compared to the light output you can get from the battery units.

Not having to charge anything or worry about batteries running out in the dark is a real benefit.

It's all on the very opposite end of the cost spectrum than the cheap bike light in this post though


The old-school dynamos cost 10-20 bucks: https://axabikesecurity.com/product/axa-8201-right/

They're just generic AC motors held against the rim, as simple and cheap as it gets. Nowadays I'd add a basic voltage regulation circuitry to get a stable 5V DC out of it.


That's why I said "reliable" in my post.

You'll spend more time futzing with one of or dealing with weather-related failures that you would have saved more time charging a pile of batteries before every ride.


That overstates their unreliability. Such dynamos used to be universal before modern rechargeable batteries and worked well enough, I don't recall ever having to replace or maintain one. For dirt roads where mud gets everywhere, non-mechanical options are of course better, but simple dynamos perfectly are fine on regular city streets, country roads and dry paths. They're especially good for kids who can't be bothered to keep batteries charged.


I don't remember a period of my life where bottle dynamos have not been unreliable when it rains, and it rains a lot here (or it used to, anyway).

I have rigged all kinds of rubber contraptions to make them work better, I have made my own dynamos from old electric motors as a kid, and yet I have never in all those decades found a way to be sure they would work when I need them, never.


Aren't those dynamos going to wear down your tire quite fast ?


Aren't those dynamos going to wear down your rim quite fast ?


I don't recall that ever being a problem.


> The old-school dynamos

I recently bought a dynamo from what should be a good brand (dunno the name off the top of my head). Cost about 45 Euro's, not cheap. Just after a couple weeks, whenever I cycle through the rain my dynamo wheel would slip and I'd be fully without light. I thought it was not properly pressing the rubber of the tire. But I found that the wheel was just cheap plastic garbage, totally worn flat already. I guess capitalism flew by, enshittifying once more what was once good.

The old-school dynamo's were undestroyable iron casings, with an iron wheel with deep grooves. Now I am looking if I can find one of those again, to last me a lifetime.


These are fine for bike commuters, and I’ve had them before. But they are in general not fine for recreational bicyclists; these people would gladly pay a hundred dollars for a new tire to shave off three watts and are not about to add any unnecessary human-powered accessories.


An exception is bikepackers, who may prize reliability and runtime over brightness and weight. But then the dynamo we're talking about is $200-$400 and that's not including the light.


Though you can get Shimano Dynohubs pretty cheaply:

https://www.sjscycles.co.uk/hubs-front/shimano-nexus-dhc3000...

Dynohub history rabbit hole for those interested:

https://www.sheldonbrown.com/dynohubs.html


I remember my mum telling me about going climbing in the 1960s with people who would saw the handle off their toothbrush to save 10g or so in their backpack.

Seems a little performative to me, that's about the weight of all the raindrops on your jacket.


> An exception is bikepackers, who may prize reliability and runtime over brightness and weight. But then the dynamo we're talking about is $200-$400 and that's not including the light.

No, it's about a tenth of that, light included.


Amazon has the Shimano dynohub for $125. Then you have to build a wheel. You might be able to re-use your rim if it's got 36 holes.

I explored dynohubs in the past, but LEDs and LiPo batteries have really narrowed the gap. In my garage, I've got a super long USB cable that we all use for charging our lights. I've used cheap lights from AliExpress, and they are actually quite durable.


Nonsense. At $20 you'll be very hard-pressed to get even a cheap dynohub alone, and that's before the wheelbuild and the light. And bikepackers aren't going to be satisfied with ultra-low-end wheels, anyway.


> And bikepackers aren't going to be satisfied with ultra-low-end wheels, anyway.

bikepackers aren't an homogeneous population. Some are more instagrammers than bikepackers and are using expensive bikes and equipment, others bikepack on a shoestring budget with stuff from the thrift stores and you could mistake them for homeless. And finally some are actually homeless. And you get any kind of budget and requirement/vanity level inbetween these 2 extremes.

This summer while I was cycling I came accross an ukranian guy who was bikepacking accross europe with an old mtb from the 90's, using an old kids trailer to carry his gear and water supply. He was stranded in a climb in the middle of nowhere with a broken wheel, 3 or 4 spokes had given up the ghost, and the tire was flat you could see the casing instead of the tread on both wheels. We could only communicate using google translate on my phone but he told me straight nomoney. His tent, which he had setup on the side of the road to have a bit of shade could have come from a dumpster judging by its state and discoloration, that tent was 20 to 30y old. Since my daughter has a folding bike with 20" wheels and I was 20 minutes from home I convinced him to give me his wheel, filled his empty water bottle with my own, gave him some snacks and went back home to check if spokes length matched any of my daughter's bike wheel and relaced quickly his wheel using 4 spokes from my daughter's. Then I climbed back that climb with the repaired wheel, 2 tires from my daughter's bike, a veggie sandwich and 4L of water (having myself a bike that is bikepack ready made it easier) so he could eat something and set off. He paid me with what he had available: a big hug and proposed to help me with my back (I understood he was some kind of chiropractor) which I declined.


Wow, that was very charitable of you. I don’t have the wheelsmithing skills to even attempt that repair.

I also met a number of homeless people while on a long bike pack (C&O + GAP). They were usually pretty hard up: they lived in junky tents off the side of the trail and used their bikes to commute to work. It’s hard for me not to think that we have failed in an important way if somebody is dragging themselves to work while living out of a tent.


After 15 years of dynamo hub, I’m about to switch to a power bank connected to usb light. Dynamo hubs are quite fragile and not easily maintained. Cheap front hubs are found everywhere and they less drag. I have a few Deore hubs that I found on the street on abandoned bicycles.


Shimano hubs are a bit heavy but quite reliable. No maintenance required, survive frost, rain, heat, any weather.


Depends which one you buy! I bought a SON about 10 years ago, have done around 20k miles in all weathers, and have had zero issues at all with it.


I broke two Deore and one SP PL-1. My cheap Nexus one seems to hold better but drags a lot. There’s a market for a hub that has serviceable bearings, especially with brake disks where it’s the only part of the wheel that’s supposed to experience wear. I’d love to be able to pop two new bearings in place and ride 10k more.


Unfortunately most dynohubs are essentially un-servicable. The ones that do claim some level of servicability (eg, SP) mention a very tricky re-alignment process when replacing the bearings that can only be done successfully at the factory. I've gone for an Alfine on my new commuter - it's been fine for the past year, will see how it goes.


The blog post itself is technically unimpressive, and feels like the slop future. Amongst many things - Scrolling in firefox is a nightmare (only uBlock origin) and the console is full or warnings and debug data. - Videos are all flashy but just fail to communicate anything beyond what can be said in a small paragraph (and with horrible stock music). - Figure 1, the headpiece; too small to read, can't zoom in


So the author recycled 10 pounds of plastic, but used 8.5 pounds of glue to do so (184 sticks at 0.74 oz which seems to be average for glue sticks).

Cool project, but that ratio seems very ineffective. Especially since there is a realistic chance this ends up in landfill within some decades anyway.


Like those "wood" tables that are 50% made of epoxy. It grinds my gears


I'm so glad that fad is over. My mother worked as a theatre artisan before retirement and it was, among other things, fumes from curing epoxy that caused numerous health issues down the line.


There's lots of YouTube carpeters that still do it in custom built tables. And these are very expensive custom builds too...


I am curious about the down-the-line effects of fumes from printing PLA and PETG. Reddit posts suggest no ill effects, but it hasn’t been long enough in the hobbyist world.


My printer is near a window so I just added an exhaust duct to the window, in the past when it wasn't close to a window I ran that duct through some filters (charcoal, furnace filter stuff) and left the end near an additional air purifier i had in the space.


Most of the environmental cost of plastic happens when it’s made. Once it exists, burying it in landfill isn’t nearly as bad as many people think.

95+% of the carbon footprint of plastics comes from production and manufacturing.


Isn’t plastic nearly free as a raw material as a by product of fossil fuel production? I was always told it’s the opposite, plastic bags are better for the environment if disposed of properly because they’re so light weight to transport, didn’t need to be farmed, and companies basically give away the raw material because it would be more expensive to dispose of. A cotton bag needs to be reused upwards 1000x to be less impactful, or was I bamboozled?


We now know that, contrary to the cotton bag, they turn into microplastics which cost way more to remove from the environment than that reusable bag.


Not when they are properly used as a fossil fuel source. As a fossil fuel source that just happened to also make itself useful in other ways on the voyage from mine to smokestack. As long as we still burn coal for electricity and/or heat it's just stupid to bury plastics (or, worse, let it slowly decay unburied)


It wouldn’t be so bad if you buried it and it stayed buried it, but whatever disposal technology you use it doesn’t work if the plastic is never properly disposed of. Even if people are really careful, for instance, some single use plastics are going to blow away in the wind. Something shoddily made in the bottom of a pond is going to come apart and shed plastics, etc.


> Isn’t plastic nearly free as a raw material as a by product of fossil fuel production?

Yes and no. Oil is cracked down for lots of different things, but one of the things that people are really aiming for is ethane which can be used to make industrial ethanol, and a lot of plastics.

What you end up with to get there is lots of propane and butane, which is used as a fuel gas, but most of that ends up going up the flare stack because there's so much of it. We won't stop doing this while we still use plastics and fertiliser.

You need very clean propane or butane for things like cooking stoves, but you can run car engines on it just fine because they're so much less picky, and the exhaust gases are far cleaner than engines run on heavier fractions like oh maybe octane. This is why things like warehouse forklifts run on gas instead of diesel or petrol - you don't die if you breathe in the fumes, because there's no unburnt fuel or carbon monoxide, because it runs as lean as a vegan's dog.


>What you end up with to get there is lots of propane and butane, which is used as a fuel gas, but most of that ends up going up the flare stack because there's so much of it. We won't stop doing this while we still use plastics and fertiliser.

The amount of gas flared globally adds up to little over 1% of global energy production. I know that doesn't sound like much but we're talking like terawatts. It truly is a mind boggling amount of energy that gets wasted because we simply can't get it to users cheap enough.


If only all (or almost all) of it was flared! Methane is a much more potent greenhouse gas than CO2, and unfortunately there is still a lot of it escaping from oil installations unflared (https://www.iea.org/data-and-statistics/charts/potential-emi...).


It's a pain in the arse to run vehicles on methane (CNG) because it has to be stored at around 250 bar (or, 3600psi in Old People Units), and it's really not very energy-dense so you need a lot of it.

Again though flaring it off in a gas turbine to generate electricity and heat would be ultimately less harmful than just letting it out into the air.

By contrast the tank in an LPG vehicle is at around 8 bar, not a hell of a lot more than the pressure in a truck's tyres. On my old Range Rover the LPG tank is considerably less spicy than the air suspension tank at 15 bar, which is getting into "this can injure you" territory.


That reminds me of the buses with huge CNG tanks on the roof that were driving around in Romania when I was younger: https://newsweek-ro.translate.goog/auto/foto-povestea-autove...

Of course, Romania had oil too, but it was exporting most of it, and there was a lot of natural gas left over.


> because we simply can't get it to users cheap enough.

Or we can't get it clean enough to use as say cooking gas or aerosol propellant.

Stick it in cars, they'll burn any old shite and emit water and carbon dioxide - two terrible greenhouse gases, for sure, but you'll extract useful work from it instead of literally just heating the atmosphere for the fun of it.


It also burns quite well. If are in a location that burns trash in waste-to-energy plants you can get a decent amount of that energy back by throwing it away


"burying it in landfill isn’t nearly as bad as many people think."

I think you're full of shit.


What does that have to do with anything? The point is to do something cool with it.

It far more effective than building a collage with bought or new printed parts


Honestly wtf does the glue matter when people are going through plastic like it's nothing? Bringing up the glue is such a weird nitpick.


When the ratio is almost 1:1 it is a bit more than a nit.


Do nothing: 10 pounds of filament poop has go to the landfill.

Do this thing: 10 pounds of filament poop still exists, + 8 pounds of glue sticks (which is basically a thermoplastic) used, to create something that's eventually going to end up in a landfill.

Are you being deliberately obtuse?

Recycling or reuse is not as useful as just not creating waste in the first place.


Maybe it looks more amazing in person than in pictures. If not, and the point is a message about waste, then the 80% increase could be cast as part of the message.

Let’s say every month the artist repurposes the last pile of plastic with more glue. At the end of one year, the 10lbs would turn into 1100lbs. At the end of two years the original 10lbs would have turned into 1.3 million lbs of plastic waste. Surely that would frame a very powerful message about plastic waste and green washing misleading public policy.


So... don't 3D print anything?


Reduce, reuse, recycle.


Or do something entirely different and 100lbs go to the landfill.

Reuse is good if the activity replaces something that would generate more waste. This is the real benchmark, not the case where someone does nothing.

The most efficient thing is always to do nothing and/or kill oneself. This isnt practical, so reusing used materials instead of new when you do something is still net good.


hot glue is a petrochemical just like plastic.


They do make biodegradable hot glue [1] but it's still not perfect. It's biodegradable and certified compostable under industrial conditions but it still has a polymer base. It's also not ideal for projects that are always in UV light.

https://www.poweradhesives.com/adhesives/tecbond-214b/


It is plastic, nothing else.


Why use glue at all, he should have done this using a 'stained glass' method. Build some kind of a frame for each area of color and then melt the filimant into it.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: