mohammed-akkad

fun isValidIPv4Address(ipAddress: String): Boolean {
    val segments = ipAddress.split('.')
    val maxNumberOfSegments = 4
    if (ipAddress.isEmpty() || segments.count() != maxNumberOfSegments) return false
    segments.forEach { item ->
        val rangeOfSegment = 0..255
        val segment = item.toIntOrNull() ?: return false
        if ((item.count() > 1 && item.startsWith('0')) || segment !in rangeOfSegment) return false
    }
    return true

jaydorsey

# Block things on LinkedIn with uBlock Origin that LinkedIn won't let you block
# Choose "Options" in uBlock Origin with a right-click, and add these to
# "My filters"

# ADDING YOUR OWN FILTERS
#
# Using Linkedin.com as an example
#
# 1. Open up the webpage
# 2. Find some text you want to block

qoomon

Conventional Commit Messages

See how a minor change to your commit message style can make a difference.

Tip

Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default

allenyllee

#!/bin/bash

# install qemu utils
sudo apt install qemu-utils

# install nbd client
sudo apt install nbd-client

mlugg

gpa: Allocator,
/// I don't know how io_uring works, so my usage here is going to be total bollocks.
/// I'm going to never init this, and I'll write:
/// ```
/// io_uring.pushSqe(.{
///     .op = .sleep,
///     .arg0 = clockid,
///     .arg1 = std.time.ns_per_s,
///     .user = ptr,
/// });

mofakhar

#!/bin/bash

#
# Initial script to create users when launching an Ubuntu server EC2 instance
#

declare -A USERKEY

#
# Create one entry for every user who needs access. Be sure to change the key to their

chripede

Self-hosted Stalwart mail server

• Self-hosted Stalwart mail server
  • Introduction
  • Before you get started
  • Basic setup
  • Stalwart
    • Install
      • Optional choices for storage

• PostgreSQL

Gabriel-Rozendo

Types

• feat Commits, that adds or remove a new feature
• fix Commits, that fixes a bug
• refactor Commits, that rewrite/restructure your code, however does not change any API behaviour
• perf Commits are special refactor commits, that improve performance
• style Commits, that do not affect the meaning (white-space, formatting, missing semi-colons, etc)
• test Commits, that add missing tests or correcting existing tests
• docs Commits, that affect documentation only
• build Commits, that affect build components like build tool, ci pipeline, dependencies, project version, ...
• ops Commits, that affect operational components like infrastructure, deployment, backup, recovery, ...

Jaffies

---Usage:
---```bash
---cat input.b | luajit main.lua | luajit
---```
---Or (with input)
---```bash
---cat input.b | luajit main.lua > output.lua
---cat input.txt | luajit output.lua > output.txt
---```
local function readIO()

rishavpandey43

Git Commit Messages Style-Guides

• Use the present tense ("Add feature" not "Added feature")
• Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
• Limit the first line to 72 characters or less
• Reference issues and pull requests liberally after the first line
• When only changing documentation, include [ci skip] in the commit title
• Consider starting the commit message with an applicable emoji

Types