Phanpy: A minimalistic opinionated Mastodon web client
phanpy.social
phanpy.social
They created https://cheeaun.life, a timeline of their life, more than 10 years ago (which looks to be kept up to date), which was my inspiration for markwhen (https://markwhen.com).
Happy to answer questions and hear feedback.
access-control-allow-origin: *
access-control-allow-methods: POST, PUT, DELETE, GET, PATCH, OPTIONS
access-control-expose-headers: Link, X-RateLimit-Reset, X-RateLimit-Limit, X-RateLimit-Remaining, X-Request-Id
access-control-max-age: 7200
This has lead to a delightful variety of custom clients like https://phanpy.social/ - https://elk.zone/ is another example that I really like.It's the complete opposite of the Twitter API situation, where they locked their API down and killed the entire ecosystem of third-party clients.
I've been trying to figure out some security problems that are a result of this CORS policy - as I'm considering it for my own application - and I can't figure out how an attack could actually work.
The API I'm working with uses Authorization: Bearer tokens, and only allows incoming requests with a valid API token.
And relevant recent discussion: https://news.ycombinator.com/item?id=40009148
Narrator: "Meanwhile, in Japan..."
red laser lights up in Nintendo IP lawyer's eye
I'm sold.
It does look pretty though.
This means that if any of those individual files are updated in the future just that file will need to be re-fetched, with all of the others staying served from cache. A single bundle would need to be fetched in its entirety on any change.
Also, it's weird that you say I'm "completely wrong" given the uncontroversial single claim I made about the cryptographic signing being what makes it complex. Since you wrote a client you have to know this is true even if you disagree with the 'complex' bit. Unless you just used a module that did it for you? https://imgs.xkcd.com/comics/python.png
This is all pretty minimal, and it's opinionated because it both doesn't look or feel like "social" media, it looks more like an RSS feed or something; and it goes against the design decisions of federation (that full instance names should be displayed, for instance).