I have a feeling that the FLOSS movement in spirit was constructed in the previous centralised computing paradigm with timesharing systems, and in some sense is left there. I wonder what its corresponding movement of our time would be, now that the pendulum has swung back from the desktop computing paradigm and into dumb terminals over a document format?
@alcinnz I think so, but not just that. If they used copyright law and GPL, I think we need to do similar forays into other fields, but I'm still quite fuzzy on the details of what that means.
@lupine For me the code is a means, not an end. The most interesting parts of the free software movement to me were always the slightly utopian visions (and I think they are very clearly widely different) about the societies around and through the code. I can imagine both communal centralised computing and individualised libertarian computing springing from the same roots, just to name two.
Do you have a good source on copy far left?
@Shamar @lupine I'd much prefer no hosting at all. Of course, I agree with your sentiment, and I used to agree with your literal statement about all users becoming hackers as well. I also used to host my own email, domains, web servers, and IRC servers. That was many years ago. Now I use Gmail, Facebook et al for mostly everything, and have almost completely dropped out of the GNU/Linux ecosystem in favour of Apple's software, because it suits my needs better, even if I don't like it.
@lupine @Shamar However, if it's specifically control and accountability you are after, couldn't that be solved through less heavy means than turning everyone into hackers? Also, I think it's worth thinking about how this translates to other fields. According to the same logic, do I also need to be able to produce my own food, or do biotech or medicine? Or is there something specific to software, and if so why?
@lupine @Shamar I'd say what's stopping them is either the produced useful things (systems, experiences, communities, etc) not being possible to squeeze into the commodity form (i.e. not being possible to sell or otherwise make profits from), or them being legally restricted from doing so. If we view code / society / law as three sides of the same coin, this makes sense; code and law both program society, and vice versa.
Dont think we need/want/could have an individualized solution where everyone does it all by themselves
I'm inspired by Community Supported Agriculture, which has quite a variety of models, what I find really exciting are those where the people getting the food are involved, at the level *they choose*, in the resourcing, governance, admin &/or growing
The Solidarity Agriculure movement in Germany is interesting
See linked github issue there
@dazinism That would be roughly the shape of my preferred counter-argument to the "hacking for the masses" as well, but thanks for the link, I have never heard of that before!
@lupine Ah, Kleiner; I should have suspected. I'm slightly familiar with his work, if not this one. Thank you for the link!
@lupine OK; I have done my homework now. What Kleiner seems to be after is roughly the same thing as the Commons Clause people are trying to fix in some sense, that is the appropriation of labour from FLOSS by companies. It's an interesting side-effect that both of these proposals are violating some of the software freedoms specifically because they are formulated without any distinction of power, etc. (1/2)
@lupine I think this is to be expected? Anything reasonably different from the GLP (in terms of scope or intention) can be assumed to end up with incompatible rules in some sense. A more important question, I think, is if copyright law is even the best place to fight this battle. There ARE other options; blockades (DDoS?), campains, strikes, etc. It seems a bit...cargo-cultish to me to try a license just because it "worked before". (2/2)
@lupine I kind of like the form vs content argument inside of that, but I think the answer is "yes, but it wouldn't work the same if it was user-developed, depending on which user's needs developed it"
@lupine It would be interesting to investigate the source of that controversy. Is it: a) actual differing interests and/or perspectives and/or lived experiences, or is it a matter of semantics or cargo-culting FLOSS licenses?
@albin I'll look up some articals for you, but the idea is that if you can do your core job without uploading a piece of data to some central servers you are forbidden from doing so. And you can't say "but we can offer more conveniences by collecting this data".
But definitely these links:
@albin From Stallman's artical:
"There are so many ways to use data to hurt people that the only safe database is the one that was never collected. Thus, instead of the EU’s approach of mainly regulating how personal data may be used (in its General Data Protection Regulation or GDPR), I propose a law to stop systems from collecting personal data."
"Taking into account the state of the art, the cost of implementation and the nature, scope, context and purposes of processing as well as the risks of varying likelihood and severity for rights and freedoms of natural persons posed by the processing, the controller shall, both at the time of the determination of the means for processing and at the time of the processing itself, implement appropriate technical and organisational measures.
(cont'd) such as pseudonymisation, which are designed to implement data-protection principles, such as data minimisation, in an effective manner and to integrate the necessary safeguards into the processing in order to meet the requirements of this Regulation and protect the rights of data subjects."
@jack Yes, exciting indeed. Though I'd prefer to have a few plans B etc lying around in case it doesn't pan out.
@bjoern I agree with your general sentiment, but not all of your historicising. In particular, you write that Stallman could have stayed away from modern computing. I would argue that he and most of the FLOSS movement indeed did so: we are talking about a man who emails web pages to himself via Emacs, and I have myself been the sort of person who runs a hacked-up Unix made from compiled components with a tiling window manager. That's even remotely how non-hackers compute, even developers.
@bjoern More importantly though, I think you are missing an important aspect of the freedom to study and modify (but I agree with everything you have!). In particular, I think WASM or minified (or just plain bad/obfuscated) JS, while being free is about as useful as binary code. And to add insult to injury, it's very hard to verify that the code you are inspecting is the actual code running under the hood.
@bjoern So in order for any user to be able to exercise their freedoms to study or modify the code (compare with everyone's right to fly of their own muscle power or breathe under water), I think further regulation of some sort is needed -- though not necessarily through licenses. Also, this may not even be possible through the Web as it exists today.
The technical norms in FOSS are unix-centric & so amenable to client/server type centralization (because of decisions made about the nature of the GNU project -- namely, the decision for the flagship free software project to be yet another unix vendor), but I don't think the legal stuff fits into that so much.
Gotta remember that the GPL was intended to counter a failure mode of informal software sharing in the lisp machine community.
Scholar Social is a microblogging platform for researchers, grad students, librarians, archivists, undergrads, academically inclined high schoolers, educators of all levels, journal editors, research assistants, professors, administrators—anyone involved in academia who is willing to engage with others respectfully.