Tootfinder

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

No exact results. Similar results found.
@aardrian@toot.cafe
2026-10-22 02:43:56

@… They don’t always (usually). It depends on a lot of factors (language, dictionary, preferences, heuristics, text-to-speech engine, etc).
I tested a few different options here:

@EarthOrgUK@mastodon.energy
2026-10-22 23:41:10

65gCO2/kWh National Grid CO2 intensity is LOW wrt last 24h so you can run your wash etc now! #green #energy

@steadystatemcr@mstdn.social
2026-10-07 08:09:26

Another day, another sealing of agricultural land.
Residents 'sickened' as farmland at the edge of Bury village eyed up for hundred of homes - Manchester Evening News
manchestereveningnews.co.uk/ne

@leftsidestory@mstdn.social
2026-10-06 01:10:40

Corners of Life II 🎆
生活的角落 II 🎆
📷 Yashica 635
🎞️ Ilford HP5 Plus, expired 1994
If you like my work, Support by buying me a coffee or a roll of film from
PayPal ‪ paypal.com/paypalme/ydcdingsite
Wise ‪

Ilford HP5 Plus 400 (FF)

English
A black and white photograph. Several fire extinguishers stand by the corner of the wall in the shade. A few meters away; there is a small cabinet with Chinese characters, reading Mini Fire Brigade, on them.

中文
一张黑白照片。照片中一些灭火器立在墙边的阴影中。几米开外有一个写着“微型消防站”的柜子。
Ilford HP5 Plus 400 (FF)

English
A black and white photograph. An arrow shaped sign on the ground points towards the camera in the sun light.

中文
一张黑白照片。地面上一个箭头标志指向镜头。
Ilford HP5 Plus 400 (FF)

English
A black and white photograph. A deserted couch stands by the side of a trash can, under the edge side of an exterior window. Over the window to inside the room, several wooden frames can be seen.

中文
一张黑白照片。一张被遗弃的沙发在垃圾桶旁边。沙发在一个窗户的下缘边。透过窗户的屋内有很多画框。
Ilford HP5 Plus 400 (FF)

English
A black and white photograph. The shadow of a high rise lies in the on the ground, separating the ground into two halves. The left is lit, with motorcycles parked in a line. The right side is a clear space.

中文
一张黑白照片。一栋高楼的影子在地面上制造出了一个分界线。左侧在阳光中,一排摩托车。右侧没有任何东西。
@tiotasram@kolektiva.social
2026-10-11 08:29:24

Trying out a new license clause and disclaimer:
4. This software is NOT used as training data for a model of code or text structure or construction, such as a large language model, transformer model, reinforcement learning agent, etc. If such a model is generative and predicts or outputs the code of this software in whole or in part, that shall be evidence of infringement of this clause of this license.
THIS SOFTWARE SHOULD NOT BE USED AS TRAINING DATA FOR A STATISTICAL MODEL OF CODE OR TEXT, NOR SHOULD STATISTICAL CODE OR TEXT MODELS BE ASKED TO READ, INTERPRET, OR OTHERWISE PROCESS ITS SOURCE CODE OR OUTPUTS. THIS SOFTWARE MAY CONTAIN CODE OR TEXT OR MAY PRODUCE OUTPUTS WHICH CAUSE MODEL ROLE CONFUSION OR WHICH OTHERWISE CAUSE UNANTICIPATED CONSEQUENCES WHEN PROCESSED.
Would genuinely welcome any thoughts about wording.
#NoAI #LLMs #AI

@ginevra@hachyderm.io
2026-08-13 03:23:01

Random tip: put 'echolalia' as a search term in you music algorithm of choice (Tidal, Spotify, Apple, Deezer etc)
Are there other search terms you've found that produce a good variety of unknown-to-you results?
#music

@saraislet@infosec.exchange
2026-10-03 18:18:20

At this point, I started to look deeper at performance. Compute instance startup was taking over 30 seconds, and each generation propagation was about 55-75 seconds
I worked this from a few angles:
- parallelize actions (health checks, integrity checks, propagation initiation, and terminating ancestors) [30% gain]
- rebuild and reduce the AMI below Ubuntu minimal to fit in 2GiB EBS volumes (reduced cost and increased speed by also bundling the glider daemon and boto3 SDK in the AMI) [30% gain]
- switched from AWS CLI to boto3 SDK [5-10% gain]
- switched from CloudFormation creation stacks to using EC2 API directly with LaunchTemplate [under 5% gain total, surprisingly, but the time to initial instance startup is faster so I might be able to do better somewhere here]
- WIP: further refactoring of the daemon propagation steps especially around initial health/integrity checks
I still think I'm missing something major that's extending propagation times, despite benchmarking phases through several trials
I also optimized for cost (reduced DDB calls, abandoned KMS, reduced log & audit retention to the latest run, etc), and it's about a penny for a 10 generation run (and it scales sublinearly, mostly, since the instances are terminated afterwards)