Blog

  • Privacy is not impunity

    Originally published April 2023. The argument hasn’t changed. The platforms have only made it more urgent.

    Every community has behaviour that is legal but corrosive: the committee member who treats the organisation’s money as their own, the volunteer who bullies newcomers until they leave, the member who harasses others and dares anyone to prove it. No law covers most of it, and no law should. For most of history it was handled by something more powerful than law: reputation. People cared what their community thought of them, and behaved accordingly.

    I made this argument in 2000, in The thin veil of civilisation. Social norms, enforced by approval and disapproval, are the real glue of a society. Laws are the backstop.

    That glue is weakening. Communities are larger, more anonymous and more transient. Someone can behave badly in one organisation and turn up fresh in the next, with a clean slate and a new set of targets. The tools communities now run on make it worse. Facebook groups and WhatsApp chats give organisers no memory and no standing: complaints vanish in a scroll, and the platform’s rules, not the community’s, decide what can be said.

    Privacy matters

    I take privacy seriously. People should control their own data, decide what is shared, and never be exposed on a whim. That principle is why I build member-owned infrastructure in the first place.

    But privacy protects people from strangers, corporations and the state. It was never meant to protect people from the consequences of how they treat others. Privacy that means no one may ever say “this person did this, and it isn’t acceptable” is not privacy. It is impunity.

    Accountability done properly

    Naming has to be done carefully or it becomes a mob. The rules that make it legitimate:

    • Conduct, not character. What someone did, not who they are.
    • Decided by those accountable, through a known process, not by whoever shouts loudest.
    • A right of reply before anything is published.
    • Proportionate and time-limited. Records expire. People can change.

    Whether to go further and name people publicly is each community’s call. I would, and I do. A community’s duty doesn’t end at its own boundary: if bad actors are quietly shown the door, they simply move on to the next organisation, which gets no warning. Keeping it private protects the offender, not the next victim. But I understand why others stop short of that, and a fair internal record is still far better than none.

    Whichever you choose, the truth matters. Publish only what you can stand behind. Anyone named falsely has the law of defamation on their side, which is exactly as it should be.

    Communities should own this

    The point is not shaming for its own sake. It’s that a community should be able to set its own standards and enforce them, on infrastructure it controls, under rules it writes. When the platform belongs to someone else, you get their rules and their priorities, and usually their silence. When it belongs to you, you can build accountability that is fair, transparent and answerable to members.

    It’s how I run Princes Park Touch, whose Hall of Shame is public, and it’s what LocalHero is built to let any community do, publicly or not.

    Fediverse Reactions
  • Native apps are (mostly) a waste of time.

    Native apps are (mostly) a waste of time.

    So you think you need an app for your phone and you were considering shelling out some cash to a developer to build you a native app. Before you waste your money (and time) paying a developer to deliver a native app the first thing you need to consider the advantages an app has over a traditional website.

    The big three are:

    1. It is installable, ie it appears on the phone home screen, this gives it a massive advantage over a traditional website in ensuring ongoing user interaction.
    2. An app is fast, ie it is faster to load and interact with than a traditional website.
    3. It can send notifications, again this increases user interaction substantially.

    Obviously these are not the only reasons but they are the major ones.

    Now here is the kicker, you can get all the above features on a website on the majority of phones right now! Goodbye native apps and welcome to the world of progressive web apps.

    What is a progressive web app (PWA), you may ask? Well at it is heart it is just a website with some additional features. Those features enable all three of the advantages I outlined above on the majority of smart phones worldwide, right now!! But being a website a PWA also has some massive advantages. They include:

    1. They are linkable, ie you can access them by opening a URL.
    2. They are much easier to build, after all they are just a website with some substantial enhancements.
    3. They are updatable, ie any changes can occur as soon as the PWA is accessed (as opposed to waiting for a user to download a new version of a native app).
    4. Being on the web they are cross platform.

    Lets look at the state of play on different phones:

    On android phones which now constitute the majority of smart phones worldwide all of the above advantages are currently already available to progressive web apps. ie visitors will be prompted to instal your website on the phone (provided it meets the PWA criteria) right now and that website if properly designed will be fast and be able to send notifications

    For appleĀ  the situation is not quite so good. Yes you can install a web app but the installation experience not obvious and there is no ability to send notifications. The good news is that but in the upcoming IOS version (IOS 12.2) there will be significant improvement. Once installed on your phone a well built progressive web app will behave like its native counterpart, with the only issue that it will not be able to send notifications. But that functionality is coming.

    Update: since March 2023 IOS supports push notification for those running PWAs on IOS 16.4 or later.

    So in conclusion is that unless you need certain hardware apis that are not supported by PWA“s yet or you desperately need notifications on Apple phones then you should find a web developer who can enhance your existing website to become a PWA. The future is PWA“s and the future (to a large extent) is already here.

  • Don’t break the web or why html is important

    I am a member of the advanced WordPress facebook group and its seems every few days someone posts and article on there waxing lyrical about the latest javacsript only theme they have built using the latest JavaScript framework and the rest api.

    Dont get me wrong, I love javscript, and I think the rest api is one of the best things to happen to WordPress but every time I read about someone usea front end framework to build a theme I shake my head.

    A wise man once said,

    just because you can doesn’t mean you should

    This applies to so many things, especially JavaScript when used to output content.Ā  In order to explain we all need to be reminded of the way the web is traditionally designed namely:

    • HTML for conĀ­tent
    • Css for preĀ­senĀ­taĀ­tion
    • Javascript for funcĀ­tionĀ­alĀ­ity

    This combination might seem old hat but it was created by smart people with good reasons.

    When done properly it has three major strengths

    1. It conveys meaning
    2. It is robust
    3. It has a clear separation of concerns

    However it can be slow so today many advocate using JavaScript to interract with apis to replace this traditional paradigm. This hasĀ  major advantage in that can be substantially faster as the client side javascript can request only the information that it needs. However it also means that javascript is now the creating the content as well as the providing the functionality

    However lets just compare how this compares to the traditional approach. Namely:

    Conveying meaning.Ā  Yes javascript can convey an experience that may be indistunguishable to the eye BUT the web is not just a visual medium for humans. Machine like search engines, and screen readers are important and in most cases a javascript front end is invisible to these agents

    Being robust. Javascript is a not a fully standardized lanaguage and is notorious for conflicts and errors, and being browser depe3ndent. So an error on a javascript front end usually means the whole site falls over. In contrast a traditional semantic html front end degrades gracefully

    Separating concerns. In a JavaScript front end you are tightly coupling functionality with content and potentially presentation as well. This actually if you change the api or you change your javascript the whole thing falls over. In contrast html is html and if the JavaScript stops working you still have the html.

    Javascript is important but its not a replacement for html. Its future is in rproviing functionality, both in enhancing the reading experience and in making the eually important area of creating, updating and deleting content on the web.

    Finally I’d like to urge you that is you need speed work on the basics like http caching, or look to modern technologies like http/2 and service workers.

  • Introducing LH Archived Post Status

    LH Archived Post status is a WordPress extension that creates an additional posts status available for content that may no longer be relevant to most visitors but should be available publicly (perhaps for historical purposes).

    I built this plugin as UI needed this flexibility whilst using WordPress as a CMS. The plugin adds a new post status that enables posts and pages (and custom post types) to be archived. Archiving in this context means that the content is still publicly available but is not published on the front page of the site or the feed. I was not satisfied with other archiving solutions which hid the content for all non logged in visitors and was not configurable.

    (more…)
  • WordPress development is apathetic

    WordPress development is apathetic

    There has been a lot of discussion that WordPress is becoming less user friendly and indeed it has got some traction as the recent WordPress 3.8 is certainly aimed (amongst other things) around making the dashboard more user friendly. Given this I don’t think wordpress is becoming less user friendly, however it’s never been friendly to newbies.

    Instead I think the area where Worpress has dropped the ball is that sensible projects that could make its so much better are not being tackled, instead development seems to be based on UI improvements and quick wins. These are great but a better WordPress platform would make these sort of improvements easier. Indeed a better platform would enable people to build their own UI. Thus rendering the rolling MP6 (and similar initiatives) into the core moot (because developers would be rolling their own version of the dashboard through plugins).

    (more…)
  • Some clarification to the webmentions discussion

    Some clarification to the webmentions discussion

    In reply to this analysis by Barnaby Walters of my original article.

    Barnaby you wrote:

    The evidence is against you here, as almost all known usage of webmention has been for short replies which don’t make sense without context.

    Actually we aren’t disagreeing, maybe I didn’t express myself well when I wrote ā€œAt the moment of the method is built around a POSSE architecture. This works well for long form articles which can stand alone but address issues or ideas that are posted on an external websiteā€.

    (more…)
  • Thoughts on extending webmentions

    Thoughts on extending webmentions

    I recently installed Matthias Pfefferle’s web mention plugin. It is a great plugin and hopefully when he has polished it up further he will push it out to the wordpress.org plugin repository so it can enjoy a wider audience. I actually think the Jetpack team should look at including an extended set of this functionality in its plugins as the potential for distributed sharing that the indieweb provides could be a major distinguishing feature for WordPress, and certainly a better bet than trying to roll their own social networking ecosystem.

    (more…)
  • LH RDF not just xml anymore

    LH RDF not just xml anymore

    LH Rdf is back!!

    Yes development has started again and the first stop is to add additional formats to the output. Previously Lh Rdf only supported RDF-xml and has been designed almost exclusively around that. Therefore to add other formats I have bundled the Easyrdf library into the plugin. When the query string lhrdf is added to the feed URL the Easyrdf parser is invoked to parse the rdf xml output string and the output is then available in various triple formats.

    See code extract:

    $graph = new EasyRdf_Graph();
    $graph->parse($out,ā€rdfxmlā€);
    $data = $graph->serialise($_GET[ā€˜lhrdf’]);

    The format chosen by value of the lhrdf variable E.G. http://localhero.biz/?feed=lhrdf&lhrdf=json

    As well as simply being cool, having an option to output JSON is the main benefit as the triples are now no longer imprisoned by the same domain policy.

  • Visualising RDF with Incontext

    Visualising RDF with Incontext

    Surfing around the internet I recently discovered SURFā€˜s InContext Visualiser, which I think is a neat way to visualise of RDF relationships, especially OAI-ORE aggregated publications

    I also discovered that people have already created a set of WordPress plugins (see: http://ep-books.ehumanities.nl/ ) to visualise books and other similar publications. However blogs do not fit into a book/chapter model.

    However given there is already a schema for publishing blog data and my lh-rdf plugin already exposes most publicly available WordPress blog data as RDF using that format. It was an obvious next step to get the visualiser working with the LH RDF output. I have done so and hopefully you think the output is cool.

    https://shawfactor.com/visualiser-test/

  • Introducing LH Tools

    Introducing LH Tools

    Intoducing LH Tools.

    LH Tools is a WordPress extension that adds an (ARC-based) RDF Store and SPARQL Endpoint to the WordPress blogging system. The store is kept separate from the WP tables (i.e. it’s not a wrapper), but you can use WP’s nice admin screens to configure it, it and embed it using the large number of developer-friendly hooks that WP offers. It is based on the original work by Ben Nowack.

    (more…)

Install Factor

shawfactor.com

Open it straight from your home screen, full screen and quicker to load.

  1. Tap the Share button . If you cannot see it, tap ••• first.
  2. Scroll down and tap Add to Home Screen.
  3. Tap Add.
  1. Tap the browser menu ā‹®.
  2. Tap Install app or Add to Home screen.
  1. In the menu bar, choose File, then Add to Dock.

Use your browser's menu to install this site or add it to your home screen.