#LoqiIt looks like we don't have a page for "timestreams" yet. Would you like to create it? (Or just say "timestreams is ____", a sentence describing the term)
#jeremycherfastimestreams is https://timestreams.org/ a proposal for "Time-aware feeds at any url. A simple protocol and file format for our digital lives."
#jeremycherfasI hope someone more skilled than me can take a look at that ^^^
#jeremycherfasAnd maybe see where it fits into IndieWeb principles (if it does).
#jeremycherfasLooks like to could PESOS Instagram streams and Pinboard bookmarks too.
#jeremycherfasNo, scartch that; it imports a copy of Instagram data.
#[KevinMarks]looks like it's reinventing atom but with headers rather than xml
#[KevinMarks]having that much control of headers is hard
#jeremycherfasThe developer, I noticed later, is the son of a good friend. I've asked for an introduction to see whether I can entice him in this direction.
#[manton]There’s some overlap between the Time Streams Day Archive and what I was trying to do with the Blog Archive Format. (Blog Archive uses HTML + MF2 + JSON Feed, which is nice because you can view it with just a web browser.)
#Summer[m]When sending mf2 properties to a Micropub server for creating a post type (note etc.), does the client need to send them as `dt-published`, or is `published` fine? The spec seems to use `published` simply but it's throwing me off!
#Summer[m] * Hi all, just wondering about something.
#Summer[m]When sending mf2 properties to a Micropub server for creating a post type (note etc.), does the Micropub client need to send them as `dt-published`, or is `published` fine? The spec seems to use `published` simply but it's throwing me off!
#Summer[m](Sorry for the double message IRC folks - just remembered it happens when I edit for a typo etc.)
#Summer[m]So am I just supposed to disregard the prefixes everywhere? h-, u- and dt-* etc.?
#Summer[m]That is, when making requests to a Micropub server.
#ZegnatNot really disregard, mf2 prefixes are never part of the mf2 JSON. They really are more parsing instructions when working with HTML, rather than part of the property name.
#ZegnatSo they shouldn’t really be there to begin with ;)
#Summer[m]Oh I see. This is a URL encoded request, support for which is mandatory. JSON support is optional for clients. I'm only trying with URL encoded at the moment and the server is unable to figure the date out.
#Summer[m]Might be something else... I'll crack on. Thank you. :)
#ZegnatOh, yeah, sorry. But even the url encoded version is based on parsed microformats, so same applies there
#ZegnatThe URL encoded request is the list that would otherwise be the `properties` object from the JSON request. It is a fairly straightforward conversion.
#ZegnatI think multiple servers actually do the reverse conversion when they receive a URL encoded POST, because they prefer to store the mf2 JSON on the server side.
#Summer[m]That makes sense. It'll probably make more sense when I add support for sending JSON requests. ;)
kraem joined the channel
#kraemlo! don't know if this is the right channel (found it through google). i'm currently developing a web app with nextjs for personal use, i'm new to web development. i am making some http requests to the backend i'm writing and i was wondering if it's ever done in a way that the server-side of a web app (i.e. next) makes the request for the client. i found that it can be done build time with
#kraemnext but i was wondering if it's possible to do on a submit for example. if this is possible i wouldn't need to have the backend listen on anything else than the CIDR address of the next app. peace! :)
#ZegnatHi kraem! This channel is mostly about development surrounding personal sites and IndieWeb technology (https://indieweb.org/). Not sure anyone here is working with next.js. There might be more node or even next related channels elsewhere that would get you much better answers.
#kraemZegnat: i found that after googling (which i should've done before posting :P ) - thanks, i found ##javascript :)
#ZegnatCool, hope they are able to help then! And of course if you see some chances for some indieweb tech in the web app you are building, we are happy to help with any questions there :)
#kraemit's actually a web app for serving my notes taken with 'vim-zettel' so i guess it would qualify as an indieweb app ;)
[KevinMarks] joined the channel
#[KevinMarks]in general, a serverside app can make a request and transform it for a client side app - we have a few indieweb tools that do that
#Zegnatkraem: definitely! Lots of talk about note collections, personal wikis, and so on :)
[schmarty] joined the channel
#kraem[KevinMarks]: i just realised the serverside wouldn't know when the client clicks submit for example. do you have any examples to point to? thanks
[grantcodes] joined the channel
#[grantcodes]I use next.js for my site and it's great
#kraem[grantcodes]: yeah i like nextjs so far. do you let server-side do any http api calls instead of the client? :)
#[grantcodes]kraem: very few, I use `getStaticProps` a lot instead mainly
hs0ucy joined the channel
#kraem[grantcodes]: cool. that seems to only work when nextjs is building the page that is being sent to the client though, right? i'd like the functionality of the nextjs server to send an api request when the client clicks a button.
#[grantcodes]Ah yeah. Well really depends how you want to do it. You can do a form that submits to a nextjs api page or client side js
[Ana_Rodrigues] joined the channel
#kraem[grantcodes]: thanks, didn't know about api routes!
#[fluffy]I finally got around to getting Authl fully-documented and on https://authl.readthedocs.io, for anyone who was interested in using this auth layer for their own projects 🙂