vporton

#!/bin/sh

# Script to run a shell command without breaching security of your home dir:

# safe cat /home/me/VERY-SECRET-FILE
# cat: /home/me/VERY-SECRET-FILE: No such file or directory

# Requires `firejail`, `expect`, `xserver-xorg-video-dummy`.
# The file /etc/X11/xorg.conf.d/dummy-1920x1080.conf is to be taken from
# https://techoverflow.net/2019/02/23/how-to-run-x-server-using-xserver-xorg-video-dummy-driver-on-ubuntu/

vporton

Response to a security audit

Trusted courts

Chain of trust is interntional. It has (at least) the following usages:

• District courts may trust supreme courts. This trust is unconditional.
• A court may trust an automated exchange. If no absolute trust, it could not function.

So, in my opinion, your response to trusted courts is invalid. If you have any response, please respond.

vporton

The future of open source is to reward open source developers with minted crypto money (instead of current inefficient or not working ways to monetize). It can be done with my Ethereum Reward Courts software.

Open source usually benefits the entire world, but only a small number of people or companies provide reward for an open source product. Instead we should mint money creating inflation in the entire world spread approximately equally between all and reward open source with those minted money. It means that open source will be both free and paid: free for users, paid by the entire world (the entity who benefits).

This way we could turn most of the closed source software into open source, because open source will become more profitable than closed source, due to a more just spreading of spents.

vporton

Keybase proof

I hereby claim:

• I am vporton on github.
• I am porton (https://keybase.io/porton) on keybase.
• I have a public key ASBwvejjmaetGkkHF7QxxH9oTLzl4_eYwHfJizu5jq8rYAo

To claim this, I am signing this object:

vporton

using System.ComponentModel.DataAnnotations;
using System.ComponentModel.DataAnnotations.Schema;

namespace BravoDB.Models.Tables
{
    [Table("AdvShows")]
    public class AdvShowsTable
    {
        [Key]
        public int AdvOrderID { get; set; }

vporton

        private static void ProcessTable(ModelBuilder modelBuilder, PropertyInfo contextMember)
        {
            Type tableType = contextMember.PropertyType.GetGenericArguments()[0];

            PropertyInfo[] members2 = tableType.GetProperties();

            foreach (var m in members2)
            {
                object[] attrs = m.GetCustomAttributes(typeof(KeyAttribute), true);

vporton

Pure Dependency Injection in D

Dependency injection

A little modified quote from Wikipedia, Dependency injection article (This quote is licensed under CC BY-SA 3.0):

In software engineering, dependency injection is a technique whereby one object (or static method) supplies the dependencies of another object. A dependency is an object that can be used (a service). An injection is the passing of a dependency to a dependent object (a client) that would use it. The service is made part of the client's state. Passing the service to the client, rather than allowing a client to build or find the service, is the fundamental requirement of the pattern.

The intent behind dependency injection is to achieve Separation of Concerns of construction and use of objects.

vporton

In D language we cannot construct an object of a template argument type in a template, as shown by the following example:

class Constructor(Result, Params...) {
    const(Result) create(Params params) {
        return new Result(params);
    }
}

void main() {
    class X { }

vporton

Modify tuple modifiers

The problem

In the standard D library it seems missing a function to modify tuple modifiers.

Consider the following:

alias t = AliasSeq!(int, float); // create tuple (int, float) of two types
alias tc = addTupleModifiers!("const shared", t);

vporton

Memoization in the D Programming Language, part 2

In continuation of the article Memoization in the D Programming Language, this article describes new features of my D library memoize-dlang.

I remind that memoization is automatically not calling a function again when called with the same parameters (usually to reduce the amount of computations).

memoize functions

memoize is the same as memoize from std.functional module from standard library Phobos (implemented differently in some very little details, namely using string mixins (autogenerated code) to implement all of memoize, noLockMemoize, synchronizedMemoize (see below) based on a common template). memoize template without maxSize argument is implemented in a quite simple way (see below). memoize with maxSize argument is implemented in a rather comple