You probably don't need fine-tuning, at least if it's just new content (and no new instructions). It may even be detrimental, since LLMs are als good at forgetting: https://twitter.com/abacaj/status/1739015011748499772
Good question, as you can see I haven't touched it for a month. I wanted to show what's possible then with open source and (open) local models and there's already so much new stuff out there.
I'll probably fix some things this week and then either update it or start from scratch. Guided generation, structured extraction, function calling and multi-modal are things I wanted to add and chainlit looks interesting.
We just held a workshop about this a few weeks ago: https://red.ht/llmappdev
We created a simple chatbot using local models with Ollama (llamacpp), LlamaIndex and streamlit.
Have a look at the streamlit folder, it's super easy.
I used this simple example to teach about RAG, the importance of the system prompt and prompt injection.
The notebook folder has a few more examples, local models can even do natural language SQL querying now.
If you want analytics you have to rely on a 3rd party provider who somehow gets the information by logging into your account. I guess if you're a key account they will send you some data and maybe even some nice visualizations.
I did some research and people really track their audience with spread sheets. Influencers send screenshots of their accounts to advertisment companies to prove how many followers they have. Seriously..
If they want to monetarize their platform they should open at least part of their API.
It has been estimated on bitcointalk that around 1-2% have been lost. That's not really a large amount. You can still divide bitcoins into satoshis (1E-8) or even further with a protocol change in the future.
Who decides what is legal and what not? Is it even legal for an ISP in the US to monitor your traffic or to act like this without a court order on behalf of a shady company? I don't get it that nobody is protesting about this...
Yes I know, this is a bug in Google Translate. However, the bug was found by a user using Google Now and was reported in the Android issue tracker. The issue was described very well and is reproducible. I am criticizing that nobody seems to check the reported issues and the time it takes for Google to fix the reported problems.
Wow, this speaks volumes about their QA process, especially for Android. This bug is known since October '12, how hard can it be for a company with 50k employees to fix a bug like this?