WeChat ID
aaronpk_tv
-
Train
2.61miDistance14:57DurationStartEnd
-
Bus
2.50miDistance17:26DurationStartEnd
-
Identiverse
https://twitter.com/Identiverse
•
Jun 28
In case you missed it: #Identiverse 2020 will be in the mile high city, Denver!! 🙌
Fantastic! Do you know the dates yet? -
-
-
Portland, Oregon • Fri, June 28, 2019 8:22am
-
Train
3.79miDistance20:16DurationStartEnd
-
Train
3.79miDistance20:16DurationStartEnd
-
AsleepAwake7h 59mSlept24mAwake for
-
Sorry can't make it tonight! See you tomorrow tho!
-
I've had this on my todo list for Aperture for quite a while: https://github.com/aaronpk/Aperture/issues/37
Moving a feed/subscription to a new channel does seem like something potentially useful for a client to do, although I'm not sure what I would want the UX of that to look like.
Before this ends up in the Microsub spec, I'd want to see at least Aperture and one other server support the feature on its own even without a client UI for it.
If any client developers have an idea for what this might look like in the apps that'd be great to see sketched out here as well.
Thanks for starting this discussion! -
One of the main reasons to use h-feed and h-entry is that RSS/Atom really only can represent blog posts and podcasts. For those purposes, they're fine formats, but the reality is there are many more kinds of content on the social web today, such as replies like this one which can't really be represented in RSS.
What features are you finding that Microsub doesn't support? Like most of the IndieWeb protocols, Microsub is supposed to be an evolving protocol based on the needs and implementations of people using it. I don't expect that we will ever say "Microsub is done!" the way that some specs put a stick in the ground, since the reality is that things change and need to adapt to new use cases to remain relevant. -
Jeannie McGeehan
https://jeannie.digital/
•
permalink
In my effort to become more involved in the IndieWed community I created indieweb.life and indieweb.social. A lot of the information out there is either out-of-date or is written so far above the head of the complete novice. A lot of it is geared towards developers and webmasters. I wanted to create a place and space where a person with only a cursory knowledge could come and get simple, easy instructions and places to go for further guidance. I wanted to create a simple “get started” site with some simple up-to-date links and instructions on indieweb.life for people looking to get started with WordPress and the IndieWeb. I also created the open Mastodon instance at indieweb.social for anyone who would like to join an instance focused on supporters and participants of the IndieWeb movement. I would really like it if some of the more experienced veterans would be willing to critique the site and maybe contribute or syndicate some content that would help new seekers. Also, if anyone would be willing to be an admin on indieweb.social then we can get listed on joinmastodon.org.
This is really cool! Out of curiosity, where are you seeing out of date information? If it's the wiki, we'd love to know which pages need an update so we can fix them! -
-
Inspired by @NikkitaFTW, I’ve decided to embark on a new adventure...
#100DaysOfDumbShit
🦄💫🤷♀️💩💖👻🥳
It’s like #100DaysOfCode but where you only build dumb shit 💁♀️ I won’t post every day, but when I have something dumb and (mostly) finished - I promise to share 💅🏼
