home.social

Search

1000 results for “dev_ric”

  1. Scopro ora che l'ottimo #bot mastodon.social/@altbot@fuzzie che serve per descrivere le immagini e dare un po' di accessibilità al #fediverso (oltre a indicizzarlo meglio per le ricerche PERSONALI) per le persone ipovedenti, *non* usa più il blob #gemini del big controller #bigG, ma invece usa => #Ovis2-8B, calcolato in locale e privatamente, e ti dice pure quanta energia viene usata con il calcolo

    Questa è l'#AI che mi piace 👍 😎

    github.com/micr0-dev/Altbot

  2. Scopro ora che l'ottimo #bot mastodon.social/@altbot@fuzzie che serve per descrivere le immagini e dare un po' di accessibilità al #fediverso (oltre a indicizzarlo meglio per le ricerche PERSONALI) per le persone ipovedenti, *non* usa più il blob #gemini del big controller #bigG, ma invece usa => #Ovis2-8B, calcolato in locale e privatamente, e ti dice pure quanta energia viene usata con il calcolo

    Questa è l'#AI che mi piace 👍 😎

    github.com/micr0-dev/Altbot

  3. Scopro ora che l'ottimo #bot mastodon.social/@altbot@fuzzie che serve per descrivere le immagini e dare un po' di accessibilità al #fediverso (oltre a indicizzarlo meglio per le ricerche PERSONALI) per le persone ipovedenti, *non* usa più il blob #gemini del big controller #bigG, ma invece usa => #Ovis2-8B, calcolato in locale e privatamente, e ti dice pure quanta energia viene usata con il calcolo

    Questa è l'#AI che mi piace 👍 😎

    github.com/micr0-dev/Altbot

  4. Scopro ora che l'ottimo #bot mastodon.social/@altbot@fuzzie che serve per descrivere le immagini e dare un po' di accessibilità al #fediverso (oltre a indicizzarlo meglio per le ricerche PERSONALI) per le persone ipovedenti, *non* usa più il blob #gemini del big controller #bigG, ma invece usa => #Ovis2-8B, calcolato in locale e privatamente, e ti dice pure quanta energia viene usata con il calcolo

    Questa è l'#AI che mi piace 👍 😎

    github.com/micr0-dev/Altbot

  5. Scopro ora che l'ottimo #bot mastodon.social/@altbot@fuzzie che serve per descrivere le immagini e dare un po' di accessibilità al #fediverso (oltre a indicizzarlo meglio per le ricerche PERSONALI) per le persone ipovedenti, *non* usa più il blob #gemini del big controller #bigG, ma invece usa => #Ovis2-8B, calcolato in locale e privatamente, e ti dice pure quanta energia viene usata con il calcolo

    Questa è l'#AI che mi piace 👍 😎

    github.com/micr0-dev/Altbot

  6. Nothing excites me more in gaming than deep, detailed, lovingly crafted world-building, and Compulsion Games' South of Midnight looks to be absolutely dripping with it. The kind of rich, lose-yourself narrative, the same feeling you get from a truly beloved novel or movie.

    It is increasingly clear that the dev team behind this game cares so, so much about getting it right. This is utterly fantastic.

    youtube.com/watch?v=b6NgLM-SS0

    #gaming #videogames #SouthofMidnight #compulsiongames #xbox

  7. Hay, for the short list of folks that follow me. I've been playing with a #terminal emulator called Wave (waveterm.dev) #waveterm. With a back end written in #Golang and #OpenSource it is fast and pretty easy to keep up with. It has been a huge time saver for me in terms of context switching. The interface is light weight and stays out of the way with great keyboard shortcut support. The widgets system that allows you to embed rich data right into your terminal is super handy and has really changed the way I have moved back to a more terminal based system, oh how I missed it.
    Works on #MacOS #Linux and even #Windows
    I recommend checking it out. Totally worth it.

  8. I made a cli tools by accident to track my #time and projects using #logseq as the source of records, combining it with contracts and #sqlite. It's a #cli tool made in #python using #typer and #rich to create nice tables. It's also ready for updates to new versions and migrate your db, if anyone wants to extend it and it's database. Any feedbacks super welcome, since coding just for your own is boring, no?
    gitlab.com/pony_m/logseq_timer

  9. Witchfire, FPS dark fantasy con elementi RPG, è ora su Steam dopo l'esclusiva su Epic Games Store. Gli sviluppatori The Astronauts sono entusiasti dell'accoglienza ricevuta, con vendite positive e oltre 1,1 milioni di wishlist. #Witchfire #videogiochi #gamingnews

    👉 absolutegamer.it/il-dev-di-wit

  10. I was having nice warm fuzzy feelings because even though #orogene itself is kind of on pause (for now), it’s actually spawned multiple widely-used projects:

    1. #miette was extracted from orogene, because it’s what I was building for rich errors/error codes/etc
    2. #kdl was created with the intention of being the configuration file for orogene, as well as an alternative syntax for package.json with more bells and whistles
    3. We had to write an NPM-compatible #semver package in Rust, because the semantics are actually different from Cargo’s semver implementation: crates.io/crates/node-semver
    4. The orogene resolver is published as a wasm NPM package, and is currently used by vscode.dev for doing in-browser, full fledged intellisense (because you need access to your dependencies to get their types, source definitions, etc). You can literally GoToDef and you don’t need a vm/desktop for it

    I think that’s it so far? And of course I’ve had the opportunity to share a lot of learning about performance that have been used by more recent package managers in other ecosystems!

  11. I was having nice warm fuzzy feelings because even though #orogene itself is kind of on pause (for now), it’s actually spawned multiple widely-used projects:

    1. #miette was extracted from orogene, because it’s what I was building for rich errors/error codes/etc
    2. #kdl was created with the intention of being the configuration file for orogene, as well as an alternative syntax for package.json with more bells and whistles
    3. We had to write an NPM-compatible #semver package in Rust, because the semantics are actually different from Cargo’s semver implementation: crates.io/crates/node-semver
    4. The orogene resolver is published as a wasm NPM package, and is currently used by vscode.dev for doing in-browser, full fledged intellisense (because you need access to your dependencies to get their types, source definitions, etc). You can literally GoToDef and you don’t need a vm/desktop for it

    I think that’s it so far? And of course I’ve had the opportunity to share a lot of learning about performance that have been used by more recent package managers in other ecosystems!

  12. I was having nice warm fuzzy feelings because even though #orogene itself is kind of on pause (for now), it’s actually spawned multiple widely-used projects:

    1. #miette was extracted from orogene, because it’s what I was building for rich errors/error codes/etc
    2. #kdl was created with the intention of being the configuration file for orogene, as well as an alternative syntax for package.json with more bells and whistles
    3. We had to write an NPM-compatible #semver package in Rust, because the semantics are actually different from Cargo’s semver implementation: crates.io/crates/node-semver
    4. The orogene resolver is published as a wasm NPM package, and is currently used by vscode.dev for doing in-browser, full fledged intellisense (because you need access to your dependencies to get their types, source definitions, etc). You can literally GoToDef and you don’t need a vm/desktop for it

    I think that’s it so far? And of course I’ve had the opportunity to share a lot of learning about performance that have been used by more recent package managers in other ecosystems!

  13. I was having nice warm fuzzy feelings because even though #orogene itself is kind of on pause (for now), it’s actually spawned multiple widely-used projects:

    1. #miette was extracted from orogene, because it’s what I was building for rich errors/error codes/etc
    2. #kdl was created with the intention of being the configuration file for orogene, as well as an alternative syntax for package.json with more bells and whistles
    3. We had to write an NPM-compatible #semver package in Rust, because the semantics are actually different from Cargo’s semver implementation: crates.io/crates/node-semver
    4. The orogene resolver is published as a wasm NPM package, and is currently used by vscode.dev for doing in-browser, full fledged intellisense (because you need access to your dependencies to get their types, source definitions, etc). You can literally GoToDef and you don’t need a vm/desktop for it

    I think that’s it so far? And of course I’ve had the opportunity to share a lot of learning about performance that have been used by more recent package managers in other ecosystems!

  14. I was having nice warm fuzzy feelings because even though #orogene itself is kind of on pause (for now), it’s actually spawned multiple widely-used projects:

    1. #miette was extracted from orogene, because it’s what I was building for rich errors/error codes/etc
    2. #kdl was created with the intention of being the configuration file for orogene, as well as an alternative syntax for package.json with more bells and whistles
    3. We had to write an NPM-compatible #semver package in Rust, because the semantics are actually different from Cargo’s semver implementation: crates.io/crates/node-semver
    4. The orogene resolver is published as a wasm NPM package, and is currently used by vscode.dev for doing in-browser, full fledged intellisense (because you need access to your dependencies to get their types, source definitions, etc). You can literally GoToDef and you don’t need a vm/desktop for it

    I think that’s it so far? And of course I’ve had the opportunity to share a lot of learning about performance that have been used by more recent package managers in other ecosystems!

  15. Hat jemand Erfahrung mit GPU Passthrough in Proxmox?
    Ich versuche es seit Stunden und komme nicht weiter.
    Meine GPU ist die Intel A380
    Auf dem Host habe ich

    ls /dev/dri/
    by-path  card0  renderD129
    In der VM aber nur
    ls /dev/dri/
    by-path  card0
    Und laut Proxmox Doku ist auf dem Host schon das richtige Modul geladen:
    lspci -k | grep -A 3 "VGA"
    11:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A380] (rev 05)
            Subsystem: ASRock Incorporation DG2 [Arc A380]
            Kernel driver in use: vfio-pci
            Kernel modules: i915, xe
    --
    ​:boost_animated:​ ​:neofox_pleading:​
    Ich bin über jede Hilfe dankbar. Stehe gerade komplett auf der Leitung.
    #boostpls #fedihelp_de #fedihelp #proxmox #gpu #passthrough #boostpls #fedihelp_de #fedihelp #proxmox #gpu #passthrough

  16. Hat jemand Erfahrung mit GPU Passthrough in Proxmox?
    Ich versuche es seit Stunden und komme nicht weiter.
    Meine GPU ist die Intel A380
    Auf dem Host habe ich

    ls /dev/dri/
    by-path  card0  renderD129
    In der VM aber nur
    ls /dev/dri/
    by-path  card0
    Und laut Proxmox Doku ist auf dem Host schon das richtige Modul geladen:
    lspci -k | grep -A 3 "VGA"
    11:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A380] (rev 05)
            Subsystem: ASRock Incorporation DG2 [Arc A380]
            Kernel driver in use: vfio-pci
            Kernel modules: i915, xe
    --
    ​:boost_animated:​ ​:neofox_pleading:​
    Ich bin über jede Hilfe dankbar. Stehe gerade komplett auf der Leitung.
    #boostpls #fedihelp_de #fedihelp #proxmox #gpu #passthrough #boostpls #fedihelp_de #fedihelp #proxmox #gpu #passthrough

  17. Hat jemand Erfahrung mit GPU Passthrough in Proxmox?
    Ich versuche es seit Stunden und komme nicht weiter.
    Meine GPU ist die Intel A380
    Auf dem Host habe ich

    ls /dev/dri/
    by-path  card0  renderD129
    In der VM aber nur
    ls /dev/dri/
    by-path  card0
    Und laut Proxmox Doku ist auf dem Host schon das richtige Modul geladen:
    lspci -k | grep -A 3 "VGA"
    11:00.0 VGA compatible controller: Intel Corporation DG2 [Arc A380] (rev 05)
            Subsystem: ASRock Incorporation DG2 [Arc A380]
            Kernel driver in use: vfio-pci
            Kernel modules: i915, xe
    --
    ​:boost_animated:​ ​:neofox_pleading:​
    Ich bin über jede Hilfe dankbar. Stehe gerade komplett auf der Leitung.
    #boostpls #fedihelp_de #fedihelp #proxmox #gpu #passthrough #boostpls #fedihelp_de #fedihelp #proxmox #gpu #passthrough