●● IRC: #techbytes @ Techrights IRC Network: Thursday, January 05, 2023 ●● ● Jan 05 [00:08] *u-amarsh04 has quit (Ping timeout: 2m30s) [00:11] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes [00:20] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [00:24] *u-amarsh04 has quit (Quit: Konversation terminated!) [00:26] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes [00:29] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes [00:45] *u-amarsh04 has quit (Quit: Konversation terminated!) [00:51] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes ● Jan 05 [02:27] *psydruid (~psydruid@jevhxkzmtrbww.irc) has left #techbytes [02:28] *psydruid (~psydruid@jevhxkzmtrbww.irc) has joined #techbytes ● Jan 05 [03:01] schestowitz >> Re: coercion & deception [03:01] schestowitz >>> There is already some good coverage of people being coerced, e.g. the [03:01] schestowitz >>> email to Renata and the demotion email that Dr Preining published. [03:01] schestowitz >> A demotion in the context of unpaid work is a weird concept. [03:01] schestowitz > Yes, but that in itself is not coercion [03:01] schestowitz > [03:01] schestowitz > Demoting somebody secretly and threatening to tell other people about it [03:01] schestowitz > is coercion. If the intention of the coercion is for the victim to work [03:01] schestowitz > without pay then it is modern slavery. [03:01] schestowitz > [03:01] schestowitz > [03:01] schestowitz >>> The analysis of the way the FSFE fellowship worked, with fake membership [03:01] schestowitz >>> cards, etc, is a strong example of deception because the members were [03:01] schestowitz >>> not recorded on the FSFE e.V. membership roll. [03:02] schestowitz >>> [03:02] schestowitz >>> Do you have any tag or category for your articles to help identify [03:02] schestowitz >>> coercion, in particular, doing work under coercion? [03:02] schestowitz >> Not coercion in particular, but:http://techrights.org/category/deception/ [03:02] -TechBytesBot/#techbytes-techrights.org | Deception | Techrights [03:02] schestowitz > There is a lot of deception in tech. What I'm specifically trying to [03:02] schestowitz > focus on is deception that is intended to make people work for free. [03:02] schestowitz > [03:02] schestowitz > Example: lets say the FSFE posts a job vacancy and asks 100 people to do [03:02] schestowitz > coding tasks but they don't have any intention to employ any of these [03:02] schestowitz > people, they are just posting these job vacancies to get people to fix [03:02] schestowitz > bugs for them. If a whistleblower in the organization reveals the [03:02] schestowitz > vacancy was a hoax then there could be a prosecution. [03:02] schestowitz > [03:02] schestowitz > I already have an example of this from an organization in another [03:02] schestowitz > country. They tried to get me to add a new feature to a well known [03:02] schestowitz > program. A normal employer would do this task in the probationary [03:02] schestowitz > period but this particular employer tried to get me to do it as a test, [03:02] schestowitz > despite the fact they can see all my code online anyway. [03:02] schestowitz > [03:02] schestowitz > [03:02] schestowitz >>> Do you have any tag or category for your articles to help identify [03:02] schestowitz >>> deception, in particular, doing work under a deceptive relationship? [03:02] schestowitz >>> [03:02] schestowitz >>> Each of these topics, coercion and deception, can be relevant in a [03:02] schestowitz >>> modern slavery prosecution. [03:02] schestowitz >>> [03:02] schestowitz >>> - coercion or deception to contribute code [03:02] schestowitz >>> [03:02] schestowitz >>> - coercion or deception to change a license to be more permissive [03:02] schestowitz >>> [03:02] schestowitz >>> - coercion or deception to do sysadmin work [03:02] schestowitz >>> [03:02] schestowitz >>> - coercion or deception to do conference organization [03:02] schestowitz >>> [03:02] schestowitz >>> - coercion or deception to do IT support, helping users [03:02] schestowitz >>> [03:02] schestowitz >>> Some of the evidence is about coercion to say or not say something. [03:02] schestowitz >>> This may not be modern slavery. Oversimplifying it, censorship doesn't [03:02] schestowitz >>> always relate to doing unpaid work. But if it intersects with the work [03:02] schestowitz >>> somebody is doing then there could be an issue. [03:03] schestowitz >> Some times this month or next month I will show how my employer tried to [03:03] schestowitz >> use my job as pretext to offer support to their family friend: [03:03] schestowitz >> [03:03] schestowitz >> http://techrights.org/wiki/Sirius_Open_Source [03:03] -TechBytesBot/#techbytes-techrights.org | Sirius Open Source - Techrights [03:03] schestowitz >> [03:03] schestowitz >>> Both the Daniel Baumann and Norbert Preining emails are encouraging them [03:03] schestowitz >>> to continue doing Debian work under a framework of coercion. This is [03:03] schestowitz >>> distinct from emails to Renata telling her what to say. [03:03] schestowitz >> The above mentions the role of guilt and humiliation to coerce workers. [03:03] schestowitz >> One more examples of that will be published tonight. Instructions under [03:03] schestowitz >> threat. [03:03] schestowitz > There is that question of how Dr Preining and I both realized we were [03:03] schestowitz > subject to secret shaming experiments and started communicating about it. [03:03] schestowitz > [03:03] schestowitz > It was me who noticed they were coercing Dr Preining and reached out to him. [03:03] schestowitz > [03:03] schestowitz > This is the thing they hate about me more than anything else. As [03:03] schestowitz > fellowship representative, I defended Michael Kappes. It was my role to [03:03] schestowitz > defend him, even if he had been guilty I still would have felt obliged [03:03] schestowitz > to speak up as the representative. That is when FSFE really turned ugly. [03:03] schestowitz > [03:03] schestowitz > [03:03] schestowitz >>> From time to time I've seen comments from companies who felt pressured [03:03] schestowitz >>> to use an open source license. For example, I feel that the tone of [03:03] schestowitz >>> this article was shaming xTuple into changing their license, without [03:03] schestowitz >>> giving any economic reason why xTuple would benefit from changing it: [03:03] schestowitz >>> [03:03] schestowitz >>> https://web.archive.org/web/20080122022821/http://blogs.cnet.com/8301-13505_1-9749950-16.html [03:03] -TechBytesBot/#techbytes-web.archive.org | OpenMFG transforms into xTuple, but misses the open-source train | The Open Road - The Business and Politics of Open Source by Matt Asay - CNET Blogs [03:03] schestowitz >>> [03:03] schestowitz >> I remember the xTuple debacle very well. [03:03] schestowitz >> [03:03] schestowitz >>> Agreed, they had been a bit naive when they started using the term open [03:03] schestowitz >>> source. But rather than mocking them, I think that the blog could have [03:03] schestowitz >>> simply left the reader with the choice, e.g. "xTuple needs to either [03:03] schestowitz >>> adopt an OSI approved license or avoid using the term open source" [03:03] schestowitz >> OSI is corrupt, deeply corrupt, it became a front group for Microsoft [03:03] schestowitz >> and proprietary GitHub. [03:03] schestowitz > Agreed, but the general understanding of what is an open source license [03:03] schestowitz > hasn't diverged too much right now. Maybe it will in future. But what [03:03] schestowitz > I'm looking for specifically is to index cases where any project has [03:04] schestowitz > been bullied, even if they simply bullied somebody to go from GPL to BSD. [03:04] schestowitz > [03:04] schestowitz > Regards, [03:04] schestowitz > Thanks Roy, I forgot about that one. First time I've seen it. [03:04] schestowitz > all best, [03:04] schestowitz Excellent talk. Covers lots of what we've been speaking about, and beyond... [03:04] schestowitz The Q&A also has some good bits, even is the "Q" is inaudible. ● Jan 05 [04:24] *u-amarsh04 has quit (Quit: Konversation terminated!) [04:26] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes ● Jan 05 [11:40] schestowitz
  • [11:40] schestowitz
    2023: Linux rusting away into non-FOSS territory Build rnote and you will see
    [11:40] -TechBytesBot/#techbytes-sysdfree.wordpress.com | 2023: Linux rusting away into non-FOSS territory Build rnote and you will see | systemd-free linux community [11:40] schestowitz
    [11:40] schestowitz

    Linux 6.2-rc2 kernel is out as the last commit in kernel.org at the start of the 2023 year. RUST is here, the initial code-base is included in the kernel. At least Arch seems to be disabling it for now, at the beta level at least, we shall see.

    [11:40] schestowitz

    Rust is not just a language, as people commonly think, it is much more. It is a building environment, system, and a mode change of the philosophy of building packages from source. Rust incorporates its own git system in pulling code in from 2nd and 3rd parties. So if you have never gotten into the real FOSS practice of auditing code before you build, try and audit this stuff. If building in C you thought [11:40] schestowitz was a practice similar to building sand castles, by comparison, this is like building sand castles with quick-sand ON QUICK SAND.

    [11:40] schestowitz
    [11:40] schestowitz
  • [11:53] *u-amarsh04 has quit (Quit: Konversation terminated!) [11:54] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes [11:57] schestowitz
  • [11:57] schestowitz
    Dissecting Guix, Part 1: Derivations
    [11:57] -TechBytesBot/#techbytes-guix.gnu.org | Dissecting Guix, Part 1: Derivations 2023 Blog GNUGuix [11:57] schestowitz
    [11:57] schestowitz

    To a new user, Guix's functional architecture can seem quite alien, and possibly offputting. With a combination of extensive #guix-querying, determined manual-reading, and plenty of source-perusing, they may eventually figure out how everything fits together by themselves, but this can be frustrating and often takes a fairly long time.

    [11:57] schestowitz

    However, once you peel back the layers, the "Nix way" is actually rather elegant, if perhaps not as simple as the mutable, imperative style implemented by the likes of dpkg and pacman. This series of blog posts will cover basic Guix concepts, taking a "ground-up" approach by dealing with lower-level concepts first, and hopefully make those months of information-gathering unnecessary.

    [11:57] schestowitz
    [11:57] schestowitz
  • [11:57] schestowitz
  • [11:57] schestowitz
    Non-Destructive Silicon Imaging (and Winner of Name that Ware December 2022)
    [11:57] schestowitz
    [11:57] -TechBytesBot/#techbytes-www.bunniestudios.com | Non-Destructive Silicon Imaging (and Winner of Name that Ware December 2022) bunnie's blog [11:57] schestowitz

    The ware for December 2022 is an AMD Radeon RX540 chip, part number 216-0905018. Congrats to SAM for guessing the ware; email me for your prize. The image is from Fritzchen Fritzs Flickr feed; I recommend checking out his photos (or you can follow him on twitter). Even if you arent into photos of chips, he elevates it to an art. Even more amazingly, all of his work is public domain; hats off to him [11:57] schestowitz for contributing these photos to the commons with such a generous license, because it is not easy to prepare the material and take images of this quality. If any of my readers happens to know him and are willing to make an introduction, Id appreciate that. I only discovered his work by chance while doing some background research.

    [11:57] schestowitz
    [11:57] schestowitz
  • ● Jan 05 [12:26] schestowitz
  • [12:26] schestowitz
    Decarbonizing Cryptocurrencies through Taxation
    [12:26] -TechBytesBot/#techbytes-Decarbonizing Cryptocurrencies through Taxation - Schneier on Security [12:26] schestowitz
    [12:26] schestowitz

    Maintaining bitcoin and other cryptocurrencies causes about 0.3 percent of global CO2 emissions. That may not sound like a lot, but its more than the emissions of Switzerland, Croatia, and Norway combined. As many cryptocurrencies crash and the FTX bankruptcy moves into the litigation stage, regulators are likely to scrutinize the cryptocurrency world more than ever before. This presents a [12:26] schestowitz perfect opportunity to curb their environmental damage.

    [12:26] schestowitz
    [12:26] schestowitz
  • [12:34] *u-amarsh04 has quit (Quit: Konversation terminated!) [12:36] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes [12:41] schestowitz
  • [12:41] schestowitz
    Breaking RSA with a Quantum Computer
    [12:41] -TechBytesBot/#techbytes-Breaking RSA with a Quantum Computer - Schneier on Security [12:41] schestowitz
    [12:41] schestowitz

    The Chinese group didnt have that large a quantum computer to work with. They were able to factor 48-bit numbers using a 10-qbit quantum computer. And while there are always potential problems when scaling something like this up by a factor of 50, there are no obvious barriers.

    [12:41] schestowitz

    Honestly, most of the paper is over my headboth the lattice-reduction math and the quantum physics. And theres the nagging question of why the Chinese government didnt classify this research. Butwowmaybeand yikes! Or not.

    [12:42] schestowitz
    [12:42] schestowitz
  • ● Jan 05 [13:25] schestowitz >> The Q&A also has some good bits, even is the "Q" is inaudible. [13:26] schestowitz > They were a potentially tough crowd. It was an "AI" conference and [13:26] schestowitz > every single one an MSc or postdoc researcher who finished a [13:26] schestowitz > project. Many of the projects were of dubious utility and morality - [13:26] schestowitz > typical academic fare of "let's do buzzword project because we can!" [13:26] schestowitz > So I hoped for some probing questions. What I got were really [13:26] schestowitz > stock internet memes. So I was a bit disappointed they didn't feel [13:26] schestowitz > able to challenge even on home ground. Or perhaps they thought my [13:26] schestowitz > critique was irrelevant/beneath response. [13:26] schestowitz > [13:26] schestowitz > These days detailed Q and A works well as interview/podcast where [13:26] schestowitz > there's more time and the pace can be regained by edits later. [13:26] schestowitz > [13:26] schestowitz > Tfanks for posting it anyway. [13:26] schestowitz > [13:26] schestowitz > best, ● Jan 05 [16:06] *u-amarsh04 has quit (Quit: Konversation terminated!) [16:07] *u-amarsh04 (~amarsh04@auubhxtweg528.irc) has joined #techbytes [16:33] schestowitz https://www.fosslife.org/network-problems-slow-remote-workforce-productivity [16:33] -TechBytesBot/#techbytes-www.fosslife.org | Network Problems Slow Remote Workforce Productivity [16:33] schestowitz " [16:33] schestowitz Many organizations are still struggling to deliver seamless digital experiences for remote workers, reports Nathan Eddy. [16:33] schestowitz Eddy cites an Exoprise Systems report, which says that 90 percent of knowledge workers face consistent technical and remote network problems, which are hampering remote workforce productivity. [16:33] schestowitz Issues include slow network response time and unpredictable application performance, exemplified by dropped Zoom calls, slow page loading, application crashes, and unresponsive endpoint devices, Eddy says. ● Jan 05 [18:29] *geert (~geert@3scxme2iddxsw.irc) has joined #techbytes ● Jan 05 [23:28] *geert has quit (Ping timeout: 2m30s)