@stigatle@yarn.stigatle.no I’ll take a copy of the conversations over the last few days in the #twtxt ITC channel and link here 👌

@stigatle@yarn.stigatle.no Just test against my pod 👌

@marado@twtxt.net I agree 💯

Given the continued hostility of jam6 and buckket over Yarn’a use of Twtxt (even after several years! 😱) I am continuing to face hard decisions.

I am not sure what to do about this. 🤔 I am quite confident that the hostility and sentiment is not held by all Twtxt users past and present 😢

This is a case of a few upset purists who prefer to mock, shame and behave passive aggressively instead of contributing to a healthy discussion and ecosystem.

I am uncertain what Yarn should do here 😢

Also character handling for password might be problematic ☝️ The code needs to handle and allow anything and everything, as yarnd doesn’t shit a shit what you type for your password 😅

Can you try https://twtxt.net – I’m also worried that if you have “Skip SSL verification” in your code (from reading @lyse@lyse.isobeef.org’s comments) that things will fail on my pod as I’m pretty sure Cloudflare will chuck a hissy fit at you 🤣

It is only until after that company has a breach, with harm caused to its end-users does the company do anything about it. I’m not really convinced that’s happening either, because the current laws scream and cry out “OMG! 😱 We need to fix the Open Source supply chain!” by companies that refuse to take any financial liability for freely using other people’s hard work that they didn’t get paid for.

Companies that use open source component freely without paying for them or contributing back should absolutely be held liable when things go wrong, NOT the open source developers. Why? Because those companies are often exploiting their end-users and often making them pay for something that is largely otherwise free (-some conveniences added on top).

One of the biggest problems I have with the currently proposed EU laws is that there is no distinction being made between “Free, non-Paid, Open Source” vs. “Commercial Software Products built from Open Source”.

I find the current situation highlights the fact that large corporations build Paid-for products and services to consumers and makes Millions or Billions of $ £ € often without as much as either a) contributing back to open source or the projects from which they borrow and depend on b) or pay for what they use or support it in any financial way.

A large part of the Open Source Model in my view is often confused with “FREE” as in $0, but this is total bullshit. Companies need to understand that reusing a piece of open source software, library or component does not imply it is FREE to you. Companies today DO NOT vet, understand, review or even remotely contribute (in many cases) bug fixes, security fixes, etc, of the component they freely take and use and profit from.

@stigatle@yarn.stigatle.no Have a look at the JavaScript for yarnd 👌

Also the car was never built and published freely in the open for all to see and study. There was and are large profitable companies behind these dangerous things.

Fair point (although extreme example to show it 😆)

Key point here: a line has to be drawn.

Right now the EU proposed laws don’t distinguish between dangerous software and non-dangerous nor free lowly lone non-paid developer vs. commercial company that profits from open source and has no liability despite making millions or billions.

I can see companies taking out liability insurance for their software teams that contribute to open source, but a lowly non-paid developer that writes some open source library or software on his own?

Yes this is true and I thought of this too in my analogy.

The question is to what extent should lowly free time non-paid open source developers be liable vs. say large corporations that commercially benefit and profit from open source and don’t contribute a dime back?

Exaxrly!

@stigatle@yarn.stigatle.no Haven’t you got media uploads working yet? 🤔

@stigatle@yarn.stigatle.no Nice! 👌 Especially on the dog fooding l 🤗

@stigatle@yarn.stigatle.no Fine by me 😆

@stigatle@yarn.stigatle.no It’s early evening over here and we went the day at a water park which was nice 👌

Reading: https://www2.deloitte.com/us/en/blog/deloitte-on-cloud-blog/2023/devops-SRE-capability-model-for-these-complementary-roles.html

I rally find this rhetoric quite counter productive 😢

Finally, like the Eclipse suggests, if the new proposed EU laws would go ahead, I too as an open source developer would also have to either a) Put up a notice stating that none of my software, libraires, tools can be used within the EU or b) Simply go closed source. – This would be extremely sad 😢 and honestly at that point I would question even continuing to be a software developer at all.

The problem and difference though is that open source is produced, published and free at no cost to the consumer. I also find the situation a bit weird from a legal standpoint as I don’t understand how the CRA and CLA can possibly override open source licenses that are also legal documents and a contract between the open source author(s) and consumers of that open source software/library/whatever.

@marado@twtxt.net I see. Thanks, read that article and it makes the problem a bit clear, especially on the liability issue. So, it seems EU lawmakers are trying to fix an economical problem by introducing a new set of laws that regulate a large part of the software industry (open source) that has effectively zero revenue?! This seems to be a bit counter intuitive to me, how are open source developers able to deal with liability for something they produce and publish for free?

What seems to be at play here is the capability of open source that has enabled great software reuse by large commercial ventures is under threat by lawmakers that don’t seem to fully grasp the landscape of open source.

The liability of software and products should be with the builders of that product. This is a bit of a tricky situation, because if you’re building a skyscraper a it falls down because of faulty concrete pylon footings, who’s at fault, who is liable? You or the company that poured the pylons?

Heading out to a water park today 😆 Last chance for the girls to have some fun before school starts back up next week 😉

@marado@twtxt.net Do you mind highlighting what the CRA and CLA are proposing that puts open source and individual open source authors at risk?

@stigatle@yarn.stigatle.no Yay weekend! 🥳

@abucci@anthony.buc.ci That’s the thing about common sense.

Ita not very common nowadays 😆

@abucci@anthony.buc.ci Wow! 😳

Do one for micro services next! 🤣

I honestly think you’ll end up reinventing the same ideas 😆

@abucci@anthony.buc.ci Hahaha this is the second report of this happening🤣🤦‍♂️

@xuu@txt.sour.is Bahahahahaha 🤣 Soo goood! 😅

@hacker-news-newest@feeds.twtxt.net This is insanely cool 🤣

@abucci@anthony.buc.ci Ahh yeah, you’re right. I have one of those X-something page long CV(s) somewhere, but I’ve given up trying to maintain it 😅

@adi@twtxt.net Why not write a new CLI? Git nowadays is just an underlying storage format and library. Consider using jesseduffield/lazygit: simple terminal UI for git commands for example.

@movq@www.uninformativ.de Oh good lordie lord 🤦‍♂️

@movq@www.uninformativ.de Hmmm

Better Nate than lever!

Is that the punchline?! 🤔

@movq@www.uninformativ.de Damnit! Please tell me what was it 🤣

@darch@twtxt.net This is true!

What about the Pocket C.H.I.P?

@movq@www.uninformativ.de I honestly tried to read this last night, but it was sooo long, got bored in the end, scrolled to the bottom and didn’t get the punchline. 😱🤦‍♂️

They are the same thing. Weird 😆 Where is your CS/Reaume? Maybe I can take a look at it and give you some feedback?

@adi@twtxt.net What’s wrong with Git?

@shreyan@twtxt.net Care to elaborate on what you mean by Twtxt is like UNIX ? 😆

@abucci@anthony.buc.ci Interesting 🤔😆

@stigatle@yarn.stigatle.no cool! 👌

@lyse@lyse.isobeef.org This is very cool indeed 👌

@jmjl@tilde.green It’s okay because Twtxt is a pull based model so all good 🤔

Didn’t know that speedtest.net has a CLI 😅

$ speedtest

   Speedtest by Ookla

[error] Error: [8] nodename nor servname provided, or not known
      Server: Foxtel Broadband - Brisbane (id: 8847)
         ISP: Aussie Broadband
Idle Latency:     9.46 ms   (jitter: 0.20ms, low: 9.25ms, high: 9.76ms)
    Download:    93.39 Mbps (data used: 50.5 MB)
                 22.67 ms   (jitter: 4.76ms, low: 10.01ms, high: 135.16ms)
      Upload:    35.10 Mbps (data used: 58.7 MB)
                880.05 ms   (jitter: 95.73ms, low: 16.75ms, high: 1823.19ms)
 Packet Loss:     0.0%

@jmjl@tilde.green Sorry, what are you being sorry about? 😅 🤔