Live data from Hacker News

Apollo Back end just made public

old.reddit.com

181–190 of 242 posts

Re: Apollo Back end just made public

#181
post #17

Earlier quoted context omitted.

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.

When they removed the upvote/downvote count, it was clear reddit was fine with manipulation. Anything I read on the website has been met with extreme skepticism since it very well could be an astroturfer. It's money. Reddit wants astroturfers, it grows their platform and helps sell ads.

> When they removed the upvote/downvote count, it was clear reddit was fine with manipulation

I wasn't a big issue to me tbh. Vote fuzzing had always made those counts meaningless.

Re: Apollo Back end just made public

#182
post #38

GitHub repo link, in case Reddit deletes the thread: https://github.com/christianselig/apollo-backend Interestingly, this seems to just be a proof of concept, and the repo is archived. While the developer of the Apollo front end is getting screwed in this whole debacle, this seems to me like an opportunity. He could literally build an alternate Reddit back end (ok, pay someone to do it, if he doesn't want to do it hi…

The interesting thing is this exact same thing happened in Hong Kong. There was an app for a popular web forum. It got banned and the developers released the code and subsequently someone turned that into the “Reddit of Hong Kong” and outgrew the original forum.

https://en.m.wikipedia.org/wiki/LIHKG

Re: Apollo Back end just made public

#183

Earlier quoted context omitted.

What are you basing this on? Do we have any data regarding the percentages of mobile/old/app users?

I wish I still had the graph, but someone posted something for their (150k subs) subreddit recently, and it was below 10% old. No idea what sub, or what the source was so, so take this with a pitcher of salt.

It's about 5%. Not much variation by sub, even the technical ones are in that range, maybe a few % higher.

Re: Apollo Back end just made public

#184

Earlier quoted context omitted.

The clowns at Reddit couldn't even specify a time. This will be a spectacular shitshow to watch.

For some reason, they gave Verge a time but not on their own post. It's at 1:30 pm EST https://www.theverge.com/2023/6/8/23754780/reddit-api-update...

Excellent thank you, I don't use the verge as a source of information, and am surprised how common they have become.

Surprising that Reddits communication on their own platform is so bad, or maybe it's not...

Thank you for the update!

Re: Apollo Back end just made public

#185
post #166
post #129

Earlier quoted context omitted.

Why would that leave Apollo dead? If they set the API charges back to zero all third party clients, including Apollo, would be happy to continue.

How do you know? I would definitely not come back after getting screwed like this.

He makes money from Apollo. Unless he has another job lined up, or a sizeable savings, he would probably enjoy his income staying as it is.

Re: Apollo Back end just made public

#186

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…

I was diving into your code and noticed you were using golang-migrate for running your migration queries. I never heard of it before and the number of databases they support sounds interesting!

How was the experience overall with this tool? If you have experience with Flyway, how does it compare?

Re: Apollo Back end just made public

#187

Earlier quoted context omitted.

I’ll be happy to once I sit down in front of my computer.

A naïve question, but why is a backend needed and why couldn’t the app call the APIs directly? Just curious to learn!

Sibling comment above says it was mostly for notification, but flowing calls through their server also meant they didn't need to resubmit to Apple most of the time when something broke on Reddit's side.

Re: Apollo Back end just made public

#188
post #161

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.

Yep, and after reading this thread (and clicking through to the reddit thread) I couldn't justify not delivering 1 little papercut of my own; I just canceled my paid account. (Although at little personal cost, since I don't normally go to reddit directly, but I paid just to stop the inline ads that I would see when I would, as often happens, end up on reddit after googling something with kagi.com or bing.com.)

> googling something with kagi.com

This always makes me chuckle. Kaging something may not be mainstream yet but Kagi-fu sounds better then Google-fu!

Re: Apollo Back end just made public

#189
post #73

Earlier quoted context omitted.

When old.reddit.com is gone, that will be the true end.

What are you basing this on? Do we have any data regarding the percentages of mobile/old/app users?

It’s not just about users, it’s about principles.

Re: Apollo Back end just made public

#190
post #17
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.

Let's talk about Rampart!
Post reply on HN