#params
TODAY (March 31) at 9:00 PM CET my generative token "nd-genuary32nd-plants-chatgpt3-001" will be released on #fxhash.
The foundation was built by using #ChatGPT and this is the result of me transforming that code into a NFT.
https://www.fxhash.xyz/generative/slug/nd-genuary32nd-plants-chatgpt3-001
#generativeart #genart #nd #chatgpt3 #plants #flower #sun #midnight #nerddisco #agpl #opensource #aiinfluenced #canvas2d #params #javascript #generative #nft #crypto #tezos #blockchain #genart #art #mastoart
The NFT itself will be released on March 31 at 9:00 PM CET on
#fxhash and it’s limited to 32 editions because of #genuary32nd. It's also using #params, so make sure to check it out 🙏
https://www.fxhash.xyz/generative/slug/nd-genuary32nd-plants-chatgpt3-001
25% will go to #TezQuakeAid
I'm also curious how people are using dry-validation/dry-schema/dry-struct to handle sinatra params from forms or sidekiq job arguments. Do people use the dry-* libraries directly, or do they use one of the other plugin libraries such as sinatra-validation, sinatra-dry_params, or sidekiq-dry?
https://github.com/IzumiSy/sinatra-validation
https://github.com/tiev/sinatra-dry_param
https://github.com/zorbash/sidekiq-dry
#dryrb #sinatra #sidekiq #params
@simon right, my suspicion is that 3→4 may not be as much of a big step in terms of #params as 2→3 was, but there's nothing to base that off of other than the noticeable omission of it and the similar performance on some tasks.
Seems possible that the lion's share of the "more bigger-er" effect at work here is in the corpus/training rather than the architecture
クソ眠くて考え忘れてたんだけど、#params にclass外部から値ねじこんだりとかしてないよね?
Today I learned about URLSearchParams: A nice way to handle url parameters with vanilla javascript!
https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams