I never thought I'd find any underwater enemy scarier than the Dopefish π± π¦ π
I've been studying game dev as a hobby for years but I struggle with the practical stuff.
Making a plan, sticking to it, staying within a reasonable scope, not working myself till burnout... these are all things I've done with poor results and I'm not sure what I can do to prevent further frustration. Any advice?
Who's your favorite kappa racer in Magma Marathon in #KitsuneTails?
Kitsune Tails is OUT NOW!! Run, jump, and dash across a land inspired by Japanese mythology and untangle the love triangle between three young women on a journey of self discovery. Explore the complicated relationships between kitsune and humans through classic platforming action.
get it now on steam https://store.steampowered.com/app/1325260 or itch https://eniko.itch.io/kitsunetails
we're a small underfunded team with a majority queer developers, and while we're punching way above our weight class we need the support of our community if this game is going to be a success. please boost this post, and if you can afford it buy it on steam and leave a positive review on the first day (the text doesn't matter, only the thumbs up, so "i like gay fops" is totally valid as a review)
i also want to prove fedi is powerful enough to make an indie game succeed, so even if you're not personally that into the game, please boost this post? π
Basically, a good way to never trust "it's okay, the data is anonymized" again is simply knowing what the "Hemisphere Program" is.
https://www.eff.org/cases/hemisphere
In short, the US government got access to number from, number to, datetime, length and sometimes location information for every call passing through AT&T's network from 1987 to today.
Then they ran an algorithm to de-anonymize every burner phone based on behavior. They did this because maybe some of those burners were used by drug dealers.
I used "crowdstrike" as a verb at work today, to paraphrase: "CI is broken because github crowdstruck us with a bad rust compiler update". AKA: usable any time an automatic update from a vendor breaks your infrastructure.
All I'm saying is, if they didn't want this neologism, they shouldn't have ruined my flight home from Italy.