Malicious #PyPI packages abuse #Gmail, #websockets to hijack systems
Malicious #PyPI packages abuse #Gmail, #websockets to hijack systems
Exploiting Trust: Malicious PyPI Packages Use Gmail and WebSockets for Cyber Hijacking
A recent discovery of seven malicious packages on PyPI highlights a concerning trend in software supply chain attacks, leveraging trusted services like Gmail for data exfiltration. With one package do...
Pretty certain #SSE (Server Sent Events) are the future. No upgrade to get #Websockets. Simply, plain old HTTP and simple message body. Though do make sure to use HTTP/2.
https://developer.mozilla.org/en-US/docs/Web/API/Server-sent_events/Using_server-sent_events
Today I learned…
1. there's a card game where you complete a task from Unix pipe commands: https://punkx.org/unix-pipe-game/ (via https://mamot.fr/@bearstech/114275843048191227)
2. there's a JavaScript x86 machine emulator so you can play that game without needing a real computer around: https://bellard.org/jslinux/tech.html
3. that JS VM gets network connectivity because someone decided to make a websocket-based VPN that passes Ethernet frames: http://www.benjamincburns.com/2013/11/10/jor1k-ethmac-support.html
In-depth tutorial from @Rock the JVM on what WebSockets are and how to implement them in Scala using http4s. #scala #websockets https://rockthejvm.com/articles/websockets-in-scala-part-1-http4s
New Kitten update
• Added `remove()` method to kitten.Component class. Use this when working with live pages and components and you want to remove a component from the page (or its parent). It will handle removing event listeners for you so you don’t end up with any memory leaks.
• Improved `update()` method so it similarly removes listeners on child components before updating the component itself in case you have class-based child components that will be reinstantiated on render.
• Updated the `send()` methods on `page.everyone` and `page.everyoneElse` so you can pass a swap target to insert the element being streamed to the page before, after, asFirstChildOf, or asLastChildOf another. (This was already there for the page.send() but now the two broadcast objects have the same consistent interface.
The @small-web/kitten npm package (Kitten’s types package) has also been updated to version 5.1.0 to reflect the latest changes.
(Remember that the new class and event-based page and component model is still experimental and largely undocumented and fully backwards compatible with the classic functional way of authoring your page routes and components.)
Enjoy!
Harnessing Human Creativity: A New Approach to Random Number Generation
In a world increasingly dominated by AI, a new web service creatively flips the script by leveraging human input for random number generation. This innovative project not only showcases the quirks of ...
https://news.lavx.hu/article/harnessing-human-creativity-a-new-approach-to-random-number-generation
> What started as an exploration into #WebSockets led us to a surprisingly effective "old-school" solution: #HTTP long polling with #Postgres
https://www.inferable.ai/blog/posts/postgres-nodejs-longpolling.mdx
A quick demonstration of using the State: Overview page in Kitten’s¹ settings while developing to keep an eye on your event and event listener counts to avoid memory leaks.
Notice how the events and listeners counts change as I navigate between the People and Settings pages in my Place² node and that they are consistent. If they were rising as I navigated back and forth I’d know I had a memory leak somewhere.
If you use Kitten’s built-in features (e.g., the `addEventHandler()` method on your `kitten.Component` subclasses, Kitten will handle adding and removing listeners for you automatically during your component’s lifecycle. You can also do so manually in your component’s automatically-called `onConnect()` and `onDisconnect()` event handlers.
This view is useful during development to ensure you don’t have any memory leaks as pages are loaded and unloaded.
¹ https://kitten.small-web.org
² Place is in early development at the moment (https://codeberg.org/place/app)
From the @DSLC chives:
"Web APIs with R: Find APIs & Communicate with other types of APIs" https://youtu.be/hDfrbKOMuyU #API #APIs #RStats #graphql #websockets #gRPC
"Bayes Rules! MCMC under the Hood" https://youtu.be/CCpL8IpUTEE #RStats
"Probabilty for Data Science: Discrete Random Variables Exercises" https://youtu.be/xHclZpPPLwA #RStats
Visit https://dslc.video for hours of new #DataScience videos every week!
Pretty soon, you’re going to be able to view your live pages and the events on them in real time while developing Kitten apps.
The improved component model with support for class-based routes (and a server-side component hiearchy that lets you build well-encapsulated components and pages and work in an event-driven way) is coming along nicely and I’m back to writing Place¹ using it.
(In the GIF, you’re looking at Place’s profile settings page. Not shown here but those profile changes reflect in realtime on all open pages. The highlighted piece of code is what streams the event details to the browser.)
Feeling more like myself today after getting my ass kicked by this bug for the past few weeks and I’m finally making progress on improving Kitten’s¹ component model.
Soon, you’ll be able to implement page event handlers in an even simpler way than before. Is your connected DOM element named `pixel`? Then export an event handler called `onPixel()` on your page route and it’ll get called when that element triggers its event.
And there’s so much more coming, including a class-based page and component model with DOM-style event bubbling on the server. This should really let you make the most of the Streaming HTML² workflow in Kitten by writing event-driven GUI-like code but for a web app without really caring about the client/server separation.
Need to update the examples, test, test, test, and update docs but this had me stumped for a while now with several false starts and I feel this implementation might just be it
¹ https://kitten.small-web.org
² https://kitten.small-web.org/tutorials/streaming-html/
Raspberry Pi Pico Servidor Websockets
En este vídeo explico como podemos crear un servidor websockets con nuestra raspberry pi pico con el cuál podemos conectar desde clientes como puede ser directamente una aplicación de escritorio o web para recibir datos JSON.
https://gitlab.com/raupulus/rpi-pico-simple-websockets-server
https://github.com/raupulus/rpi-pico-simple-websockets-server
watching a possible heisenbug. looks like i now have enough debugging output in to stop it happening. posting about it in an attempt to prod sod's law into tripping it.
Guess I'm striking out on making my #Django chess game use #Websockets. There are a number of write-ups by people who seem to have done it... I've tried a number of things based on them. And unfortunately, they are all bewildering to me.
If any kind soul would be willing to peek, my "non-websocket", but totally functional project is https://github.com/ology/django-chess-inspector to see how it can be refactored? I will pay you.
Basically I make a JS post like this, for each move:
Help? :)
Elsevier may wish they had checked the revision a bit more carefully
https://community.nodebb.org/topic/254c582c-b8f0-4fef-a746-b7a012e4dad5/elsevier-may-wish-they-had-checked-the-revision-a-bit-more-carefully.
#ycombinator #nodebb #forum #community #discussion #javascript #nodejs #mongodb #redis #websockets
For the F# code of today, let's wrap a websocket connection in an IObservable<T> Personally, I don't like fire and forget async things, but I kind of wanted just to get it out I'll figure out later when I clearly need to change this, and I won't be able
He actualizado el artículo.
Añadimos una situación muy común. Los usuarios tendrán que compartir un recurso que no se puede paralelizar. Podrías imaginar en una impresora. Si un usuario está imprimiendo, los demás tendrán que esperar.
#htmx #django #python #celery #huey #djangochannels #websockets #webdev