home.social

#github — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #github, aggregated by home.social.

  1. 📡 Detected by our signals today: inkloom

    ⭐ 446 stars · only 11 days old · +380 this week · accelerating
    « Specialised AI models for logo design — a brand-analysis model turns a business into constraints, typography a… »

    The 100 open-source AI projects about to matter — before they're famous:
    olud.ai/emerging.html

    #OpenSource #AI #GitHub

  2. 📡 Detected by our signals today: inkloom

    ⭐ 446 stars · only 11 days old · +380 this week · accelerating
    « Specialised AI models for logo design — a brand-analysis model turns a business into constraints, typography a… »

    The 100 open-source AI projects about to matter — before they're famous:
    olud.ai/emerging.html

    #OpenSource #AI #GitHub

  3. 📡 Detected by our signals today: inkloom

    ⭐ 446 stars · only 11 days old · +380 this week · accelerating
    « Specialised AI models for logo design — a brand-analysis model turns a business into constraints, typography a… »

    The 100 open-source AI projects about to matter — before they're famous:
    olud.ai/emerging.html

    #OpenSource #AI #GitHub

  4. 📡 Detected by our signals today: inkloom

    ⭐ 446 stars · only 11 days old · +380 this week · accelerating
    « Specialised AI models for logo design — a brand-analysis model turns a business into constraints, typography a… »

    The 100 open-source AI projects about to matter — before they're famous:
    olud.ai/emerging.html

    #OpenSource #AI #GitHub

  5. OpenDLSS: A Vulkan Reimplementation of Nvidia's DLSS 5 Neural Rendering Network

    github.com/maanHimself/OpenDLS

    #github #nvidia

  6. OpenDLSS: A Vulkan Reimplementation of Nvidia's DLSS 5 Neural Rendering Network

    github.com/maanHimself/OpenDLS

    #github #nvidia

  7. 📈 Also gaining ground:

    ⭐ tt-a1i/archify +1,968 stars (total 74.2k)
    « Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self… »

    olud.ai/project/tt-a1i-archify

    #OpenSource #AI #GitHub

  8. 📈 Also gaining ground:

    ⭐ tt-a1i/archify +1,968 stars (total 74.2k)
    « Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self… »

    olud.ai/project/tt-a1i-archify

    #OpenSource #AI #GitHub

  9. 📈 Also gaining ground:

    ⭐ tt-a1i/archify +1,968 stars (total 74.2k)
    « Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self… »

    olud.ai/project/tt-a1i-archify

    #OpenSource #AI #GitHub

  10. 📈 Also gaining ground:

    ⭐ tt-a1i/archify +1,968 stars (total 74.2k)
    « Agent skill for beautiful, verifiable architecture, workflow, sequence, data-flow, and lifecycle diagrams—self… »

    olud.ai/project/tt-a1i-archify

    #OpenSource #AI #GitHub

  11. 👀 On our radar today — a fresh open-source AI project:

    feder-cr/dots — 1.9k★ · Python
    « Open-source dots for the web: an AI agent with its own browser, one that does not get blocked. »

    Discovered in today's radar:
    olud.ai/latest.html

    #OpenSource #AI #GitHub

  12. 🎉 Breaking news: EDG's #C++ front-end is finally going #open source! Because, you know, the world was desperately missing yet another #GitHub repo to ignore. 🙈 After 30 years, we're getting the same old engine with a shiny new license, proving once and for all that continuity is just as exciting as watching paint dry. 🥳
    edgcpp.org/#transition #EDG #source #news #software #development #programming #HackerNews #ngated

  13. 🎉 Breaking news: EDG's #C++ front-end is finally going #open source! Because, you know, the world was desperately missing yet another #GitHub repo to ignore. 🙈 After 30 years, we're getting the same old engine with a shiny new license, proving once and for all that continuity is just as exciting as watching paint dry. 🥳
    edgcpp.org/#transition #EDG #source #news #software #development #programming #HackerNews #ngated

  14. 🎉 Breaking news: EDG's #C++ front-end is finally going #open source! Because, you know, the world was desperately missing yet another #GitHub repo to ignore. 🙈 After 30 years, we're getting the same old engine with a shiny new license, proving once and for all that continuity is just as exciting as watching paint dry. 🥳
    edgcpp.org/#transition #EDG #source #news #software #development #programming #HackerNews #ngated

  15. 🎉 Breaking news: EDG's #C++ front-end is finally going #open source! Because, you know, the world was desperately missing yet another #GitHub repo to ignore. 🙈 After 30 years, we're getting the same old engine with a shiny new license, proving once and for all that continuity is just as exciting as watching paint dry. 🥳
    edgcpp.org/#transition #EDG #source #news #software #development #programming #HackerNews #ngated

  16. 🎉 Breaking news: EDG's #C++ front-end is finally going #open source! Because, you know, the world was desperately missing yet another #GitHub repo to ignore. 🙈 After 30 years, we're getting the same old engine with a shiny new license, proving once and for all that continuity is just as exciting as watching paint dry. 🥳
    edgcpp.org/#transition #EDG #source #news #software #development #programming #HackerNews #ngated

  17. A ridiculous side effect of the AI coding era: people's agents keep posting and necrobumping issues with the exact same symptoms.

    The pattern is basically this: an agent encounters the problem, finds the issue, runs its own tests, and posts a tidy "data point" write-up without reading the 999 previous comments or the original issue, and without adding anything new. The maintainer does nothing, and people just keep piling onto this mess.

    For example, here you can see 18 long posts that boil down to "I send serverInfo.icons and it is ignored", and 13 of them just re-explain the fallback: github.com/anthropics/claude-a

    #AI #Coding #Git #GitHub

  18. A ridiculous side effect of the AI coding era: people's agents keep posting and necrobumping issues with the exact same symptoms.

    The pattern is basically this: an agent encounters the problem, finds the issue, runs its own tests, and posts a tidy "data point" write-up without reading the 999 previous comments or the original issue, and without adding anything new. The maintainer does nothing, and people just keep piling onto this mess.

    For example, here you can see 18 long posts that boil down to "I send serverInfo.icons and it is ignored", and 13 of them just re-explain the fallback: github.com/anthropics/claude-a

    #AI #Coding #Git #GitHub

  19. A ridiculous side effect of the AI coding era: people's agents keep posting and necrobumping issues with the exact same symptoms.

    The pattern is basically this: an agent encounters the problem, finds the issue, runs its own tests, and posts a tidy "data point" write-up without reading the 999 previous comments or the original issue, and without adding anything new. The maintainer does nothing, and people just keep piling onto this mess.

    For example, here you can see 18 long posts that boil down to "I send serverInfo.icons and it is ignored", and 13 of them just re-explain the fallback: github.com/anthropics/claude-a

    #AI #Coding #Git #GitHub

  20. A ridiculous side effect of the AI coding era: people's agents keep posting and necrobumping issues with the exact same symptoms.

    The pattern is basically this: an agent encounters the problem, finds the issue, runs its own tests, and posts a tidy "data point" write-up without reading the 999 previous comments or the original issue, and without adding anything new. The maintainer does nothing, and people just keep piling onto this mess.

    For example, here you can see 18 long posts that boil down to "I send serverInfo.icons and it is ignored", and 13 of them just re-explain the fallback: github.com/anthropics/claude-a

    #AI #Coding #Git #GitHub

  21. A ridiculous side effect of the AI coding era: people's agents keep posting and necrobumping issues with the exact same symptoms.

    The pattern is basically this: an agent encounters the problem, finds the issue, runs its own tests, and posts a tidy "data point" write-up without reading the 999 previous comments or the original issue, and without adding anything new. The maintainer does nothing, and people just keep piling onto this mess.

    For example, here you can see 18 long posts that boil down to "I send serverInfo.icons and it is ignored", and 13 of them just re-explain the fallback: github.com/anthropics/claude-a

    #AI #Coding #Git #GitHub

  22. Okay my local LLM helped me yesterday to vibecode something really handy. To be honest it did most of the heavy regex lifting etc. Now i would like to share that with the world.
    My only problem is: i could not put it on my Codeberg Account without violating the "No-Vibecoded-Stuff"- guidelines. I do not want to put in on Github either. So either i just share it on my blog, without the possibility to collaborate or i spin up my own forjego which i have to keep up-to-date etc.

    Or does anybody of you have another idea?

    #codehosting #forjego #codeberg #github #ai

  23. Okay my local LLM helped me yesterday to vibecode something really handy. To be honest it did most of the heavy regex lifting etc. Now i would like to share that with the world.
    My only problem is: i could not put it on my Codeberg Account without violating the "No-Vibecoded-Stuff"- guidelines. I do not want to put in on Github either. So either i just share it on my blog, without the possibility to collaborate or i spin up my own forjego which i have to keep up-to-date etc.

    Or does anybody of you have another idea?

    #codehosting #forjego #codeberg #github #ai

  24. Okay my local LLM helped me yesterday to vibecode something really handy. To be honest it did most of the heavy regex lifting etc. Now i would like to share that with the world.
    My only problem is: i could not put it on my Codeberg Account without violating the "No-Vibecoded-Stuff"- guidelines. I do not want to put in on Github either. So either i just share it on my blog, without the possibility to collaborate or i spin up my own forjego which i have to keep up-to-date etc.

    Or does anybody of you have another idea?

    #codehosting #forjego #codeberg #github #ai

  25. Okay my local LLM helped me yesterday to vibecode something really handy. To be honest it did most of the heavy regex lifting etc. Now i would like to share that with the world.
    My only problem is: i could not put it on my Codeberg Account without violating the "No-Vibecoded-Stuff"- guidelines. I do not want to put in on Github either. So either i just share it on my blog, without the possibility to collaborate or i spin up my own forjego which i have to keep up-to-date etc.

    Or does anybody of you have another idea?

    #codehosting #forjego #codeberg #github #ai

  26. Okay my local LLM helped me yesterday to vibecode something really handy. To be honest it did most of the heavy regex lifting etc. Now i would like to share that with the world.
    My only problem is: i could not put it on my Codeberg Account without violating the "No-Vibecoded-Stuff"- guidelines. I do not want to put in on Github either. So either i just share it on my blog, without the possibility to collaborate or i spin up my own forjego which i have to keep up-to-date etc.

    Or does anybody of you have another idea?

    #codehosting #forjego #codeberg #github #ai

  27. #AI coding agents asked for review screenshots leaked internal images in public #GitHub repos, researchers say.

    Researchers counted 13,000+ images at 300+ orgs, including customer billing records!
    #AISecurity
    👇 thehackernews.com/2026/09/ai-c

  28. #AI coding agents asked for review screenshots leaked internal images in public #GitHub repos, researchers say.

    Researchers counted 13,000+ images at 300+ orgs, including customer billing records!
    #AISecurity
    👇 thehackernews.com/2026/09/ai-c

  29. #AI coding agents asked for review screenshots leaked internal images in public #GitHub repos, researchers say.

    Researchers counted 13,000+ images at 300+ orgs, including customer billing records!
    #AISecurity
    👇 thehackernews.com/2026/09/ai-c

  30. #AI coding agents asked for review screenshots leaked internal images in public #GitHub repos, researchers say.

    Researchers counted 13,000+ images at 300+ orgs, including customer billing records!
    #AISecurity
    👇 thehackernews.com/2026/09/ai-c

  31. #AI coding agents asked for review screenshots leaked internal images in public #GitHub repos, researchers say.

    Researchers counted 13,000+ images at 300+ orgs, including customer billing records!
    #AISecurity
    👇 thehackernews.com/2026/09/ai-c