home.social

#socket — Public Fediverse posts

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

  1. Каналы и авторизация в Centrifugo: как безопасно подключить real-time в Laravel

    Real-time без авторизации опасен. Если пользователь может подписаться на чужой канал, он может получать чужие уведомления, статусы заказов, сообщения, события админки или финансовые обновления. В обычном HTTP API такая ошибка выглядела бы как доступ к чужому endpoint. В WebSocket-архитектуре ошибка такая же, просто выглядит менее очевидно. Разбираем в Centrifugo: публичные и приватные подписки, connection token, subscription token, права доступа и безопасное подключение

    habr.com/ru/articles/1035472/

    #realtime #centrifugo #socket

  2. #Socket detected a #supplychainattack on 84 #TanStack #npm packages, including popular ones like tanstack/react-router, which were compromised with suspected credential-stealing malware. The attack involved a chained #GitHub Actions attack and resulted in the publication of malicious packages authenticated through the project’s #OIDC trusted-publisher binding. socket.dev/blog/tanstack-npm-p #tech #media #news

  3. #Socket detected a #supplychainattack on 84 #TanStack #npm packages, including popular ones like tanstack/react-router, which were compromised with suspected credential-stealing malware. The attack involved a chained #GitHub Actions attack and resulted in the publication of malicious packages authenticated through the project’s #OIDC trusted-publisher binding. socket.dev/blog/tanstack-npm-p #tech #media #news

  4. #Socket detected a #supplychainattack on 84 #TanStack #npm packages, including popular ones like tanstack/react-router, which were compromised with suspected credential-stealing malware. The attack involved a chained #GitHub Actions attack and resulted in the publication of malicious packages authenticated through the project’s #OIDC trusted-publisher binding. socket.dev/blog/tanstack-npm-p #tech #media #news

  5. #Socket detected a #supplychainattack on 84 #TanStack #npm packages, including popular ones like tanstack/react-router, which were compromised with suspected credential-stealing malware. The attack involved a chained #GitHub Actions attack and resulted in the publication of malicious packages authenticated through the project’s #OIDC trusted-publisher binding. socket.dev/blog/tanstack-npm-p #tech #media #news

  6. #Socket detected a #supplychainattack on 84 #TanStack #npm packages, including popular ones like tanstack/react-router, which were compromised with suspected credential-stealing malware. The attack involved a chained #GitHub Actions attack and resulted in the publication of malicious packages authenticated through the project’s #OIDC trusted-publisher binding. socket.dev/blog/tanstack-npm-p #tech #media #news

  7. ## LibreSSL 4.3.1 released!

    * Internal improvements
    - Remove the unused sequence number from X509_REVOKED.
    - Replace a call to atoi() with strtonum() in nc(1) and replace a
    misleading use of ntohs() with htons().
    - openssl(1) speed now uses HMAC-SHA256 for its hmac benchmark.
    - Reimplemented only use of ASN1_PRINTABLE_type() in openssl(1) ca.
    The API will be removed in an upcoming release.
    - Add curve NID to EC_POINT objects so the library has a clue on which
    curve a given EC_POINT is supposed to live.
    - Use curve NID to check for compatibility between group and points
    in various EC API. This isn't 100% failsafe but good enough for sane
    uses.
    - Require SSE in order to use gcm_{gmult,ghash}_4bit_mmx().
    On rare i386 machines suporting MMX but not SSE this could result
    in an illegal instruction.
    - Cleaned up asn1t.h to make it somewhat readable and more robust by
    using C99 initializers in particular.
    - Further assembly macro improvements for -portable.
    - Add fast path for well-known DH primes in DH_check() (including
    those from RFC 7919). Some projects still fiddle with this in 2025.
    - Rewrite ec_point_cmp() for readability and robustness.
    - Improve EVP_{Open,Seal}Init() internals. This is legacy API that
    cannot be removed since one scripting language still exposes it.
    - ASN1_BIT_STRING_set_bit() now trims trailing zero bits itself rather
    than relying on i2c_ASN1_BIT_STRING() to do that when encoding.
    - Fix and add workarounds to libtls to improve const correctness and
    to avoid warnings when compiling with OpenSSL 4.
    - Prefix EC_KEY methods with ec_key_ to avoid problems in some static
    links.

    undeadly.org/cgi?action=articl

    Go read ALL about it here!

    #SSL #libre #BSD #openBSD #OpenSource #programming #networking #Secure #Socket #Layer

  8. ## LibreSSL 4.3.1 released!

    * Internal improvements
    - Remove the unused sequence number from X509_REVOKED.
    - Replace a call to atoi() with strtonum() in nc(1) and replace a
    misleading use of ntohs() with htons().
    - openssl(1) speed now uses HMAC-SHA256 for its hmac benchmark.
    - Reimplemented only use of ASN1_PRINTABLE_type() in openssl(1) ca.
    The API will be removed in an upcoming release.
    - Add curve NID to EC_POINT objects so the library has a clue on which
    curve a given EC_POINT is supposed to live.
    - Use curve NID to check for compatibility between group and points
    in various EC API. This isn't 100% failsafe but good enough for sane
    uses.
    - Require SSE in order to use gcm_{gmult,ghash}_4bit_mmx().
    On rare i386 machines suporting MMX but not SSE this could result
    in an illegal instruction.
    - Cleaned up asn1t.h to make it somewhat readable and more robust by
    using C99 initializers in particular.
    - Further assembly macro improvements for -portable.
    - Add fast path for well-known DH primes in DH_check() (including
    those from RFC 7919). Some projects still fiddle with this in 2025.
    - Rewrite ec_point_cmp() for readability and robustness.
    - Improve EVP_{Open,Seal}Init() internals. This is legacy API that
    cannot be removed since one scripting language still exposes it.
    - ASN1_BIT_STRING_set_bit() now trims trailing zero bits itself rather
    than relying on i2c_ASN1_BIT_STRING() to do that when encoding.
    - Fix and add workarounds to libtls to improve const correctness and
    to avoid warnings when compiling with OpenSSL 4.
    - Prefix EC_KEY methods with ec_key_ to avoid problems in some static
    links.

    undeadly.org/cgi?action=articl

    Go read ALL about it here!

    #SSL #libre #BSD #openBSD #OpenSource #programming #networking #Secure #Socket #Layer

  9. ## LibreSSL 4.3.1 released!

    * Internal improvements
    - Remove the unused sequence number from X509_REVOKED.
    - Replace a call to atoi() with strtonum() in nc(1) and replace a
    misleading use of ntohs() with htons().
    - openssl(1) speed now uses HMAC-SHA256 for its hmac benchmark.
    - Reimplemented only use of ASN1_PRINTABLE_type() in openssl(1) ca.
    The API will be removed in an upcoming release.
    - Add curve NID to EC_POINT objects so the library has a clue on which
    curve a given EC_POINT is supposed to live.
    - Use curve NID to check for compatibility between group and points
    in various EC API. This isn't 100% failsafe but good enough for sane
    uses.
    - Require SSE in order to use gcm_{gmult,ghash}_4bit_mmx().
    On rare i386 machines suporting MMX but not SSE this could result
    in an illegal instruction.
    - Cleaned up asn1t.h to make it somewhat readable and more robust by
    using C99 initializers in particular.
    - Further assembly macro improvements for -portable.
    - Add fast path for well-known DH primes in DH_check() (including
    those from RFC 7919). Some projects still fiddle with this in 2025.
    - Rewrite ec_point_cmp() for readability and robustness.
    - Improve EVP_{Open,Seal}Init() internals. This is legacy API that
    cannot be removed since one scripting language still exposes it.
    - ASN1_BIT_STRING_set_bit() now trims trailing zero bits itself rather
    than relying on i2c_ASN1_BIT_STRING() to do that when encoding.
    - Fix and add workarounds to libtls to improve const correctness and
    to avoid warnings when compiling with OpenSSL 4.
    - Prefix EC_KEY methods with ec_key_ to avoid problems in some static
    links.

    undeadly.org/cgi?action=articl

    Go read ALL about it here!

    #SSL #libre #BSD #openBSD #OpenSource #programming #networking #Secure #Socket #Layer

  10. ## LibreSSL 4.3.1 released!

    * Internal improvements
    - Remove the unused sequence number from X509_REVOKED.
    - Replace a call to atoi() with strtonum() in nc(1) and replace a
    misleading use of ntohs() with htons().
    - openssl(1) speed now uses HMAC-SHA256 for its hmac benchmark.
    - Reimplemented only use of ASN1_PRINTABLE_type() in openssl(1) ca.
    The API will be removed in an upcoming release.
    - Add curve NID to EC_POINT objects so the library has a clue on which
    curve a given EC_POINT is supposed to live.
    - Use curve NID to check for compatibility between group and points
    in various EC API. This isn't 100% failsafe but good enough for sane
    uses.
    - Require SSE in order to use gcm_{gmult,ghash}_4bit_mmx().
    On rare i386 machines suporting MMX but not SSE this could result
    in an illegal instruction.
    - Cleaned up asn1t.h to make it somewhat readable and more robust by
    using C99 initializers in particular.
    - Further assembly macro improvements for -portable.
    - Add fast path for well-known DH primes in DH_check() (including
    those from RFC 7919). Some projects still fiddle with this in 2025.
    - Rewrite ec_point_cmp() for readability and robustness.
    - Improve EVP_{Open,Seal}Init() internals. This is legacy API that
    cannot be removed since one scripting language still exposes it.
    - ASN1_BIT_STRING_set_bit() now trims trailing zero bits itself rather
    than relying on i2c_ASN1_BIT_STRING() to do that when encoding.
    - Fix and add workarounds to libtls to improve const correctness and
    to avoid warnings when compiling with OpenSSL 4.
    - Prefix EC_KEY methods with ec_key_ to avoid problems in some static
    links.

    undeadly.org/cgi?action=articl

    Go read ALL about it here!

    #SSL #libre #BSD #openBSD #OpenSource #programming #networking #Secure #Socket #Layer

  11. ## LibreSSL 4.3.1 released!

    * Internal improvements
    - Remove the unused sequence number from X509_REVOKED.
    - Replace a call to atoi() with strtonum() in nc(1) and replace a
    misleading use of ntohs() with htons().
    - openssl(1) speed now uses HMAC-SHA256 for its hmac benchmark.
    - Reimplemented only use of ASN1_PRINTABLE_type() in openssl(1) ca.
    The API will be removed in an upcoming release.
    - Add curve NID to EC_POINT objects so the library has a clue on which
    curve a given EC_POINT is supposed to live.
    - Use curve NID to check for compatibility between group and points
    in various EC API. This isn't 100% failsafe but good enough for sane
    uses.
    - Require SSE in order to use gcm_{gmult,ghash}_4bit_mmx().
    On rare i386 machines suporting MMX but not SSE this could result
    in an illegal instruction.
    - Cleaned up asn1t.h to make it somewhat readable and more robust by
    using C99 initializers in particular.
    - Further assembly macro improvements for -portable.
    - Add fast path for well-known DH primes in DH_check() (including
    those from RFC 7919). Some projects still fiddle with this in 2025.
    - Rewrite ec_point_cmp() for readability and robustness.
    - Improve EVP_{Open,Seal}Init() internals. This is legacy API that
    cannot be removed since one scripting language still exposes it.
    - ASN1_BIT_STRING_set_bit() now trims trailing zero bits itself rather
    than relying on i2c_ASN1_BIT_STRING() to do that when encoding.
    - Fix and add workarounds to libtls to improve const correctness and
    to avoid warnings when compiling with OpenSSL 4.
    - Prefix EC_KEY methods with ec_key_ to avoid problems in some static
    links.

    undeadly.org/cgi?action=articl

    Go read ALL about it here!

    #SSL #libre #BSD #openBSD #OpenSource #programming #networking #Secure #Socket #Layer

  12. Of interest to #Canadians. With the Fedi skew to tech-knowledgeable people, this probably isn't news to many.

    But if you're looking to buy #electrical stuff - power bars, extension cords, multi-outlet wall taps that convert 1 #socket into 3 or 2 into 6, all this sort of stuff - be careful where you buy it.

    The big hardware stores / home centres sell this stuff, but at stupidly-high #prices. There's no reason a 10-foot extension cord should cost $25, or a power bar $40. So many people reasonably look for #cheaper alternatives.

    A lot of #stores and sellers operating in the ... less-well-regulated portions of the market bring this stuff in cheap directly from sellers/manufacturers in China or other countries. Independent stores, mall kiosks, people selling out of their home - their products may not be approved for sale in Canada, because they don't have the necessary #safety #certification. And many of *those* products are actually downright dangerous. I've taken a lot of them apart and seen the many, many ways they can kill you or burn your house down.

    Instead, get this stuff at #Dollarama. Their stuff is actually safety-certified by one of the required labs - #CSA, #UL, or most likely #ETL. It's approved for sale in #Canada. And it's still cheap. It might be a little more than guy-with-a-sales-counter-in-a-dilapidated-strip-mall, but not by enough to matter.

    Other big chains might be okay - but I haven't personally verified those.

    #PowerBar #ExtensionCord

  13. Of interest to #Canadians. With the Fedi skew to tech-knowledgeable people, this probably isn't news to many.

    But if you're looking to buy #electrical stuff - power bars, extension cords, multi-outlet wall taps that convert 1 #socket into 3 or 2 into 6, all this sort of stuff - be careful where you buy it.

    The big hardware stores / home centres sell this stuff, but at stupidly-high #prices. There's no reason a 10-foot extension cord should cost $25, or a power bar $40. So many people reasonably look for #cheaper alternatives.

    A lot of #stores and sellers operating in the ... less-well-regulated portions of the market bring this stuff in cheap directly from sellers/manufacturers in China or other countries. Independent stores, mall kiosks, people selling out of their home - their products may not be approved for sale in Canada, because they don't have the necessary #safety #certification. And many of *those* products are actually downright dangerous. I've taken a lot of them apart and seen the many, many ways they can kill you or burn your house down.

    Instead, get this stuff at #Dollarama. Their stuff is actually safety-certified by one of the required labs - #CSA, #UL, or most likely #ETL. It's approved for sale in #Canada. And it's still cheap. It might be a little more than guy-with-a-sales-counter-in-a-dilapidated-strip-mall, but not by enough to matter.

    Other big chains might be okay - but I haven't personally verified those.

    #PowerBar #ExtensionCord

  14. Of interest to #Canadians. With the Fedi skew to tech-knowledgeable people, this probably isn't news to many.

    But if you're looking to buy #electrical stuff - power bars, extension cords, multi-outlet wall taps that convert 1 #socket into 3 or 2 into 6, all this sort of stuff - be careful where you buy it.

    The big hardware stores / home centres sell this stuff, but at stupidly-high #prices. There's no reason a 10-foot extension cord should cost $25, or a power bar $40. So many people reasonably look for #cheaper alternatives.

    A lot of #stores and sellers operating in the ... less-well-regulated portions of the market bring this stuff in cheap directly from sellers/manufacturers in China or other countries. Independent stores, mall kiosks, people selling out of their home - their products may not be approved for sale in Canada, because they don't have the necessary #safety #certification. And many of *those* products are actually downright dangerous. I've taken a lot of them apart and seen the many, many ways they can kill you or burn your house down.

    Instead, get this stuff at #Dollarama. Their stuff is actually safety-certified by one of the required labs - #CSA, #UL, or most likely #ETL. It's approved for sale in #Canada. And it's still cheap. It might be a little more than guy-with-a-sales-counter-in-a-dilapidated-strip-mall, but not by enough to matter.

    Other big chains might be okay - but I haven't personally verified those.

    #PowerBar #ExtensionCord

  15. Of interest to #Canadians. With the Fedi skew to tech-knowledgeable people, this probably isn't news to many.

    But if you're looking to buy #electrical stuff - power bars, extension cords, multi-outlet wall taps that convert 1 #socket into 3 or 2 into 6, all this sort of stuff - be careful where you buy it.

    The big hardware stores / home centres sell this stuff, but at stupidly-high #prices. There's no reason a 10-foot extension cord should cost $25, or a power bar $40. So many people reasonably look for #cheaper alternatives.

    A lot of #stores and sellers operating in the ... less-well-regulated portions of the market bring this stuff in cheap directly from sellers/manufacturers in China or other countries. Independent stores, mall kiosks, people selling out of their home - their products may not be approved for sale in Canada, because they don't have the necessary #safety #certification. And many of *those* products are actually downright dangerous. I've taken a lot of them apart and seen the many, many ways they can kill you or burn your house down.

    Instead, get this stuff at #Dollarama. Their stuff is actually safety-certified by one of the required labs - #CSA, #UL, or most likely #ETL. It's approved for sale in #Canada. And it's still cheap. It might be a little more than guy-with-a-sales-counter-in-a-dilapidated-strip-mall, but not by enough to matter.

    Other big chains might be okay - but I haven't personally verified those.

    #PowerBar #ExtensionCord

  16. Of interest to #Canadians. With the Fedi skew to tech-knowledgeable people, this probably isn't news to many.

    But if you're looking to buy #electrical stuff - power bars, extension cords, multi-outlet wall taps that convert 1 #socket into 3 or 2 into 6, all this sort of stuff - be careful where you buy it.

    The big hardware stores / home centres sell this stuff, but at stupidly-high #prices. There's no reason a 10-foot extension cord should cost $25, or a power bar $40. So many people reasonably look for #cheaper alternatives.

    A lot of #stores and sellers operating in the ... less-well-regulated portions of the market bring this stuff in cheap directly from sellers/manufacturers in China or other countries. Independent stores, mall kiosks, people selling out of their home - their products may not be approved for sale in Canada, because they don't have the necessary #safety #certification. And many of *those* products are actually downright dangerous. I've taken a lot of them apart and seen the many, many ways they can kill you or burn your house down.

    Instead, get this stuff at #Dollarama. Their stuff is actually safety-certified by one of the required labs - #CSA, #UL, or most likely #ETL. It's approved for sale in #Canada. And it's still cheap. It might be a little more than guy-with-a-sales-counter-in-a-dilapidated-strip-mall, but not by enough to matter.

    Other big chains might be okay - but I haven't personally verified those.

    #PowerBar #ExtensionCord

  17. Petite introduction sur les réseaux IP et les sockets tirée du stream Twitch d'hier avant de se lancer dans le codage d'un exemple d'utilisation de socket en UDP.

    videos.apprendre-delphi.fr/w/c
    (aussi dispo sur YouTube)

    Aujourd'hui on tentera de comprendre le fonctionnement de SNMP et de discuter avec mon imprimante réseau. Si tout se passe bien, vendredi et samedi on transforme l'essai en composant pour VCL/FMX afin de surveiller les imprimantes réseau par drag & drop dans n'importe quel projet.
    (et plus tard je coderai la version UDP de la "socket messaging library for Delphi")

    #Delphi #Socket #Network #IP #TCP #UDP #SNMP

  18. Внутреннее устройство веб-сервера. Часть 1: От syscalls до WSGI

    В этой статье мы разберём, какие механизмы предоставляет Linux для работы с сетью и как на их основе строятся фреймворки и библиотеки, которыми мы пользуемся каждый день. К концу статьи мы напишем минималистичный WSGI -веб-сервер, с помощью которого можно запускать произвольные WSGI -приложения.

    habr.com/ru/articles/1002550/

    #сервер #backend #python #сокет #socket #sockets #системное_программирование #linux_kernel #ядро_линукс #системные_вызовы

  19. Внутреннее устройство веб-сервера. Часть 1: От syscalls до WSGI

    В этой статье мы разберём, какие механизмы предоставляет Linux для работы с сетью и как на их основе строятся фреймворки и библиотеки, которыми мы пользуемся каждый день. К концу статьи мы напишем минималистичный WSGI -веб-сервер, с помощью которого можно запускать произвольные WSGI -приложения.

    habr.com/ru/articles/1002550/

    #сервер #backend #python #сокет #socket #sockets #системное_программирование #linux_kernel #ядро_линукс #системные_вызовы

  20. Внутреннее устройство веб-сервера. Часть 1: От syscalls до WSGI

    В этой статье мы разберём, какие механизмы предоставляет Linux для работы с сетью и как на их основе строятся фреймворки и библиотеки, которыми мы пользуемся каждый день. К концу статьи мы напишем минималистичный WSGI -веб-сервер, с помощью которого можно запускать произвольные WSGI -приложения.

    habr.com/ru/articles/1002550/

    #сервер #backend #python #сокет #socket #sockets #системное_программирование #linux_kernel #ядро_линукс #системные_вызовы

  21. Внутреннее устройство веб-сервера. Часть 1: От syscalls до WSGI

    В этой статье мы разберём, какие механизмы предоставляет Linux для работы с сетью и как на их основе строятся фреймворки и библиотеки, которыми мы пользуемся каждый день. К концу статьи мы напишем минималистичный WSGI -веб-сервер, с помощью которого можно запускать произвольные WSGI -приложения.

    habr.com/ru/articles/1002550/

    #сервер #backend #python #сокет #socket #sockets #системное_программирование #linux_kernel #ядро_линукс #системные_вызовы

  22. @Larvitz
    I have almost the same set-up:
    - without Selinux has I'm running on #arch but with #rootless containers.
    For #traefik I activated #socket github.com/eriksjolund/podman-

    The next step for me will be to use #podman's secrets. Thanks to your article I discovered their existence!

  23. Oh, also in my bag of old parts were a bunch of different DIP sockets, and wow are some of them incredibly made. There's some by a company called Cambion I wasn't familiar with, but they appear to be MilSpec-rated DIP-40 sockets. The plastic frame appears to be some nice engineering plastic - maybe POM? - it's tougher and stiffer than any nylon I've seen, much less the cheap sockets you buy. The contacts seem to be nicely plated phosphor bronze or something, and THICK.

    It feels like I could beat someone to death with one of these things!

    #socket #DIP #POM #nylon #contacts #TheyDontMakeThemLikeTheyUsedTo

  24. Shuttle XPC slim DH810 is a 1.35 liter desktop PC with an LGA1851 socket for Intel Arrow Lake-S chips

    The Shuttle XPC slim DH810 is a compact desktop computer that measures just 190 x 165 x 43mm (7.5″ x 6.5″ x 1.6″) and has an internal volume of just 1.35 liters. While that makes it larger than some mini PCs that have mobile processors soldered to their motherboards, the DH810 stands out because it has an Intel LGA1851 socket with support for user-replaceable desktop processors.

    Shuttle […]

    #arrowLakeS #lga1851 #miniPc #shuttle #shuttleXpcSlimDh810 #socket

    Read more: liliputing.com/shuttle-xpc-sli

  25. Shuttle XPC slim DH810 is a 1.35 liter desktop PC with an LGA1851 socket for Intel Arrow Lake-S chips

    The Shuttle XPC slim DH810 is a compact desktop computer that measures just 190 x 165 x 43mm (7.5″ x 6.5″ x 1.6″) and has an internal volume of just 1.35 liters. While that makes it larger than some mini PCs that have mobile processors soldered to their motherboards, the DH810 stands out because it has an Intel LGA1851 socket with support for user-replaceable desktop processors.

    Shuttle […]

    #arrowLakeS #lga1851 #miniPc #shuttle #shuttleXpcSlimDh810 #socket

    Read more: liliputing.com/shuttle-xpc-sli

  26. Shuttle XPC slim DH810 is a 1.35 liter desktop PC with an LGA1851 socket for Intel Arrow Lake-S chips

    The Shuttle XPC slim DH810 is a compact desktop computer that measures just 190 x 165 x 43mm (7.5″ x 6.5″ x 1.6″) and has an internal volume of just 1.35 liters. While that makes it larger than some mini PCs that have mobile processors soldered to their motherboards, the DH810 stands out because it has an Intel LGA1851 socket with support for user-replaceable desktop processors.

    Shuttle […]

    #arrowLakeS #lga1851 #miniPc #shuttle #shuttleXpcSlimDh810 #socket

    Read more: liliputing.com/shuttle-xpc-sli

  27. Shuttle XPC slim DH810 is a 1.35 liter desktop PC with an LGA1851 socket for Intel Arrow Lake-S chips

    The Shuttle XPC slim DH810 is a compact desktop computer that measures just 190 x 165 x 43mm (7.5″ x 6.5″ x 1.6″) and has an internal volume of just 1.35 liters. While that makes it larger than some mini PCs that have mobile processors soldered to their motherboards, the DH810 stands out because it has an Intel LGA1851 socket with support for user-replaceable desktop processors.

    Shuttle […]

    #arrowLakeS #lga1851 #miniPc #shuttle #shuttleXpcSlimDh810 #socket

    Read more: liliputing.com/shuttle-xpc-sli

  28. Intel Nova Lake-S: especificaciones, cambios a nivel de arquitectura, socket, precio y posible fecha de lanzamiento blog.elhacker.net/2025/08/inte #hardware #socket #intel #ultra #cpu #npu

  29. Blogged. Use #Gleam to implement a #Socket.IO server on #Deno

    https://hashset.dev/article/2025/07/20/use-gleam-to-implement-a-socket-io-server-on-deno/

    I've finally written about using #gleam, which I find a fantastic language. Awkwardly enough my first blog post about it is for the #JavaScript target :ablobglarezoom: hopefully more posts will follow where I'm using gleam on the #erlang BEAM
  30. @bookwyrm Installed, running (not thanks to #redis, #socket and python
    bookwyrm.projetretro.io/user/s

    now gonna find all the book in the house to scan them

  31. Better experience and fast, secure way to create a connection with MariaDB.

    // Config.php

    $mariadb = ini_get('pdo_mysql.default_socket');

    $pdo = new PDO("mysql:unix_socket=$mariadb;dbname=test", 'root', '');

    if($pdo){
    echo "Database connection success!";
    }

    #php #mariadb #pdo #socket #mysql #mysqli #mysqlpdo

  32. Better experience and fast, secure way to create a connection with MariaDB.

    // Config.php

    $mariadb = ini_get('pdo_mysql.default_socket');

    $pdo = new PDO("mysql:unix_socket=$mariadb;dbname=test", 'root', '');

    if($pdo){
    echo "Database connection success!";
    }

    #php #mariadb #pdo #socket #mysql #mysqli #mysqlpdo

  33. Better experience and fast, secure way to create a connection with MariaDB.

    // Config.php

    $mariadb = ini_get('pdo_mysql.default_socket');

    $pdo = new PDO("mysql:unix_socket=$mariadb;dbname=test", 'root', '');

    if($pdo){
    echo "Database connection success!";
    }

    #php #mariadb #pdo #socket #mysql #mysqli #mysqlpdo

  34. Better experience and fast, secure way to create a connection with MariaDB.

    // Config.php

    $mariadb = ini_get('pdo_mysql.default_socket');

    $pdo = new PDO("mysql:unix_socket=$mariadb;dbname=test", 'root', '');

    if($pdo){
    echo "Database connection success!";
    }

    #php #mariadb #pdo #socket #mysql #mysqli #mysqlpdo

  35. Better experience and fast, secure way to create a connection with MariaDB.

    // Config.php

    $mariadb = ini_get('pdo_mysql.default_socket');

    $pdo = new PDO("mysql:unix_socket=$mariadb;dbname=test", 'root', '');

    if($pdo){
    echo "Database connection success!";
    }

    #php #mariadb #pdo #socket #mysql #mysqli #mysqlpdo

  36. Good morning! ☕

    Last weekend I kept exploring multiprocess programming in PHP.
    I just published Part 3 of my “Parallel Processing in PHP” series. This time, it’s about multiplexing streams with stream_select().

    In this post, I show how to:
    ✅ Fork multiple child processes
    ✅ Communicate using stream_socket_pair()
    ✅ Use stream_select() to handle messages concurrently

    Read it here 👉 dev.to/robertobutti/parallel-p

    #php #socket #tutorial @thepracticaldev

  37. bizzare - 50 quid for a 1 gang 13A #mains #socket with both USB charger and #Bluetooth squawk box, sold by some designer place in #London.

    Who even would want such a thing?

  38. bizzare - 50 quid for a 1 gang 13A #mains #socket with both USB charger and #Bluetooth squawk box, sold by some designer place in #London.

    Who even would want such a thing?