duplicates = multiple editions
A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen
A Classical Introduction to Modern Number Theory, Kenneth Ireland Michael Rosen
| # install pip & virtualenv | |
| # create a virtual environment for your webapp | |
| # install django in the new virtualenv | |
| cd ~/tmp | |
| PYVE=2.7 | |
| PYVER=2.7.3 | |
| STVER=0.6c11 | |
| # go directly to the source to get the latest and greatest | |
| wget http://pypi.python.org/packages/$PYVE/s/setuptools/setuptools-$STVER-py$PYVE.egg#md5=fe1f997bc722265116870bc7919059ea |
| Introduction | |
| ============ | |
| Futoshiki (不等式, meaning “inequality”) is a Japanese logic puzzle similar to | |
| Sudoku and the like. Numbers from 1 to n must be placed on an n-by-n grid | |
| (which usually already contains some values) such that each row and each column | |
| is a permutation of `[1..n]`. Additionally, less-than or greater-than signs are | |
| placed between cells, constraining their mutual ordering. | |
| An example puzzle looks like this: |
TLDR: JWTs should not be used for keeping your user logged in. They are not designed for this purpose, they are not secure, and there is a much better tool which is designed for it: regular cookie sessions.
If you've got a bit of time to watch a presentation on it, I highly recommend this talk: https://www.youtube.com/watch?v=pYeekwv3vC4 (Note that other topics are largely skimmed over, such as CSRF protection. You should learn about other topics from other sources. Also note that "valid" usecases for JWTs at the end of the video can also be easily handled by other, better, and more secure tools. Specifically, PASETO.)
A related topic: Don't use localStorage (or sessionStorage) for authentication credentials, including JWT tokens: https://www.rdegges.com/2018/please-stop-using-local-storage/
The reason to avoid JWTs comes down to a couple different points:
| Host rpi1 | |
| HostName raspberrypi1.local | |
| User pi | |
| Host rpi2 | |
| HostName raspberrypi2.local | |
| User pi |
This gist lists challenges you run into when building offline-first applications based on IndexedDB, including open-source libraries like Firebase, pouchdb and AWS amplify (more).
Note that some of the following issues affect only Safari. Out of the major browsers, Chrome's IndexedDB implementation is the best.
When this bug occurs, every time you use the indexeddb, the WAL file grows. Garbage collection doesn't seem to be working, so after a while, you end up with gigabytes of data.
Both things have been introduced recently, and let you access even private ec2 instances
# Assumes valid AWS Credentials in ENV
| from __future__ import annotations | |
| from typing import ( | |
| Any, | |
| Awaitable, | |
| Callable, | |
| Iterable, | |
| Literal, | |
| Mapping, | |
| ParamSpec, |