capjamesg[d]Next.js is a JavaScript framework developed by Vercel and a community of open-source contributors that may be used to develop a personal website.
LoqiIt looks like we don't have a page for "IndieWeb Utils" yet. Would you like to create it? (Or just say "IndieWeb Utils is ____", a sentence describing the term)
capjamesg[d]IndieWeb Utils is a library that contains a set of building blocks for creating IndieWeb applications in Python, developed by {{capjamesg}}.
@AstraLumaIf you're serious about a decentralized web, go look at federation technologies like ActivityPub or IndieWeb, and think about how we can enable less-technical people to use these.
Often times, tech dev isn't shiny and full of buzzwords. It's grinding through through problems. (twitter.com/_/status/1473324373071253511)
[tantek]in particular it looks like you could start a /Next.js#How_To section with at least the mention of how to setup webmentions (that tutorial that's linked from the /Webmention page)
boffosocko.comedited /handwriting (+726) "added Rocketbook and Livescribes as potential platforms/solutions; removed extra see also link; moved Alton Brown and Jeff Bridges to appropriate sections; link to article and synopsis; brainstorming section to encourage experimentation" (view diff)
@pbakaus↩️ IndieWeb, @GrantForTheWeb and others are all fighting the good fight, but (imo) lack product designers and managers laser focused on consumer use cases and product market fit. Need to invest in marketing these web2 movements to folks. (twitter.com/_/status/1473411930379358208)
@pbakausThe most uncomfortable thought I have about web3 is that we* let it happen. We could have solved transactions and payments. We could have invested in more robust decentralized social layers. Web3 tries to fill gaps we left. Probably time to course correct. *the web2 community (twitter.com/_/status/1473411190084698114)
@danyork@pbakaus@GrantForTheWeb Yes, the original Web 1.0 was, and still is, massively decentralized. And many aspects of "Web 2.0" were as well. But to your point, the independent projects didn't have product designers who could create the UX that consumers wanted. The platforms DID create easy UX. (twitter.com/_/status/1473419263625019392)
[tantek]looks like Paul works at Google now, does he know the history of how G+ essentially fumbled their huge opportunity to make it all work with open standards? (my blog post0
[schmarty]Plenty of stuff that works with plenty of ideas floating around about how to improve or scale. Few people with the skills and time who actually show up.
[tantek][schmarty] I think that obscures it. Why is "UX problem" a labor problem and not say, "Feed parsing" a labor problem? Why does the latter attract sufficient developer surplus time (and community!) to create openly, while the former does not?
[tantek]saying it is a "labor problem" obscures harder questions of why we got plumbing-centric open source projects/communities, but no respective UX-centric open design projects/communities?
[schmarty]Many open source communities or at least their maintainers focus on plumbing and downplay other kinds of contributions, from UX to docs to emotional labor and more
[schmarty]UX work is also a kind of work that creates work. So a UX person can show up and do a great job for a project but unless they are also ready to contribute code, there's a reliance on those who will write the code to take the notes and act on them
[tantek]edgeduchess[d], there are difficult coordination problems in "just" plumbing work too, witness the "what do we have to do to ship a release of the phpmf2 parser" discussion in #microformats
[tantek]the other pattern that we saw early on in the #microformats community is frankly a huge disparity in the average level of frankly, "social/emotional maturity" between folks who were plumbing-centric and folks who were design-centric.
[schmarty]There is no "IndieWeb project", there are dozens, built by different people at differing times. Things drift in and out of compatibility and relevance as the community iterates
[schmarty]edgeduchess[d] that is a great question with many possible answers. Typically I think we would start with: what do YOU (the someone showing up wanting to help) want for your own personal website
edgeduchess[d][tantek]: Yeah I understand where you're coming from. There's also a related problem with technical founders in startups. If the leads don't care about good design, it doesn't get prioritized.
[tantek]and we've found that to be a fairly good filter to dissuade the "I'm here to fix all your problems because I'm an expert that knows best" folks
edgeduchess[d]In an environment where tech voices abound, it might be hard to make designers feel welcome and important, also because of that difference in approaches.
LoqiTypical use of the term roadmap does not refer to actual roads, maps, or maps of roads - instead, keep a personal priority ordered list of what you're specifically Working On, and for unsorted or vague desires, add them to an unordered Itches list, on your User page or your project's page https://indieweb.org/roadmap
[tantek]by working on their own site, they become the best folks to understand what is the next thing they need/want, which may very well be very different than what others need/want on their personal site
[tantek]this is a fundamental assumption problem. there is no "collective roadmap", and if there were it would likely exclude quite a lot of folks who have different wants/needs
[tantek][KevinMarks] that's a details of plumbing-projects feature support thing, has nothing to do with UX-focus that edgeduchess[d] and I'm talking about
[schmarty]There was some interesting stuff done by Simply Secure about design for decentralized systems which was not tied to any particular software. It's interesting to read through and see what assumptions are baked in
[tantek]lots of folks went in different directions (which is ok), lots of folks built mockups or prototypes, yet none of those got any critical mass of collaboration
[schmarty]That was funded work I think. Not sure by whom or who might be using it to guide their work today, but it has a lot of stuff that feels geared more towards Mastodon like stuff
[tantek]a lot (most?) of those early on UX efforts (first few years of IndieWebCamps) were solo-driven and thus died when people got bored, distracted, hired, or burnt out
[schmarty]Known has gone back to a community model with slower updates. I'm not aware of anyone offering to host it these days. It's kind of Tumblr-like, I guess.
[tantek]so the only "sustainable" way to do good incremental UX is when you do it first and foremost for your own personal website, because you *will* keep coming back to that
[tantek]if you start with a "help all the non-tech people" goal, and work on it alone, I can pretty much guarantee you will get bored, distracted, hired, or burnt out
[schmarty]micro.blog is very active and has a lot of ways to interact thanks to being built with APIs in mind. There are apps focused on Twitter-style microblogging, on photography, on podcasting, and more
LoqiMake what you need is an IndieWeb principle that helps creators focus on creating & publishing things prioritized by what they need & want for their own personal site https://indieweb.org/make_what_you_need
[schmarty]I would be interested in seeing someone try out an IndieWeb-powered small community in the vein of Darius Kazemi's https://runyourown.social/
[schmarty]What I am trying to describe is: a small thing built and managed by a community to meet the community's needs, based on IndieWeb building blocks rather than Mastodon/ActivityPub