#the first three were the only auto entries everything else was submissions
Explore tagged Tumblr posts
Text
Okay, think I've got the list. With apologies to anyone who get cut. I'll start working on grouping everyone tomorrow. In the meantime, if you want to send in infodumps/propaganda about these nonships, by all means do! That will give me something to work with when I build the graphics
James Ironwood and Boyd Drake (RWBY and Ducktales/DTLS)
Isaac "Felix" Gates, David Gates, and Jaune Arc (RvB, Camp Camp, RWBY/Luna Brothers)
Louie Duck and Oscar Pine (Ducktales and RWBY/DTLS)
Knight and Survivor Slugcat (Hollow Knight and Rainworld)
Brett Hand and Susie (Inside Job and Deltarune)
Pizzazz and Roxanne Wolf (Gem and the Holograms and FNAF)
Trunks Briefs and Chibiusa (Dragonball Z and Sailor Moon)
Halloween and Nightcore (Castles of the Calendar and Holiday Spirits)
Mamoru Amami and Steven Universe (GaoGaiGear and Steven Universe)
Penny Polendina and Uran (RWBY and Astro Boy)
Wahuu Matsuri and Adam Ainosuke (Tokyo Ghoul and Sk8 the Infinity)
Jon Sims and Jonny D'ville (TMA and The Mechanisms)
Eddie Munson and Jason Scott (Stranger Things and Power Rangers 2o17)
The Aurora and BEE (The Mechanisms and Archivistbot)
Wakko Warner and Babs Bunny (Animaniacs and Tiny Toons)
Zuko and Todoroki Shouto (A:tLA and BNHA)
Diamonds Droog and Kaz Brekker (Homestuck and Six of Crows)
Tucker Foley and Clawdeen Wolf (Danny Phantom and Monster High)
Team Lit (from White Boy Bracket)
Stanley and Cesare (from White Boy Bracket)
Cody Burns and Penny Proud (Transformers Rescue Bots and The Proud Family)
Leo Walker and Iris (Egyxos and Lolirock)
Tim Stoker, Lup and Taako (TMA and TAZ)
Globine and Webby (Globi and Ducktales)
Rouge the Bat and Meta-Knight (Sonic and Kirby)
Jevil, Marx, and Dimentio (Deltarune, Kirby, and Super Paper Mario)
Ruby and Rarity (Pokespe and MLP:FiM)
Madoka and Sakura (Madoka Magica and Cardcaptor Sakura)
Cody Burns, Marinette, and Mirabel (Rescue Bots, MLB, and Encanto)
Bill Cipher and Ouma (Gravity Falls and Danganronpa)
Church and Kris Dreemur (RvB and Deltarune)
Gregory, Crying Child, and Omori (FNAF and OMORI)
Sonia Nevermind and L (Danganronpa and L)
Cassandra Cain and Soundwave (DC and Transformers)
Dick Grayson and Drift (DC and Transformers)
Tim Drake and Red Alert (DC and Transformers)
Rook Blonko and Prowl (Ben 1o and TFA)
Bruce-Damian Wayne and Tony-Morgan Stark (DC and MCU)
Pit and Sora (Kid Icarus and Kingdom Hearts)
Rosaline and Lucas (Super Mario Galaxy and Mother 3)
Roy and Roy Koopa (Fire Emblem and Super Mario Bros)
Meg Griffin, Bert, and Ernie (Family Guy and Sesame Street)
Riley Freeman and Jack Horner (Boondocks and Puss in Boots)
Stanley Parable and Arthur Dent (Stanley Parable and Hitchhiker's Guide)
Chidaruma and Lord English (Dorohedoro and Homestuck)
Ruby Rose and Fukase (RWBY and Vocaloid)
Yang, Gumi, and IA (RWBY, Vocaloid, and Cevio)
Leonardo, Dewey Duck, and Sonic (Rise:TMNT, Ducktales, and Sonic movies)
Nightcrawler and Nightwing (DC and X-Men)
Alfred, Bucky, and Steve (DC and Marvel)
Yelena Belova and Damian Wayne (Marvel and DC)
Ventus and Hunter (Kingdom Hearts and The Owl House)
Mark Beaks and Tyrian Callows (Ducktales and RWBY/DTLS)
Lancer and Bowser Jr (Deltarune and Super Mario)
Shigeo and Molly McGee (MP1oo and The Ghost and Molly McGee)
Isabelle and Doomslayer (Animal Crossing and Doom)
Mystery Kids (?)
Gentle Heart Lamp and Chris Walker (CareBears and Outlast)
Grumpy Bear and Billy Hope (CareBears and Outlast)
Boyd Drake and Penny Polendina (Ducktales and RWBY/DTLS)
Maya Fey and Doctor- 12 (Ace Attorney and Doctor Who)
Mario and Sonic (Super Mario Bros and Sonic franchise)
Han Solo and Peter Quill (Star Wars and MCU)
Commander Fox and Commissioner Gordon (Star Wars and DC)
#believe it or not a couple of those dtls ones were submissions ^_^#the first three were the only auto entries everything else was submissions
30 notes
·
View notes
Text
Version 434
youtube
windows
zip
exe
macOS
app
linux
tar.gz
I had a great three weeks working on long overdue network updates. Most of the changes this week restore old account management UI for server admins, but there are a couple of fixes and improvements for regular users as well.
The network version goes up to 20 today. Clients and servers can only talk to each other if they are on the same version, so if you want to talk to the PTR, you will want to update at some point. No rush, but if you try to talk to the server on an older client, you will get a polite error message.
regular user stuff
On review services, you can now pause repository account sync, update downloading, and update processing separately. If you don't want to process right now but still want the client to be grabbing update files for later, or you want to pause all service network traffice for a while but still process your backlog, it should now be easy to set up.
I fixed an annoying bug where going from 'random' file sort to one with asc/desc sort order by loading a favourite search would always default the asc/desc to the top value. Guess what hydev's default sort is.
Server administrators can now set messages to accounts. If you get a message, your client should get the update within a day or two, at which point it will appear in a popup box and be viewable on review services.
Server administrators can now set some account types to be user-creatable--no need to mess around with registration keys or access keys yourself, the client can fetch them for you from the server. A new button on the manage services edit panel checks this and can do it for you. I understand the PTR is likely to move to this in future for accounts with sibling and parent petition permissions, since grouping these by account will be useful for janny petition workflow. Having separate accounts for these complicated uploads will also allow better account management (including the above rudimentary messaging) for users who make common errors with sibling or parent submissions.
I believe I fixed a bug in repository processing that caused some newer users to get stuck with siblings and other data that was later deleted. This should not happen again, and I am now planning ways to efficiently fix the problem retroactively. (If you were hit by this and want the non-efficient fix, hit 'reset processing->reprocess content' for the repo under review services).
Some users recently got some scary errors about an invalid repository update file. This was the result of the client becoming confused about which update files it should have for a repository. I am still investigating why this happened, but to fix the immediate issue I have added a maintenance routine (under the new review services->reset downloading) that triggers a full resync of update metadata and delete surplus records. This function will fire automatically in future if the service encounters borked update files of any kind. If you got these errors, please try firing it and let me know how you get on.
admin improvements
After a very long delay, account management is finally back. If you have permission to modify accounts, the 'modify an account' service admin menu item works again and launches a fully revamped window. You can also launch account modification from manage tags for a particular tag selection, the thumbnail right-click for file repository files, or the petition processing page.
The new window shows better data about accounts, and lets you zoom in on individual ones to see current account type, expiration, banned status, or message. It also shows if you are editing yourself!
The account modifications are: change account type, set/extend/clear account expiration, ban, unban, and the new 'set message'. All modifications now print janny and subject account key to the server log. I removed the old 'superban' (which deleted all that user's content contributions), but it will likely return in future.
The service admin menu also has a new 'review all accounts' entry that lets you see a simple summary list of all accounts, which you can then select for modification.
The manage account types dialog now lets you set up auto-account creation. It works a bit like subscriptions, with a 'account creation velocity' limit of 'x accounts per y time delta', like '10 per day'. This defaults to off obviously, but if you set some account types to auto-create, users will be able to see that in manage services.
future admin improvements
As always, there was much more I wanted to do than could get done. I wasn't able to finish improving petition processing workflow or add custom update duration, a serverside tag filter, or a server message, but I was able to get the important network stuff done I needed for these things. Since incrementing the network version is always such an obstacle, I am confident I will now be able to work on these things in normal weekly work. Please let me know how they work out for you as I roll them out.
full list
network updates:
the hydrus network version is now 20. update your clients if you want to keep syncing with the PTR! no rush, but if you try to talk to a new server on an older client, or _vice versa_, you will get a polite error message
most of the updates this week are for server administrators and jannies. I have reactivated old functions that were broken long ago and added some new features. the rest is mostly code cleanup and refactoring, improved error handling, preparation for the future, and other unexciting (but still important) work that had piled up
.
clientside network/repo stuff for regular users:
repositories now have separate pause/play for account sync, update download, and update processing. the confusing old 'working' button is replaced with separate pause/play bitmap buttons
admins can now attach a message to individual accounts. if you get a message attached, you will see it as a popup message, and on review services, after the next account sync (within a couple of days)
a hydrus server may now allow automatic account creation. a button to check for creatable account types and then create a new account is added to 'manage services'. the PTR is likely to move to this sort of system for upload siblings/parents permissions, where getting away from my shared blob mega-account will make it easier to group petitions in the janitor workflow
a logical bug in repository update processing order is fixed. I believe this was the source of some bad siblings for new users who did a lot of syncing in one go. there is no efficient re-processing fix available atm (you'll want 'reprocess content' atm), but I plan to split processing into more pause/play for mappings/siblings/parents, which should add more 'reprocessing' tools
I cleaned a bunch of the UI code related to networking--in manage services and elsewhere, so there should be fewer bugs, confusion, and UI lag when using these controls. a whole load is still a mess though!
fixed the 'see special permissions' button in review services
repositories have a new maintenance function, accessed through the new 'reset downloading' button on review services, that force-resyncs all update hashes. this _should_ fix the unusual issue a handful of users had with an extra (invalid/404ing) update hash on the PTR. this function will also auto-trigger on various error states. the reason some users had an extra update hash in storage is still under investigation
.
other stuff, mostly boring:
fixed an issue with the new file sort asc/desc button where a transition from 'random' to another sort type using a favourite search would always reset the sort order to the top value
my asynchronous job object now has a default errback to catch errors more gracefully by default and with special handling in future. clicking an async button in a dialog will now show you the error there and then, rather than just the hidden error popup on the main window
added convenience links to the latest build on github to the help menu and html help
fixed another place in local file importing where a file that did not pass file import options checks would set 'skipped' status. in now sets 'ignored' like everything else
fixed a bug when an 'undelete' call is sent to the media viewer when no media is set (usually during startup/shutdown)
I disabled progress gauge 'pulsing' across the program. the way this was first implemented applied too often--I will bring it back to only apply when a job is both indeterminate and currently working
my custom button class can now launch its own yes/no confirmation dialogs on click
removed a subtag regen routine in the 425->426 update step that was bugging out due to bitrot--it now makes a popup message on boot asking for the routine to be run manually
fixed a typo bug in the 'subscription snapshot' debug command
misc ancient python 2-to-3 code cleanup
updaned cloudscraper to 1.2.58
.
admin stuff:
.
account modification:
after a very very long delay, account modification is back. if you have permission to manage accounts, you can directly modify accounts using an account key from the services->admin menu, or for tag repositories you can do it from 'manage tags' from the cog menu on a selection of tags, or for file repositories you can do it from the file right-click menu on an uploaded file, or any petition processing page if you have modify accounts permission
the available account modification routines are: change account type, set/extend/clear expiration, ban, unban, set message (new!)
the modification routines now print summaries to the server log when they fire, including janny and subject account key
the server admin menu now lets you see a list of all the accounts on the service, and also launch the new modification window from it for a selection of accounts
the account modification window is also no longer a dialog, but a normal panel that lets you interact with the rest of the program while open
the modify UI is now completely async. it loads account information in the background, and all server modification commands and subsequent account refreshing are the same
the modify UI now lists separate row summaries, including account type and banned info, for all the accounts it is loaded with. accounts can be checked to apply actions only to a subset. you can also copy the checked account keys
the modify UI also highlights if you are one of the accounts being modified, kek
the modify UI now shows ban, expiration, and message info, and the 'account info' dict (which is still not great, but can be extended in future), for any listed account when it is clicked
I have dropped 'superban' (which deleted all the account's previous content contributions along with the ban) for now. it'll likely return in one form or another in a future account permissions overhaul
fixed some dedupe and de-surplus bugs in the 'modify accounts' logic
fixed some account ban status presentation logic
the UI code has been cleaned up generally
retired the old 'get an account's info' admin menu item, since modify accounts dialog now fetches this better
hydrus accounts now synchronise twice as fast, every 250,000 seconds
.
account types:
account types now support optional automatic account creation, default off. it works like a subscription file velocity--'x new accounts per y time delta'.
modifying account types now prints summaries, with janny account key, to the log
account types now use a newer data serialisation format. the way they are tracked behind the scenes is neater
.
petitions:
I did not have time to do the petition overhaul. however, I have prepared the network for it, and I have a plan, so I hope to be able in the coming weeks to improve fetch time for petition counts, make a summary list of all petitions, and implement background petition fetching to improve turnaround time
the petition UI now has a button to copy the petitioner's account key (e.g if the janny wants to send it to an admin with account modification permission)
.
service options:
hydrus services now have a separate 'options' object that is synced to all clients alongside account sync. this will be expandable in future without network version hassle
the options object now contains stub values for 'server message', 'update period', and 'tag filter'. these values are not yet editable, but I will add them and plug them in in the coming weeks
.
boring network/repo update stuff:
services now print to log when they host on a port. this applies to the server and the client (for client api and local booru)
the repository update routine is now careful to process updates in index order--previously they were unintentionally processed in pseudorandom order, meaning if the processing backlog was long enough, certain add/delete updates of bad content could occur in reverse order. I believe this was the source of some odd persistent bad siblings some users saw after doing a lot of first-time 'catch-up' processing when first syncing with the client
the server tracks account_type_keys and account_type_ids in a more careful, service-specific way. all access and modification of account type is cleaned up
the AccountType object is graduated to the new serialisation format. the server db stores them in a new table and will convert all legacy objects on update
deleted the double-ancient YAML AccountType
critical network errors during repository download are now handled a little cleaner and trigger a metadata full resync
the server is better about exiting cleanly--last-minute repository metadata changes and very recent session keys are saved
wrote a new account account type change routine for the server. it prints a summary, including janny account key, to the log
wrote a new account expiration set/extend modification routines for the server. they prints a summary, including janny account key, to the log
wrote a new ban routine for the server. it prints a summary, including janny account key, to the log
wrote a new unban routine for the server. it prints a summary, including janny account key, to the log
wrote a message-set routine for the server. it prints a summary, including janny account key, to the log
restored and expanded old server db tests for service creation, account initialisation, account type addition and deletion, registration key/access key/account generation, basic mappings addition, account identification by mapping content, and account modifications: account type, ban, unban, set expires, set message
fleshed out and fixed old server unit tests
refactored a bunch of server and network code, including to new 'networking' modules, and added a heap of type hints
refactored all the server-client variable de/serialisation code, and a bunch of network object code
refactored clientside service ui to a new file
refactored client network and service panel gui code to new modules
refactored the client manage services edit panels to their own, less confusing and coupled, classes
refactored the client review services panels to their own, less confusing and coupled, classes
cleaned up the clientside service ui, added and migrated to nicer new async functions for server calls
cleaned a ton of server and network code in general
cleaned up some json/POST variable parsing
cleaned admin service menu code
next week
I will catch up with the regular work I missed over the three weeks. I will also try to get optional update duration done for the server. And lastly, I absolutely want to figure out macOS releases that work on Big Sur, which is another thing I have left for too long. The test github build some users have been working on apparently works, so I just have to integrate their script into my own github build routine and, fingers crossed, we should be good.
0 notes