MichaelTaylor3D

This post links my 3Box profile to my Github account! Web3 social profiles by 3Box.
    
  ✅ did:3:bafyreiee5db7tnq62y7rbyco4zgzhags3zsvqq2zwxn3w36itmqhyno3ay ✅
    
    Create your profile today to start building social connection and trust online at https://3Box.io/

MichaelTaylor3D

using System;
using System.IO;
using Org.BouncyCastle.Crypto.Engines;
using Org.BouncyCastle.Crypto.Modes;
using Org.BouncyCastle.Crypto.Parameters;


namespace TestConsole
{
    class Program

MichaelTaylor3D

<div>
  <table
    cellpadding="0"
    cellspacing="0"
    role="presentation"
    width="550"
    class="wrapper"
  >
    <tbody>
      <tr>

MichaelTaylor3D

Keybase proof

I hereby claim:

• I am michaeltaylor3d on github.
• I am michaeltaylor3d (https://keybase.io/michaeltaylor3d) on keybase.
• I have a public key ASBW-VuolcHsA4r2i41JcfV31NsjtMm6al38DvTlZIYF7Qo

To claim this, I am signing this object:

MichaelTaylor3D

To install an executable (.exe) as a Windows service, you can use the node-windows package in conjunction with the install.js script. Here's an example of how to set up a script to install an executable as a Windows service:

1. Install node-windows:

npm install -g node-windows

2. Create a new JavaScript file (e.g., install-exe-service.js) in your project folder:

MichaelTaylor3D

Title: Add Custom Headers Configuration for DLaaS Data Layer Plugin Services

Current Behavior: DLaaS uses a job queue pattern to do work on the local machine. Jobs are queued up in SQS, and any number of workers can join/leave the system. Additionally, each individual worker has multiple parallel threads dedicated to processing jobs from the job queue.

To utilize the existing system and its paradigm, the Datalayer Uploader plugin was developed, creating a serverless API with the correct datalayer uploader interface. The API receives the store and filenames from the datalayer and creates a job in the job queue that maps to an S3 uploader job in the worker. The API will queue up the job, and the next available worker thread will pick it up and upload the required files to S3 to be served through a CDN.

The system has shown to work as expected; however, the configuration in the datalayer's config.yaml only accepts the base host of the plugin interface. The original intention was that a localhost service

MichaelTaylor3D

worker_processes 1;

events {
    worker_connections 1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

MichaelTaylor3D

chia wallet get_transactions --clawback
chia rpc wallet spend_clawback_coins "{\"coin_ids\":[\"TRANSACTION_ID\"], \"force\":true, \"fee\":0}"

MichaelTaylor3D

#!/usr/bin/env python3

import requests
import fuse
from fuse import FUSE, FuseOSError, Operations

class ChiaDataLayerFileSystem(Operations):
    def __init__(self, rpc_base_url):
        self.rpc_base_url = rpc_base_url

MichaelTaylor3D

const fs = require('fs');
const readline = require('readline');

// Input file path with one NFT ID per line
const inputFile = 'nft.csv';

// Output batch script file path
const outputFile = 'generate_offers.bat';

// Read the NFT IDs from the input file