Hello!
I'm Oleksandr Buzynnyi, 27 yo deep learning engineer.
Here is my tech blog, contacts and maybe I'll add something else later.
Need to start from something :D
Some little facts:
Currently I have 5+ years of machine learning and deep learning commercial experience.
Curious about intelligence in all forms and flavours, contemporary polymatic research, complexity science, statistical physics, thermodynamics, informational theory in context of AI etc.
Contacts:
- Codewars (since Nov 2015)
- Github (since May 2016)
- Gitlab (since Jun 2022)
- Mastodon : @sophronesis@soc.ua-fediland.de (since Oct 2022)
- Telegram (links dump)
- Email :
$ echo "c29waHJvbmVzaXNAZGlzcm9vdC5vcmcK" | base64 -d
- Bitcoin :
bc1qxawfjk0y9d69frdk2l6c6qzty8z8f4kpqmjpv9
- Monero :
88McNuddP9t9gNnNdKp8jeLY1V9h5ztA9Rgn1gHRStEcMvHtiWaxmqB64pZq1iJqWcTSbcjpYJxjp87rsashm6e6Q7Q2e3V
Telegram autoscheduling
2023-05-20
Link to the project: https://gitlab.com/sophronesis/tgautoschedule
I've been posting on telegram for several years now and learned many things on how to do this more efficiently. One of the things I choose to optimize is scheduling. You can't just dump 100+ posts onto your subscribers, most will just feel overwhelmed from it, scroll past 3-5 memes and move to next channel. Not good.
The first thing to do was just using plain built-in scheduling. It's decent, but has some limits, such as:
- 100 scheduled messages limit (I know, Durov is squeezing extra storage, yeeaaah...)
- you need to manually put each message on timer with fixed time, you can't just dump everything you find interesting to a meme grinder, it takes lots of unnecessary manual labor to convert this turbulent flow to a laminar one.
So i came with the only possible conclusion - to make my own scheduling script. I started with Telethon, but quickly found out that you can't use copy_message()
method there.
So let's define the basics. We have one channel that we will call "Queue" which we use to store scheduled edge memes for them to later be posted to another channel called "Target". The only thing this script does is it gets a random message from "Queue" using some given sampler function, sends it to "Target" and if it's successfully posted - deletes an original in "Queue". That's not rocket science, everything is plain and simple.
To use it you need to do several things:
- Get your "api_id" and "api_hash" from https://my.telegram.org/ (Go to "API Development tools" -> "Create new application" -> "Create application" and fill the rest)
- Put your "api_id" and "api_hash" to config.json in your folder
- Put your username or some unique name to "username" to config.json
- Modify the
createSchedule()
function or create your own and replace the name inscheduleF = createSchedule
with your own function. Just remember that the scheduling function should output a list of events (transferring of messages) for a current day. Each event is tuple with 3 elements:- time of day in "hours:minutes" to post on
- source channel name (both plain channel name and @username are valid)
- target channel name
- Run
src.py
and enjoy the reduction in time needed to maintain your shitposting channel
Site launch
2023-04-24
Finally after more than 5 years I'm ready to launch my personal site as I see fit. Currently it's just more like skeleton of what I want to do with it, but it's enough to be published. Main site design (all as one html page) was inspired by John doe's site. Static site is generated with minimal resources (pages/blog posts are stored as markdown files and compiled to html).
Currently it have (will be updated later):
- Working RSS feed (not just example.com link)
- Contacts page
And what I plan to do in some time:
- Old content from telegram/github/gitlab as blog posts here
- Restyle site to change to more darker color scheme / JS-free dark mode
- Possibly multilanguage pages (EN/UA)
Wildpipes project
2022-08-19
Wildpipes is a project to ease transfer text or image data to or from different destination points with terminal.
Project started as two simple bash aliases to get clipboard data or to send data to it. It's all implemented in pure bash so won't add extra time overhead, just pure syntactic sugar.
Input destinations:
- Output of some command
- Xorg monitor clipboard
- Termbin link (temporary text storage)
- Image from cam
- Screenshot of a screen
- Sound message (ggwave)
- Image file
- Telegram bot's last recieved message
- QR code
Output destination:
- Text in console (stdout)
- Xorg monitor clipboard
- Termbin link (temporary text storage)
- Image file
- Sound message (ggwave)
- Telegram message (with given reciever ID) (need to be autorize bot first)
- Tab in firefox
- Display (e.g. to show image)
- QR code (as image)
- QR code (as terminal ascii)
- OCR recovered text
Package comes in to different install variants:
- Minimal (default) (only simplest commands)
- Full (installs all necessary packages for all destinations support)
Full conversions map:
wp.sanity_check.sh can interactively verify which of packages are available.