im trying to create a python program that prints out top posts, but i need to make an app. i cant figure out how to

Hi folks!

I wanted to share a quick note about Developer Platform accounts and authentication.

Next week we will be launching Developer Accounts that are associated with your Reddit accounts.

This means that all new users, as well as all of our existing users, will see an account creation prompt when using Devvit.

Your account will be created and associated to the Reddit account you are logged in with. This will not impact your existing apps or projects in development. Note that developer accounts can only be tied to Reddit accounts with verified emails. We are requiring verified emails to ensure we have a standardized avenue for important communications related to app review, allowlist requests, and other administrative items related to your apps. This will also allow us to send updates about the platform and new programs to those who are interested.

We hope to continue improving developer account management and project management once this change is in effect.

Let us know if you have any questions.

We created application and generated oauth_token but we can't find the way how to use it to login into API to receive more information about our subredit posts (we need information if the post is approved or not for us to embed it on website). We also can't find it in the reddit api documentation. Any response is appreciate, thank you in advance.

We're gonna set up an internal developer portal for a team of 28 devs, and I'm on the case to figure out which one we should go with. I want to know your thoughts - what have your experiences been like with different portals? I've only a little experience with Backstage but have experienced (and heard) some mixed things about it, and luckily we've got some budget. Let me know!

Hello, everyone.

I want to use the Reddit API just to experiment a bit with its data. I want to build an app for customer discovery and market research, and right now I haven't written a single line of code. I only want to see what I can do with the API and then I might build something.

However, the registration form is asking me for OAuth Client ID, an About URL and Redirect URI. How am I supposed to have these when I haven't even started building anything yet? I'm a senior year undergrad CS student and at this point I'm only looking to experiment a bit.

Can people please guide me how I can register for the API?

If this is not the right place to ask this question, please, let me know where I can post it.

Thanks.

Say I've built the core functionality of an LLM-based API (or really any API for that matter) and now I want to publish it. There's clearly a lot that needs to happen in between those two things.

In particular, we need:

• An API developer portal

• User registration

• User authentication

• Billing

• Usage monitoring

• API key provisoning

• Documentation

Is anyone aware of an easy solution for implementing all or most of the above (I'm happy to handle my own documentation) that is also scalable (eg, will minimize AWS-, Azure-, etc... lock-in, and will be performant)?

One option seems to be use Stripe for billing, something like Auth0 for authentication, React for the UI, then build a FastAPI internal API for the React app, maybe Plotly or something like that for showing usage data, which can also be pulled from the API.

But that does seem like it may add up to a lot of work. Is there a better way of doing this?

It may also be worth noting that I eventually plan on creating a paid web app so it'd be great if I didn't end up with two different user account databases that are entirely separate, still happy for separate platforms though, similar to ChatGPT vs OpenAI Developer Platform.

I came across Backstage.io and getport.io, both of which claim to be Internal Developer Portal solutions. Do these represent the IDP (platform) in the GitOps sense or do they have different purposes?

In platform engineering, the definitions related to Developer Portal are as follows:

• Web portals for observing and provisioning products and capabilities. ---- from CNCF tag-app-delivery

• An internal developer portal/ graphical user interface: In case users don’t want to push manifests directly to git, we should provide them with a user interface that will enable them to see what’s running as well as to execute processes that will create new resources and store them in git. Our recommended tool here is Port. ---- from thenewstack

• Service catalogs, developer portals or platform UIs, e.g. Backstage: tools from this category are not an IDP, but they can play a very useful role in your IDP setup. As Gartner’s Software Engineering Leader’s Guide to Improving Developer Experience puts it: “Internal developer portals serve as the interface through which developers can discover and access internal developer platform capabilities.” ---- from humanitec

And, a architecture diagram from CNOE can be display all details of Internal developer platform(IDP):

From the quotation above, it can be seen that the definition and tool selection of the Developer Portal are dazzling. Do you have any suggestions or opinions?

A little background: I've been tasked with setting up an IDP (internal developer portal) for work, and have been evaluating the space to see what's out there.

So far, for free / OSS options, it seems like my only real choice is Backstage, which to be honest is a stinker. The thought process is, why invest the time and effort into wrangling that framework into something that works for us, when we could just build something ourselves in the tech stack we're already comfortable with, and it would take the same amount of time? Backstage out of the box provides so little as to be near-useless.

Then there's the paid options, of which I've found about six. They all seem good, and that Venn diagram has some overlap, but none of them quite spark joy. And finding pricing / demos / etc. is not very easy without engaging a possibly arduous sales process.

My requirements aren't so much for a platform as they are for a portal. We don't care to orchestrate or manage clusters / images / what have you from the tool. It's mostly documentation, new developer on-boarding (here's the landscape and who to talk to), and risk management (code health and related metrics, vulnerability info, package dependencies), and the ability to integrate with some existing infra to draw in more info.

So as I keep digging into this landscape, and continue contemplating spinning my own solution, I wanted to ask: what is the community's experience here? What has worked and what hasn't? Are there any Backstage success stories that don't involve brand-new teams being spun up to manage Backstage?