Birds on a Balustrade, Melchior d'Hondecoeter, c. 1680 - c. 1690
D’Hondecoeter was the preeminent specialist in the genre of bird painting, and his work was in great demand. He painted birds from all corners of the world with a refined feeling for detail, colour, and liveliness. Here he portrayed a chicken, a hoopoe, and a parrot. D’Hondecoeter made studies in oil, which he could repeatedly use in his workshop as an aidememoire while painting. The birds occur in identical poses in other pictures.
Jonkheer J.S.H. van de Poll Bequest, Amsterdam
oil on canvas, h 51cm × w 163cm × d 10cm
http://www.rijksmuseum.nl/en/collection/SK-A-695
#rijksmuseum #musea #collection #art #mastodonart #mastoart #random
Birds on a Balustrade, Melchior d'Hondecoeter, c. 1680 - c. 1690
D’Hondecoeter was the preeminent specialist in the genre of bird painting, and his work was in great demand. He painted birds from all corners of the world with a refined feeling for detail, colour, and liveliness. Here he portrayed a chicken, a hoopoe, and a parrot. D’Hondecoeter made studies in oil, which he could repeatedly use in his workshop as an aidememoire while painting. The birds occur in identical poses in other pictures.
Jonkheer J.S.H. van de Poll Bequest, Amsterdam
oil on canvas, h 51cm × w 163cm × d 10cm
http://www.rijksmuseum.nl/en/collection/SK-A-695
#rijksmuseum #musea #collection #art #mastodonart #mastoart #random
Cheap used bike decision chain:
1. Huffy or other "bike shaped object": DO NOT BUY
2. Does the seat post move? No? DO NOT BUY
3. Spray painted over components? Only buy if you expect to replace them all, indicates poor care (or stolen) generally DO NOT BUY
4. Missing major components (brakes, shifters): DO NOT BUY
5. Major, major frame rust: only buy if you are looking for a project, can be fixed.
6. Rusty chain: -$15.00 off price. Needs a new one. Indicator of rest of bike care/wear.
7. Heavily rusted rear sprocket, wear: -$15.00 off price
8. Lightly rusted rear sprocket: easy to clean, don't worry about it.
Always assume new tires and tubes, maybe tire liners (approx $100, plus or minus, depending on what tires you replace them with)
Cheap used bike decision chain:
1. Huffy or other "bike shaped object": DO NOT BUY
2. Does the seat post move? No? DO NOT BUY
3. Spray painted over components? Only buy if you expect to replace them all, indicates poor care (or stolen) generally DO NOT BUY
4. Missing major components (brakes, shifters): DO NOT BUY
5. Major, major frame rust: only buy if you are looking for a project, can be fixed.
6. Rusty chain: -$15.00 off price. Needs a new one. Indicator of rest of bike care/wear.
7. Heavily rusted rear sprocket, wear: -$15.00 off price
8. Lightly rusted rear sprocket: easy to clean, don't worry about it.
Always assume new tires and tubes, maybe tire liners (approx $100, plus or minus, depending on what tires you replace them with)
»Math.random() is not so random — The Illusion of Randomness in JavaScript:
Don’t Trust Math.random() - Uncovering the Hidden Predictability of Random Numbers.«
In some applications random numbers are very useful but not unique and therefore you should consider where to use it. In this regard, there are for example, UUID v4 or Nano ID and the same.
🧑💻 https://vinitshahdeo.substack.com/p/mathrandom-is-not-so-random-the-illusion
#javascript #random #illusion #coding #js #code #nanoid #notunique #unique #dev #webdev #math #donttrust #uuid #uuidv4
I hope this dystopian nightmare story we're living through ends with " ... And they lived happily ever after, to the end of their days."
#random #funny #fyp #viral #explorepage #explore #foryou #foryoupage #trending
I hope this dystopian nightmare story we're living through ends with " ... And they lived happily ever after, to the end of their days."
#random #funny #fyp #viral #explorepage #explore #foryou #foryoupage #trending
Bowl with two pearl chasing dragons among clouds, anonymous, c. 1680 - c. 1720
Mr and Mrs Drucker-Fraser Bequest, Montreux
turning, h 9.6cm × d 20.4cm
http://www.rijksmuseum.nl/en/collection/AK-RBK-16285-B
#rijksmuseum #musea #collection #art #mastodonart #mastoart #random
Bowl with two pearl chasing dragons among clouds, anonymous, c. 1680 - c. 1720
Mr and Mrs Drucker-Fraser Bequest, Montreux
turning, h 9.6cm × d 20.4cm
http://www.rijksmuseum.nl/en/collection/AK-RBK-16285-B
#rijksmuseum #musea #collection #art #mastodonart #mastoart #random
Earlier today, the dog went on full alarm mode at the gate. Barking, snarling, warning of intruders. Kept on doing it! Couldn't figure out what he was going on about.
It was a...er... fierce BEACH BALL... Neighbor's grandkids were over at their pool yesterday and a beach ball ended up over the wall, and it was in the street. Every time it would blow back and forth on the street, the dog would go into a frenzy!
(walked him over there, let him smell the ball, and threw it back over the wall into their pool).
About the #random thingie ... I need random data in #swad to generate unpredictable #session IDs.
I previously had an implementation trying the #Linux-originating #getrandom if available, with a fallback to a stupid internal #xorshift#PRNG, which could be disabled because it's obviously NOT cryptographically secure, and WAS disabled for the generation of session IDs.
Then I learned #arc4random is available on many systems nowadays (#FreeBSD, #NetBSD, even Linux with a recent-enough glibc), so I decided to add a compile check for it and replace the whole mess with nothing but an arc4random call IF it is available.
arc4random originates from #OpenBSD and provides the only sane way to get cryptographically secure random data. It automatically and transparently (re-)seeds from OS entropy sources, but uses an internal CSPRNG most of the time (nowadays typically #ChaCha20, so it's a misnomer, but hey ...). It never fails, it never blocks. It just works. Awesome.
I revisited that, AGAIN. Getting #random data in #poser now has yet another fallback, in case we don't have #arc4random and we also don't have #getrandom: read from /dev/random and/or /dev/urandom, "old style" 🙈. Still better to try this before resorting to a simple little #xorshift.
In the best case — arc4random found — this is still all the code of PSC_Random_bytes() 😆:
arc4random_buf(buf, count);
return count;
https://zirias.github.io/poser/api/latest/class_p_s_c___random.html
More #poser improvements:
* Use arc4random() if available, avoids excessive syscalls just to get high-quality random data
* Add a "resolver" to do #reverse#DNS lookups in a batch, remove the reverse lookup stuff from the connection which was often useless anyways, when a short-lived connection was deleted before resolving could finish 🙈
As a result, #swad can now reliably log requests with reverse lookups enabled 🥳
About the #random thingie ... I need random data in #swad to generate unpredictable #session IDs.
I previously had an implementation trying the #Linux-originating #getrandom if available, with a fallback to a stupid internal #xorshift#PRNG, which could be disabled because it's obviously NOT cryptographically secure, and WAS disabled for the generation of session IDs.
Then I learned #arc4random is available on many systems nowadays (#FreeBSD, #NetBSD, even Linux with a recent-enough glibc), so I decided to add a compile check for it and replace the whole mess with nothing but an arc4random call IF it is available.
arc4random originates from #OpenBSD and provides the only sane way to get cryptographically secure random data. It automatically and transparently (re-)seeds from OS entropy sources, but uses an internal CSPRNG most of the time (nowadays typically #ChaCha20, so it's a misnomer, but hey ...). It never fails, it never blocks. It just works. Awesome.