It would be cool to have a shared community repository of site adapters, in the spirit of adversarial interoperability [1]. It's probably the most tedious and boring part of such projects, once it's abstracted away it would be much more fun to experiment. This could also be useful for projects like Fraidycat [2] or RSS feed generators like Politepol [3], alternative UIs like Woob [4] etc
There's a huge amount of conceptual similarity between Wildcard and Electric Tables. I think I like (from the videos) the table approach of Wildcard a bit better, but it looks like Wildcard is more single-page focused, while Electric Tables is more focused on bringing multiple pages together into a single table.
I can envision something like the Wildcard UI, but Electric Tables concepts, so the table follows you from page to page, but can be augmented from data from the specific page - allowing you to save one or more rows from each page you visit to the master table (e.g. a single product from a product page, or a list of products from a search result).
A very common usage pattern that I find myself in is searching Amazon for products, opening individual ones, deciding that product is useless/useful, making notes about specific features. The Wildcard concept of modifying the page directly ("hide this product, never show it to me again", "add a note to this product", "fix the unit price info for this product to be a standardized unit") might be done on either the search result or the individual product page, but would be representing data on a "obscure product search" table.
The same thing happens with research on obscure programming issues - again, it'd be really cool to be able to augment my Google Search results like Wildcard Shows, but from both the search results page, as well as from the actual page being referenced.
A community repository would be super nice for those. Something along the lines of DefinitelyTyped[1], all managed through git, easily integrates with other stuff (like shown on npmjs.org when the @types package exists), allows maintainers to "own" the adapters they contribute by making a PR. It's really the N adapters * T time per adapter that really makes it hard for one person to do. That plus monitoring API changes/flakiness of each adapter to make sure the data is still solid.
It would be cool to have a shared community repository of site adapters, in the spirit of adversarial interoperability [1]. It's probably the most tedious and boring part of such projects, once it's abstracted away it would be much more fun to experiment. This could also be useful for projects like Fraidycat [2] or RSS feed generators like Politepol [3], alternative UIs like Woob [4] etc
[0] https://github.com/geoffreylitt/wildcard
[1] https://www.eff.org/deeplinks/2019/10/adversarial-interopera...
[2] https://fraidyc.at
[3] https://github.com/taroved/pol
[4] https://woob.tech