Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Apollo Back end just made public

old.reddit.com

Post reply on HN
Print view View original

51–60 of 242 posts

Re: Apollo Back end just made public

#51

Post by qball »

wkat4242 wrote: post #9
spiderfarmer wrote: post #2

All this backlash is going to kill Reddit. It will take a thousand little cuts for sure, but it started the moment they announced their ludicrous pricing.

I wonder.. The very same thing hardly seems to have hurt Twitter.

Maybe so, but Reddit is not Twitter; API access is far more important for Reddit because its official client is garbage and can't handle the long-form content that Reddit is known for.

This will have outsized implications for the 1% of users who actually post the content the other 99% come to see in a way that Twitter (and its 280-character comment limitation) does not.

Re: Apollo Back end just made public

#52

Post by 542458 »

AndrewKemendo wrote: post #12

What if all the blackout communities move to an open source, community funded, community owned and run version of Apollo? I’d be happy to try and convince my 100k community to Apollo and if the UX is similar for web and mobile then I’m not sure switching costs would be that high during the blackout. I’d help fund it but all my money is wrapped up in my trash cooperative.

I haven’t seen a compelling OS alternative to Reddit yet. The ones I’ve seen have all either been big on decentralization at the expense of long load times and a lot of UI complexity, or big on 4chan-style dialogue with little moderation. Neither of those sounds like a great migration path. IMO this is the same problem “migrate off Twitter” efforts had.

Re: Apollo Back end just made public

#54

Post by pbronez »

AndrewKemendo wrote: post #12

What if all the blackout communities move to an open source, community funded, community owned and run version of Apollo? I’d be happy to try and convince my 100k community to Apollo and if the UX is similar for web and mobile then I’m not sure switching costs would be that high during the blackout. I’d help fund it but all my money is wrapped up in my trash cooperative.

I was very confused about why you would tie your money up in a cooperative you think is run very poorly, then discovered it’s literally about waste management!

Re: Apollo Back end just made public

#55

Post by pwillia7 »

fron wrote: post #17
trollied wrote: post #8

There's a Reddit CEO AMA later today: https://www.reddit.com/r/reddit/comments/144ho2x/join_our_ce... Can't see it being anything other than a PR disaster for them, unless they change their stance.

It's more than likely that they'll inject their own softball questions and focus on those instead of addressing everyone's concerns in any meaningful way.

good test for the new AI bot accounts

Re: Apollo Back end just made public

#56

Post by pjc50 »

wkat4242 wrote: post #9
spiderfarmer wrote: post #2

All this backlash is going to kill Reddit. It will take a thousand little cuts for sure, but it started the moment they announced their ludicrous pricing.

I wonder.. The very same thing hardly seems to have hurt Twitter.

https://edition.cnn.com/2023/02/10/tech/twitter-top-advertis... : more than half their advertisers quit.

Re: Apollo Back end just made public

#58

Post by revskill »

andremedeiros wrote: post #4

Hi all! I wrote this code, and for educational purposes, I’d be more than happy to answer any questions. A gentle reminder that the whole history is here for show. This is very vulnerable — you can see the times I was in a rush, or when I took my time. You’ll find my mistakes. Either way, all I ask is please be kind. I know there are 50 things I could have done better, but this is a product of the reality at the time…

Are you proud of your code ? Which design patterns do you use ? Any lessons that you've learned to be shared ? Thanks.

Re: Apollo Back end just made public

#59

Post by doublerabbit »

gtsteve wrote: post #24
andremedeiros wrote: post #15

Earlier quoted context omitted.

I’ll check in with Christian and see what he wants to do. Got any particular recommendations?

Some options spring to mind: 1. All rights reserved - the source is visible but not open. 2. AGPL, to ensure that if someone does take this forward, no part of it can be closed source without your agreement. 3. MIT, which is extremely permissive and effectively you don't care what someone does with it, commercial or not. Depending on your comfort level I would start with the middle option, I don't think people tend t…

All rights reserved feels more the right kick to me

Gives those who wish to learn and stops from anything taking the future glory.

Re: Apollo Back end just made public

#60

Post by andremedeiros »

irisgrunn wrote: post #43
andremedeiros wrote: post #4

Hi all! I wrote this code, and for educational purposes, I’d be more than happy to answer any questions. A gentle reminder that the whole history is here for show. This is very vulnerable — you can see the times I was in a rush, or when I took my time. You’ll find my mistakes. Either way, all I ask is please be kind. I know there are 50 things I could have done better, but this is a product of the reality at the time…

Wouldn't it be possible to change it to use Lemmy or some other alternative?

Honestly, Lemmy would probably not need half this code. We wrote this to work with an entity that exists in a “come and get it” model. Lemmy being open source means we could build the features right in the server and slash this code to a bare minimum (mostly the watcher stuff at this point.)
Post reply on HN