http://www.pji.co.kr/get.do?ex=Coupon&ac=selectCoupon&szDiscountCode=<쿠폰 코드>
ex) http://www.pji.co.kr/get.do?ex=Coupon&ac=selectCoupon&szDiscountCode=JY25
[{"szdiscountnamelocal":"(JY25) 배달 주문 시 피자(L이상) 30% 할인","szdiscountcode":"JY25","szdecode":"30","szfreeproduct":"","ndiscountid":"4266","szvalidatedate":"1"}]
Hi Nicholas,
I saw you tweet about JSX yesterday. It seemed like the discussion devolved pretty quickly but I wanted to share our experience over the last year. I understand your concerns. I've made similar remarks about JSX. When we started using it Planning Center, I led the charge to write React without it. I don't imagine I'd have much to say that you haven't considered but, if it's helpful, here's a pattern that changed my opinion:
The idea that "React is the V in MVC" is disingenuous. It's a good pitch but, for many of us, it feels like in invitation to repeat our history of coupled views. In practice, React is the V and the C. Dan Abramov describes the division as Smart and Dumb Components. At our office, we call them stateless and container components (view-controllers if we're Flux). The idea is pretty simple: components can't
| document.write("<script src='http://libs.baidu.com/jquery/2.0.0/jquery.min.js'>\x3c/script>"); | |
| !window.jQuery && document.write("<script src='http://code.jquery.com/jquery-latest.js'>\x3c/script>"); | |
| startime = (new Date).getTime(); | |
| var count = 0; | |
| function unixtime() { | |
| var a = new Date; | |
| return Date.UTC(a.getFullYear(), a.getMonth(), a.getDay(), a.getHours(), a.getMinutes(), a.getSeconds()) / 1E3 | |
| } | |
| url_array = ["https://github.com/greatfire/", "https://github.com/cn-nytimes/"]; |
I'm geographically located in Seoul, Korea and traffic to api.fmf.io always get routed via LAX servers. My server is located in Tokyo, Japan so it adds up a lot of delay on the request. Tried with different ISPs and all same result. My friends are also experiencing this with their free plan enabled website, but I'm also experiencing this in pro-enabled paid plans.
This lasted for a quite long time (over several month) and my friend got a response from CloudFlare rep. that it's a temporarily routing problem and will be resolved soon. However seems like this is not the case.. If this is not getting resolved, I'm considering and testing migration of all my company and personal paid plans to Fastly.
Exporting password + one-time code data from iCloud Keychain is now officially supported in macOS Monterey and Safari 15 (for Monterey, Big Sur, and Catalina). You can access it in the Password Manager’s “gear” icon (System Preferences > Passwords on Monterey, and Safari > Passwords everywhere else), or via the File > Export > Passwords... menu item). You shouldn't need to hack up your own exporter anymore.
After my dad died, I wanted to be able to have access any of his online accounts going forward. My dad was a Safari user and used iCloud Keychain to sync his credentials across his devices. I don’t want to have to keep an OS X user account around just to access his accounts, so I wanted to export his credentials to a portable file.
| from optparse import OptionParser | |
| import sys | |
| import redis | |
| __author__ = 'Jimmy John' | |
| __doc__ = ''' | |
| This is a script to make a copy of a redis db. Mainly to be used for cloning AWS Elasticache | |
| instancces. Elasticache seems to disable the SAVE/BGSAVE commands and you do not have access to | |
| the physical redis instances. The UI allows you to create 'Snapshots', but no way to download |
| <!DOCTYPE html> | |
| <html> | |
| <head lang="ko"> | |
| <meta charset="UTF-8"> | |
| <title>넙죽이</title> | |
| <script type="text/javascript"> | |
| function draw() { | |
| var canvas = document.getElementById('kaist_chan'); | |
| var ctx = canvas.getContext('2d'); | |
| ctx.fillStyle = 'rgba(22, 160, 220, 1)'; |
| 밝밝따맣밝빠따박다맣밝밤따밣따박다빠따밦밦다타맣발발따빠따발다밞따밞따박다맣밞발따빠따발타발따발따맣밞밤따빠따발다밦따밝따박다맣밞빠따발다밣따밣따밣따맣밣밦따빠따받타밤따발따맣밞밣따빠따밣빠따밤타다밞따맣밞밣따빠따밣빠따밤타다밞따맣밞밞따빠따밝밦다밣따타밣따맣밝발따빠따밦따밝따박다맣밝밦다밞따빠따밝발따타밤따맣밣밝다빠따빠따밦발다밞따다맣밝빠따받타맣발발다맣밣발따맣발발따빠따밦타밞따밤다밣따맣밣발따빠따밦타밤따밣따맣밞빠따밣다빠따발다밦따발다맣밦발따밝따밤다빠따맣밞빠따밤타빠따밦다밣따맣밝밤따빠따밦다밝따받다밣따맣밣발따빠따밣타밦따발다발따맣발발따빠따밦타밞따밤다밣따맣밝밤따밣따박다빠따밣밣다타맣밞빠따밦타빠따밣밣따다밞따맣밦발따밝따밤다빠따밝받따다맣밝밦다밞따빠따밝발따타밤따맣밣밝다빠따빠따밦발다밞따다맣밝빠따받타맣밝빠따밣타맣발발다맣발발다맣밣발따빠따밣따밝다밤따맣밝밝따맣발발따빠따발다밞따밞따박다맣밞발따빠따발타발따발따맣밞밤따빠따발다밦따밝따박다맣밞빠따발다밣따밣따밣따맣밞빠따밣타빠따발타밞따밣다맣밝밤따빠따밝따밦다밞따밝다맣밦발따밝따밤다빠따맣밞빠따밝타빠따밣밝따다밣따맣발발따빠따밝타밞따발다밣따맣밣밝다빠따밝타빠따밣다맣밣밝다빠따빠따밦발다밞따다맣밝빠따받타맣발발다맣밣발따빠따밣따밝다밤따맣발밞따발다맣발발따빠따발다밞따밞따박다맣밞발따빠따발타발따발따맣밞밤따빠따발다밦따밝따박다맣밞빠따발다밣따밣따밣따맣밞빠따밣타빠따발타밞따밣다맣밝밤따빠따밝따밦다밞따밝다맣밦발따밝따밤다빠따맣밞빠따밝타빠따밣밝따다밣따맣발발따빠따밝타밞따발다밣따맣밣밝다빠따밝타빠따밣다맣밣밝다빠따빠따밦발다밞따다맣밝빠따받타맣발발다맣밣발따빠따밣따밝다밤따맣밝빠따박다맣발발따빠따발다밞따밞따박다맣밞발따빠따발타발따발따맣밞밤따빠따발다밦따밝따박다맣밞빠따발다밣따밣따밣따맣밞빠따밣타빠따발타밞따밣다맣밝밤따빠따밝따밦다밞따밝다맣밦발따밝따밤다빠따맣밞빠따밝타빠따밣밝따다밣따맣발발따빠따밝타밞따발다밣따맣밣밝다빠따밝타빠따밣다맣밣밝다빠따빠따밦발다밞따다맣밝빠따받타맣발발다맣밣발따빠따밣따밝다밤따맣밝빠따받다맣발발따빠따발다밞따밞따박다맣밞발따빠따발타발따발따맣밞밤따빠따발다밦따밝따박다맣밞빠따발다밣따밣따밣따맣밞빠따밣타빠따발타밞따밣다맣밝밤따빠따밝따밦다밞따밝다맣밦발따밝따밤다빠따맣밞빠따밝타빠따밣밝따다밣따맣발발따빠따밝타밞따발 |
I have spent quite a bit of time figuring out automounts of NFS shares in OS X...
Somewhere along the line, Apple decided allowing mounts directly into /Volumes should not be possible:
/etc/auto_master (see last line):
#
# Automounter master map
#
+auto_master # Use directory service
| //Install Macports. | |
| //Install aircrack-ng: | |
| sudo port install aircrack-ng | |
| //Install the latest Xcode, with the Command Line Tools. | |
| //Create the following symlink: | |
| sudo ln -s /System/Library/PrivateFrameworks/Apple80211.framework/Versions/Current/Resources/airport /usr/sbin/airport | |
| //Figure out which channel you need to sniff: | |
| sudo airport -s | |
| sudo airport en1 sniff [CHANNEL] |