Skip to main content

Biomedical and Electrical Engineer with interests in information theory, evolution, genetics, abstract mathematics, microbiology, big history, IndieWeb, mnemonics, and the entertainment industry including: finance, distribution, representation

boffosocko.com

chrisaldrich

chrisaldrich

+13107510548

chris@boffosocko.com

stream.boffosocko.com

www.boffosockobooks.com

chrisaldrich

mastodon.social/@chrisaldrich

micro.blog/chrisaldrich

 

@QwxleaA @ade_oshineye @houshuang Some have been experimenting with using the Webmention spec to allow one wiki, note, or digital garden space interact with another. It's become quite common in the blogosphere, why not for online notes or zettelkasten?
https://indieweb.org/Webmention

 

I'm sorry you've run into this issue. I can't help but wonder if most of the spam is really pingback spam? Much of what you've gotten likely isn't arriving via webmention as I see the following header in your page:
<link rel="pingback" href="https://webmention.io/www.miriamsuzanne.com/xmlrpc" />

My guess along with some minor sleuthing is that the entirety of the spam you're seeing is of the pingback variety as the mechanism by which webmention works is mean to actively decrease the amount of unwanted spam. Vanishingly little Webmention spam has been seen in the wild.

Removing the pingback link from the header of that particular page (or others that might get linked to with heavily trafficked sites like CSS-Tricks which are often pirated) should solve your immediate problem. Hopefully those who are working on additional anti-spam features will add to these measures to further mitigate this sort of issue for the broader publics' use and adoption. I've personally experienced this sort of "attack" at least once in the pingback space and another using the even older refbacks specification. On my small personal site, I leave them all on however, particularly for the small slice of academic blogging community that still uses pingbacks and the benefits generally outstrip the annoyance. Naturally your mileage may vary and you may consider turning them off.

Of course, you'll probably also realize that the reason the CSS-Tricks notification was caught in spam was because it also came in as a pingback and not by webmetion. (I'm pretty sure that they don't have webmention set up to send them, so their site would have only sent a pingback.)

Many of the older systems, including WordPress which are frequently used by these same sorts of pirates, will still send/trigger pingbacks. Within the IndieWeb space, most sites explicitly sending webmention notifications will include h-cards with author names and timestamps which is part of why Max Böck’s filtering solution works well.

On the positive side, I wonder if this sort of notification behavior might help sites like CSS-Tricks to track these sort of bad actors for help in potential take downs of this sort of piracy?

 

@benwerd @benwerd@mastodon.social It would be cool if they could easily expose numbers of interactions (reads, replies, bookmarks, etc.) as a signal in a way such that social readers could filter using this data along with tags/categories for prioritizing what we might want to read.

Selfishly they could use these signals internally for better measuring engagement with articles and particular writers. Is it high quality engagement (useful comments, reads) versus lower quality engagement (bookmarks which might indicate "I read the headline and might be interested").

Highly enterprising publications, and especially "local" publications/newspapers, might consider offering IndieWeb as a Service to allow their readers the ability to have their "own platform" within the publisher's platform/stack. This could be done on a co-op basis or potentially even bundled into subscription prices. Something along the lines of Kinja perhaps, but with more ownership/control/ability to move. Or perhaps a white-labeled version of something like micro.blog, but run/managed by the NYT, WSJ, other?

A well tummeled version of the Hometown fork of Mastodon with "local only posting" could be an engaging thing for a sophisticated newspaper or magazine to create. The publication could have closer control/moderation of the local posting for article related conversations, but people could still communicate with others outside of that "home" server. Alternately, in the standard Mastodon model, the "public timeline" could be filtered for posts about or commenting on the outlet's own content and all other content goes into the federated timeline.

Publications offering their own microsub social reader interfaces could be fun and clever. It could be an interesting way to have a more streamlined reading experience for paid subscribers among other potential options. This could be an interesting interface for helping people build a truly custom reading experience specifically for them, particularly for larger newspapers with large amounts of content that could be better filtered and personalized to individuals.

 

@TerribleMia You've got your own site and control your URLs, so you're definitely on it! And you've got Webmentions for additional icing on the cake. Kudos! I'm glad you've managed to get things set up and working for yourself. It definitely helps to have small bite-sized pieces of technology to rely on to get it all going.

You're right that it's a lot of work on individuals, but there are some emerging platforms/providers attempting to make all of this technology easier on the general public who don't have the time, technical skills, or desire to maintain any of their own systems. Micro.blog is one of these options to be sure. A few others can be found here: https://indieweb.org/Quick_Start With available small building blocks that interoperate, hopefully it will be easier for companies to provide a variety and plurality of tools to make the entire enterprise easier for all of our friends and family.

Congratulations again!

 

@lordmatt I'm not aware of a centralized collection (yet). Some, but not all, of the projects and sites you'll find at https://indieweb.org/discovery have some resources for finding people who can send/receive webmentions. Everyone on @microdotblog certainly can.

 

A refback (remember those?!) today reminded me about this post: Non-technical IndieWeb: Fun, Creativity, Community, and “Content” https://boffosocko.com/2020/12/20/non-technical-indieweb-fun-creativity-community-and-content/
I should try to add more on and to my IndieWeb Collection https://boffosocko.com/research/indieweb/

 
 

@MuireallPrase Maybe this helps with context? https://boffosocko.com/2022/05/09/the-logos-ethos-and-pathos-of-indieweb/
I like your site; glad to virtually meet another who's interested in physics, math, and typesetting!

 

Kudos to @KevinMarks for his recent work on @Tumblr to add microformats to make it more IndieWeb friendly!
https://changes.tumblr.com/post/683524731509653505/friday-may-6th-2022

 

@edheil Because of the IndieWeb principle of plurality, you've got a tremendous amount of choice. Part of the issue is that there are SO MANY options and potential combinations of doing things.

What do you want the site to do? How much admin time to you want to spend on it? How flexible and modifiable do you want it to be? What skills do you have? What skills do you want to work on?

Both of the options you mention are excellent, though there's probably more immediate flexibility in WordPress with plugins. If you want something with no admin, but still some reasonable flexibility then micro.blog is a great way to go. (All three support a very broad range of all the IndieWeb building blocks. Of course, this doesn't even touch the custom-built or static site generator spaces which are also available options. And who's to say you should only have one site? ;)

This is a great question to ask in the IndieWeb Dev chat channel for advice from a bigger group of people with a tremendous wealth and diversity of building experience. https://chat.indieweb.org/dev

 

@edheil Bridgy matches posts on your site to Twitter using one of a few methods so that it can backfeed the proper replies to the appropriate posts. Providing it with syndication links is usually easiest, and on WordPress try: https://indieweb.org/u-syndication#How_to_link_from_WordPress

David Shanske's Syndication Links plugin also should have a checkbox set up (non-Gutenberg) for more easily syndicating to Twitter and other services if you like. There are many ways to publish to Brid.gy without visiting it for each. Using Shankse's plugin which sends it Webmentions is probably the easiest, though it may require proper markup in your theme. For the technical part see: https://brid.gy/about#publishing which explains in outline how it works.

I think many of the options are documented either here or on related pages: https://indieweb.org/Getting_Started_on_WordPress

For other options and advice, it may be best/easiest to visit the IndieWeb WordPress chat at chat.indieweb.org/wordpress

 

@edheil Which of the various methods (manually, plugin(s), other) are you using? On fragility front, I'm not too worried as it is open source and has folks helping. It's also only a bridge as I can reply directly to your site.
https://brid.gy/about#cost
https://indieweb.org/Bridgy#Statistics

 

At Homebrew Website Club watching with great anticipation as @KevinMarks adds microformats to the base Tumblr theme to help make it more IndieWeb friendly.
https://events.indieweb.org/2022/05/monthly-guiding-compass-homebrew-website-club-nS6KBMwoZDFm

 

@omgmog@indieweb.social Glad to see others using Known and using it to syndicate to Mastodon!

 

@alexwilliams Micro.blog is an inexpensive turnkey IndieWeb friendly solution for doing something like that. Bring your own domain or subdomain and you're off to the races with all the benefits and none of the overhead or work.