As per title. Unlisted posts can not be reblogged, but the web UI still shows a reblog icon for such posts, and it can be clicked. After spinning for a while it then returns to its initial state, which is confusing (especially if you’re unaware of the limitation of reblogging unlisted posts).
The official mobile client does better: there such posts apparently don’t have the reblog icon. An alternative solution is Mastodon’s (web UI’s) way of showing a boost icon, but disabling it (so that it doesn’t react to clicks).
(The instance I’m on is pixelfed.social. The most recent post I had this issue with was federated from https://vernissage.photos/@magda/7470629220893329794#)
Attached is a screenshot of one of my filters, and of a post on my timeline matching the filter (see the hashtags at the end). There’s nothing (at all) in the console log. My handle is @uusijani@mastodon.social. The post in this case apparently comes from a federated blog.
I have a feeling that most times I’ve seen posts that should have been filtered out, they’ve been boosted ones and not OC from people I follow. But obviously it could just be that I don’t follow many people who post about things that I like to hide with filters.
After last night’s refresh I’m now running 2024.10.4. Attempting to update Nordpool, fmi-hass-custom and pytapo fail with:
Unable to install package nordpool==0.4.2: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package fmi-weather-client==0.4.0: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
Unable to install package pytapo==3.3.32: error: failed to create file `/snap/home-assistant-snap/637/.lock` Caused by: Permission denied (os error 13)
It’s apparently due some changes in core, as some people running HA inside a customized Docker have also suffered this.
In the previous latest/stable, updating Nordpool and FMI weather client failed with errors about pip’s version, so I had reverted those back to their earlier versions and put off retrying the updates until now. Pytapo could be a dependency of Tapo Camera Control, which also updated recently.
Elokuussa kerrottiin VR:n suunnittelevan yhteistyössä Itä-Lapin kuntien kanssa päiväjunayhteyttä Kemijärvelle (https://yle.fi/a/74-20107386#). Eilen VR on avannut varaukset ensi kesään saakka, mutta näitä mainittuja päiväjunia sieltä ei löydy. Pyytäisinkin siksi toimitukselta seurantajuttua aiheesta: onko nuo suunnitelmat peruttu vai mitä niille kuuluu.
I’m just making this note here publicly, since I was first going to pose this as a question, but then managed to solve it by myself:
For background, I recently switched my Mattermost from a tar archive installation to installing it from the package repository, and simultaneously switched it from using a MySQL database to using PostgreSQL, all in one fell swoop by exporting the old content, doing a fresh install, and then importing. This appears to have mostly worked, with just user profile images having been lost, and passwords requiring a reset, both of which (I’ve gleaned from various places) were to be expected.
However, all bot accounts also seem to have been converted into normal user accounts somewhere during this process. So far the only issue I’ve discovered resulting from this is this entry getting logged repeatedly:
Failed to get system bot caller="app/post.go:2205" component=post_reminders error="SqlBotStore.Get: Bot does not exist., resource "Bot" not found, id: <my system bot's id>"
I solved this by running
sudo -u mattermost mmctl user convert --bot "<bot id>" # replace <bot id> with your real system bot account id
Since that seems to have gone well (the error messages stopped), I went ahead and converted the rest of the bot accounts back to true bots likewise.
Paljon onnea parikymppiselle! Kohti seuraavia kymmenlukuja!
Luulin vielä lopussakin, että tämä oli Pieniä ihmeitä, mutta tämähän olikin näitä Silmiksen pieniä ihmeitä.
”Istahdin kävelykadun penkille, silmäilin vaivihkaa, oliko kukaan kiinnittänyt huomiota ähräämiseeni. Ei. Tässä iässä on se hyvä puoli, että on näkymätön.”
Tai sitten olivat niin kuin minä, joka ajattelen, että avun tarjoamista tärkeämpää on antaa avuntarvitsijan pitää kiinni näkymättömyydentunteestaan, koska niin itse pulassa ollessani haluaisin, vaikka ongelma olisi miten ylitsepääsemätön yksin ratkaista. Eli klassinen suomalainen ”oho, liukastuin ja pää halkesi, mutta onneksi sentään kukaan ei huomannut”.
