EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 14
WeChat ID
aaronpk_tv
-
Stepping back a bit, I think we should look at the end goal from the users perspective.
This seems to be a problem primarily when both people have their own website and their content is automatically pulled into micro.blog from their own feeds.
With that in mind, the best solution is one which will require the least amount of behavior change as well as technical change on behalf of both people. This likely means micro.blog will have to do some additional work, but that seems appropriate since in this situation micro.blog is acting as an aggregator between two independent websites.
The way micro.blog can best facilitate this kind of interaction would be to match up the replies itself, and not require any additional steps for the user replying. Since micro.blog is already consuming a feed from my site, if it encounters any posts in that feed with an in-reply-to url, micro.blog should check whether that url is one of its own, or whether it's indexed as a canonical url from someone's site that it has also previously pulled in. Then it can match up the conversation thread. If there is no match, then a perfectly acceptable first version would be to just ignore the post and not pull it in to micro.blog at all. This way neither the person replying nor the person being replied to need to fiddle with any markup or make additional feeds or make decisions about syndicating at each post.
I believe JSONFeed has the concept of an in-reply-to url, but Atom/RSS do not. This means this feature will only work with JSONFeeds, but I think that is an acceptable compromise. Of course if micro.blog started consuming h-entrys that would also work but that's a different conversation. -
San Francisco, California • Mon, February 26, 2018 12:19pmHello San Francisco!
-
Plane
588.04miDistance102:45DurationStartEnd
-
Portland (PDX) to San Francisco (SFO)toAlaska Flight 387
-
Delayed. New estimated departure time is 10:15am.
-
Train
8.90miDistance21:03DurationStartEnd
-
-
-
-
AsleepAwake7h 18mSlept15mAwake for
-
-
"I've already made some progress; so far my iOS application shares the state of my phone battery at https://dri.es/status. This is what it looks like:
This was inspired by Aaron Parecki, who not only tracks his phone battery but also tracks his sleep, his health patterns and his diet. Talk about owning your own data and liking tacos!" -
-
I have reluctantly accepted the fact that I am a “self-employed creative”, a job title that sounds like it comes from a bystander quote in a NY Times article about Portland’s artisanal popcorn scene.
But that is exactly what I am; I mainly work for myself and my livelihood comes from a podcast, an online course, and an illustrated book filled with cartoon cats explain Roth IRAs. I dress up in glittery spandex costumes to teach about budgeting.
And 3 days a week, I get up at 4:30AM to vacuum and clean toilets at a gym for 50 cents above minimum wage. Sometimes other gigs come my way. Between these 2-5 jobs in a given month, my bills are more than covered, and I put aside a few hundred to a few thousand in savings each month.
I’m doing fine financially; I funded a 13-country trip in cash a few months back, I have 8 months of expenses in an emergency fund, and a healthy retirement portfolio. I buy nice coffee whenever I want it. I don’t have any debt.
But I’m always, always hustling. I clock 50-65 hours a week of “on-task work time” in Toggl (no writing this isn’t counted), and I’ve had 2 rest days since 2018 began. There’s never enough time for sales when you’re also making a show every week and writing a book and booking non-profit gigs and managing the logistics for a book printing.
I hate how being your own boss, especially in the personal finance world, is about projecting this air of LOVING your job all the time. I *do* love my work, but I *hate* being self-employed.
I miss having co-workers. I miss having an office. I miss having a *boss*. I miss having paid vacation or sick time or occasional weekends off. I hate having to wear every single hat: Broadcaster + Teacher + HR + Accounting + Writer + Sales + Marketing + Web Designer.
I hate the self-doubt that comes from making creative work in a vacuum, and the loneliness that comes from being your own boss. So there it is. If someone else would give me a job as awesome as this, I’d take it in a heartbeat. But until I see someone hiring for a cat-based purrsonal finance instructor and media mogul, I guess I’ll keep on purring along. #selfemployed
-
EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 25
Awesome! Great to hear other areas where this has worked well. Do you have any thoughts between it just applying to channels and it applying to the posts? What does your IRC client do?
(Originally published at: https://eddiehinkle.com/2018/02/25/5/reply/)
I do think it should be a preference, tho maybe hidden by default is okay. The trick is once the channels without new content are hidden, you have to have a way to quickly show them again in case you want to be able to look at old content again.
As for the posts: Slack, IRC clients, as well as Twitter, show all the posts, not just the unread ones. I don't think I personally would use the "show only new posts" feature except in certain cases such as when I suspect there might be some old unread posts that have been buried somehow. I prefer to have some visual indicator about whether a post has been read rather than hiding it completely. In either case, you'd need a quick way to toggle between showing all posts vs showing unread posts.
