i feel really weird about people who say not to include the ai model in co-authored-by i feel like it's pretty apparent at this point that i'm very against ai contributions but i feel like it's a good thing to know if a commit was ai generated so i can avoid projects that are very dependent on it i guess the argument is "don't advertise for big tech's ai" but i'd rather know that you are actually using ai rather than having that obscured to old prs or not disclosed at all
@iam this is how i've felt for a very long time i'd say threads' fediverse support ended up being fairly inconsequential for most users but i very much like the existing community, even with its issues, over meta's shit
would there be any interest in a c# and maybe python wrapper for the iceshrimp api? i can't guarantee i'd keep it completely up to date all the time but it may be useful to someone it'd basically be regular api stuff and i can probably fire an event on notification if you want to listen instead of just running it one shot this wouldn't be any official capacity but i'm probably the most familiar with the api
for reference the iceshrimp scope allows clients to create a linked iceshrimp api session from a mastodon api session it has a warning on it because the iceshrimp api is not scoped (except for roles) as the frontend needs to be able to do anything with it
@pancakes@meow.company
. i use arch 
on desktops and debian 
on servers. this cat bites @CaptAsh :3
1💜1
1❤️1
1
1