The ai training data flag
Has_not_been_viewed_much
81–90 of 127 posts
Re: Has_not_been_viewed_much
#82I thought this was lovely, and was surprised by the date: https://www.artic.edu/artworks/196937/summer-moon-at-miyajim...
1930s is the tail end of Shin Hanga: https://en.wikipedia.org/wiki/Shin-hanga
Re: Has_not_been_viewed_much
#83
Re: Has_not_been_viewed_much
#84did it get hug of death?
I read that some people are having trouble with cloudflare and VPNs. Being an art school, I imagine they’re disinclined to make it easier for a bazillion people every day to thoughtlessly point a scraper at their site to vacuum everything up for training data.
Re: Has_not_been_viewed_much
#85I just wish the variable was called "has_been_viewed_much".
Wouldn’t a view count with range filtering provide the best flexibility?
Absolutely, I was purely reacting to the "not". Every variable named not-something will lead to difficult-to-read code with double-negation like "if (!isNotSomething()) {...}".
Re: Has_not_been_viewed_much
#86I used to borrow the books which had "to be disposed if not lent in the next 3 months" slip in them. Never regretted reading them. The best one included a very odd short story by Flann OBrien about a carpenter who walls himself inside the oak panelling of a build he is working on, and a woman convinced Sago farming will cure Ireland's famine.
I understand the romantic appeal of discovering "abandoned" books and forgotten ideas.
However I suspect my reaction to your anecdote is very different to the one that most people might have, because I think that behaviour is harmful to the library. ( A very minor harm, but a harm nonetheless. )
They have identified books that people don't borrow, and have made it clear they want to get rid of them. That's to benefit the library, catalogue and storage isn't free and endless.
So they have a signal that no-one is borrowing these books, and they can replace it with books that do get borrowed.
Along you come and interrupt that signal, in a way that doesn't have underlying desire to borrow that book. So the clock gets reset, and so it goes.
In software development terms, imagine you develop a product with a number of features with a public API, and telemetry points that a feature goes unused. You want to clean up the code so you mark some endpoints as deprecated and list that in your change log.
Now imagine there's a developer who looks at the changelog for deprecation warnings, then goes out their way to develop apps that call them.
"Unloved books" might seem more romantic than un-called API endpoints, but the library needs to rotate and refresh to stay healthy.
If you want unloved books, then pick them up for next to nothing from the sale outside the library, most libraries will practically give away books they've rotated out, and you're actually doing them a favour "disposing" of them while likely giving them a token amount of money for it.
Re: Has_not_been_viewed_much
#87I used to borrow the books which had "to be disposed if not lent in the next 3 months" slip in them. Never regretted reading them. The best one included a very odd short story by Flann OBrien about a carpenter who walls himself inside the oak panelling of a build he is working on, and a woman convinced Sago farming will cure Ireland's famine.
Struggling to find the carpenter’s story, do you remember the title by any chance? Thanks!
It was a hardback of early works and unfinished pieces. I can't find publication details but there have been some recent publications including "Slattery's Sago Saga" which is the other story I mentioned, so maybe it would be in them?
Re: Has_not_been_viewed_much
#88I used to borrow the books which had "to be disposed if not lent in the next 3 months" slip in them. Never regretted reading them. The best one included a very odd short story by Flann OBrien about a carpenter who walls himself inside the oak panelling of a build he is working on, and a woman convinced Sago farming will cure Ireland's famine.
I understand the romantic appeal of discovering "abandoned" books and forgotten ideas. However I suspect my reaction to your anecdote is very different to the one that most people might have, because I think that behaviour is harmful to the library. ( A very minor harm, but a harm nonetheless. ) They have identified books that people don't borrow, and have made it clear they want to get rid of them. That's to benefit…
If the library wanted to get rid of them, they would've quietly removed the books; I suspect they want people to read them before they're removed, hence the "please give this book a chance" marker.
A deprecation marker is a "this will be removed"; these markers are "this will be removed if nobody reads them even with this marker in them".
Re: Has_not_been_viewed_much
#89I just wish the variable was called "has_been_viewed_much".
why, though? the current version is the interesting property
There's a rule of thumb somewhere that booleans should always be named / represent something positive, so "enabled" instead of "disabled", "visible" instead of "hidden", and "has_been_viewed_much" instead of "has_not_been_viewed_much".