EdwardHinkle
https://github.com/EdwardHinkle
•
Feb 10
WeChat ID
aaronpk_tv
Sunday, February 11, 2018
| bicycle |
43 min
|
|
7.1 miles
|
bicycle |
-
-
Some silo examples of "home" vs "notifications":
and of course more on the wiki
Some discussion from IRC about whether hardcoding a "home" channel even makes sense in the first place.
-
Okay, it sounds like we have a proposal for some changes around how these channels are handled:
• The only special uid is `notifications`
• A Microsub server is required to start with a single "Home" channel, the uid can be whatever it wants
• Users can remove or rename the initial default channel
• Servers MUST return the `notifications` channel as the first channel in the list
• Servers MUST ignore the `notifications` channel when reordering channels
• Clients SHOULD show the `notifications` channel separately in the UI -
- aaronpk@aaronparecki ~/Code: curl -I https://ascraeus.org/article/websub-part-ii-aperture
- HTTP/1.1 200 OK
- Server: nginx
- Date: Sun, 11 Feb 2018 19:01:10 GMT
- Content-Type: text/html; charset=utf-8
- Content-Length: 55151
- Last-Modified: Sun, 11 Feb 2018 18:53:48 GMT
- Connection: keep-alive
- Keep-Alive: timeout=10
- Vary: Accept-Encoding
- ETag: "5a80913c-d76f"
- Cache-Control: max-age=0
- Accept-Ranges: bytes
-
Here is a diff of the changes.
The main differences can be read here:
-
at StreamPDXPortland, Oregon • Sun, February 11, 2018 3:19pmDay 2 interviews #streampdx
-
Well that's not what I was expecting this issue to be about. Do you mean that you're going to run a server on behalf of the iOS client, so that you can send push notifications to it? I hadn't considered having Aperture send out WebSub notifications for content added to its channels, but that makes sense now that you mention it!
-
Let's talk about usernames (www.b-list.org)
-
