Hoy tengo la preocupación por la flotilla por las nubes.
https://globalsumudflotilla.org/tracker/ ⌘ Read more****
# I am the Watcher. I am your guide through this vast new twtiverse. # # Usage: # https://watcher.sour.is/api/plain/users View list of users and latest twt date. # https://watcher.sour.is/api/plain/twt View all twts. # https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri. # https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject. # # Options: # uri Filter to show a specific users twts. # offset Start index for quey. # limit Count of items to return (going back in time). # # twt range = 1 195947 # self = https://watcher.sour.is?offset=195319 # next = https://watcher.sour.is?offset=195419 # prev = https://watcher.sour.is?offset=195219
response.url
value to fetch it again for updates without having to do extra calls (you can store it verbatim or as a flag to be able to change the proxy later).t
export async function fetchWithProxy(url, proxy=null) {
return await fetch(url).catch(err => {
if (!proxy) throw err;
return fetch(`${proxy}${encodeURIComponent(url)}`);
});
}
// Using it with
const res = await fetchWithProxy('https://twtxt.net/user/zvava/twtxt.txt', 'https://corsproxy.io/?');
// Get the working url (direct or through proxy)
const fetchingURL = res.url;
// Get the twtxt feed content (or handle errors)
const text = await res.text();
https://my-proxy?$TWTXT_URL
since it allows you to define with more freedom any proxy without a prefix format.cors-anywhere
or build their own (with twtxt it should just be a GET).
Access-Control-Allow-Origin
header, so i just jumped into building a backend instead. did you find away around this limitation? :o
User-Agent
header appears to be fixed. \o/OPTIONS
request for my feed coming from something that claims to be Firefox, pointing to your feed URL in the query. No clue what this is about. In any case, it's rejected with a 405 Method Not Allowed
.If-Modified-Since
or If-None-Match
request headers. This way, if the feed hasn't changed, the web server can reply with a 304 Not Modified
and no body at all, saving unnecessary traffic. But again, this is really not an issue for me at all. I just wanted to make sure you're aware of it, that's all. It might be even already on your agenda. Or you might decide to never do anything about it, which is also fine for me. :-)
localstorage
and server-based file caching.
zs
looks pretty cool! I love simple static site generators, and look forward to trying it on my next web site project. Kudos!
zs
external command capability itself that now lets you do things like:
$ zs newpost
$EEDITOR
🤞groff --version
)?
groff --version
)?
man-pages
project: https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man/man7/ascii.7man-pages
project: https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man/man7/ascii.7man ascii
, you get this nice table, but there’s a weird vertical line at the bottom. That line is supposed to be a vertical rule and is supposed to go from the bottom of the table all the way to the top.man ascii
, you get this nice table, but there’s a weird vertical line at the bottom. That line is supposed to be a vertical rule and is supposed to go from the bottom of the table all the way to the top.