• 0 Posts
  • 8 Comments
Joined 1 year ago
cake
Cake day: June 24th, 2023

help-circle

  • That ship has sailed… So many sites don’t actually change pages, they just load different data - it’s way faster and looks better

    Problem is, the back button takes you off the site no matter where you are, so now you can change the URL and change the history through code to have the best of both worlds

    Then, there’s the people who do it badly, and there’s the people who think “hey, if you need pro StarCraft level clicking speed to back out of my site, maybe for some reason that will make them decide to stay”


  • As a late millennial and a programmer, I’ve got you.

    So when you request a web page, before anything else, the server gives you a 3 digit status code.

    100s means you asked for metadata

    200s mean it went ok

    300s means you need to go somewhere else (like for login, or because we moved things around)

    400s mean you messed up

    500s mean I messed up

    So this is in the 400s. Each specific code means something - you’ve probably seen 404, which means you asked for a page that isn’t there. And maybe 405, which means you’re not allowed to see this

    418 means you asked for coffee, but I’m a teapot


  • It’s weird to think about, but data has a shelf life. Software needs to grow and be pruned regularly, or it dies.

    Social media is both - the data dump is useless without an ecosystem of tools around it, and if the data itself stops interacting with the zeitgeist of the parent society, it basically becomes an old journal. It’s interesting to a very specific group of people, and literally no one else wants to see it (aside from a few gems picked out and cleaned up for public consumption)

    At any point we could go back to Reddits explosion after the digg migration. We could pull up posts that mirror exactly what’s happening now. It’d be interesting for sure, and there’s days of then-now posts that people could be making…but instead we just have people telling us about their memories of that process.

    Why? Because that data is old and stale. You’d have to hunt it down with tools not intended for it, filter out the best of it, fix broken links, and probably put it through a slur filter


  • Nah, that’s not quite right.

    Tiny federates with huge - nothing happens, they just exchange metadata. Dancer@tiny subs to something on huge - now you have one community, with a lot of updates, coming at tiny. Maybe it drops some. Still not an issue

    Hugo@huge subs to something on tiny - now something@tiny is cached on huge, still not a problem.

    Now something@tiny is in the feed on huge. A million people comment. This is a problem… For huge mostly. Over at little, people are commenting on something@tiny. They might see doubled up comments or orphaned comments, but mostly they just don’t see most of the stuff from huge

    So generally, it’s not an issue. In certain situations, there will be hiccups, but it will keep chugging along




  • I’m considering a free version on the app stores with limited ads(subtle and no tracking), a paid version without them, and one with optional donations on alternative stores.

    I don’t like ads and I don’t want to shove them down unwilling throats, but most people don’t care (and frankly I need the money)

    Among the ones that do, there’s those that hate seeing them, and ones with privacy concerns. If I make them subtle and offer an upgrade to remove them, I hope that’ll satisfy one group, and the other one can get a build where the ad libraries were never installed in the first place