Tootfinder

Opt-in global Mastodon full text search. Join the index!

No exact results. Similar results found.
@aardrian@toot.cafe
2026-10-20 01:32:50

I like how El-Sayed handles this.
bsky.app/profile/abdulelsayed.
I don’t think he knew this kid was a (GOP-connected Christian nationalist) plant:

@NFL@darktundra.xyz
2026-10-24 13:19:18

Inside the silent messages Boye Mafe sends every game day espn.com/nfl/story/_/id/502588

@neverpanic@chaos.social
2026-10-23 13:21:54

Status: Scanning an entire distribution for certain CA certificates…

A command line interface showing three colored progress bars at the bottom for "download", "extract" and "analyze". Above the progress bars, there are log messages for HTTP requests to a server for many distribution RPM packages.
@unixorn@hachyderm.io
2026-07-25 17:22:59

Periodic reminder for people interested in #HomeLab and #SelfHosting
There is a @… bot that replaces the old gup.pe homelab bot.
Mention it in your homelab or self hosting posts and it will boost them. Follow it to see all the homelab posts it boosts that may not normally get federated to your instance.
For those who don’t know, these bots exist because when you look for a a hashtag, your server only checks the posts that have been federated to it.
In order for a message to be federated to your server, the author (or one of the people boosting it) have to be followed by someone on your server. If no one touching the message is being followed, it’ll never get federated to your server and you won’t see it.
Hashtags are great for finding messages, but only messages that were federated to your server. They don’t help message propagation.

@timfoster@mastodon.social
2026-09-24 18:24:36

Yesterday: me complaining at engineers for using 1-line commit messages.
Today: me looking at AI-generated commit messages, and actually losing the will to live.

@bobmueller@mastodon.world
2026-10-08 22:00:04

Good News Of The Day.
There are turtles involved.
wgbh.org/news/local/2026-10-06

@CerstinMahlow@mastodon.acm.org
2026-10-19 20:41:08

RE: mstdn.social/@watson_news/1174
Warum das also sehr sinnvoll war, dass man sich früher™️ Musikkassetten aufgenommen hat!

@unixorn@hachyderm.io
2026-07-25 17:26:05

Periodic reminder for people interested in #HomeAssistant
There is a @… bot that replaces the old gup.pe home assistant bot.
Mention it in your homeassisitant posts and it will boost them. Follow it to see all the #homeasistant posts it boosts that may not normally get federated to your instance.
There’s also @… - follow that and it will automatically boost everything you post with #homeassistant without you having to remember to mention the bot.
For those who don’t know, these bots exist because when you look for a a hashtag, your server only checks the posts that have been federated to it.
In order for a message to be federated to your server, the author (or one of the people boosting it) have to be followed by someone on your server. If no one touching the message is being followed, it’ll never get federated to your server and you won’t see it.
Hashtags are great for finding messages, but only messages that were federated to your server. They don’t help message propagation, but these bots will.

@hacksilon@infosec.exchange
2026-10-20 17:52:25

Update on the #homeassistant restore - everything worked almost perfectly. Three gotchas I found so far:
- The “restoring” page would just keep displaying, since after the restore, the service no longer responded to homeassistant.local. Luckily I saw my soundbar turn on, which is always a good indicator that HA rebooted.
- The backup seemingly did not contain the sound files I had uploaded, so my improvised temporary doorbell is borked until I upload a new sound file.
- The most interesting one: The zigbee devices did not reconnect initially, except for a single one, and the reason was interesting - I learned something new about Zigbee today.
Apparently Zigbee has a frame counter, and the devices will remember the last frame counter they observed, and refuse messages with a lower count afterwards. The backup contained stale frame counters, since the machine died several hours after the last backup, hence, all devices were refusing messages from the coordinator. The solution was to power-cycle all mains-powered devices. The battery-powered devices came back automatically after that, except for two buttons which I had to re-pair manually. Credits to Claude for figuring this out based on the logs.
Other than that, quite happy with the “restore from backup” on Home Assistant for now. Now I only need to reconfigure my two wall tablets to point to the new local home assistant URL, as the RPi has a different hostname on my network now, and the wall tablets used the local alias of the old machine for the connection, as I did not want to route them via the internet ingress through Nabu Casa. But that’s not the fault of the backup, that’s just me configuring my stuff weird.

@laimis@mstdn.social
2026-08-04 22:59:33

I needed a push delivery of some 3rd party service events that service itself didn't provide. I could get the info with polling but it would be very inefficient. It turns out the same 3rd party publishes the notifications I needed to their discord server. So what do you do? Join their discord. Build a custom version of vencord with custom plugin that intercepts discord messages. And then pings my service that needs the info. It's so stupid but sometimes you just have to roll...