WeChat ID
aaronpk_tv
Wednesday, July 4, 2018
| bicycle |
35 min
|
|
5.4 miles
|
bicycle |
-
-
At the end of the day federated social software is only kinda good at content consumption and does almost nothing for content production and people like using computers more to make things than they do consuming of things
feel like we should really have a focus on making things and again and making that as seamless and easy as possible
-
I’ve made you an itty bitty experiment just in time for independence day–
a tool to create websites contained within their own link.
🌐 http://about.bitty.site - a brief summary
⚙️ http://how.bitty.site - how it works
What might you make with it?
🇺🇸 http://independence.bitty.site
-
Testing out a fix for my whitespace bug.
This should look better on micro.blog now. -
One more newline test.
Apparently the last change broke how my posts display in Mastodon, this should look better now. -
Nope, I also don't have permission to create repositories on the Microformats org on GitHub.
-
sknebel
https://github.com/sknebel
•
Jul 4
Looking at this again, I'm not sure what a good spot for a general note would be.
If you ok it I'd prepare a pull request adding the header to the examples?
At the very least adding the
Acceptheader to the examples is a good place to start, go for it! -
cactus
https://github.com/cactus
•
Jul 4
go-camo was indeed originally intended to proxy only images, for two reasons: 1) the camo project it was inspired by only proxied images 2) my use-case at the time only required proxying of images
Later, a fork was created by a user to additionally proxy fonts and css. I wasn't comfortable including those in go-camo -- see discussion on https://github.com/cactus/go-camo/issues/20.
In my experience, video files are "usually" either linked (by url, no content warning), uploaded (service hosts it, so no content warning), or inlined from some hosting service (eg. youtube, vimeo; ssl provided by service). Video files are also generally much larger than image content.
Can you further describe your use-case/requirements for proxying video?
Ah, I can see why css/js could be an issue for some uses.
I'm using this on the server side of my new social reader application so that all image/video URLs presented to the reader apps are https and from the same origin. The videos come from either Instagram, Twitter, or peoples' own blogs hosting video files directly. Because the majority of the content is twitter-like short posts, the video files are normally always under a minute long so they aren't actually that big.
-
