07.13.19
Gemini version available ♊︎Consultation About Direction and Future Focus for Techrights
Summary: We invite ideas and recommendations for the future of the site, notably which topics and aspects are worth covering as a matter of higher priority
ABOUT EIGHT years ago we asked on at least a couple of occasions what to do next. We asked readers. Why? Because collective thinking and brainstorms are more likely to reach good conclusions. Readers had seen Novell’s collapse and recognised the lingering threat of software patents, including Microsoft infiltration at Nokia (with a warchest of patents), just shortly after the CPTN debacle. Back then, around 2011, things were very different. That was 3 years before SCOTUS deciding on Alice and way, way before 35 U.S.C. § 101 had any real ‘teeth’. Microsoft’s patent war on Android was still in its diapers and it continues to this date (with a new lawsuit earlier this year).
“Software patents have become a bit less of a problem.”Microsoft is still a problem. Software patents have become a bit less of a problem. In our daily links we’ll soon shelve some more news about the USPTO, the latest from Coons, and 35 U.S.C. § 101. The short story is, software patents continue to perish (in courts at least), Andrei Iancu accelerates granting of more such fake patents, and law firms-bribed politicians try to change the law for the third year in a row (we don’t expect anything to come out of it, never mind those fake debates).
On “TM and TR direction” (Tux Machines and Techrights), one reader made some suggestions to us a few hours ago. “Few sites cover software freedom in general,” he explained, “despite (or maybe because of) it being so important. Thus TR should include work towards eliminating even the ghost of software patents because they stand in the way of Software Freedom, and you have good contacts within EPO and the good staff rely on TR coverage because it is the only site doing so. That and, first and foremost, to be really clear, TR should continue advancing Software Freedom in all its forms. IMO.”
“The short story is, software patents continue to perish (in courts at least)…”“More about TR,” he continued, “if you make several inventories and then look at the intersections, the overlap should give strong suggestions about what to pursue. Probably a pen and paper approach would be most thorough.”
“Of each of your connections on social control media, IRC, e-mail, and any forums, what is the main interest for each?
“Then separately, what are you yourself best at and what are you eager to write about?
“Which articles have gotten the most positive responses and why? Which direction do they point?
“Which articles have gotten the most negative responses and why? Of the negative responses, sort away the ones based on dogma or ideology and see what’s left and if those can be addressed.
“What should be covered as a matter of priority and what strategy should be adopted?”“As for random ideas, would a one- or two-month partnership or collaboration with the FSF or OSI be of benefit to both parties? If there is something that you would like to write about or focus on for a time that overlaps with their goals then it might be something to consider.
“Though I’d say the web layouts for both need adjustment so that the columns reflow. Though that’s really superficial considering the amount of effort required. Maybe a cheap, used smartphone with no SIM and just wireless would help there. The main page for TR is way to “busy” and hard to visit or find things.”
Back in April a reader sent us some suggestions, having grown a bit sour/disappointed with the FSF because of inaction on important issues (we also took note of that [1, 2, 3] and had done so for years). Judging by some comments in Diaspora [1, 2], the FSF just isn’t sufficiently concerned about Microsoft anymore.
What do other readers think? What should be covered as a matter of priority and what strategy should be adopted? Suggestions can be sent to bytesmedia@bytesmedia.co.uk which is an impersonal address several of us read. █
ᶃ Gemini Space
This post is also available in 
Content is available under CC-BY-SA