cambridgeport90[<vikanezrimaya> "The better option would be of co" <- I agree. But when hosting oneself, how do we deal with issues like the log in page being hammered?A friend of a friend of mine did that, and he won't do it anymore because of the fact his instance was backed as well by Active Directory (why the log on page was being hammered with bad authentication reuests, though, I'm not sure.)
[snarfed]whether and how much to self host is always a good debate! but there's no single right answer, and we're a "big tent" kind of group. you can never self host everything, or every layer in the stack π
[snarfed]we care about owning your identity and data online, and the keys there are having your own domain and being able to export your data. beyond that, we're open to many different ways and places to host, both self hosting and otherwise
LoqiWeb hosting can be the primary regular cost in maintaining an IndieWeb site; this page lists several options from free on up depending on your publishing needs, like a static, shared, private, or dedicated server https://indieweb.org/hosting
capjamesg[d]Say I wanted to create a coffee post with information like {"varietal": "SL24-", "region": "Kenya"}. Should I nest those attributes as "properties": {ATTRIBUTES}?
sknebelso yes, you can make up a few (potentially prefixed, e.g. capjamesg-coffee-region) of your own properties and put them on the post. or nest them in their own microformats object to keep them together, kind of a matter of taste
sknebelthe prefixes are a microformats2 thing for people experimenting with properties that are only for their own use, not something generally proposed, to avoid potential naming conflicts and giving humans seeing them a hint
[Gabriele_Girel]Hej everyone! Dunno if this is the right place, but when I set up webmentions on my website I wrote a short javascript library that can be easily used by anyone. It is also easily extendable with more features, so if anyone is interested in trying this out any feedback is always welcome π https://github.com/ggirelli/easy-webmention-js
jamietannacapjamesg[d] something I'm starting to favour is making it i.e. a `drink-of` a URL, and that URL then contains all information about the coffee. Then when rendering the site / have some cache in our site, we can look up that URL and provide an `h-cite` of the data
capjamesg[d]I want to report on coffees I am drinking. The original idea was to style them more like notes but having the option to add meta information (i.e. roaster, varietal) would be useful.
jamietannacapjamesg[d] yeah, then the benefit is that you could i.e. create a central service ( /pipes ) which would allow others to do the same. But there's also some info that may be specific to yours, so may be a bit more complex and may be worth doing just for you right now
jamietannare your thoughts yesterday about sending the Bearer token in a cookie, I'd opted for encrypting the cookie with a shared secret owned by the Micropub client, but then when the form is rendered it's in the `access_token` hidden field
Zegnatcapjamesg[d]: for comparison, it might be interesting to check https://github.com/aaronpk/Teacup and how it shapes the entries it posts. That is another drink tracker for Micropub
[grantcodes], [KevinMarks], [fluffy], [schmarty], KartikPrabhu, Seirdy, shoesNsocks, hendursaga, tetov-irc, jeremycherfas and capablecable[d] joined the channel