• 0 Posts
  • 912 Comments
Joined 10 months ago
cake
Cake day: February 18th, 2024

help-circle

  • The problem is that the actual use cases (which are still incredibly unreliable) don’t justify even 1% of the investment or energy usage the market is spending on them. (Also, as you mentioned, there are actual approaches that are useful that aren’t LLMs that are being starved by the stupid attempt at a magic bullet.)

    It’s hard to be positive about a simple, moderately useful technology when every person making money from it is lying through their teeth.




  • TLDR: You set a donation amount, it uses your GitHub account and the projects you use and distributes it through their dependencies and the dependencies of dependencies. You can also customize to exclude or boost specific things.

    Might be over-simplified, but that looks like the basic idea.

    Details

    You log in with your GitHub or GitLab account and nominate how much you’d like to donate every month – could be as little as $2 or as much as $100k. thanks.dev then collates the dependency tree across all the repositories in all the organizations you have access to and trickles your donation across that tree 3 levels deep, up to 8 decimal places on the dollar. You can scale your donation per open source project via boosting, or alternatively, you can exclude projects you don’t want any money going to. Everything else is automated.

    Why do we think this is a good approach?

    thanks.dev solves the “Who should I donate to and how much should I give them?” component of supporting open source. We think the biggest side effect of this barrier is the unbalanced distribution of donations across the ecosystem, with popular projects receiving the lion’s share of donations. The motivated minority primarily donate to the handful of projects that are top of mind. For example, Webpack receives close to $200k in funding per year via OpenCollective but its direct dependencies receive minuscule amounts of funding, and there are 80+ of them.

    Furthermore, thanks.dev makes it super easy for companies – especially larger organizations to support open source. How else could they manage the logistics of supporting the thousands of projects they depend on? There really is no way without significant effort.

    Another benefit of thanks.dev’s approach is that deeply nested packages get supported via an accumulation of micro-donations, which should ameliorate the funding component of the recent log4j incident.

    What are our ultimate goals for thanks.dev?

    An open source ecosystem in which maintainers can focus on their projects full-time, be funded by the companies that depend on them, and for those companies to attain a competitive advantage via access to faster, cheaper & more sustainable execution.

    https://thanks.dev/static/why


  • Actual researchers aren’t the ones lying about LLMs. It’s exclusively corporate people and people who have left research for corporate paychecks playing make believe that they resemble intelligence.

    That said, the academic research space is also a giant mess and you should also take even peer reviewed papers with a grain of salt, because many can’t be replicated and there is a good deal of actual fraud.









  • Mostly hyping up very simple things?

    LLMs don’t add anything vs actively scanning for a handful of basic rules and link scanning. Anything referencing a bank that isn’t on a whitelist of legitimate bank domains in a given country would likely be more effective.

    The language stuff is the only parts they’re actually good at.

    Chatbots are genuine dogshit, PDF to podcast is genuine dogshit, poetry is genuine dogshit.