Hacker Newsnew | past | comments | ask | show | jobs | submit | Jarwain's commentslogin

With LLM's, I wonder how far away we are from "a cooking ground for people to experiment with ideas"

Getting further all the time; with LLMs you're offloading all of your experimenting to VC jerks

You say this like "oh it's just acts on a different kind of opiod receptor" means that it's not meaningfully different.

Your comment also seems to imply that this treatment involves consuming ibogaine habitually or regularly

The protocol for ibogaine treatment, according to the article and the experiments being done, do not have this requirement.

Like other treatments involving psychedelics and hallucinogens, the protocol here is that a one-off treatment, a single dose, results in meaningful improvements in both addictive behaviors and PTSD symptoms a month later and potentially longer

This is not the same as something like methadone or naltrexone, which _are_ what you describe: replacing a more harmful opiate with a less harmful one.


The effect could be totally psychosomatic, that’s the thing we don’t know at this point. The fact is that noribogaine acts on the my opioid receptor, regardless.

There's some prior work on the codebase thing:

[Unison](https://www.unison-lang.org/docs/the-big-idea/) content addresses every definition. Kinda interesting.

A [Code Property Graph](https://en.wikipedia.org/wiki/Code_property_graph) takes a codebase and turns it into three graph representations: it's AST, a Control Flow Graph, and Program Dependence Graphs. These graphs are overlaid and shoved into a single property graph. It's a structure mainly used by some static analysis tools like [Joern](https://joern.io/)

---

This has been a topic of a lot of interest and research for me. I've been experimenting with figuring out a system inspired by these ideas, among others, to apply the same idea (shoving multiple graph representations together) to a broader set of information


I'm a big fan of bolt hangers personally. They also mark the spot, provide a nice anchor point, and don't require chopping!


Looks like something that would pop a tire if you drive over one


Not much difference between a 12" and a 18" lag bolt for the purpose of "how much trash is visible and impacts terrain".

Surface feels a bit fairer in that sense. Or at least, easier to measure.


If it was that'd be an absurd amount of weed being left behind to make a mark on the map.


The problem isn't that there aren't solutions, the problem is getting everyone on board


This penalizes honest mistakes, or moop from prior years resurfacing, or wind blowing trash into camp, or any number of things that are outside of a given camp's control

The moop map, and community holding itself accountable, seems to be a decently functioning system.

Not to mention the administrative overhead, at the org level and at the camp level.

Frankly being a camp of 100+ people, not just taking dues but also handling this Deposit, and distributing the cost fairly?

Running a camp is enough of a pain in the ass without adding on this kind of thing.

Monetary incentive systems like what you're suggesting are just a way of enforcing culture. If culture spreads organically, why bother with the overhead of bringing money into the picture?


Honestly, that contrast is what draws me in. In the same way ultralight hiking forces you to think about and let go of extraneous weight, going to Burning Man and doing the whole camp thing and seeing the city work showcases the "dead weight" of "making things happen".


They aren't referring to the regulatory requirement, but the response, I think?

Like if people can put in this much time and effort in a remote desert environment to meet regulatory requirements, and document their efforts so thoroughly, why can't corpos?


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

Search: