HardSecurity

MeatballWiki | RecentChanges | Random Page | Indices | Categories

Sometimes, when you give up on individuals or groups, SoftSecurity is inadequate. In those cases, HardSecurity controls access to the community: to its people, its resources, its functionality, its commons. Of course, don't be paranoid; sane people DefendAgainstParanoia. Don't give up on others if life is telling you to grow as a person. HardSecurity is security which involves the use of force. HardSecurity is like rock. It's strong until broken, when it shatters into unrepairable pieces. Some ideas. ● AuditTrail. Use the system's omniscience to judge people in real time. ● PoliceForce. Many communities need some sort of police action. It seems kind of anti-social to impose force from "above", seemingly external to the community, but a PoliceForce provides a BalancingForce to a community. It balances the explosive power of disrespect for fellow citizens' rights and freedoms. ● CommunityWarning. Give peers the ability to punish bad behaviour. ● CommunityExile. Exile troublesome members from the community. This can be for a limited amount of time or a LifetimeBan. Technically difficult to do online with AnonymousIdentity, though HardBanning is still very common. ● PersonalIdentification. Create a login system by which you can track each member's identity. But LoginsAreEvil, and people may create a PublicAccount to thwart you. ● HumanVerification. ConfirmHumanity?. A TuringTest. As in, a captcha (See WikiPedia:captcha). Detect whether or not the agent is human as a way to exclude bots. A bunch of crucial actions (registering for a site, editing a wiki page) require a mechanism that confirms it's a person, not a script. Usually a distorted image with text in it, something a computer can't process but people can. ●AccessLevels. Provide a hierarchy of privileges to different members of the community. The higher one is, the more power, freedom and control one has. Contrast PeerPrivilege. ● FunctionalAccess. The inverse of AccessLevels. Break the system down into its core functions, dole them out separately to each person based on her role. ● WeightedFranchise. Give more valued members of the community more weight when making decisions. ● SubscriptionFee. Control members' access through an ongoing fiscal arrangement. ● GatedCommunity. Only let a select and invited group of people into the "club". (aka "by invitation only.") ● TrustMetric / WebOfTrust. Using network flow theory, these systems reject newly petitioning members that the community feels aren't trustable, or CommunityExile those who have harmed the community. That is, they only let those people into the "club" that the community feels are trustable. ● RatingSystem?. Give or restrict people access based on some rank or score either computed algorithmically or as rated by other individuals. Alternatively, either rank or hide content based on some rating system. This way, malicious individuals or contentious content can be removed based on some consistent metric. A superset of a VotingSystem?. (See also other ideas in the CategoryRatingSystem.) ● DelayAction. Create an impervious fence with time. Make it impossible for an attacker to get results right away. ● FlyPaper?. A LandMine that serves to weed out people who do not fit the CommunityExpectations. Usually presented as some sort of PricklyHedge, but can be any BarrierToEntry?. (e.g. MeatballWiki requires people to UseRealNames, and to not use TimeStamps)

Interesting: AuditTrail and DelayAction are also listed on SoftSecurity. Others are missing: SurgeProtector, SecurityByObscurity(?) and EnforceResponsibility.

CategoryWikiTechnology CategoryHardSecurity

Discussion

UserName (required):