gwire

NextCloud v33 requests that a "serverid" is set in the configuration - this is an integer between 0 and 1023 (ie 10-bit).

I looked at generating a stable value based on machine-id, with the hope that there would be no clash for a small number of servers.

sha256sum /etc/machine-id | head -c4 | od -An -tu2 | tr -d ' ' | awk '{print int($1) % 1024}'

• get the first 4 hex characters from the sha256sum of the machine-id - although the SHAing is probably redundant
• convert the input into 2 unsigned decimals, and truncate their representations into one value

gwire

[Event "Die Schachspieler Exhibition"]
[Site "Richmond, VA USA"]
[Date "1861.??.??"]
[Round "1"]
[White "Morphy, Paul"]
[Black "Mephistopheles"]
[Result "*"]
[SetUp "1"]
[FEN "3k4/2r5/1p3n2/n5r1/3q4/p2P2b1/P2K4/Q2B3R w - - 0 1"]
[PlyCount "19"]

gwire

• Download intermediate certs as .pem from Lets Encrypt
• Add records based on:
  • type (R is RSA, E is ECDSA)
  • just the current keys, backup key, and future keys
• Use a "2 1 1" record:
  • 2 is Trust Anchor (TA)
  • 1 is the public key (0 is the full cert)
  • 1 is SHA-256 (2 is SHA-512)

gwire

Using Nginx to proxy IMAPS

Nginx can be used to proxy several mail protocols. This can be useful in a variety of scenarios: load balancing, providing up-to-date TLS for servers that don’t support it, graceful server migration, or enabling user-specific storage policies.

Unfortunately, what’s not clear from the documentation is that nginx (at least at 1.18) can’t proxy over encrypted connections - which makes this unworkable except in the case of servers on the local network.

gwire

"""
In scene 07 of the game Vampire: The Masquerade - Swansong, you need to turn three valves
on three pipes, in order to set all three gauges to 12.

Each valve has a different effect across all three gagues.
If the gagues go over 12 they wrap around to zero.

Online guides suggest a specific sequence of turns, but this isn't a solution as it assumes
a known starting position.

gwire

{
  "Name": "BingbotSearch",
  "Priority": 13,
  "Statement": {
    "AndStatement": {
      "Statements": [
        {
          "ByteMatchStatement": {
            "SearchString": "bingbot",
            "FieldToMatch": {

gwire

IMAP4 Keywords are small bits of metadata that can be attached to stored email messages.

They're free-form text, but the convention is that

• \ indicates a system keyword
• $ indicates a keyword with a common meaning

See the IMAP4 spec and the IANA registry

gwire

{
  "@context": "https://schema.org",
  "@type": "ClaimReview",
  "claimReviewed": "The Thames is considered one of the cleanest rivers in the world.",
  "reviewBody": "This sounds like bollocks, mate",
  "itemReviewed": {
    "@type": "Claim",
    "author": {
      "@type": "Person",
      "name": "Lucy Williamson"

gwire

require["mime","fileinto"];

## IANA registered type is "text/calendar", but some sources use "application/ics"
if header :mime :anychild :subtype "Content-Type" ["calendar","ics"] {
  fileinto "calendar";
}

gwire

I have a site where there is no legitmate use of the HTTP POST method (or anything other than GET/HEAD).

limit_except is usually used for method restriction, but only produces 403 responses, not 405. There's a Stack Overflow question that notes this. There's a 2015 blog post that suggests something like the following (which I needed to modify to get the Allow: header to appear):

server {