| cgi-bin | |
| images | |
| admin | |
| includes | |
| modules | |
| templates | |
| cache | |
| media | |
| js | |
| language |
For direct image URL, the image quality is much lower than the original upload (the resolution and size of the original upload can be found in the right sidebar). This is not the case few years ago when the original image was accessible through right click, but on 2017, Wix acquired DeviantArt, and has been migrating the images to their own image hosting system from the original DeviantArt system. They linked most of the direct images to a stripped-down version of the original images; hence the bad image quality. Below are the three different formats of direct image URLs I found:
/v1/fill inside: this means that the image went through Wix's encoding system and is modified to a specific size and quality. In this case, you remove ?token= and its values, add /intermediary in front of /f/ in the URL, and change the image settings right after /v1/fill/ to w_5100,h_5100,bl,q_100. The definitions of the values can be found in [Wix's Image Service](https://support.wi
| Filter | Description | Example |
|---|---|---|
| allintext | Searches for occurrences of all the keywords given. | allintext:"keyword" |
| intext | Searches for the occurrences of keywords all at once or one at a time. | intext:"keyword" |
| inurl | Searches for a URL matching one of the keywords. | inurl:"keyword" |
| allinurl | Searches for a URL matching all the keywords in the query. | allinurl:"keyword" |
| intitle | Searches for occurrences of keywords in title all or one. | intitle:"keyword" |
| # /usr/share/BasiliskII/keycodes | |
| # | |
| # Basilisk II (C) 1997-2005 Christian Bauer | |
| # | |
| # This file is used to translate the (server-specific) scancodes to | |
| # Mac keycodes depending on the window server being used. | |
| # | |
| # The format of this file is as follows: | |
| # | |
| # sdl <driver string> |
| # recursive search for keys containing "string" stripping empty results | |
| jq '.. | objects | with_entries(select(.key | contains("ftp"))) | select(. != {})' | |
| # same, but output propper array | |
| jq '[ .. | objects | with_entries(select(.key | contains("ftp"))) | select(. != {}) ]' | |
| # or | |
| jq 'map( .. | objects | with_entries(select(.key | contains("ftp"))) | select(. != {}) )' | |
| # transform input from {type: a, amount: 1} to {a: 1} and sum all values by type | |
| jq '[ .[] | {(.type): .amount} ] | map(to_entries) | add | group_by(.key) | map({key: .[0].key, value: map(.value) | add}) | from_entries' |
#Lessons From A JavaScript Code Review
I was recently asked to review some code for a new JavaScript application and thought I might share some of the feedback I provided as it includes a mention of JavaScript fundamentals that are always useful to bear in mind. Code reviews are possibly the single biggest thing you can do to improve the overall quality of your solutions and if you're not actively taking advantage of them, you're possibly missing out on bugs you haven't noticed being found or suggestions for improvements that could make your code better.
##Challenges & Solutions
Code reviews go hand-in-hand with maintaining strong coding standards. That said, standards don't usually prevent logical errors or misunderstandings about the quirks of a programming language. Even the most experienced developers can make these kinds of mistakes and code reviews can greatly assist with catching them.
Often the most challenging part of code reviews is actually finding an experienced developer you trust to complete
