Nik
Principled Software Engineer, Gentleman Programmer.
Current #Pachli steward (see link or follow @pachli@mastodon.social)
2:252/21.8
I wonder if the rise in fascination with and unquestioning acceptance of LLM output is caused by COVID induced brain damage, or if it's only correlated with it.
Something prophetic about beginning the day by pressing a button labelled "Start grind".
`` Now all the models have been trained on open source code GitHub's raising the Copilot costs to price open source developers out of using the models as a way of preventing model collapse. ``
@jonny@neuromatch.social @f4grx@chaos.social @OmegaPolice@hachyderm.io @srtcd424@mas.to @be@floss.social
so if you have any more competent hardware than that then self hosting a runner is a win
Only if you assume that my time to set up and continually maintain a piece of internet connected infrastructure is free.
The hardware cost is the least interesting part of the expenses saved by using GH runners.
@gvs @frameworkcomputer @Dynamodreher Absolutely not.
Choosing to use Framework (given that they're more expensive than competing brands) is a political choice, based on their previous values.
Continuing to use them, now that you know they're happy to fund groups that would happily see e.g. other software maintainers deported, interred, or worse, is also a political choice.
If you haven't already, go read up on the paradox of tolerance.
@Dynamodreher @frameworkcomputer they've been explicit that it's a deliberate choice:
https://community.frame.work/t/framework-supporting-far-right-racists/75986/2
we want to be transparent that bringing in and enabling every organization and community that we can across the Linux ecosystem is a deliberate choice.
Look, I might as well just change the BIO text field to:
This is the correct approach, as different clients may display your profile/bio info however they see fit, and in different contexts (viewing your account standalone, viewing your account in a list of accounts, ...). Some clients show pronouns, some don't.
Some users might even elect not to show emojis, or images, or disable animation.
If you want full control over the presentation then linking to a PDF is probably best.
@GuillaumeRossolini@infosec.exchange @timbray@cosocial.ca https://curl.se/dev/vuln-disclosure.html
There is no bug bounty and the curl project never offers rewards for reported vulnerabilities.
More in https://daniel.haxx.se/blog/2026/01/26/the-end-of-the-curl-bug-bounty/
@mwichary@mastodon.online In the photo example, of the two scenarios:
- The user wants to perform a full rotation
- The user accidentally double-taps the "rotate 90" button
the second scenario seems much more likely. The user might have dexterity problems that make double taps more likely, or they might have a situational disability that makes double taps more likely (e.g., passenger in a car over a rough surface).
@haubles@hachyderm.io Did anything that can be shared publicly come out of this, that might be useful for other organisations?
E.g., planned policy changes, or changes to training or onboarding practices?
@OmegaPolice@hachyderm.io @bms48@mastodon.social @jonny@neuromatch.social @f4grx@chaos.social @srtcd424@mas.to @be@floss.social
Basically, literally, a remote Git ref plus a discussion.
No, there's a lot more than that.
For example, lists of assignees, reviewers, the review state, a record of output/decisions from tasks run on the PR (e.g., CI steps, CLA bots).
PRs can have their own description, distinct from any commit messages. State like draft, ready to review, closed, approved, merged, abandoned. References to open issues, projects, etc.
@jonny@neuromatch.social @OmegaPolice@hachyderm.io @bms48@mastodon.social @f4grx@chaos.social @srtcd424@mas.to @be@floss.social
- Yes, no
- https://en.wikipedia.org/wiki/Brooks%27s_law
- Demanding that other people do unpaid work on your behalf is deeply, deeply rude.
RAYE - WHERE IS MY HUSBAND! (Official Music Video)
@OmegaPolice@hachyderm.io @bms48@mastodon.social @jonny@neuromatch.social @f4grx@chaos.social @srtcd424@mas.to @be@floss.social
Cross-repo links are ... just links
I don't think that's the case either. Linking to PRs and issues in project Y from project X:
- in the project X view shows you things like "Is this issue closed?"
- in the project Y view shows you "which other projects have referenced this issue in their own issue?", so you get useful cross-repo communication.
> Now, we search for web sites (or don't even search for web sites, yay abstraction layers that separate us from actual raw information) using "natural language" to try and coax out info.
If you think wanting natural language search is a recent desire, or invention, or a tool of the neurotypical, you are woefully misinformed.
E.g., https://www.mcgovern.org/the-legacy-of-patrick-j-mcgovern/from-the-pages-of-tech-history/april-4-1973-geologists-use-natural-language-system-to-study-moon-samples/ from the early '70s.
Or https://github.com/JanWielemaker/chat80 in the early '80s.
More history in https://www.e3s-conferences.org/articles/e3sconf/pdf/2021/05/e3sconf_iccsre2021_01039.pdf.
@OmegaPolice@hachyderm.io @bms48@mastodon.social @jonny@neuromatch.social @f4grx@chaos.social @srtcd424@mas.to @be@floss.social
GitHub is not Twitter. Every repo has a clear owner account/org; I need to go to their instance to access and engage.
That is explicitly not the plan. See https://unnamed.website/posts/forge-federation-myths/ and (linked to from https://forgejo.org/2023-01-10-answering-forgejo-federation-questions/ which is the closest thing to a vision for this that I could find, even if it is several years old).


