• 12 Posts
  • 389 Comments
Joined 1 year ago
cake
Cake day: July 5th, 2023

help-circle








  • Glad to help. Some of the non-ISBN content I’ve read and tracked on StoryGraph is the mega-web-novel Worm and various interstitial PDF mini-stories that an author posted on their website as part of a continuing Sci-Fi series. All of this content on the service is user-input. All you would have to do is create the feature. When I discovered it, I realized how awesome it is to be able to track such content.

    Remember - great artists steal. So go check out the community features on Literal and the tracking features and user-entry features on StoryGraph.


  • I’m loving StoryGraph. I value its vast array of books, audiobooks, internet based “non-book books” (things that don’t have an ISBN). Also, it’s book import isn’t perfect but very nice. Lastly, I love their metrics. They’ve done an awesome job of it and it’s a joy to see them.

    I enjoy Literal.Club for its large number of clubs and high interactivity. There are network effects that Literal has which StoryGraph just hasn’t achieved yet.

    StoryGraph has tried to implement Community and Book Clubs but it doesn’t work the same way - Literal’s Clubs are for discussing books in general, while StoryGraph’s book clubs are focused on reading one book at a time, with deadlines, discussion sections etc.

    A combination of the two which I can pay for would be mind blowing! 😊







  • Part of what you’ve described is market economics. They want your loyalty and they want to track your purchases to sell that data to advertisers. Do they need an app for that? Absolutely not. They can and do host websites with the same deals and all you have to do is login. The reason they push you to their app is because either the app is something they spent a bunch of money on and want to increase customer adoption. Or, they have added massive new tracking capabilities and want to spy on their users on behalf of advertisers, so they need you on their app.

    None of this is related to the technical aspects of this question. In fact, most of these companies would resist you installing their app on an “app server” simply because then they wouldn’t be able to track your location and other phone details easily. Defeating the purpose of your idea.

    Oh, and as for the watermelon - there’s a sweet spot between the prices which is usually $5 if you use their loyalty card and not their app. That’s the price you pay for your phone’s privacy and resources - a buck. Not a fair trade, but it is what it is.

    p.s. I hear you about the three prices thing. It’s frustrating. Grocery shopping is not simple. It’s all about hunting for deals and accepting the time vs money trade off. I’m sorry you are in this situation. I am too.



  • Why does it need to be an app then? And why one server?

    Literally, what you’ve described is the www. The browser is your thin client. It connects to not one but many millions of servers and is able to use their resources to run queries, access menus, place orders. All that jazz.

    Oh, and with the ridiculous advancements in technology, streaming services and games work amazingly too! Video streaming is so well studied that every Tom, Dick, and Disney has started their own streaming service and is charging through the nose for it. Every year, folks get arrested for running Plex servers or IPTV with millions of hours of pirated content that is used by thousands of their happily paying customers (more happy than Disney’s customers).

    And Amazon Luna and Xbox and PlayStation have all shown how game streaming can be so easily done over HTML5. The only blocker on making that the default way of gaming is Apple’s greed. Not that it’s a good default. There’s something to be said about mobile hardware and chip design that has made amazing advancements in the last few years in the GPU space, making on-device processing really worth it.

    Don’t remember what it’s called but there’s an internet law - that any advancement in hardware will immediately be offset by more expensive software requirements which will consume more of those resources. Looking at you, Chrome. Also looking at you, react framework.