MrCopilot

Applications depend on data to function, and in the modern world that data is usually stored somewhere up in the nebulous concept known as the "cloud" but is actually a computer processing your requests and spitting back data. During the development of an application decisions about how to supply the required data and service those requests for more must be made.  Here is a non-exhaustive list of options: Real live production Actual Data. That poor lil computer in the cloud did nothing to deserve being pummeled with malformed and/or repeated requests for the same data during live testing. Let alone tortured with automated testing on every commit. Be a considerate developer. Local Representative fake Data This is a good starting point. It has the unfortunate side effect of having to be manually updated, maintained, and carefully constructed with every edge case.  Local Cached data captured from live session. Few downsides, requires vigilant maintenance and api level checks and...

After a week of poking and prodding, installing, configuring, and much studying of documentation, code, infrastructure and general vibe & culture, and in the spirit of my new motto, " You can complain or you can help ", Here is where I am on Tokodon: The Bug that brung me: I haven't even filed it. Bad developer. Quote post do not display properly in notifications timeline. Added code to display the quoteposts but header still missing. These unknown posts fill the More->Posts list for some reason when present. That reason is the quote type I added was not excluded from the any of the exclusive lists, boosts, replies, mentions, follows...FIXED it also wasn't handled properly anywhere else FIXED This was likely missed in test as notification test data json was missing QuotePosts I mangled the json data, KDE CI let me know via email after I had gone to bed. Basically the equivalent of pushing unreviewed/untested commits just before clocking out on Friday at 5:01pm....