Thank you to the GGML team for the tensor library that powers Ollama’s inference – accessing GGML directly from Go has given a portable way to design custom inference graphs and tackle harder model architectures not available before in Ollama."
Thanks for the linked article! I was looking for a local vision model to recognize my handwritten notes, and this article provided a good TLDR about doing this in Ollama.
I think Ollama can improve TLDR and add more attribution to llama.cpp to their README. I don't understand why there's no reply from ollama maintainers for so long
How is this not a compliance risk? Automatically transferring data, including personal data, to the cloud without explicit consent raises GDPR concerns.
It appears they don't care about those people. Windows is not the product.
If you are not consuming their cloud product AND providing a stream of your telemetry data for them to monetize, you are of no value to MS and so invisible.
Microsoft will give them whatever they request. When you spend that much money you can just ask for a custom build. I would imagine that NSA TAO and other such parts of the USG are provided access to much of the Windows source already.
Microsoft and US intelligence and the US armed forces are practically vertically integrated at this point, they are the Lockheed of software.
I remember seeing "Windows is a service" update popups in my Windows 10 VM. That was the last straw before I went out of my way and disabled the deliberate RCE^W^W Windows Update services completely.
They will force it, probably. I think for enterprise edition, they will allow it.
Also, guys be ready to make your phone number ready because Microsoft seems to require it. They have successfully impinged their tentacles on people's privacy.
Click "Setup for Work or School", then click "Domain Join instead". Since they don't want to figure out a way to expose DNS settings in OOBE (that you might need to discover a domain controller), they just ask you to set up a local administrator account and assume you'll complete the join at the desktop.
This is how I've always setup 10 and 11 Pro, I never knew about the whole unplug the ethernet method. I knew that was required for Home, but not Pro.
If google is generating content that you will sell as a book yes. Legally you could get sued. Remember google uses the content under fair use for there service. You can't claim fair use when you try to sell someone elses code.
I agree that what Google does is considered fair use. They show your content as snippets and they gain knowledge about topics and improve their search engine based on your content. I don’t see a big issue with what Github is doing either, as long as it’s not a near duplicate of the original content.
What would this tracking mean in regards to following the EU ePrivacy directive? My understanding is that session resumption mechanisms could be used to track users by capturing the session ID and associating it with the user's IP address, it should follow that the use of such devices should be allowed only for legitimate purposes, with the knowledge of the users concerned?
"(24) Terminal equipment of users of electronic communications networks and any information stored on such equipment are part of the private sphere of the users requiring protection under the European Convention for the Protection of Human Rights and Fundamental Freedoms. So-called spyware, web bugs, hidden identifiers and other similar devices can enter the user's terminal without their knowledge in order to gain access to information, to store hidden information or to trace the activities of the user and may seriously intrude upon the privacy of these users. The use of such devices should be allowed only for legitimate purposes, with the knowledge of the users concerned.
25) However, such devices, for instance so-called "cookies", can be a legitimate and useful tool, for example, in analysing the effectiveness of website design and advertising, and in verifying the identity of users engaged in on-line transactions. Where such devices, for instance cookies, are intended for a legitimate purpose, such as to facilitate the provision of information society services, their use should be allowed on condition that users are provided with clear and precise information in accordance with Directive 95/46/EC about the purposes of cookies or similar devices so as to ensure that users are made aware of information being placed on the terminal equipment they are using."
Source: (24) Terminal equipment of users of electronic communications networks and any information stored on such equipment are part of the private sphere of the users requiring protection under the European Convention for the Protection of Human Rights and Fundamental Freedoms. So-called spyware, web bugs, hidden identifiers and other similar devices can enter the user's terminal without their knowledge in order to gain access to information, to store hidden information or to trace the activities of the user and may seriously intrude upon the privacy of these users. The use of such devices should be allowed only for legitimate purposes, with the knowledge of the users concerned."
The ePrivacy Directive makes a bit of a distinction between data stored on the client, vs network information. Cookies are the former, IP addresses are the latter. From reading the paper, the TLS session ID is stored on the client, and sent to the server. So for the ePD, this is in the same category as cookies, not IP addresses.
The complicating factor is that the TLS session ID has a legitimate purpose, and this tracking is a secondary use of that data. I know what GDPR says about that topic, but I'm less familiar with the ePD. I'm trying to read the law, but it's less approachable than GDPR. I think secondary uses still require strict consent, but I'm not sure.
The UK implementation of ePD is a pretty strict application, only allowing 2 grounds to use a "cookie" (note that means other identifiers like session identifiers, although everyone says cookie.
One grounds is necessity to deliver the packets to you (IP address can be used to route a reply back to you in TCP/IP), and the other grounds is to deliver a feature you explicitly request, and can't be done otherwise (adding an item to your shopping basket, for example).
Neither lets you go beyond functionality, so use of a TLS session identifier to me would be a straightforward breach, if the purpose was anything beyond basic connection setup. At that point, informed, explicit, specific, opt-in consent is required. And contrary to all the illegal cookie walls, you can't require or presume this consent - that isn't consent!
Thank you to the GGML team for the tensor library that powers Ollama’s inference – accessing GGML directly from Go has given a portable way to design custom inference graphs and tackle harder model architectures not available before in Ollama."
Source: https://ollama.com/blog/multimodal-models