tanglebones

using System;
using System.Linq;
using System.Net;
using System.Text;
using System.Threading;
using System.Threading.Tasks;

namespace Server
{
    public static class Program

rxaviers

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

atduskgreg

Canidae
Felidae
Cat
Cattle
Dog
Donkey
Goat
Guinea pig
Horse
Pig

josephbadow

I'm running a dockerized Firefly III on a Raspberry 3 in my local network. With the help of an additional nginx Container and a self-signed SSL Certificate I was able to set up https.

Maybe somebody will find this guide helpfull, it took me a couple of tries to get it right.

Install Docker on the Raspberry

Simply follow the official documentation at https://docs.docker.com/install/linux/docker-ce/debian/#install-using-the-convenience-script. You'll need to run the script if you are using the default Raspberry OS: Raspbian.

Install Docker Compose using Python PIP

Use Pythons package manager PIP to install Docker Compose, details can be found on docker.com as well: https://docs.docker.com/compose/install/#install-using-pip. Before you can follow the guide you'll need to install python-pip.

CoconutMacaroon

This has been moved. It is now here: https://github.com/CoconutMacaroon/Teams-Mods

CoconutMacaroon

#!/bin/bash
usage() {
    echo "TkFNRQogICBpbnN0YWxsLW1vZGVybi11bml4LnNoIC0gSW5zdGFsbCBzb21lIHVzZWZ1bCB1dGlsaXRpZXMgZnJvbSBNb2Rlcm4gVW5peAoKU1lOT1BTSVMKICAgaW5zdGFsbC1tb2Rlcm4tdW5peC5zaCBbT1BUSU9OXQoKREVTQ1JJUFRJT04KICAgSW5zdGFsbCB1dGlsaXRpZXMgZnJvbSBNb2Rlcm4gVW5peAoKICAgLWEKICAgICAgQ3JlYXRlIGFsaWFzZXMgZm9yIGNvbW1hbmRzIGJlaW5nIGluc3RhbGxlZCBpbiB+Ly5iYXNocmMKCiAgIC1iCiAgICAgICBJbnN0YWxsIGJhdCwgYSByZXBsYWNlbWVudCBmb3IgY2F0CgogICAtZAogICAgICBJbnN0YWxsIGR1ZiwgYSByZXBsYWNlbWVudCBmb3IgZHUKCiAgIC1oCiAgICAgICBQcmludCB0aGlzIGhlbHAKCiAgIC1sCiAgICAgICBJbnN0YWxsIGxzZCwgYSByZXBsYWNlbWVudCBmb3IgbHMgLSBBUk0gdmVyc2lvbgoKICAgLWYKICAgICAgIEluc3RhbGwgZnNmLCBhIGZ1enp5LWZpbmRlcgoKICAgLXQKICAgICAgIEluc3RhbGwgdGxkciwgaGVscC1wYWdlcyB3aXRoIGV4YW1wbGVzIGZvciBjb21tYW5kcyAtIFJlcXVpcmVzIG5vZGUuanMvbnBtIHRvIGJlIGluc3RhbGxlZAo=" |
        base64 --decode
}

update() {
    sudo apt-get update
}

0xabad1dea

Risk Assessment of GitHub Copilot

0xabad1dea, July 2021

this is a rough draft and may be updated with more examples

GitHub was kind enough to grant me swift access to the Copilot test phase despite me @'ing them several hundred times about ICE. I would like to examine it not in terms of productivity, but security. How risky is it to allow an AI to write some or all of your code?

Ultimately, a human being must take responsibility for every line of code that is committed. AI should not be used for "responsibility washing." However, Copilot is a tool, and workers need their tools to be reliable. A carpenter doesn't have to