You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Instantly share code, notes, and snippets.
🎯
Focusing
Wlad Paiva
wladpaiva
🎯
Focusing
Indie Hacker Crossfitter bootstrapping SaaS and open sourcing payments.
🏎️ http://turboship.dev
Wherever HTML is rendered on GitHub (gists, README files in repos, comments on issues and pull requests, ...) you can use any of the HTML elements that GitHub Flavored Markdown (GFM) provides syntactic sugar for. You can either use the syntactic sugar that GFM (or other GitHub-supported markup language you're using) provides or, since Markdown can contain raw HTML, you can enter the HTML tags manually.
But GitHub also allows you to use a few HTML elements beyond what Markdown provides by entering the tags manually, and some of them are styled with CSS. Most raw HTML tags get stripped before rendering the HTML. Those tags that can be generated by GFM syntactic sugar, plus a few more, are whitelisted. These aren't documented anywhere that I can find. Here's what I've discovered so far:
The standard way of understanding the HTTP protocol is via the request reply
pattern. Each HTTP transaction consists of a finitely bounded HTTP request and
a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream
their possibly infinitely bounded data. The advantages is that the sender can
send data that is beyond the sender's memory limit, and the receiver can act on