The Doctor @drwho@hackers.town

https://github.com/virtadpt/exocortex-halo/tree/master/environment-sensor-esp8266

#python #micropython #esp8266 #iot #enviroment #monitoring

Yeah!

#python #exocortex #halo #environmentmonitoring #PoC

https://github.com/virtadpt/exocortex-halo/tree/master/environment-sensor-raspbian

Building out a #python test environment on Audra to tinker with that AHT-20 sensor.

Is anybody familiar with slixmpp? #xmpp #python

#python #multiprogramming

https://gitlab.com/ltgiv/polycephaly

In reworking some of my bots to use #matrix instead of #xmpp, I'm looking at using a single unlisted room instead of chats to individual accounts (1:1 chat, not MUC).

This changes the command parser substantially. Probably more than I think.

What I'm considering is whether to keep the commands looking like "Bot, do this thing..." or switching to "Do this thing..." and the bots present look at the message, see if it's from their owner (me, in this case), and if so proceed to parse the command. The latter means that failed parses would fall into the same case as mis-parses, and result in a storm of error responses from every bot that doesn't have commands like that.

Of course, bots could easily just not send error responses, but that messes up the "there really is an error" handling case.

I'm also toying with the idea of having both use cases implemented for usability's sake (plus, it adds the "send commands directly to the bot" case).

What do you think, #fediverse?

#exocortex #bots #python

Rhasspy: A #foss personal assistant written in #python that is designed with self-hosted utility software (speech recognition, speech to text, natural language processing, and speech synthesis) primarily, instead of outsourcing it to untrusted third parties.

https://github.com/synesthesiam/rhasspy

#india #ff #introductions

#infosec #hacker #pwnagotchi

I make stuff that crunches numbers. Got tired of red team, now sysadmin/defense.

My imaginary friends are better conversationalists than I am, and are written in #python and #ruby.

#ai #ml #exocortex #bots

Lots of augmentations of the hardware and software kind. Chances are you might have a conversation with one of them and not realize it. About a third of me is prosthetic these days.

#electronics #hamradio

I suck as an electrical engineer but sometimes I can patch stuff together.

#locksport

I like picking locks. Still trying to get good with padlocks.

#homestuck

I assume you've been told about Homestuck.

#osint #information

I like to be well informed. The downside of this is that I don't sleep well anymore.

#goth #industrial #synthwave

I love music.

#linux #archlinux #vi #vim

Yes, I use Arch. I don't care what you use as long as it does what you need.

#searx STILL doesn't play nicely with #python 3.

wtf?

Okay, this is weird...

I have a server written in #python that can accept HTTP PUT requests on a particular URI:

https://github.com/virtadpt/exocortex-halo/blob/master/exocortex_xmpp_bridge/rest.py#L146

I also have a client written in Python which sends messages to the server on that URI with PUT requests:

https://github.com/virtadpt/exocortex-halo/blob/master/system_bot/system_bot.py#L164

Here's what's messing with me:

On my x86-64 boxen, this works just fine. It does what you'd expect, reliably, on demand. On my Raspbian machines, though, the exact same request doesn't work. The JSON doesn't deserialize.

Has anyone ever seen this before?

If I wanted to double-check my work porting #python 2 code to Python 3, would the `2to3` utility be useful for this?

So, I use run.sh scripts to instantiate #python virtualenvs, and supervisord to execute the run.sh scripts to start up system_bot.py.

If I tell supervisorctl to stop systembot (the service name), the bot keeps running, but run.sh may or may not be terminated. So there's an orphaned bot running in the background.

I suspect that I'll have to add something to the supervisord manifests.

Hmm.