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

help-circle

  • kimli@lemmy.mltoAsklemmy@lemmy.mlTips for a new user!
    link
    fedilink
    English
    arrow-up
    4
    ·
    edit-2
    1 year ago

    If you know of a community and you can’t find it in all, paste the whole URL in the search field ( https://lemmy.ml/c/linux ) and then you can subscribe.

    This indicates your instance there’s someone interested in this community and it’ll start getting future content

    Only the first user would need to do this, for those after, the community will show when searching in all

    Edit: autocorrect


  • This is not complete by any means but this is what I did (recently):

    • Explore around: Currently there’s an influx of new user and communities (subreddits) being created. Total users has doubled (give it take) in 10 days. Active monthly users has increased 6x in the same 10 days
    • Try to engage: For many (most?) of us this is a brand new place. Not so long ago it felt rather quiet (I remember taking a look a few months back and thinking “It’s a cool idea but there’s not enough content”) As a forever lurker, this has been easier said than done. The vibe I get (YMMV) is from early Slashdot / Slashdot clones, only much more vibrant. I haven’t seen something similar in a really long time
    • Missing content? Either you wait (keep exploring) or become proactive. Even if you intend to hand it over down the line, create/start building any community you are missing. For those that are joining after you, it’s reassuring having a moment of “Hey, here there’s also interest in $RANDOM_THING”
    • Be aware of size: Recently I was taking about this. Some "not so large subreddits " have 10x users subscribed as users in the whole “lemmyverse”? “lemmy ecosystem”? (I’m still not sure how it’s named)
    • The system is quite new and has had a sudden explosion in popularity. Be prepared to see some rough edges here and there.

    A couple of things that might be odd to get your head around:

    • Instances: Although you can think of instances as a “whole reddit” they all work together. Both of us are on different instances and I’m commenting on your post. I’m not even sure without scrolling on which server resides the post
    • Fediverse: The collaboration is not constrained to instances alone. I was engaging (from Lemmy) with a post originating on a different platform (kbin) and checking how it looks on a third platform (Mastodon). The analogy might be bad, but think of commenting from Reddit on a post originated on digg and checking how you see/comment on it from Twitter.

    But the most important part, enjoy your time here


  • At least, I understood it in some other way.

    With some “back of the envelope” calculations (using Reddit provided revenue and user number) Reddit’s revenue (not earnings) / user month is $0.12 , around $1.4 user/year

    In the case of Apollo, the “intended” revenue per Apollo user would be $2.5 per user month, around $30 user /year

    From the body of the post, search for the following header: Why do you say Reddit’s pricing is “too high”? By what metric?

    The $20 Million is what would cost to continue using the API with the intended price point.

    Also, $500.000 year would be revenue, not earnings. As I understood, he’s not a “solo” developer working in his basement. There’s people and infraestructure to pay from that number (I don’t know neither how many people nor how much costs “keeping the lights on”, but anyway, I don’t think those numbers are relevant)

    My own opinion: Let’s say Reddit’s break even point is around the Apollo’s intended cost / user. That would mean that with a revenue of $0.12 per month * user, Reddit would be losing around $800 million / month. That’s close to $10.000 million / year. Even as a ballpark figure, I find it suspicious to say the least.

    BTW: I’ve never used Apollo. RIF user from long long before they had to change the App name



  • It’s been a few years since I used keepalived so my knowledge might be outdated.

    You are correct that the VMs should be in different servers. To test around you can set up on the same, but this shouldn’t be done in production environments, if you lose the host, you lose the service.

    Keepalived will make sure your service is available in an IP. To say, you have two (it can be configured for more than two) servers with (A) 192.168.0.2 and (B) 192.168.0.3 which provide the service you want to provide. With Keepalived you’ll configure a common IP for both of them, let’s say 192.168.0.4

    While working, server A will be available at 192.168.0.2 and 192.168.0.4 while server B will be available at 192.168.0.3. If server A fails keepalived will “move” 192.168.0.4 to server B, so 192.168.0.2 will not be available and server B will be available at 192.168.0.3 and 192.168.0.4.

    No matter which server is up / primary, your service will always be available at 192.168.0.4

    For the mirroring part, you need to solve it in another step outside from keepalived. For example, MariaDB provides multimaster replication “out of the box” with galera (the recommendation is at least 3 nodes)

    For files, depending on your filesystem you should have to rsync, use some shared units, distribute filesystem (Ceph), …



  • I’ve been using Namecheap for personal domains for around 10 years now. Since a few years back, privacy guard is included in the domain price (at least for .com domains) so your name, address, … won’t appear directly on whois queries.

    As it’s just one domain, (longterm) pricewise I don’t think there’ll be a big difference with any of them. 1 or 2 € per year, maybe. It’ll be more important to check longterm price of the domain (.com / .io / …), as you’ll probably find some offer for the first year.

    FWIW, namecheap publishes a recurrent offer around 10th October (apart from some random offers every once in a while) If you go with them, you can register for one year and renew the domain for a longer period when you find an offer.