• 2 Posts
  • 41 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle
  • The common thread I’ve seen online is this:

    • Google’s search algorithm sucks. I always append reddit.com to get good forum results
    • Reddit’s search algorithm sucks.

    These two tools are quickly becoming coupled for Google-Fu expert users. The historical forum history that goes back 3-5 years on Reddit is their goldmine. You can’t just make a new subreddit overnight when a sub gets paywalled. All of that historical data will be lost and paywalled.

    I think a paywall could be an effective money maker for Reddit because they’ve basically become their own Google - in that each subreddit acts like a unique website with real, human, responses. The only problem is that reddit has a god awful search algorithm that they refuse to improve. So people use Google to essentially search reddit. The “whales” so-to-speak are the only people they need to capture. People like myself (frugal people) aren’t in their peripherals. But the people that think “I’ll pay each month for NYT” or “it’s just a few dollars for the WSJ” are going to use the same logic for Reddit: “it’s a small amount of money to have access to high quality forums on X, Y, and Z”.

    In addition, this might bolster Reddit’s content even further. Since paywalled subs will automatically reduce the amount of AI content spammed on them, they will inherently increase the legitimacy of each forum.

    Lastly, this will give them a path towards monetization for moderators which doesn’t require them skimming off of their own pay checks to achieve it.

    Do I like this? No. Is this fair? Also no. People contributed to Reddit under the impression that their data would be available and accessible to anyone with an Internet connection. That implicit guarantee is being violated. It’s an afront to the hard working individuals that have developed these communities brick by brick.

    But does this “solution” make a lot of business sense? Possibly. As long as they survive the changeover in the short term, I think they’ll thrive from this choice for the reasons I stated above.

    Again, it’s going to give them a pathway for:

    • Monetization
    • Reduce AI spam (a big fear of all forums)
    • They could make even more money off the back of this

    I’m pretty much over Reddit anyways. Lemmy has been my backup social media for a while now. The Internet is still free - for now. I just hope we can all find better search engines and forums in the future. Google has been degrading. Reddit has been locking things down. We obviously need to pivot to other platforms. Or maybe just go back to the old days where you find niche forums hosted by some dude in his basement. Nothing wrong with that.




  • Display and layout rules aren’t difficult at all. Maybe I’m just not experienced enough. I’ve been a web dev for nearly a decade now and I feel like I’ve got the hang of it. That being said, I don’t work on projects that have to work on everything from a Nokia to an ultra wide monitor. We shoot for a few common sizes and hope it clears between edge cases nicely. What is an example of something that wraps randomly?


  • Genuinely, though, CSS is fairly clear cut about the rules of positioning and space. Relative positioning is one of the most important concepts to master since it allows things to flow via the HTML structure and not extra CSS. Fixed positioning is as if you had no relative container other than the window itself. Absolute positioning is a little weird, but it’s just like fixed positioning except within the nearest parent with relative positioning.

    Everything else is incredibly straight forward. Padding adds space within a container. Margins add space outside a container. Color changes text color. Background-color changes the background color of an element.

    Top, left, right, and bottom dictate where the element should be positioned after the default rules are applied. So if you have a relative div inside a parent which is half way down the page, top/right/left/bottom would move the element relative to it’s position within the parent. If you made the div fixed, it would be moved relative to the window.

    Lastly, if you’re designing a webpage just think in boxes or rows and columns. HTML can define 75% of the webpage structure. Then with just a bit of CSS you can organize the content into rows/columns. That’s pretty much it. Most web pages boil down to simple boxes within boxes. It just requires reading and understanding but most people don’t want to do that to use CSS since it feels like it should just “know”.

    As someone who has built QT, Swing, and JavaFx applications, I way prefer the separation of concerns that is afforded us via HTML JS and CSS.












  • Captain Janeway@lemmy.worldtoProgrammer Humor@lemmy.mlCSS Humor
    link
    fedilink
    arrow-up
    26
    arrow-down
    1
    ·
    edit-2
    6 months ago
    #moustache {
      position: absolute;
      bottom: 10px;
      margin: 0 auto;
    }
    

    If that doesn’t work:

    #moustache {
      position: absolute;
      bottom: 10px;
      left: 50%;
      transform: translateX(-50%);
    }
    

    Relative positioning is preferred but not always available if the parent face is positioned absolutely.

    Edit: adjusted bottom from 0 -> 10px since 0 would be at the bottom of the chin but there is obviously some padding to bring it nearer the lip





  • Captain Janeway@lemmy.worldtolinuxmemes@lemmy.worldHtop too
    link
    fedilink
    arrow-up
    5
    arrow-down
    1
    ·
    7 months ago

    Is there a perfect scheduler that is non-optimal in the Big(O) sense but is optimal if you’re looking at maximizing hardware utilization? In other words, scheduler that takes a long time to determine CPU utilization for each process, but provides an optimal total CPU utilization? I realize that it would not be ideal since we’d essentially have these “sudden stops” as it recalculates the schedule. I’m just more interested in the theory.