timothyham

A Short IPv6 Guide for Home IPv4 Admins

This guide is for homelab admins who understand IPv4s well but find setting up IPv6 hard or annoying because things work differently. In some ways, managing an IPv6 network can be simpler than IPv4, one just needs to learn some new concepts and discard some old ones.

Let’s begin.

First of all, there are some concepts that one must unlearn from ipv4:

Concept 1

davepcallan

using Microsoft.AspNetCore.Diagnostics;
using Microsoft.AspNetCore.Mvc;
using System.Net;

namespace Samples;

public class GlobalExceptionHandler(ILogger<GlobalExceptionHandler> logger) : IExceptionHandler 
{
    public async ValueTask<bool> TryHandleAsync(
          HttpContext httpContext, 

davidfowl

using System.Data.Common;
using System.Runtime.CompilerServices;
using System.Text;
using Npgsql;

GetCatalogItemsSql(null, null, null, 10);

void GetCatalogItemsSql(int? catalogBrandId, int? before, int? after, int pageSize)
{
    // This looks like it would be susceptible to SQL injection, but it's not.

davidfowl

using System;
using System.Threading.Tasks;

namespace System.Collections.Concurrent
{
    public static class ConcurrentDictionaryExtensions
    {
        /// <summary>
        /// Provides an alternative to <see cref="ConcurrentDictionary{TKey, TValue}.GetOrAdd(TKey, Func{TKey, TValue})"/> that disposes values that implement <see cref="IDisposable"/>.
        /// </summary>

jelster

using Microsoft.AspNetCore.Mvc.Testing;
using System.Net;
using System.Threading.Tasks;
using Xunit;
using System.Net.Http;
using System.Collections.Generic;
using Newtonsoft.Json;

namespace Api.FunctionalTests
{

vlkam

        
        // https://support.hockeyapp.net/kb/api/api-crashes
        public static async Task<bool> SendHandledException(CaughtExceptionModel model)
        {
            string version = DeviceInfo.AppVersion;
            var arr = version.Split('.');
            string short_ver = arr[arr.Length - 1];
            var deviceInfo = Plugin.DeviceInfo.CrossDeviceInfo.Current;

            StringBuilder sb = new StringBuilder(12000);

madskristensen

using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Http;
using Microsoft.AspNetCore.WebUtilities;
using Microsoft.Net.Http.Headers;
using System.IO;
using System.Security.Cryptography;
using System.Threading.Tasks;

public class ETagMiddleware
{

gboudreau

Exporting your 2FA tokens from Authy to transfer them into another 2FA application

IMPORTANT - Update regarding deprecation of Authy desktop apps

Past August 2024, Authy stopped supported the desktop version of their apps:
See Authy is shutting down its desktop app | The 2FA app Authy will only be available on Android and iOS starting in August for details.

And indeed, after a while, Authy changed something in their backend which now prevents the old desktop app from logging in. If you are already logged in, then you are in luck, and you can follow the instructions below to export to tokens.

If you are not logged in anymore, but can find a backup of the necessary files, then restore those files, and re-install Authy 2.2.3 following the instructions below, and it should work as expected.

jgold6

* Reducing executable size: 
http://developer.xamarin.com/guides/cross-platform/deployment,_testing,_and_metrics/memory_perf_best_practices/#Reducing_Executable_Size

* Use the linker (iOS [1],  Android [2]) to remove unnecessary code from your assemblies
[1] https://developer.xamarin.com/guides/ios/advanced_topics/linker
[2] https://developer.xamarin.com/guides/android/advanced_topics/linking

* Reference third-party libraries judiciously

* Applying constraints to generics may reduce app size, since less code would need to be included (haven’t verified this)

rudyryk

//
//  Countdown.cs
//  Created by Alexey Kinev on 11 Jan 2015.
//
//    Licensed under The MIT License (MIT)
//    http://opensource.org/licenses/MIT
//
//    Copyright (c) 2015 Alexey Kinev <[email protected]>
//
using System;