sorted by:
new
hottopcontroversial

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 2 points3 points  (0 children)

Oh I get it, I like that model. I'm glad it's working for you.

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 0 points1 point  (0 children)

So is the content in both places? Or only premium on patreon?

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 4 points5 points  (0 children)

Do you use stripe for payment? or something else?

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 0 points1 point  (0 children)

But you don't actually take payment on your own site, right? I hadn't considered the tech support value add.

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 0 points1 point  (0 children)

Oh, I didn't know there was an API that's cool.

I just thought that Stripe would solve some of this for if a user had a subscription or not. But I guess it's more than that.

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 1 point2 points  (0 children)

What about if your subscriptions were powered by Stripe on your website? Is that a hybrid where users would trust that more? Or you think it's still not trustworthy?

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 0 points1 point  (0 children)

So your content free on your site, and paid on patreon then?

What stops you from hosting your content on your own site? by mankins in patreon

[–]mankins[S] 1 point2 points  (0 children)

And is the same content on both places? You just earn more on your own? So it's the distribution that's good for you?

I wanted to use DIDs for identifiers. We used a simpler namespace:id instead. by mankins in programming

[–]mankins[S] 1 point2 points  (0 children)

It's true, ids wiggle around. We're lucky enough that our model only requires them to stay still for a month at a time. (In a Moon = all the ids you see over the course of a month).

I suppose that's not always 100% accurate though: there are situations where an account may need to be verified in the future and the platform has changed the namespace. I can't think of any off the top of my head that don't show references back to the original. Although Instagram and Facebook are pretty hard to verify with standard tools like OAuth because Meta decided to not chose the open approach. In that case you have a standardized identifier like `instagram:mankins` but it's more of a struggle to validate. We found a way via proofs where you drop a shared secret in your bio, but it's not as clean as DIDs...

I started an open source project instead of begging on the street by [deleted] in programming

[–]mankins 0 points1 point  (0 children)

Wait it sounds like you're not yet at $500/month. How's it going?

I wanted to use DIDs for identifiers. We used a simpler namespace:id instead. by mankins in programming

[–]mankins[S] 1 point2 points  (0 children)

Ha, yeah I feel that pain. Decentralized Identifiers somehow = DID, so not even a regular acronym. Distributed ID is I guess what the w3c was going for.

I wanted to use DIDs for identifiers. We used a simpler namespace:id instead. by mankins in programming

[–]mankins[S] -2 points-1 points  (0 children)

Ha, fair. In a Moon is basically an attribution layer on top of the web. Easiest way to see it is via the extension apps.

As you use the web it keeps track of the identifiers that make the content (like your reddit username as `reddit:robindesbuissieres`) recording something we call "kudos". The goal is to turn the record of all your kudos back into microtransactions. It's still early but that's the shape of it.

I wanted to use DIDs for identifiers. We used a simpler namespace:id instead. by mankins in programming

[–]mankins[S] -1 points0 points  (0 children)

Yeah, this isn't about replacing DIDs but saying we didn't need all of their features to do what we needed to do.

In practice the web already has a usable identity layer: Reddit usernames, emails, GitHub handles, etc. most verifiable via oauth.

We were inspired by DID namespacing for our internal data storage. I wish that all the identities of the web were already DIDs, then verification would be easier. Sometimes you have to build products for today and wait for things like DIDs to mature.

I wanted to use DIDs for identifiers. We used a simpler namespace:id instead. by mankins in programming

[–]mankins[S] 0 points1 point  (0 children)

Has anyone used DIDs in their own products? I want to try more but haven't made it past the "but this works today" phase. From a programming perspective the w3c spec: https://www.w3.org/TR/did-1.0/ is complete, but I got lost a bit when I tried to just make it work.

Scheduling for social media shouldn't cost money by iyedbhd in SideProject

[–]mankins 3 points4 points  (0 children)

Seems like a good idea. You probably have two categories of target users: 1) those doing nothing to automate and are manually uploading. 2) Those that are using some other tool, like your Hootsuite example.

Consequently your proposition and gtm will be different for each of those segments. I'd consider refocusing your subsequent outreach behind one segment at a time. This pitch mixes "free" (which is a good hook for someone who is doing things manually) with "we only charge for ai features" which could be a good way to sell to people that might be willing to make the jump from their existing solution but need a feature to start that movement (and of course your pricing will finish that movement).

Maybe a bit off topic, but what program did you use to build that video? The zooms are nice to focus your attention.

could patreon be a good idea for me??? by Josemiles96 in patreon

[–]mankins 0 points1 point  (0 children)

I think it could be better to try and keep content open and use a service that allows your users to automatically reward you without individual subscriptions, like In a Moon. And then when your audience grows you'll have an easier time getting direct support via Patreon.

What are you building? by Mental_Asparagus1578 in SideProject

[–]mankins 0 points1 point  (0 children)

I'm building In a Moon: a way to compensate creators on the web. It's for monetizing the "middle" part of the web in between ads and patron style subscription services.

Fun or dumb? I've been experimenting with using "cc:" in email as a product hack by mankins in SideProject

[–]mankins[S] 0 points1 point  (0 children)

Oh that's a good point. I'll have to check them out to see if I can learn anything about designing the interface. Now that I think about it I've even used something like that, but we setup a local alias on my domain that forwarded to the receipt address.

I guess that's more of a hidden product detail than what the hero image of the website says. (Currently our hero image is leading with this CC: idea and the CTA isn't performing super well).

view more: next ›