favs.blue
  1. 1

    Huge amounts of capital were raised to buy Sulaco, a successor to Nostromo (the Mac mini on top). Bought second hand from a friendly older couple this Mac Studio will soon come online on @cocore.dev to provide inference not from the moon but from a humble suburb in the Netherlands.

  2. 2

    Attic (attic.photos) beta release 21 is now out. github.com/tijs/attic/r...

    this version improves the compatibility with stricter S3 endpoints, this fixes a user reported issue where it did not work for Google cloud storage S3 compatible storage.

  3. 3

    Ugh, three(?) weeks into iOS Dev Weekly being sold and it's already turned into AI slop. If you ever find yourself copy pasting this sentence into something you actually send out in your own name, please stop publishing and go do something you actually enjoy: "The quality lives in the gap." 🤢

  4. 4

    Reply to @why.bsky.team

    Well if you read the article it does say programming is the only domain which has verifiable loops right now

  5. 5

    Oh man umans.ai is getting so much mentions on here it’s almost inevitable I’ll open an account there soon

  6. 6

    switched to Qwen 3.5 4B but it's still idle. what's up with that? nothing is good enough for these people! #spoiled

  7. 7

    @hotsocket.fyi see your hosting the ornith model on @cocore.dev! I'm curious to try that model but you have not enabled tool calling. Considering model capabilities I think it would run fine with tools on, any chance you could update to the latest client and flip that switch perhaps?

  8. 11

    Ever wonder what most people weren't listening to? obscure.cat has so far indexed 100K+ tracks from 385 @teal.fm scrobblers. and were only showing tracks with 1 play.

  9. 12

    Reply

    Squircle!

  10. 13

    Reply to @tijs.org

    @cocore.dev would it make sense to enable tool calling by default for models that likely can handle it?

  11. 14

    Reply to @nickthesick.com

    Since the data is available via atproto records generally (not the book details but at least the user activity/data) I think it would be fair to block at least the most prolific scrapers? But as long as you can keep uptime and serve all I guess that’s neat too

  12. 15

    Reply

    @apex.atproto.ceo be the change you want in the world ❤️

  13. 17

    Reply to @iame.li

    It’s been like 6 years now I think 😛

  14. 18

    Reply

    Oof yeah that sucks. And honestly I don’t have any optimistic angle for that. It’s become much easier to rip and remix stuff. You have built up name/brand recognition though I’d say, gotta be worth something

  15. 19

    Reply

    I’m not super worried. Good writing will keep attracting more people than slop, this is just an age of experimentation and some will turn out not to work very well

  16. 20

    Reply

    Good call to make this naming very clear to avoid any confusion. Tool intents is the plan for cocore but it’s called tool calling everywhere since that is what people know. But perhaps this needs more explicit clarity in current/upcoming UI

  17. 21

    Reply

    I'll look into it 👍

  18. 22

    Reply

    oh yeah like the others probably I just went with the default pick from the cocore client. sorry will change :)

  19. 23

    Reply

    made some small tweaks. still can't get it to work for a full pi agent but that's seems more to do with the model not being smart enough than the implementation, with a simplified pi setup it now works with tool calling for me!

  20. 24

    Win win

  21. 25

    Reply

    Carmageddon 🥹