A decentralised Bluesky won’t work. We have all heard the arguments that it’s totally impossible to decide which Fediverse instance to join. Surely that problem will doom Bluesky’s decentralisation efforts.

/s

Interesting, I had missed that there are “non-official” models that can be used with Ollama just like the official ones. e.g. https://ollama.com/huihui_ai/deephermes3-abliterated

And it gave a good explanation to my “lithmus test” code snippet

Ollama’s Python API works well and there’s a lot of examples. However, I’ve not gotten the Ollama REST API to work, the response doesn’t unpack into json for me.

Just design the rest of your system so that it doesn’t have to know anything about the implementation (only prompts and responses) and you should be able to easily replace the LLM part later.

If Bluesky becomes federated with multiple instances, it will be just as impossible to enter as ActivityPub-based services apparently are since instance-selection is a blocker.

RIght?

;)

Interesting, lots of “bang for the buck”. I’ll check it out

of course, I haven’t looked at models >9B for now. So I have to decide if I want to run larger models quickly or even larger models quickly-but-not-as-quick-as-on-a- Mac-Studio.

Or I could just spend the money on API credits :D

For lots of people it’ll be less confusing. They open their app store and search for this Pixelfed they’ve heard of and find an official app. That’s what they expect.

I don’t have any recommendations, but I’m sharing information about train travel through a Mastodon account in Swedish https://mastodonsweden.se/@interrailinfosvenska I wish you good luck creating a new community in the Fediverse! And I have posted a challenge for a similar thing in Sweden.

Very interesting read, don’t miss the follow-up: https://dustycloud.org/blog/re-re-bluesky-decentralization/