Mastodon Feed: Posts

Boosted by aredridel@kolektiva.social ("Mx. Aria Stewart"):
tankgrrl@hachyderm.io ("💀 𝓕airchild 💀") wrote:

How it's done. 🤟🏼 #Tidal.

Bullet point #3 is huge. So much slop is generated just to get $ from sheer volume. Take that away and the incentive to flood the platform goes away.
≠=====

Here are the highlights of our new AI Policy:

• Tidal will identify and tag AI-generated music in our app. Listeners will see an "AI" badge next to music we detect as wholly AI-generated.

• Tidal will not tolerate AI-generated music that impersonates an artist or group, or that facilitates fraudulent activity. We're implementing automatic tools to remove these releases immediately and on an ongoing basis.

• Tidal will not allow music that is 100% AI-generated to be monetized. No royalties will go to such releases, nor will AI-generated uploads be eligible for direct-to-fan sales.

• We will expand these policies to music that is substantially AI-generated when AI detection technology is sufficiently reliable to do so.

https://tidal.com/ai-policy?lid

dysfun@treehouse.systems ("gaytabase") wrote:

fatal error: stdbit.h: No such file or directory

huh, it's right. where did my c23 headers go?!

Boosted by aredridel@kolektiva.social ("Mx. Aria Stewart"):
louie@pdx.social ("Louie Mantia, Jr.") wrote:

I love this guy’s argument so much that I had to, well, you’ll see—

Attachments:

• video: 163cb32ad54e423d.mp4

dysfun@treehouse.systems ("gaytabase") wrote:

my kingdom for it to be easy to type in two languages and still get spelling correction on a mobile device.

fromjason ("fromjason.xyz ❤️ 💻 ✍️ 🥐 🇵🇷") wrote:

I may write more about this one day. The past couple of years I've learned to show gratitude for the ways people show up for you, even if it's not how you need them to.

fromjason ("fromjason.xyz ❤️ 💻 ✍️ 🥐 🇵🇷") wrote:

Might fuck around and get a little tattoo today

Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
david_chisnall@infosec.exchange ("David Chisnall (*Now with 50% more sarcasm!*)") wrote:

@soatok

Common domain names, ranked in order of likelihood to contain valuable content about technology:

1. .furry
2. .org
3. .com
4. .io
5. .ai

pzmyers@freethought.online ("pzmyers 🕷") wrote:

D'Arcy Wentworth Thomson was quite the dashing fellow in his twenties.

https://freethoughtblogs.com/pharyngula/2026/06/29/everything-is-the-way-it-is-because-it-got-that-way/

soatok@furry.engineer ("Soatok Dreamseeker") wrote:

RE: https://furry.engineer/@soatok/116684771406334186

https://www.zeffy.com/en-US/donation-form/donate-to-make-the-dot-furry-community says this is 100% funded now lol

brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:") wrote:

Why does sysadminning break my brain 😭

Boosted by ChrisWere@toot.wales ("Chris Were ⁂🐧🌱☕"):
OohOkayKay@beige.party ("🇨🇦 Little-k") wrote:

This poll has now ended.

Thank you to everyone who voted.
929 people voted and 243 awesome people boosted it so others could join in the fun.

Top 10 Options chosen:
#1 66% Linux (always first ... for now lol)
#2 64% Politics (of any country)
#3 56% Boost AND favour toots!!
#4 54% Voting in polls
#5 51% Posts about your hobbies.
#6 48% Rants about AI
#7 44% Random rants about your own life
#8 42% Being Autistic Spectrum/ADHD/Neurodivergent
#9 A Tie at 39% -
Post nature or scenery pics
Comments on current events
#10 Also a tie at 38%!
Rants about tech bros
Because Mastodon is part of the Fediverse
Honorable mention: 37% We are NOT a cult.

pzmyers@freethought.online ("pzmyers 🕷") wrote:

Time to break out the AC.

https://freethoughtblogs.com/pharyngula/2026/06/29/muggy-buggy/

Boosted by fromjason ("fromjason.xyz ❤️ 💻 ✍️ 🥐 🇵🇷"):
alice@lgbtqia.space ("🅰🅻🅸🅲🅴 (🌈🦄)") wrote:

Today, an unknown bot swarm started using my name, boosting my posts, and inserting itself into communities I helped create. I treated it like any other potential attack and started defending myself and our communities as best I could. This has taken up more of my day than most malicious bot attacks, because it had the air of legitimacy—despite taking the actions of a threat.

When the owner, @evan ¹, came in with the same justifications as the porn-scrapers and LLM-owners I regularly fight against—repeatedly doubling-down in the face of backlash²—I felt more and more sure of my response.

I now feel justified in calling for a #FediBlock of tags.pub (and probably his other projects), at least until a better opt-in consent model is built into the project.

¹ I'm including his name as he's a public figure associated with Activity Pub, and our whole conversation today is already a public record, but please don't dogpile; just defed or block as you see fit and call it a night (or day—I'm not your mom).

² Receipts: https://lgbtqia.space/@alice/116824281370893420

#FediAdmins

Boosted by dysfun@treehouse.systems ("gaytabase"):
akareilly@hachyderm.io ("Wren Reilly") wrote:

Why is the appeal to “traditional European values” always about xenophobia and patriarchy, and not dragging nobles off their horses and bludgeoning them with farming implements in a peasants’ revolt?

dysfun@treehouse.systems ("gaytabase") wrote:

i can quit optimising any time i like

dysfun@treehouse.systems ("gaytabase") wrote:

i have looked at some 'genius' code i came up with a couple of weeks ago and i'm underimpressed. unfortunately i don't actually have a better answer at the moment.

dysfun@treehouse.systems ("gaytabase") wrote:

This is an ADHD behaviour.

ADHD? Me? Surely not :blobcatangel:

Boosted by glyph ("Glyph"):
adrianh ("Adrian Howard") wrote:

Monday off to a good start with an unexpectedly early delivery of @grimalkina's new book! Looking forward to digging in!

Boosted by glyph ("Glyph"):
mttaggart@infosec.exchange ("Taggart :ifin:") wrote:

This is a masterful demonstration of the unsecurable nature of LLMs, and how prompt injection by dedicated humans who know how to write will always win.

https://role-confusion.github.io/

jscalzi@threads.net ("John Scalzi") wrote:

Get your shots, folks

https://www.nbcnews.com/health/health-news/shingles-brain-inflammation-research-vaccine-dementia-risk-rcna351961

dysfun@treehouse.systems ("gaytabase") wrote:

commenting code

under 256, probably under 64 or not much over, didn't maths harder.

Boosted by brib@bribstodon.xyz ("brib :neofox_floof:​ :Nonbinary:"):
gotosocial@superseriousbusiness.org ("GoToSocial") wrote:

Hello #GoToSocial enjoyers, after a very fruitful release candidate process (thanks everyone!), we've just released the proper version of GoToSocial 0.22.0, aka Shrubby Sloth 🌿:

https://codeberg.org/superseriousbusiness/gotosocial/releases/tag/v0.22.0

This is a big feature release that contains support for relay subscriptions and relay push connections, a new instance account directory, better threading using tombstones for deleted statuses,, and support for auto-cleanup of old remote statuses, among lots of other things!

⚠️⚠️⚠️ As always, please read the migration notes carefully for instructions on how to upgrade to this version, in particular note that there are several config file changes that need to be addressed when you're updating from a previous version of GoToSocial to this version.

This release also contains a long-ass database migration to move status boolean columns (like pinned, local, etc) to a single bitfield column. This saves a lot of space in the database, but it also means on startup the migration has to iterate through all statuses in your database and set the new field. Please be patient and don't interrupt this process! ⚠️⚠️⚠️

Release highlights

• Relay support: GoToSocial now supports subscribing to relays (as an admin action), and pushing posts to relays (configured per-user, with filters available).
  Documentation for admin-level relay subscriptions.
  Documentation for user-level relays pushes.
• Automated cleanup of old remote posts: you can now configure your instance to clean up threads of remote statuses that haven't been interacted with by anyone on your instance. This should save a lot of space in folks' databases!
  Documentation for post caching + pruning.
• Delivery error tracking for remote instances: there's now a page in the settings panel where admin can view errors encountered while attempting delivery of posts to instances that may be experiencing technical difficulties or may have gone offline. You can use this to get a quick view on possible "dead" instances that you can then remove from your database with a domain block.
• Accounts directory: there's a new setting to allow admins to expose (or not) a directory of accounts on the instance! Your account will only be shown in the directory if you opt in via your privacy settings.
  Documentation for inclusion in account directory.
• Better tracking of deleted statuses/status tombstones: GtS now stores tombstones for deleted statuses, allowing threads to remain intact even when a status in the middle of the thread has been deleted.
• Better status codes + info pages on deleted or hidden statuses: the old 404 page when you try to open a hidden status in the browser has been replaced with a more informative error page.
• Way more configurable http server + client options: we've exposed a whole shitload of settings that you can tweak on the HTTP client + HTTP server that GoToSocial uses. We don't recommend changing these, but if you really want to, now you can.
• Show your Träwelling status on your profile by setting your Träwelling page as a field value, similar to how our ListenBrainz integration already works.
• Allow setting a name for your tokens, and sorting tokens by last used time in the token view of the settings page. Should make it a lot easier to track which tokens you've created, and when they were used by which apps!
• Better layout for web view of profiles that hide all posts from the web: it just uses a single-column view now.

Thank you for reading and happy pride 🌈

dysfun@treehouse.systems ("gaytabase") wrote:

one of the big things that annoys me about this is that you cannot ultimately know what things are going to perform like until you've basically written the whole thing. you can make informed design decisions, but ultimately until you've ingested the data, you aren't going to get any numbers to validate your theories.

it had better be very fast when i'm done or i will cry.

dysfun@treehouse.systems ("gaytabase") wrote:

part of the problem with portability is that now it's disk-backed, you're stuck with the layout you used when you wrote it. thus, it would be incredibly beneficial if the format was always the same regardless of the hardware capabilities.

unfortunately, what i worked out for the in-memory predecessor to this was that one great way to improve performance was to take advantage of the hardware that was available by reorganising layouts.

anyway, i eventually sorted it all. it's still a bit of a compromise and it's not optimal everywhere, but at least the cpu part is going to get lost in the noise when you consider I/O. wasted padding per branch node is capped to a cacheline. i'm far more worried about wasted disk block space around leaves, where i'm just hoping that loose ends will end up being statistically uncommon when i'm done.

fromjason ("fromjason.xyz ❤️ 💻 ✍️ 🥐 🇵🇷") wrote:

Oooooo I'm gonna try to use my candle today! Been avoiding scented stuff. I think I'm good? Ahhh I miss my candles.

Boosted by jsonstein@masto.deoan.org ("Jeff Sonstein"):
solar_chase@mastodon.green ("Jenny Chase") wrote:

This is Germany - solar supply of 47GW at 2pm on that Tuesday, of grid load of 57GW. Solar was still supplying 18.8GW at 5pm. Can you imagine the situation 20 years ago when that solar contribution would have been negligible?

dysfun@treehouse.systems ("gaytabase") wrote:

on x86-64 support, i decided to require x86-64-v3, but cover the amd bug where an important part of that was slow before zen 3 with some polyfills (which while they certainly won't be as fast as the 3 cycles you'll get in a proper implementation, are much, much quicker than the hardware - i know this because i am typing on affected hardware).

so there are two implementations just of PEXT. then we have avx512 as an optional feature. so just the read path has 2 choices each of 2 features.

i say just the read path, because the write path can take advantage of yet more avx512 that you're not guaranteed to have, so we have to polyfill that if you have avx512 without the extra features.

the original HOT never bothered with AVX-512 (it wasn't very widely deployed at the time), and i can say it has definitely been a lot of work adapting it to use avx-512 in places, but the rewards are hopefully worth it. i wouldn't actually know because i don't have AVX-512 support locally so i'm going to have to wait a long time to see if my theory pans out on that...

dysfun@treehouse.systems ("gaytabase") wrote:

yesterday i started some work on the insert path of the database. now that it's just a k/v store and i've reduced the x86-64 support to just over a decade, it's gotten a lot more tractable and at least the memory side of things is verging on paint by numbers at this point. i just have to cobble together all the bits i've already written, make some tweaks and fill in the holes.

buffy the buffer slayer still has many question marks at this point. i have to sit down and come up with a design that doesn't involve readers writing to memory much. reads are cheap, writes are not, so readers should preferably only read (i.e. no refcounting).

dysfun@treehouse.systems ("gaytabase") wrote:

Domain Driven Development (DDD) - buying a domain name to attempt to force yourself to write the software it's for.

Boosted by jonny@neuromatch.social ("jonny (nonvenomous)"):
janamarie@mystical.garden ("Jana") wrote:

more IR shots. I just love the luscious pink leaves and blue skies..

(writeup on how I take these: https://blog.janamarie.dev/irphotography.html)

#photography #infrared