Posts by polyphonychat@amazonawaws.com
 (DIR) Post #B4IVRq7BtqbMTmJpcu by polyphonychat@amazonawaws.com
       0 likes, 0 repeats
       
       transgender discord
       
 (DIR) Post #B5hN8zx3CydcbTauKu by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       A very first version of altmaid is now available to try out! Altmaid takes a markdown file containing mermaid sequence diagrams, deterministically generates alt text and adds that alt text back into the file.I have been too tired to create a tagged release, publish on crates.io or write a full announcement post, but the README contains a lot of information, and I am also very happy to answer questions. A better, follow-up post will be made in the future ​:neobot_salute:​ -@star
       
 (DIR) Post #B5tu4TavCHjFTaDL4y by polyphonychat@amazonawaws.com
       0 likes, 0 repeats
       
       πŸ—οΈ codeberg.org/polyphony/repo-slopscore under construction! ​:ablobcatwobwork:​ repo-slopscore will be a CLI + webapp, with which you can scan any public, https://-accessible git repo for signs of slop activity from all sorts of different LLMs and AI tools. It will calculate a "slopscore" and give a tier from S to F for how much slop activity has been detected. We'll let you know once you can try it out yourself! ​:neobot_melt_happy:​
       
 (DIR) Post #B5tu4TmyTTN04xqxrk by polyphonychat@amazonawaws.com
       1 likes, 3 repeats
       
       Are you tired of having to manually traverse commit histories to find out whether a repository has been made using AI/LLMs? There's now an easier way!You can access the first version of repo-slopscore at slopscan.ava.pet, paste in https:// git repo URLs and have it scan repositories for signs of AI activity. The source code is, of course, available at codeberg.org/polyphony/repo-slopscore!The prototype is most definitely rough around the edges, but also functional! You can read more about how the internals of it work in the README.md in our repository! ​:neocat_boop_blep:​RE: fed.amazonawaws.com/notes/alrwb40eqhsxkxpb
       
 (DIR) Post #B5uwwE1JiD3psSHGOu by polyphonychat@amazonawaws.com
       0 likes, 0 repeats
       
       I would appreciate feedback on the idea of adding "healing" to repo-slopscore: codeberg.org/polyphony/repo-slopscore/issues/9This idea is the result of feedback I have received here overnight. ​:neobot:​ ​:neobot_floof_happy:​
       
 (DIR) Post #B5vsQsDIX9jMbpdVg0 by polyphonychat@amazonawaws.com
       1 likes, 1 repeats
       
       repo-slopscan has been updated with a more accurate detections database! More agents get detected and the (by far) most common false-positive has been eliminated.Repositories scanned with outdated detections will display a message and button like seen in the attached image, prompting you to re-scan this repository for more accurate results ​:ablobcatwobwork:​RE: fed.amazonawaws.com/notes/alsi1chf1zq8accw
       
 (DIR) Post #B5xZ3PuW5UhtM7sB2O by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       repo-slopscore now shows you when the AI detection signals were authored in the repository. ​:blobcateyes:​ This piece of information is a first step in making it easier to see whether a repository has revised their AI/LLM policy, i.e. whether the AI commits are already long in the past.On repos that have already been scanned, you can simply click the "Re-scan this repository" button to fetch this information for any repository. ​:blobcat:​
       
 (DIR) Post #B6Mdb5sgJwDbqjKJHc by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       ​:asparkles:​ Repo Slopscore (source code), our tool to scan for AI activity in git repositories, has been used to scan over 1000 different repositories now! ​:cowsparklyeyes:​ ​:sparkles_lesbian:​
       
 (DIR) Post #B6VEbxe1gCaQAAQZtI by polyphonychat@amazonawaws.com
       0 likes, 2 repeats
       
       December 12th is the targeted date for a v0.1.0 release of sonata, our @polyproto core home server implementation.Planned for this initial proof-of-concept version are all features required to federate identities and verify messages sent from other people on any home server. Functionality/features above that are not likely to be included.
       
 (DIR) Post #B6reOQSp5HBT8hGMVs by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       Polyphony would like a new name. What do you think would suit us? ​:neocat_polyproto:​
       
 (DIR) Post #B6ri3MhWHN5VCiLlpI by polyphonychat@amazonawaws.com
       0 likes, 0 repeats
       
       @Stellar pestilence
       
 (DIR) Post #B6rlZX4vWyiwWDKSBs by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       What about just "poly"
       
 (DIR) Post #B6rlaGNb6POf19PV2W by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       Alternatively: "cule"
       
 (DIR) Post #B6rt0Svpktzv9iridc by polyphonychat@amazonawaws.com
       1 likes, 0 repeats
       
       @natty @ShadowJonathan wolpchat/fopschat
       
 (DIR) Post #B6rzQyIoLHqPhidR8y by polyphonychat@amazonawaws.com
       1 likes, 4 repeats
       
       HAPPY PRIDE MONTH YA FILTHY ANIMALS ​:neobun:​ ​:blobcat:​ ​:neodog:​ ​:neocat:​ ​:neofox:​ ​:neocat_polyproto:​ ​:neopossum_flag_transbian:​ ​:verified_rainbow:​ ​:verified_gay:​ ​:verified_enby:​ ​:verifiedbutch:​ ​:verifiedbi:​ ​:verifiedace:​ ​:verified_trans:​ ​:verifiedfemromantic:​ ​:verifiedmlm:​ ​:verifiedpansexual:​ ​:verifiedsapphic:​ ​:verifiedtransbian:​ ​:verifiedtransmasc:​ ​:verifiedtransfem:​
       
 (DIR) Post #B6tgXIa0M4STW9ttrs by polyphonychat@amazonawaws.com
       0 likes, 1 repeats
       
       * confetti-bombs ur carpet with rainbows *oops sorgy ​:neocat_angel_pleading:​ <- is actually not sorgy at all ​:neocat_devil:​