@dbread @web3isgreat lol the grift is limitless with these guys hahaha. Freaking you have 100k+ worth of crypto if not more and going for some airdrops.... man
Playin around with my new pocket oscilloscope
https://www.youtube.com/watch?v=YzCkjb2ZlA8
Working on my #liquidClock
It's awesome how little code it needs to work.
The strategy for datetime updates is to get a hourly timestamp to synchronize via mqtt.
My new favourite open source mastodon client is https://phanpy.social by @cheeaun.
It is a web app, but can be added to your Home Screen like any other app (even on iPhone).
The attention to detail and minimalist, yet playful, UI is just out of this world. Whenever I use my other client, I wish for their features.
My absolute favourite feature is using different colours to highlight replies, private messages, boosts and hashtags.
I used to be a DJ, mixing mostly electronic net music. It was a big thing 15-20 years ago. I had a website for it which I shut down years ago.
I now have now reactivated the site at https://inanace.net. Many of the netlabels from those days have disappeared, so the site is an archive of the music from those golden times. Have a look if you like and I'll see if the scene still exists! That's why I created this account.
What this story solved:
I once improved a dollhouse with an old house gong ding-dong bell. Then I added an #Arduino to trigger it with my not-so-smart doorbell of my real home. It was awesome. But some weeks ago it stopped working, so the solution was, to fix something in a remote datacenter in another country on a virtual server. To make a ding go dong.
That does not seem right.
Thanks for reading :)
#eof
I only depend on mosquitto_sub and pub for live demos and debugging, so the charmful workaround was to register another listener for the default port like
`listener 1883`
`protocol mqtt`
Now I am happy again, my bridge works and all my privacy is gone again.
Updating to the #snap release of mosquitto was the most simple way to fix the first problem (reconnects).
The second problem should be no problem, but the shell clients seem not to allow unencrypted 8883 connections. There are some command line options that should circumvent the problem `--insecure`.
But *protocol error* still occurred.
Related problem 5 years ago :/ https://stackoverflow.com/questions/56361192/configuring-mosquitto-mqtt-broker-to-listen-on-multiple-ports
Another #IoT journey report.
My broker was no more compatible to the bridge at home so continuous reconnects every second was the result.
Another problem is that I serve non-encrypted mqtt over 8883 what confuses the #mosquitto clients.
(8883 is the default for TLS encrypted connections)
Changing that port is not an option as enough devices in the #hackerspace and at friends homes depend on it.
@jfbastien Olfactory Studio, where "code smell" is literal.
@hanno Getting a uniformly distributed random number with an upper bound is surprisingly hard with web APIs. And StackOverflow is just full with wrong answers.
Crypto scammer suddenly pleads guilty in trial surrounding EXW fraud
December 13, 2023
https://web3isgoinggreat.com/?id=exw-fraud