in reply to feld

ideally. the route was built back when trains topped out at like 40mph or less and has been used for decades for freight moving at even slower speeds. Obviously it's not really feasible for a private company to do all that but it's completely absurd that neither they nor the local municipalities have even bothered to put up fences where the line cuts through residential and business areas.

(welcome to the new boss, same as the old boss)

Some Startups Are Demanding 12-Hour Days, Six Days a Week from Workers

it.slashdot.org/story/25/10/25…

in reply to André Polykanine

Я про альтернативные решения и не знал, правда меня вся эта тема с децентрализованными соцсетями и прочим в целом обошла стороной. Знаю что API тут вроде как чуть более богат чем доступен в TWBlue. А может и нет.

one of the most irritating parts of running your own instance is having to modify source files just to change your character limits. there are plenty of posts out there describing how to change the character limits for posts, but almost none on how to change the limit for alt text (1500):

here's the source file where the alt text char limit is buried:
/instance/app/javascript/mastodon/features/ui/components/focal_point_modal.jsx

and here's the source that needs to be changed:

<FormattedMessage id='upload_modal.detect_text' defaultMessage='Detect text from picture' />
</button>
<CharacterCounter max={1500} text={detecting ? '' : description} />
</div>

<Button
type='submit'
disabled={!dirty || detecting || isUploadingThumbnail || length(description) > 1500 || is_changing_upload}
text={intl.formatMessage(is_changing_upload ? messages.applying : messages.apply)}
/>
</form>

change "1500" to whatever value you want.

#mastoAdmin

reshared this

in reply to Emmanuele Bassi

Sorry about that. I‘m using a PowerMac and Snow Leopard as well (sometimes) and am happy about every port that still works. But I thought it would be my job to write patches for software that won‘t run on that machines anymore otherwise. Would be a pity if removing support would become an act of collective punishment for some bullies existing in any community. Technical reasons, yes, of course. There‘s no contract for eternal support, paid forever or sth.

‘ Doctors have warned that the government’s decision to exclude health and social care workers from its covid vaccination programme is putting patients at risk and will have a major impact on an overstretched NHS.’

🤦 Unbelievably shortsighted, based on what exactly!

bmj.com/content/391/bmj.r2141

my piece about some current events, somewhat political

Sensitive content

in reply to LeonianSpookyVerse🎃

@LeonianUniverse It can do a few things, although I'm not totally sure what's changed in 26 as I only just updated a few days ago and didn't have a ton of time to play around until this weekend. You're able to take a picture or screenshot of something, and then either ask ChatGPT about it or use Google to find similar items. It can also do things like read text aloud, add events you see in public to your calendar, and a few other things like that.

🦣 Před dvěma lety napadlo @fabia_man založit vlastní instanci.
Robin přišel s názvem Mamutovo – a od té doby má fediverse o jednoho mamuta navíc 😄

Dnes je mamutovo.cz pevnou součástí @oscloud 💚
Od té doby se s @cynik_obecny snažíme, aby Mamutovo bylo vždy na nejnovější verzi a běželo tak, jak má.

🎂 Happy Birthday, Mamutovo!

#mastodon #oscloud #fediverse #mamutovo

This entry was edited (6 days ago)

GmsCompatLib version 101 released


Changes in version 101:

  • fix a font preloading crash caused by the GmsFontProvider shim introduced in the previous release

A full list of changes from the previous release (version 100) is available through the Git commit log between the releases.

GmsCompatLib is a core component of the GrapheneOS sandboxed Google Play compatibility layer.

This update is available to GrapheneOS users via our app repository and and will be obsoleted by the next OS release including the changes in the base package.

Google Camera's Dependence On Google Play Resolved In Latest GmsCompatLib


Pixel Camera recently added a hard dependency on Google Play services. It still works on GrapheneOS, but started requiring sandboxed Google Play services.

GmsCompatLib version 100 for GrapheneOS 2025102300 or later restores support for Pixel Camera without Play services:

grapheneos.social/@GrapheneOS/…

GmsCompatLib version 100 released


Changes in version 100:

  • add shim implementation of GmsFontProvider to prevent crashes of apps depending on Play services when it's missing or disabled (restores support for using Pixel Camera without Play services with recent Pixel Camera versions depending on it for this)
  • extend shim for background service starts to address edge cases where a foreground service is required
  • fix NoOpPrewarmService chain crash in Pixel Camera caused by lack of privileged OS integration

A full list of changes from the previous release (GrapheneOS version 2025102300) is available through the Git commit log between the releases.

GmsCompatLib is a core component of the GrapheneOS sandboxed Google Play compatibility layer.

This update is available to GrapheneOS users via our app repository and and will be obsoleted by the next OS release including the changes in the base package.

GrapheneOS Foundation Does Not Make App or Services Recommendations


While we greatly appreciate businesses seeing value in our work, selling devices with GrapheneOS preinstalled or being a business in the privacy/security space, recognising our users buying services/products, and so donating to us. GrapheneOS has no official direct affiliations.

Unless mentioned by the project account no team members make any recommendations on behalf of the project for any app/product/service, any that may be linked, are personal recommendations or just to make users aware they exist for them to decide for themselves.

Vanadium version 142.0.7444.48.0 released


Changes in version 142.0.7444.48.0:

  • update to Chromium 142.0.7444.48
  • allow registration of passkeys regardless of residentKey value

A full list of changes from the previous release (version 141.0.7390.122.0) is available through the Git commit log between the releases.

This update is available to GrapheneOS users via our app repository and will also be bundled into the next OS release. Vanadium isn't yet officially available for users outside GrapheneOS, although we plan to do that eventually. It won't be able to provide the WebView outside GrapheneOS and will have missing hardening and other features.

GrapheneOS version 2025102300 released


Tags:

  • 2025102300 (Pixel 6, Pixel 6 Pro, Pixel 6a, Pixel 7, Pixel 7 Pro, Pixel 7a, Pixel Tablet, Pixel Fold, Pixel 8, Pixel 8 Pro, Pixel 8a, Pixel 9, Pixel 9 Pro, Pixel 9 Pro XL, Pixel 9 Pro Fold, Pixel 9a, emulator, generic, other targets)

Changes since the 2025102200 release:

  • fix signing the GmsCompatLib package with a dedicated cross-device key, which was added in the last release but wasn't being replaced by a release key and blocked moving the last release past Alpha
  • kernel (6.12): update to latest GKI LTS branch revision

All of the Android 16 security patches from the current November 2025, December 2025 and January 2026 Android Security Bulletins are included in the 2025102301 security preview release. List of additional fixed CVEs:

  • Critical: CVE-2025-48593, CVE-2025-48631
  • High: CVE-2022-25836, CVE-2022-25837, CVE-2023-40130, CVE-2024-43766, CVE-2025-22420, CVE-2025-22432, CVE-2025-32319, CVE-2025-32348, CVE-2025-48525, CVE-2025-48536, CVE-2025-48555, CVE-2025-48564, CVE-2025-48565, CVE-2025-48566, CVE-2025-48567, CVE-2025-48572, CVE-2025-48573, CVE-2025-48574, CVE-2025-48575, CVE-2025-48576, CVE-2025-48577, CVE-2025-48578, CVE-2025-48579, CVE-2025-48580, CVE-2025-48582, CVE-2025-48583, CVE-2025-48584, CVE-2025-48585, CVE-2025-48586, CVE-2025-48587, CVE-2025-48589, CVE-2025-48590, CVE-2025-48592, CVE-2025-48594, CVE-2025-48596, CVE-2025-48597, CVE-2025-48598, CVE-2025-48600, CVE-2025-48601, CVE-2025-48602, CVE-2025-48603, CVE-2025-48604, CVE-2025-48605, CVE-2025-48609, CVE-2025-48612, CVE-2025-48614, CVE-2025-48615, CVE-2025-48616, CVE-2025-48617, CVE-2025-48618, CVE-2025-48619, CVE-2025-48620, CVE-2025-48621, CVE-2025-48622, CVE-2025-48626, CVE-2025-48628, CVE-2025-48629, CVE-2025-48630, CVE-2025-48632, CVE-2025-48633, CVE-2025-48634

2025100901 provides at least the full 2025-11-01 patch level and the Android 2025-11-05 patch level (Pixel Update Bulletin could have fixes we don't get early) but will remain marked as providing 2025-10-05.

For detailed information on security preview releases, see our post about it.

I have completed my email migration to Stalwart and I only hit one bug where an account somehow got messed up from imapsync and lost its INBOX and Stalwart couldn't deliver messages in the queue because of that and nothing would let me create the INBOX manually, so I had to delete and resync

Otherwise: it works. Thunderbird handles autoconfig nicely, iOS doesn't (expected). Contacts and calendars and sieve working.

Spam filtering seems to be working so far but it does feel more opaque overall because I'm used to having my fingers in every service that comprises a modern mail setup. But that leads to lack of tight integration which was also frustrating

in reply to feld

curious to hear how it goes if something goes wrong. One big benefit of postfix and dovecot that they are pretty fine with things going wrong and recovering from that. Partly because everything is mapped to the filesystem and you can do easy tooling around it. Mess up some filtering subsystem? Postfix will queue it and you can inspect the failure via cli. Fix the issue and the queues clear out.
in reply to holga

@hpk yes it holds stuff in an internal queue if there are issues with delivery which is nice

I am not a fan of RocksDB because I have been able to get it into a state where the software using it doesn't want to start up because of some unclean shutdown issue and I don't know how to fix it. Haven't seen a way to fix it... so I don't trust that. I'm using Postgres right now for the main storage which is fine but a bit unnecessary, i could just be using ZFS and I'll probably switch to that. Filesystem storage is good enough for me when they aren't actually leveraging the database properly anyway.

If you are into #tranceMusic #uplifting #vocalTrance, have a listen to these stunning tracks

Paipy & Elles de Graaf - The Last Time

Driftmoon X XiJaro & Pitch - Rise Again

RAM & Arctic Moon & Stine Grove - A Billion Stars Above

There's such a thing as too much anti-fraud protection.

I tried six times to order a replacement part from Braun's website. Each time I'd get a confirmation of the order, followed immediately by a notification that it had been canceled.

I finally get on customer support and they dig into it and come back and tell me that my IP address is too far from my address.

Ummm. Okay, so maybe it's Apple's private relay. But no. I turn that off and it still does the same thing. Also, curiously. Apple Pay fails as well as soon as I enter my address.

My shipping address is a couple miles away from my house in the same town. Most IP locators think my IPV4 address is an about 20 miles away in another town. My IPv6 is listed as being in Oregon, another state.

But seriously. Who expects IP location to be accurate enough to protect against fraud? That's nuts. Is this some European concept of how IP addresses work?