home.social

Search

649 results for “coreforge”

  1. For those of you in #antiRacism work, here is a fact that may help you

    Via Senator #Padilla:

    “In fact, the USDA has several tools available which would enable #SNAP benefits to be paid through or close to the end of November.”

    #USpol #CareForEachOther

    padilla.senate.gov/newsroom/pr

  2. #NotNews24 | #UnbreaklingAfterDinnerDoughnutNotNews... #NotNearly24... #FrequentlyFewer... #OftenLess...

    This should really come as #NoSuprise to #Anyone; but, this: 🔼​⬆️​🆙​⬆️​🔼​ is not #TheMostEvilThing I've #DoneToday...

    #IF you #Imagine I'm in "need" of a #SelfAppointedNetNanny to #Moderate #MyContent for me; #ThinkAgain... And, #DoubleCheck your #FalseEquivalence before you #ComeForMe...

    🧙⚔️🤖🐺🤖⚔️🧙 | :fediverse:​​🎠🦹🦄🦹🎠:fediverse:​

    vmst.io/@PSiReN/10985135747740

  3. Топ-7 платформ для проведения IT-соревнований

    Говорят, что спортивное программирование — совсем другая область, которая сильно отличается от рабочих задач. Пусть так. Но опыт показывает, что умный и талантливый человек проявит себя в обеих сферах. Если он стал чемпионом по спортивному программированию, в ML-соревновании или CTF — то и спрос на такой талант больше обычного. А сколько отличных проектов создано на хакатонах! Вспомнить хотя бы приложение MSQRD , которое написали на хакатоне за 48 часов, а потом продали Фейсбуку за десятки миллионов долларов. Здесь мы собрали семь лучших платформ для проведения IT-соревнований. Для участников это состязательные платформы, а организаторам они помогут автоматизировать рутину и сконцентрироваться только на качестве мероприятия. Из обзора вы узнаете: Где самое активное ML-комьюнити в России. Какая платформа предлагает самый большой функционал для проведения соревнований. Чем отличаются различные платформы для соревнований по спортивному программированию. Как провести любое IT-мероприятие на одной платформе. Что делать, если нужно локальное решение для IT-соревнования.

    habr.com/ru/articles/895538/

    #хакатоны #спортивное_программирование #Codenrock #MLсоревнования #CTF #Ejudge #PhystechGenesis #All_Cups #ЯндексКонтест #ODSai #Open_Data_Science #Codeforces

  4. A 3-year-old kid came up to me while I was coding for today’s #codeforces round, and asked me about the iPad. I showed him #cmatrix in iSH and he thought I was hacking 🤣

  5. A 3-year-old kid came up to me while I was coding for today’s #codeforces round, and asked me about the iPad. I showed him #cmatrix in iSH and he thought I was hacking 🤣

  6. A 3-year-old kid came up to me while I was coding for today’s #codeforces round, and asked me about the iPad. I showed him #cmatrix in iSH and he thought I was hacking 🤣

  7. I/Pu reveals #Earth mainly accreted from volatile-poor differentiated #planetesimals: science.org/doi/10.1126/sciadv ("we show that #CoreFormation alone is unlikely to explain the iodine/plutonium difference between mantle reservoirs") -> Earth Formed from Dry, Rocky Building Blocks: caltech.edu/about/news/earth-f

  8. 🚀 Coforge’s new Quasar accelerators, AgentSphere and Trust AI, bring LLM routing, Model Garden and Retrieval‑Augmented Generation to enterprises. Discover how these open‑source‑friendly tools boost generative AI workflows and secure AI trust. Dive into the details! #Coforge #Quasar #AgentSphere #TrustAI

    🔗 aidailypost.com/news/coforge-l

  9. So with the release of #midnight there has been a lot of upheavel in the #wow addon community, which has caused me to have to look at new UI addons, and I am struck by just how crazy the whole ecosystems licensing situation seems to be.

    There are a lot of opensource addons, but there are also a lot where the authors want to retain control so they explicitly write an empty license which reserves all rights for themselves. When I ask authors to change the license to actually allowing copying the addon for installation I invariably get some sort of response of the form "The license is only for modifying my addon's source, not using it." IANAL, but to me that falls flat because:

    1. Absent an explicit grant there is no implicit right to use it anyway
    2. There may be an implicit license created because the author uploaded it to something like curseforge, but that is both somewhat vague for the users, and leaves the authors exposed since they have not disclaimed any implied warranty granted by their implied license.
    3. For addons there is no object code/artifact that can bear a different license than the source code.

    When I had to deal license issues in the past lawyers have told me is that if there is an ambiguity in the license and you have a written statement from the copyright holder about their intention a court will generally use their written statements to interpret the license. So the action of me asking for the change and them telling me they don't think they need to change their license because it grants me the rights may resolve the issue for me, but I find that unsatisfying.

    In some ways it is not a big deal, either just ignore it like everyone else, or don't use the addons. But I can't help but feel a lot of this is people who have never written software vibe coding licenses for their vibe coded addons, which makes me actually worry a lot about what this looks like for more consequential opensource projects.

  10. So with the release of #midnight there has been a lot of upheavel in the #wow addon community, which has caused me to have to look at new UI addons, and I am struck by just how crazy the whole ecosystems licensing situation seems to be.

    There are a lot of opensource addons, but there are also a lot where the authors want to retain control so they explicitly write an empty license which reserves all rights for themselves. When I ask authors to change the license to actually allowing copying the addon for installation I invariably get some sort of response of the form "The license is only for modifying my addon's source, not using it." IANAL, but to me that falls flat because:

    1. Absent an explicit grant there is no implicit right to use it anyway
    2. There may be an implicit license created because the author uploaded it to something like curseforge, but that is both somewhat vague for the users, and leaves the authors exposed since they have not disclaimed any implied warranty granted by their implied license.
    3. For addons there is no object code/artifact that can bear a different license than the source code.

    When I had to deal license issues in the past lawyers have told me is that if there is an ambiguity in the license and you have a written statement from the copyright holder about their intention a court will generally use their written statements to interpret the license. So the action of me asking for the change and them telling me they don't think they need to change their license because it grants me the rights may resolve the issue for me, but I find that unsatisfying.

    In some ways it is not a big deal, either just ignore it like everyone else, or don't use the addons. But I can't help but feel a lot of this is people who have never written software vibe coding licenses for their vibe coded addons, which makes me actually worry a lot about what this looks like for more consequential opensource projects.

  11. So with the release of there has been a lot of upheavel in the addon community, which has caused me to have to look at new UI addons, and I am struck by just how crazy the whole ecosystems licensing situation seems to be.

    There are a lot of opensource addons, but there are also a lot where the authors want to retain control so they explicitly write an empty license which reserves all rights for themselves. When I ask authors to change the license to actually allowing copying the addon for installation I invariably get some sort of response of the form "The license is only for modifying my addon's source, not using it." IANAL, but to me that falls flat because:

    1. Absent an explicit grant there is no implicit right to use it anyway
    2. There may be an implicit license created because the author uploaded it to something like curseforge, but that is both somewhat vague for the users, and leaves the authors exposed since they have not disclaimed any implied warranty granted by their implied license.
    3. For addons there is no object code/artifact that can bear a different license than the source code.

    When I had to deal license issues in the past lawyers have told me is that if there is an ambiguity in the license and you have a written statement from the copyright holder about their intention a court will generally use their written statements to interpret the license. So the action of me asking for the change and them telling me they don't think they need to change their license because it grants me the rights may resolve the issue for me, but I find that unsatisfying.

    In some ways it is not a big deal, either just ignore it like everyone else, or don't use the addons. But I can't help but feel a lot of this is people who have never written software vibe coding licenses for their vibe coded addons, which makes me actually worry a lot about what this looks like for more consequential opensource projects.

  12. So with the release of #midnight there has been a lot of upheavel in the #wow addon community, which has caused me to have to look at new UI addons, and I am struck by just how crazy the whole ecosystems licensing situation seems to be.

    There are a lot of opensource addons, but there are also a lot where the authors want to retain control so they explicitly write an empty license which reserves all rights for themselves. When I ask authors to change the license to actually allowing copying the addon for installation I invariably get some sort of response of the form "The license is only for modifying my addon's source, not using it." IANAL, but to me that falls flat because:

    1. Absent an explicit grant there is no implicit right to use it anyway
    2. There may be an implicit license created because the author uploaded it to something like curseforge, but that is both somewhat vague for the users, and leaves the authors exposed since they have not disclaimed any implied warranty granted by their implied license.
    3. For addons there is no object code/artifact that can bear a different license than the source code.

    When I had to deal license issues in the past lawyers have told me is that if there is an ambiguity in the license and you have a written statement from the copyright holder about their intention a court will generally use their written statements to interpret the license. So the action of me asking for the change and them telling me they don't think they need to change their license because it grants me the rights may resolve the issue for me, but I find that unsatisfying.

    In some ways it is not a big deal, either just ignore it like everyone else, or don't use the addons. But I can't help but feel a lot of this is people who have never written software vibe coding licenses for their vibe coded addons, which makes me actually worry a lot about what this looks like for more consequential opensource projects.

  13. So with the release of #midnight there has been a lot of upheavel in the #wow addon community, which has caused me to have to look at new UI addons, and I am struck by just how crazy the whole ecosystems licensing situation seems to be.

    There are a lot of opensource addons, but there are also a lot where the authors want to retain control so they explicitly write an empty license which reserves all rights for themselves. When I ask authors to change the license to actually allowing copying the addon for installation I invariably get some sort of response of the form "The license is only for modifying my addon's source, not using it." IANAL, but to me that falls flat because:

    1. Absent an explicit grant there is no implicit right to use it anyway
    2. There may be an implicit license created because the author uploaded it to something like curseforge, but that is both somewhat vague for the users, and leaves the authors exposed since they have not disclaimed any implied warranty granted by their implied license.
    3. For addons there is no object code/artifact that can bear a different license than the source code.

    When I had to deal license issues in the past lawyers have told me is that if there is an ambiguity in the license and you have a written statement from the copyright holder about their intention a court will generally use their written statements to interpret the license. So the action of me asking for the change and them telling me they don't think they need to change their license because it grants me the rights may resolve the issue for me, but I find that unsatisfying.

    In some ways it is not a big deal, either just ignore it like everyone else, or don't use the addons. But I can't help but feel a lot of this is people who have never written software vibe coding licenses for their vibe coded addons, which makes me actually worry a lot about what this looks like for more consequential opensource projects.

  14. @wall0159 @WBOrcutt @breadandcircuses

    We have quite enough knowledge to get started and adapt, so let's get on it right away. To anyone reading who lacks the knowledge or courage to step up, please do. We'll be there to listen to your ideas, boost your confidence and move forward. We'll make it fun and beautiful. Modesty need not be austere. Rather, we focus on function!

    #SocialLearning #LifestyleChange #SustainableLifestyle #SustainableCommunities #MutualAid #CareForEarth #permaculture