From nobody Wed Nov 22 04:42:22 2023 X-Original-To: freebsd-hardware@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SZpWP22wZz51mwM; Wed, 22 Nov 2023 04:42:25 +0000 (UTC) (envelope-from grarpamp@gmail.com) Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SZpWN1q7jz3dwm; Wed, 22 Nov 2023 04:42:24 +0000 (UTC) (envelope-from grarpamp@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=GAz0pRpR; spf=pass (mx1.freebsd.org: domain of grarpamp@gmail.com designates 2607:f8b0:4864:20::e2f as permitted sender) smtp.mailfrom=grarpamp@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-vs1-xe2f.google.com with SMTP id ada2fe7eead31-45d9689b65dso2154115137.0; Tue, 21 Nov 2023 20:42:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1700628143; x=1701232943; darn=freebsd.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=8/9epigCmT7oLEq+fiQ1sdwGqWB5XIGaEKdAjxsvX6I=; b=GAz0pRpRuo+OIN+C9doT53UnF4duUc0wqJTu2hKNb+3gmcPH5k5ZOQXwYmH4TMj1F9 Pw1zqMLQ+Ms5upz8ODUjHuy9sfT/KqjdFdjyA/jzh1Wl6rHnw/upBqVXxcxrpYa+lJQk c0ne0j6WaGbIs+HQOxH3FWCIJJjuAxihyd+4sHUcTKYbecywI2qu8qQ947iYljRjhFfj J4UXjksvJt1ce+2mqR8jx8z/SI4p7IvSu0eAjpBj0O/aHMi3saZO/VWkBcMp8EMMUG2p a9WESWKE8G1s6pNeipefbrfEF/Pa/jr7JeAFHLe1j5LbyziaerNLWttrJW8iV+36sAMo RWKg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1700628143; x=1701232943; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=8/9epigCmT7oLEq+fiQ1sdwGqWB5XIGaEKdAjxsvX6I=; b=jbz3peY3xuEaTN2FtYfxh8FRYc94WTC/SNKEzda5fV5UFT4/ta6OBP89FTP7QtSWdd opbmZs/LzOGtd+z/CHI5xiXiahQKonwwe9McMGNGuR+hkO6dC+OnusODp0xrBFTJhL90 iHaHoVS6wOYIfUeSl8A/zRm8Z+6yk3xqr7cnOSvHngJTc54Sz7QJMtSb93niB15Bgs/g a2O+m6qPCdU+Oj0jMX1kgc6GOdU+xAp6VNYdwcdsauUrh1/oCLvvEV71x5g6uqFEATY9 Sb4DZKugHOmk9oOWEWA+2L3J6Jt5u0Hoz7WiPmNTgxnaEX97COj50qBxedobJkJHA1fV dqKQ== X-Gm-Message-State: AOJu0YzYmxHoMnIZT7qXt/hRkwvZEYWEMuNpVcofgg7SpFYY8oIJDqV1 IGTBrTIpZuhaU7HE2ZMdgJt472wfxBzDovh9BpgmRu8ruCS/MeBy X-Google-Smtp-Source: AGHT+IHvD+OAwVjM/oZtgtjSUh5hlC8RagY5/bAkTNUgZjJCkW1rS154FpTKpDzYkutf6W29P0m/ZPQ2Y8dCTvBofFM= X-Received: by 2002:a05:6102:4421:b0:45d:9113:328b with SMTP id df33-20020a056102442100b0045d9113328bmr1622984vsb.24.1700628142935; Tue, 21 Nov 2023 20:42:22 -0800 (PST) List-Id: General discussion of FreeBSD hardware List-Archive: https://lists.freebsd.org/archives/freebsd-hardware List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hardware@freebsd.org MIME-Version: 1.0 Received: by 2002:a05:612c:791:b0:434:4f32:1aa with HTTP; Tue, 21 Nov 2023 20:42:22 -0800 (PST) From: grarpamp Date: Tue, 21 Nov 2023 23:42:22 -0500 Message-ID: Subject: Cryptocurrency, FreeBSD, and on Phones could all Benefit Together [was: poor documentation] To: freebsd-questions@freebsd.org Cc: info@freebsdfoundation.org, freebsd-jobs@freebsd.org, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Spamd-Result: default: False [-4.00 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-1.000]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[text/plain]; MLMMJ_DEST(0.00)[freebsd-questions@freebsd.org,freebsd-jobs@freebsd.org,freebsd-hackers@freebsd.org,freebsd-hardware@freebsd.org]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::e2f:from]; FROM_EQ_ENVFROM(0.00)[]; RCVD_TLS_LAST(0.00)[]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; FROM_HAS_DN(0.00)[]; ARC_NA(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_FIVE(0.00)[5]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4SZpWN1q7jz3dwm X-Spamd-Bar: --- [re was: Well, no entity in the world has ever made perfect docs that cover or teach everyone everything, not possible :) And FreeBSD has recently been making some good major updates across its entire documentation space.] And now there are some new possibilities that some entities are beginning to embrace to see what works... FreeBSD has the power to serve cryptocurrency nodes to the world. Indeed, it serves up some crypto nodes, some crypto corporations run on it, some crypto client software is run by crypto users on it, etc. So if FreeBSD community would like to improve documentation, hardware support, desktop, features, consultancy services, educational and howto media channels, and more... Perhaps they could consider for some things there... - Posting up on the worldwide crypto job boards. - Running crowdfunds, prediction markets, bounties. - Setting aside some portion for a crypto endowment. - Enabling crypto donations, sponsorship, referrals, etc. There are a lot of potential crypto funders out there who like opensource but can't send tips and sponsorship to FreeBSD and community because they still don't accept crypto. Reaching out to and engaging with the crypto world, porting all the popular crypto coins client software to FreeBSD, getting mutual awareness adoption and cross-marketing going between FreeBSD and the Crypto Scene, can all help bring new resources and ideas and users into some of the areas you seek to address. Those job boards could even yield a new job in the crypto space, then you could donate part of your pay to those working on FreeBSD in the form of cryptocurrency. Partnering with the crypto community could also be perhaps the fastest way to fund getting FreeBSD ported and running as the OS on an opensource crypto phone. A lot of the Crypto Scene don't really trust their Google'd Apple'd OS as a good idea on their crypto phones and are looking for an alternative OS, especially given devices like PinePhone, Librem, etc are coming out. Take a look at how hardware and software and the crypto scenes are coming together to accomplish things. And at how entities and non-profits, and individuals are accepting and using crypto. Consider recognizing the advent and power of cryptocurrency and working that greenfield to build mutually beneficial ecosystems. After all, cryptocurrency is the future, and those who are integrating some of its models would be well positioned to prosper in that future. Happy hacking :) -- YouTube search: xWAwK2fHArc , _U3lEc-IFr8 , ... https://duckduckgo.com/?ia=videos&iax=videos&q=voluntaryism https://odysee.com/@Anarchast:2 https://bitchute.com/ || https://rumble.com/ || https://odysee.com/ X.com: NameRedacted247 || Rumble.com: v3x4ssy https://libertarianinstitute.org/books/voluntaryist-handbook/ #OpenFabs , #OpenHW , #OpenAudit , #FormalVerification #CryptoCrowdFunding , #PredictionMarkets , #OpenTrust #GuerrillaNets , #P2PFiber , #GNURadioRF , #PrivacyCoins #DropGangs , #CryptoUAPeez , #DistributedEverything , ...