This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| slider1:mode=0<0,0,0{Send,Receive}>Mode | |
| slider2:track.send=0<0,0,0{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128}>Track | |
| slider3:tracks.receive=0<0,0,0{1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71,72,73,74,75,76,77,78,79,80,81,82,83,84,85,86,87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127,128}>Tracks | |
| slider4:_global.leafac_Inter_plugin_communication.blocks=1<1,10,1>Blocks | |
| options:gmem=leafac_Inter_plu |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ------------------------------------- | |
| Translated Report (Full Report Below) | |
| ------------------------------------- | |
| Process: REAPER [71676] | |
| Path: /Applications/REAPER.app/Contents/MacOS/REAPER | |
| Identifier: com.cockos.reaper | |
| Version: 6.43.0_0e4a702u (6.43.0_0e4a702u) | |
| Code Type: ARM-64 (Native) | |
| Parent Process: REAPER [71667] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| // ScreenWriter | |
| #text = "alskdjf alkdfjkls fal kfs aflksafsdjkl fsdk jl jklsad kljfds | |
| jkladfj kldfj klfd jslfasd jklfdk jlas akjlsdfs jklfd jkladf jlkfda jklafd jklfd | |
| ajlksfdal jkfas djksdfaj klafsd jl ljafsd jlkfdasl jadfs lkjfdas lkadlfs kfs klaj | |
| fajldks"; | |
| #font = "Arial"; | |
| //@param1:scroll_progress 'Progress' 0 0 1 0.5 0.0001 | |
| //@param3:font_size 'Font Size (px)' 40 20 250 150 4 |
- Consider following the supposedly bad practice of using a database (SQLite, in this case) as a queue, because it’s simpler.
- Passwordless authentication (Magic Authentication Links)
- https://github.com/nickbalestra/zero
- https://github.com/mxstbr/passport-magic-login
- https://github.com/vinialbano/passport-magic-link
- http://www.passportjs.org/packages/passport-passwordless/
- https://github.com/florianheinemann/passwordless
- https://hacks.mozilla.org/2014/10/passwordless-authentication-secure-simple-and-fast-to-deploy/
- https://reallifeprogramming.com/how-to-implement-magic-link-authentication-using-jwt-in-node-8193196bcd78?gi=10747bc1322e
- Don’t say whether the user is on the database: https://www.linkedin.com/pulse/dont-do-you-implement-magic-links-authentication-adrian-oprea
- https://blog.jacksonbates.com/passwordless
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| hs.alert("Hammerspoon configuration loaded") | |
| hs.hotkey.bind({"⌥", "⌃"}, "return", function() hs.reload() end) | |
| hs.hotkey.bind({"⌥", "⌃"}, ",", | |
| function() hs.execute([[code ~/.hammerspoon]], true) end) | |
| hs.hotkey.bind({"⌥", "⌃"}, "space", function() hs.toggleConsole() end) | |
| hs.hotkey.bind({"⌥", "⌃"}, "escape", function() | |
| hs.osascript.applescript("beep") | |
| hs.sound.getByName("Submarine"):play() | |
| end) |
References
- https://docs.datasette.io/en/stable/full_text_search.html
- https://kimsereylam.com/sqlite/2020/03/06/full-text-search-with-sqlite.html
- https://hackernoon.com/sqlite-the-unknown-feature-edfa73a6f022
- https://saraswatmks.github.io/2020/04/sqlite-fts-search-queries.html
- https://stackoverflow.com/questions/52803014/sqlite-with-real-full-text-search-and-spelling-mistakes-ftsspellfix-together
- https://www.sqlite.org/fts5.html#the_experimental_trigram_tokenizer
- ‘required’ doesn’t stop the field from being whitespace
- ‘pattern’ isn’t checked if the field is left empty and it isn’t ‘required’
- You can do ‘required pattern=".\S."’ if you want a quick-and-dirty solution
- SQLite’s datetime functions are all UTC, but they don’t explicitly include the timezone information
- In JavaScript (browsers & Node.js) datetimes without explicit timezone information are interpreted as local time
- In servers (for example, DigitalOcean & GitHub Actions machines) the timezone is usually set to UTC
- In development, the timezone is set to the user’s timezone
- We can change the timezone for the Node.js process in macOS/Linux with the TZ=UTC environment variable
- On Windows, the only solution is to temporarily change the OS timezone
- This sounds too heavy-handed and storing datetimes without an explicit timezone seems like a bad idea, anyway
- So the best solution that works everywhere is to avoid using SQLite datetime functions for generating values that will be stored in the database (it’s still fine to use them for queries)
- To be exact, I’m talking about SQLite’s CURRENT_TIMESTAMP, datetime() and so forth
- The correct way of doing it is using the more generic SQLite datetime function