WeChat ID
aaronpk_tv
-
Bake, Don’t Fry (Aaron Swartz: The Weblog) (www.aaronsw.com)"Some people seem to think that I want to bake because of perfomance. Honestly, I don’t care about performance. I don’t care about performance! I care about not having to maintain cranky AOLserver, Postgres and Oracle installs. I care about being able to back things up with scp. I care about not having to do any installation or configuration to move my site to a new server. I care about being platform and server independent. I care about full-featured HTTP implementations, including ETags, Content-Negotiation and If-Modified-Since. (And I know that nobody else will care about it enough to actually implement it in a frying solution.) I hope that clarifies things."
-
Day 9. I don't really know what I was going for here. I had this tune in my head on the bike ride home from downtown this evening. This one only took an hour or so to jot down, since I wasn't going for any particular sound. The animation kind of sums it up. #100daysofmusic #100daysproject #the100dayproject -
Portland, Oregon • Thu, December 29, 2016 2:47pm
-
I decided to make that my project for today! You're not crazy :-)
-
Day 9: Webmention form #100DaysOfIndieWeb
I finally brought back the Webmention form on my website! At the bottom of my posts, you'll see a Webmention form now!continue reading... -
@indiescripter Thanks for the explanation! It's great to hear this feedback from people new to #indieweb.
Your point about your expectation of being able to like or comment on the post directly on my website is interesting. I took the comment box off of my website a long time ago, with no regrets. I like that it encourages people to write replies in a space of their own. (Ideally on their own website, but at the very least from their own Twitter account).
However, it would be interesting to see what would happen if I let people "like" posts directly on my website, even if they don't have their own website yet. Maybe I'll do that for one of the 100 days! -
@indiescripter I think you've probably got a pretty good start on the IndieWeb philosophy. And an even better start in that you're writing your thoughts on your own website first and then syndicating them to silos like Twitter. I think that part of what you're missing about being able to reply to Aaron's original post is that his site both sends and accepts a new web protocol known as Webmention (http://indieweb.org/webmention). Thus on his original post, you'll see that I've "liked" it by making a post on my own site (http://stream.boffosocko.com/2016/liked-aaron-pareckis-100-days-of-indieweb-147eda7b83), and then in the background sending a webmention from my server to his to notify him about it. He can then decide whether or not to accept and/or display it (in this case mine appears next to his star icon at the bottom of the post). For the likes and comments/replies on his post, you can hover and find the permalinks for all of the responses on other people's originating sites. I'm sure yours would have shown up too, but I suspect that your site isn't sending webmentions yet, so his site is unaware that your post exists. I'm sure he'll have seen the Twitter response you gave though. I know Aaron also often syndicates copies of his posts to Twitter. There's another IndieWeb related service known as Brid.gy which bootstraps webmentions onto Twitter (in addition to other social silos) so that replies or comments to the copy that got syndicated to Twitter also send copies to the original post. In this case, he only syndicated it to news.indieweb.org, so it was less simple for you to have interacted with his post because there wasn't a Twitter version for you to interact with. You'll find that within the broader community that different members will support varying levels of functionality (based mostly on what they're interested in), so someone like Tantek (tantek.com) will post on his own site and syndicate to Twitter, but he doesn't yet display webmentions. You can, however, post your replies to him on your own site and syndicate them to Twitter (perhaps using Brid.gy publish?) to reply to his syndicated copy on Twitter where he'll see the notification of your reply. You yourself serve as another example as you don't (yet?) offer a comment field on your own post. Perhaps you may never, but that's your choice. (I'll mention incidentally that many static website owners are using Aaron's Webmention.io for sending/receiving webmentions, see also: https://indieweb.org/webmention.io.) I think that a lot of the goal is to not only have fun with what you're doing on your own website, but do things which you find interesting/useful for yourself. Are you interested in locations/check-ins [http://indieweb.org/location]? Reading related posts [http://indieweb.org/read]? Maybe other types of status updates [http://indieweb.org/posts]? Always work on your own itches [http://indieweb.org/itch] first. Just be careful, because lurking in IRC or browsing the IndieWeb wiki for a while and seeing what others are working on or doing can make you very "itchy". Though the reverse is true that seeing what others have done (even how silos have done things in the past) can make it easier for you to build it not only better, but perhaps more quickly. Perhaps the CMS or language you're using is being used by others in the community [http://indieweb.org/projects]? This may make it easier for you to go farther/faster by using their opensource code, or perhaps make it better by contributing some of your own thoughts/feedback/code? Keep up the search, and let us know if we can be of further help/assistance.
-
This is such a great writeup! Thanks for chiming in!
-
AsleepAwake7h 59mSlept51mAwake for
-
Portland, Oregon • Wed, December 28, 2016 5:33pmBirthday drinks! Come on by if you're in the neighborhood!
-
Day 8. Today's song is an experiment in not using any percussion and trying to create the sense of rhythm other ways. A lot of this was inspired by one of @adamsinger's Creative Commons tracks. I wanted to see what it would take to create something with a similar feel. There's also a hint of Royksopp in here. #100daysofmusic #100daysproject #the100dayproject
-
100 Days of Music
100 Days of Music is a project to write a short 30-90 second song every day for 100 days. My goal is to create something that's "finished" enough to be able to use it as a podcast or video intro song. It doesn't have to be long, but has to sound decent.continue reading... -
Day 8 part 2: Birthday Balloons! When you visit my home page today, you'll see balloons floating up from the bottom of the screen! All the code is in a self-contained javascript file if you want to use this on your site too! https://aaronparecki.com/assets/birthday.js #100DaysOfIndieWeb
-
@indiescripter hm, what do you mean "silo-centric"? We often replicate silo UX on our own sites, and we syndicate to silos to reach audiences that are there, but ultimately it's about owning your identity and data. If you want to see a variety of things I'm working on, check out my "100 days" project where I work on something IndieWeb for 100 days: https://aaronparecki.com/tag/100daysofindieweb You'll find plenty of non-silo things there!
