> I see, what do you think would be best for me to do?
Not sure. One option that comes to mind is to put the AI usage behind a one-time-only popup that confirms (via a checkbox) that the user understand that by using the AI features, their information will necessarily have to be sent to a third-party AI processor.
If they decline those terms, then the AI button/boxes go back to being disabled.
If they accept the terms and conditions for AI, then record that in their profile and don't display the terms and conditions for AI usage again.
So even though you are still leaking their data, at least it will be with their express permission.
I have these in my google calendar. Kinda forgot they were japanese and they don't line up with our (european) weather perfectly, but i still enjoy seeing them there.
It's one-indexed, counting that actual pages in the PDF. The nominal page numbers (as seen on the header/footer) are often different since you don't typically number title pages and the like, which is called "front matter". [0]
It's probably linking to the 'sequence number' rather than the page number. The cover is the first sequence number but doesn't have a page number. So if there was a few blank pages before the numbered pages started, it would probably be off by that many. I'll bet there are ways to mitigate that— PDF usually seems pretty good about dealing with the discrepancies between print and digital document structures.
Did that with an old Thinkpad (X32 iirc) years ago. I use Gentoo and some packages (like gcc) could only be compiled during winter months or in a fridge.
Also sucessfully rescued some old NVidia card with baking oven around that time…
.svg){kind=link}
