You can find this feature in Settings > Download Twitter Archive. It might take 24 hours to receive.
Unzip the file and open the data folder in your terminal:
cd ~/Downloads/twitter-archive-zip-you-downloaded/data(I have seen reports that this function may no longer be working, so this guide is mostly useful to those who were lucky enough to already have downloaded their archive.)
Previously, front matter REQUIRED a layout property (e.g. layout: ../../layouts/MarkdownPostLayout.astro) Now, it's ALSO OK to include your layout as an import in "setup":
setup: |
import Layout from '../../layouts/BlogPost.astro'
import SomeOtherComponent from '../../components/SomeOtherComponent.astro'
Discord timestamps can be useful for specifying a date/time across multiple users time zones. They work with the Unix Timestamp format and can be posted by regular users as well as bots and applications.
The Epoch Unix Time Stamp Converter is a good way to quickly generate a timestamp. For the examples below I will be using the Time Stamp of 1543392060, which represents November 28th, 2018 at 09:01:00 hours for my local time zone (GMT+0100 Central European Standard Time).
| Style | Input | Output (12-hour clock) | Output (24-hour clock) |
|---|---|---|---|
| Default | <t:1543392060> |
November 28, 2018 9:01 AM | 28 November 2018 09:01 |
| // // with thanks | |
| // https://dev.to/emreloper/react-router-v6-in-two-minutes-2i96 | |
| // https://github.com/ReactTraining/react-router/blob/dev/docs/installation/getting-started.md | |
| // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/9d29adedf662de685356f711951ef8b9e8342865/types/react-router/index.d.ts#L1 | |
| // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/9d29adedf662de685356f711951ef8b9e8342865/types/react-router-dom/index.d.ts#L1 | |
| // // release notes | |
| // https://github.com/ReactTraining/react-router/releases/tag/v6.0.0-alpha.3 | |
| declare module "react-router-dom" { |
| int[][] result; | |
| float t, c; | |
| float ease(float p) { | |
| return 3*p*p - 2*p*p*p; | |
| } | |
| float ease(float p, float g) { | |
| if (p < 0.5) | |
| return 0.5 * pow(2*p, g); |
| all: private-plugin-one private-plugin-two | |
| private-plugin-one: | |
| . ./private-keys.conf && \ | |
| echo "Installing plugin one with private key \"$$PLUGIN_ONE_KEY\"" | |
| private-plugin-two: | |
| . ./private-keys.conf && \ | |
| echo "Installing plugin two with private key \"$$PLUGIN_TWO_KEY\"" |
| var Middleware = function() {}; | |
| Middleware.prototype.use = function(fn) { | |
| var self = this; | |
| this.go = (function(stack) { | |
| return function(next) { | |
| stack.call(self, function() { | |
| fn.call(self, next.bind(self)); | |
| }); |
All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent
| // ES6 w/ Promises | |
| // Note: From a React starter template - see https://t.co/wkStq8y3I5 | |
| function fetchData(routes, params) { | |
| let data = {}; | |
| return Promise.all(routes | |
| .filter(route => route.handler.fetchData) | |
| .map(route => { | |
| return route.handler.fetchData(params).then(resp => { | |
| data[route.name] = resp; |
I'm going to be deprecating the current Readernaut API in favor of a newer more built-out version. People using the current version have two weeks to switch over to the new API. Currently you can find your API_KEY by viewing source on any page and searching for "api_key" in the output (this will get better later). Here are some example endpoints:
/services/api/USERNAME/notes//api/v1/notes/note/?username=YOUR_USERNAME&api_key=YOUR_API_KEY&user__username=USERNAME