Episode 19: Soft-Launching Monocle and Aperture
Soft-launching Monocle and Aperture, and thinking about private feeds
continue reading...
WeChat ID
aaronpk_tv
Wednesday, March 14, 2018
| bicycle |
52 min
|
|
8.4 miles
|
bicycle |
-
-
One of the many ways we motivate engineers to write more docs.
#writethedocs #docsoritdidnthappen #tshirt #carrotnotthestick
-
This is documented here: https://indieweb.org/Microsub-spec#Remove_Entry_from_a_Channel -
As of a few days ago, Aperture now downloads any media resources it encounters and rewrites the URLs in the post to its own copy it is hosting. You shouldn't need to do anything differently in the client, and all the URLs will be https now.
I'm not sure this needs to be something in the spec, since the Microsub server can just rewrite the URLs transparently if it wants. -
This has been implemented in Aperture, Monocle, Together, and Indigenous, and documented at https://indieweb.org/Microsub-spec#Mark_Entries_Read so I'm going to close this issue. Let's open new issues for any future discussion about the specific behaviors within read-state tracking.
-
I'm thinking about using a new Microsub property in the entry to indicate the response URLs that may exist for this post.
{ "type": "entry", ... "_like": "https://aaronparecki.com/xxxxxxx", "_repost": "https://aaronparecki.com/yyyyyyyy" }alternately:
{ "type": "entry", ... "_actions": { "like": "https://aaronparecki.com/xxxxxxx", "repost": "https://aaronparecki.com/yyyyyyyy" } }For likes and reposts, from a UI perspective, we want to know whether the user has already liked or reposted a post (a boolean yes/no), in order to style the like/repost button differently, so in that case it makes sense to have those be a single string. (The client could send a Micropub delete request with the URL if the user taps the button again, to delete the like/repost.)
For replies, I'm not sure what we actually want the client to indicate. Long-term it would be great if the client had the ability to show the full conversation thread, so in that sense it makes sense to handle replies differently from likes and reposts. Maybe we can handle this question separately for replies.
In the case of likes and reposts, we only care about the URLs of the user's own like/repost posts. Showing other people who have liked or reposted a post is a different problem, since that does not affect the state of the action buttons.
In thinking through this, I'm leaning towards the second JSON option above, nesting the data under
_actions, since this data is limited in scope to help indicate the state of the action buttons. It is not meant to cover displaying all responses to a post. -
alans
https://micro.blog/alans
•
permalink
@aaronpk Mind helping me diagnose something? I think this like is marked up correctly as a
u-like-of, but it appears on your site as an "other mention." Do you notice anything funny in my markup?
You've got an h-entry in your h-entry! Check out the extra nested in the parsed result: https://pin13.net/mf2/?url=https%3A%2F%2Fprettygoodhat.com%2Flike%2F1520909433%2F -
Good call, I'll add this. I wish IFTTT would support custom headers or at least the Authorization header tho! This has been a problem for me in the past as well. Maybe if a bunch of us keep requesting it they'll eventually add it.
-
grantcodes
https://github.com/grantcodes
•
Mar 14
Not exactly an issue but why should the server have the option to only return
true/falsefor the unread count on a channel? Could it not be selected on the client and just useif > 0logic?I suppose maybe some servers will only be able to return
true/falsewhich makes it easier to build a server...
In Aperture, I wanted the option to choose whether to return boolean or counts (or disable it completely) per channel. This way the client can just react to the data it has. -
I was just thinking about this the other day! I wasn't sure whether you'd want to hyperlink the @-mention to the user's canonical domain or keep it as the micro.blog profile link, but eddie's idea of adding an invisible link inside the h-entry would work too!
-
@aaronpk I started playing my microcasts playlist today without looking at the upcoming episodes. Little did I realize, I would hear a Percolator episode! Yay!! 👏👏
-
Is this something you'd want to change per database? Or would it be something on the whole installation? An easier version of this could be to use the .env file to hold the settings, that way you could avoid needing to make a UI to manage it.
-
🔔 The Homebrew Microblog Meetup is tonight! 6pm at Rogue Eastside! 🎉🍻 And a great sunny day for it too! ☀️ #indieweb #microblog #pdx https://indieweb.org/events/2018-03-14-homebrew-microblog -
Portland, Oregon • Wed, March 14, 2018 5:47pmHomebrew Microblog Meetup! #indieweb — with microformats
-
nitinthewiz
https://github.com/nitinthewiz
•
Mar 14
Ah, yes, using the .env file makes sense. I've got only one database and so it doesn't matter. But I could see someone using different databases for different purposes (one for day trips, another for hiking?) and so need different maps.
But as I said, while writing it, I decided to move permanently to the mapbox tiles and have made the change on my install.
Say, what and how do you use different databases? Is your installation used by different people?
I have a primary database for my GPS logs, and I have another big one for all my weather data. Every 5 minutes a script checks my current location, looks up the weather at that location, and writes it to that database. That’s how the little weather info appears on my posts. I’ve also used other databases for testing the app so I can write to a test DB, or storing other home automation data. -
-
