#dev 2021-09-28

2021-09-28 UTC
vikanezrimaya, Lohn and [Rose] joined the channel
#
GWG
aaronpk[d]: Can I prevail on you to comment in a back and forth between jamietanna and myself?
#
Loqi
Ok, I'll tell them that when I see them next
#
[tantek]
!tell capjamesg[d] reminder: add yourself and your first "like" permalink to the end of this section! https://indieweb.org/like#IndieWeb_Examples
hendursaga and [jeremycherfas] joined the channel
#
capjamesg[d]
[tantek] I was just looking at this page: https://microformats.org/wiki/get-started
#
capjamesg[d]
"If you have a blog: add hAtom to your blog pages"
#
capjamesg[d]
Maybe this should be updated to also mention h-feed and other standards one can use.
#
capjamesg[d]
I couldn't edit the wiki by the way 😄
#
capjamesg[d]
(The Gist is private)
#
capjamesg[d]
Sorry. I meant to post that in #microformats.
#
capjamesg[d]
Wrong channel.
#
capjamesg[d]
[tantek] I added my likes pages to the wiki.
#
[tantek]
capjamesg[d] at what point did you get stuck re: couldn't edit the wiki ?
#
capjamesg[d]
Creating an account.
#
capjamesg[d]
"Please contact an admin to create an account. "
koire and [max] joined the channel
#
capjamesg[d]
What are the advantages of keeping multiple IndieWeb projects separate vs. together? I have been thinking about consolidating my microsub server, micropub client and server, and webmention receiver.
#
Loqi
It looks like we don't have a page for "advantages of keeping multiple IndieWeb projects separate vs. together" yet. Would you like to create it? (Or just say "advantages of keeping multiple IndieWeb projects separate vs. together is ____", a sentence describing the term)
#
capjamesg[d]
My thinking is that having everything running under one repository would mean I don't need to run three separate apps in the cloud. I'd also be able to provide a quick "get started" stack in one repo for people who want to host their own servers for the above things but don't want to do all of the implementation.
tetov-irc, ShinyCyril, akevinhuang, KartikPrabhu and [manton] joined the channel
#
[manton]
[tantek] Morning! I was out yesterday so just catching up… I’m interested. Is the microformats.org page still the official spec for h-feed?
#
[snarfed]
capjamesg: big question! breaks down into codebase/version control (monorepo vs multirepo), build and dependency management (monolith vs modular, compile time vs runtime), and production architecture (monolith vs SOA vs microservices)
#
[snarfed]
no "right" answers, but personally i'm a fan of monorepos, modular internal build, and monoliths until you're really really big. some of those may be minority opinions though
#
[snarfed]
open source often tends toward very multirepo/microservices since most project ownership/maintenance is loose and distributed
justache joined the channel
#
capjamesg[d]
I have not seen many monorepos for IndieWeb projects like micropub / webmention receivers which is why I thought I'd ask about this.
#
capjamesg[d]
Technically, I'd have to consolidate all of the database tables into one file, but that isn't too much hassle.
#
capjamesg[d]
Having them all as a monorepo would make deployment easier.
#
GWG
[manton]: Yes to your question about h-feed. There's also a GitHub issue tracker
#
capjamesg[d]
There would be separate README.md files for each project so everything is clear.
#
capjamesg[d]
github.com/microformats/h-feed/
#
aaronpk
a lot of my website is a monorepo, it's also not open source
#
capjamesg[d]
My main site is not open source but all of my back-end services are.
#
aaronpk
i did split out a lot of functionality though, usually as open source projects that are actually run as independent services that others can use, and I am now questioning whether that was actually a good idea
#
capjamesg[d]
I noticed you had webmention.io separate from Telegraph, etc.
#
capjamesg[d]
What was your reasoning behind that?
#
capjamesg[d]
I like the argument about independent services. My question is now whether having a "one stop service" is maybe worth considering.
#
aaronpk
well, webmention.io is on a super legacy stack so I don't want to add any more features to it really
#
aaronpk
which actually brings up another issue with doing this as a bunch of small services, it's a lot more maintenance overhead in keeping libraries up to date
#
[KevinMarks]
it was good insofar they make sense as separate composable protocols
#
[KevinMarks]
and James can build them bit by bit, gradually swapping your implementations for his
#
capjamesg[d]
I agree aaronpk.
#
capjamesg[d]
In my case I am using similar dependencies across the board (bs4, mf2py, etc.) and separate repos means I will need to update dependencies individually.
#
capjamesg[d]
I wonder what impact a monorepo would have on issue filing.
#
capjamesg[d]
There would probably need to be dedicated tags for each service provided so as to ensure "micropub" and "microsub" issues are clearly distinct from a maintainer perspectiev.
#
capjamesg[d]
GWG I left a few comments in some of the h-feed issues you filed. I'll stay posted on them.
#
capjamesg[d]
[snarfed]++ aaronpk++ [KevinMarks]++
#
Loqi
[snarfed] has 30 karma in this channel over the last year (57 in all channels)
#
Loqi
[KevinMarks] has 18 karma in this channel over the last year (48 in all channels)
[jacky] joined the channel
#
[tantek]
snarfed, interesting, I think I've leaned more towards finer granularity repos like for libraries or even "just" files, perhaps because I want them to be able to independently iterate/evolve.
#
[tantek]
[manton] glad to hear it! And yes the microformats wiki for the h-feed spec, and GitHub for issues: https://microformats.org/wiki/h-feed
#
Loqi
Tantek Çelik
#
[tantek]
aaronpk, that Foone thread, could such renaming (like crytypo 😂 ) be something a Micropub client could help you with?
#
capjamesg[d]
[tantek] independent evolution is a good argument for keeping them separate.
#
capjamesg[d]
What is a monorepo?
#
Loqi
It looks like we don't have a page for "monorepo" yet. Would you like to create it? (Or just say "monorepo is ____", a sentence describing the term)
#
capjamesg[d]
A monorepo is when a software maintainer bundles multiple projects into a single working repository.
#
capjamesg[d]
I’d love to get a few pros and cons on that page
#
capjamesg[d]
(Someone may be able to improve my definition)
#
GWG
[tantek]: Do you have any good advice about iterating on a spec?
#
GWG
I know you have done it lot
#
GWG
Microformats has change control.. but I am thinking general philosophy of what approaches work as a participant
#
[tantek]
GWG, that's a loooong conversation. Fundamentally specs/standards are agreements the implementations voluntarily sign-up for because it's more advantageous to them than not. Another way to look at specs (especially single-implementation specs) is that they're implementation documentation that says what the implementation is intended to do.
#
[tantek]
when that expands to cover the details of what a format looks like (bytes/chars in a file) or how to interact in a protocol (what network request to initiate to whom with what bytes/chars, or how to respond to such a request), then that can be the start of a specification
#
[tantek]
good way to start learning how to "think" like a spec author/editor, is to document what your existing code does with formats and protocols
#
[tantek]
when that documentation becomes general enough that someone else decides they could implement something else that does the same thing with formats and protocols, then it has taken a big step towards being a potential spec
#
GWG
It's just I've been participating in several community specs and want to improve my participation
#
capjamesg[d]
[tantek] You should document that somewhere on the IndieWeb wiki. I think it could be useful for a lot of people interested in the thinking behind standards.
#
[tantek]
GWG sure, and doing the above with your code will help you build&grow the skills you need to improve your participation
#
[tantek]
capjamesg[d] yeah it something I should incorporate into a follow-up blog post to how to do open standards development
#
Loqi
[Tantek Çelik] Ten years ago today: 10 Practices for Good Open Web Standards Development https://tantek.com/2011/168/b1/practices-good-open-web-standards-development They’ve stood the test of time (except email). Since then, there are more good practices, anti-...
#
@theBenForce
Will web 3.0 make webmentions easier?
(twitter.com/_/status/1442912297786036224)
[tw2113_Slack_] joined the channel
#
[tw2113_Slack_]
Web3 feels very web elite running away to their blockchain towers and I doubt it’s going to be all that inclusive while they shout the loudest about it
#
sknebel
if we define web 3.0 as "webmentions", then yes
#
sknebel
not a worse definition than all the others :P
#
[tantek]
what are w3bmentions
#
Loqi
It looks like we don't have a page for "w3bmentions" yet. Would you like to create it? (Or just say "w3bmentions is ____", a sentence describing the term)
#
[tw2113_Slack_]
You think Joe and Diana Smith have time, resources, and whatnot to look at blockchain? no they’re too busy working multiple jobs just to survive
#
[tw2113_Slack_]
i’ll stick with my homies in web1/web2
#
capjamesg[d]
My haha was about the w3bmentions, to be clear.
#
capjamesg[d]
I have many thoughts about this web 3 discussion but none baked enough to share.
#
[tw2113_Slack_]
word
#
capjamesg[d]
Suffice to say the open web was designed for everyone with clear purpose. I struggle to see that purpose in some “web 3” or whatever that really means tools.
#
capjamesg[d]
The semantic closeness that I feel between cryptocurrencies and decentralization / other discussions going on makes me uneasy.
#
[tantek]
see toot from Eugen
#
Loqi
[Eugen] It's frustrating how cryptocurrency has poisoned all conversation about decentralization.
#
[KevinMarks]
we should go to web4 in the spirit of RSS3
#
Loqi
definitely
#
capjamesg[d]
Loqi agrees 🙂
#
[tw2113_Slack_]
Winer approved?
edburns[d] and superkuh joined the channel
#
[KevinMarks]
Not exactly
#
[tantek]
tw2113, the more relevant question is, which implementers are interested? focusing on any one individual's "approval" is SPOF anti-pattern
#
Loqi
[dshanske] #88 Extension to Allow Clients to Get Tokens Secured by Ticket
#
GWG
In the interim, I'm updating Yarns, so can do something internally
tetov-irc joined the channel