I grew up on a farm at Dunneworthy, near Ararat, where independence isn’t a lifestyle choice. Nobody is coming to fix the pump. You work it out, or it doesn’t get done. But nobody on a farm is truly alone either. They turn up when the shed burns down, and everyone knows who pulls their weight and who doesn’t. Self-reliance and community weren’t opposites. They were the same habit, seen from two sides.

Rugby taught me the same thing. I played at state level, then semi-professionally in England, until a broken leg ended it. Fifteen stubborn individuals only become anything when they agree to play for each other. The best players I knew were the most independent-minded and the most committed to the side.

Then I spent fifteen years in banking, and learnt the opposite lesson. A large organisation offers neither independence nor community. You don’t govern yourself, and you don’t really belong to anything you help govern. You comply. Decisions arrive from somewhere above, wrapped in process, owned by no one you can argue with. I chafed under it.

It took me a while to realise the Greeks had already named what I was looking for.

Free, together

To the ancient Greeks, independence and community were not in tension. Freedom, eleutheria, meant not having a master: not being a slave, and not living under a tyrant. But it was not the modern freedom to be left alone. A free man was free because he took part. He spoke in the assembly, argued, voted, and then lived under laws he and his fellow citizens had made. Aristotle called us politikon zōon, creatures of the polis. Outside a community, he said, a man is either a beast or a god.

But the Greek idea had a blind spot. Citizenship was for a minority, and women, slaves and foreigners were shut out. But the core insight survives: you cannot be free alone, and you cannot be free in a community you have no say in running.

The new tyrants

Look at where most communities live now.

The local footy club runs on a Facebook group and a WhatsApp chat. The residents’ association keeps its members in a spreadsheet on someone’s Google Drive. The choir, the surf club, the parents’ committee: all of them tenants, on land owned by a handful of companies on the other side of the world.

Those companies are not malicious. But they are masters. They decide who can see a post, what may be said, which members are reachable, what the data is worth and to whom. They change the rules without a vote. When a community’s page is shut, its group throttled or its history lost, there is no assembly to appeal to. The Greeks had a word for rule like that, and it was not democracy.

We have rebuilt the tyranny the Greeks fought to escape, and we did it for convenience.

Self-government is a practice

I founded Princes Park Touch to have fun, and it became something more. Today it has more than 760 members, and 500 to 600 people play each season. It runs on its own infrastructure: its own website, its own member records, its own communications, with no Facebook group holding the keys. Members can see the rules. The club answers to them, and every year the committee reports to them at the AGM.

It is not frictionless. Self-government never is. People have to turn up, argue, accept outcomes they voted against, and hold each other to the standards they set. That is the price of freedom, and it is cheaper than the alternative.

That is why I build LocalHero. It started in 2016 as a way to link local content to local people. It has become a platform that lets community organisations own what they depend on: their website, their members, their data, and increasingly their AI tools. Because a community that does not control its own infrastructure cannot govern itself.

Independence needs community, and community needs independence

I still dislike being told what to do by people I didn’t choose and can’t remove. But the cure for that was never isolation. It was building communities worth belonging to, and making sure they belong to their members.

The Greeks understood that the free individual and the self-governing community are one thing, not two. Online, we have forgotten it. We traded the assembly for the feed, and citizenship for a terms-of-service checkbox.

We can take it back. It starts one organisation, one community at a time.

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.

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.

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.

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.

Posts are available directly for any visitor but can have a custom message added that flags that they may no longer be relevant.

WordPress’ default post statuses currently work very much like an on/off switch as far as a finished post is concerned. Of the eight default statuses, Published is the only one that is public, while all the rest remain behind the curtain in various states of unreadiness. None of the statuses, apart from Published, adequately indicate that a post is complete or finished or its relevancy.

Fortunately, WordPress makes it possible for developers to register their own custom post statuses, which is what I’ve done with this plugin. It allows you to archive posts in the same way that you might archive email.

Archived Post Status is compatible with posts, pages, and custom post types, giving you a wide array of possible use cases:

• Archive pages or posts from a conference or event for editing and re-use next year
• Archive real estate listings for records
• Cycle portfolio content in and out of the site as necessary
• Temporarily remove listings from a site that indexes businesses or organizations
• Archive products to bring back for future use

While custom post types seem to be one of the most likely uses for this plugin, you may not want to have the archived status available to all post types. Thisd can be done by slecting the appropriate posts types in the settings area.

If you need to public archive completed posts, but hide them from the front page, feeds, and flag their state this simple plugin will do the trick. Installation instructions etc are available here:
https://lhero.org/portfolio/lh-archived-post-status/