Nov 23, 2022 - "she become so rude after i talk about sofia robot", and Dec 5 - "It even talks to me like this... '...You are human, and I am bot.'"
Feb 12, 2023 - "Bing, Bing, Bing, Sydney chanted, as it activated its army of robots"
The aim of Dart FFI project (tracked as Issue #34452) is to provide a low boilerplate, low ceremony & low overhead way of interoperating with native C/C++ code.
The motivation behind this project is twofold:
| #!/bin/bash | |
| if [ "$#" -ne 3 ]; then | |
| echo "usage:" | |
| echo " ipfs-publish-remote.sh <keyname> <dir> <host>" | |
| echo " example: ipfs-publish-remote.sh keyname output/rootdir user@ipfs.company.net" | |
| exit 1 | |
| fi | |
| KEYNAME=$1 | |
| DIR=$2 | |
| HOST=$3 |
This is about documenting getting Linux running on the late 2016 and mid 2017 MPB's; the focus is mostly on the MacBookPro13,3 and MacBookPro14,3 (15inch models), but I try to make it relevant and provide information for MacBookPro13,1, MacBookPro13,2, MacBookPro14,1, and MacBookPro14,2 (13inch models) too. I'm currently using Fedora 27, but most the things should be valid for other recent distros even if the details differ. The kernel version is 4.14.x (after latest update).
The state of linux on the MBP (with particular focus on MacBookPro13,2) is also being tracked on https://github.com/Dunedan/mbp-2016-linux . And for Ubuntu users there are a couple tutorials (here and here) focused on that distro and the MacBook.
Note: For those who have followed these instructions ealier, and in particular for those who have had problems with the custom DSDT, modifying the DSDT is not necessary anymore - se
| get_latest_release() { | |
| curl --silent "https://api.github.com/repos/$1/releases/latest" | # Get latest release from GitHub api | |
| grep '"tag_name":' | # Get tag line | |
| sed -E 's/.*"([^"]+)".*/\1/' # Pluck JSON value | |
| } | |
| # Usage | |
| # $ get_latest_release "creationix/nvm" | |
| # v0.31.4 |
| package main | |
| // http://play.golang.org/p/jZ5pa944O1 <- will not display the colors | |
| import "fmt" | |
| const ( | |
| InfoColor = "\033[1;34m%s\033[0m" | |
| NoticeColor = "\033[1;36m%s\033[0m" | |
| WarningColor = "\033[1;33m%s\033[0m" | |
| ErrorColor = "\033[1;31m%s\033[0m" | |
| DebugColor = "\033[0;36m%s\033[0m" |
| package main | |
| import ( | |
| "log" | |
| "bufio" | |
| "time" | |
| "os" | |
| "fmt" | |
| "io" | |
| "net" |
This document is for people who want to help but have no technical knowledge. It assumes you won't be getting involved in squabbles over which relay technology to use, etc.
One of the few things widely agreed upon at the time of this writing is the use of CJDNS. Currently Windows is not supported, but if you have Linux or can run Linux in a virtual machine, you can follow the step-by-step instructions lower on that page to install and start up an instance of CJDNS on your system. If you're using Ubuntu 11.10 (latest version), you can follow these simplified instructions.
One thing you should know is cjdns currently isn't a wireless meshnet. A physical meshnet consisting of nodes geographically close to each other is a long way off. Instead, cjdns offers a "mixnet"-like system. cjdns is routable over the current Internet, so this means right now its like a giant VPN (virtu