Quote from Lucio Buffalmano on August 25, 2021, 9:36 pm

Thank you for the idea, Matthew!

 

Quote from Ali Scarlett on August 25, 2021, 10:26 pm

A couple more options as well:

Option 2:

(Option two because it picks up from Matthew's great option above.)

Ramit has his own solution.

He uses Amazon Simple Storage Service (i.e. "Amazon S3") for his ebook "50 Proven Email Scripts":

Option 3:

The more budget-friendly option would be for Lucio to upload his ebooks to a free service where he can get a shareable link. Then, share that link on a private page on TPM.

One platform he can upload his ebooks to is Notion:

Or, Evernote:

And, of course, there's Google Drive.

This way, Lucio can release the latest versions on any of those free platforms and update them whenever he wants. And, instead of sending out individual copies time and time again when someone requests one (which would be once for older PU members and then again every time there's an update), Lucio can simply send a link to the private TPM page along with a password.

Or, give certain accounts automatic permission to access the private page.

If anyone sees any issues with these alternative options, feel free to share.

Quote from Lucio Buffalmano on August 25, 2021, 10:50 pm

Thank you Ali!

Quote from Matthew Whitewood on August 26, 2021, 8:32 am

Ali's ideas remind me of Lucio's link to Healthy Habits via WordPress upload.
It's the same as the Amazon S3 hosting except using whatever hosting provider Lucio uses.

So I guess this can also be an option.
And one could ask subscribers to bookmark that link.

Though I see the issue is that people could distribute copies easily by sharing the link.
But it's hard to stop people from sharing book copies anyways.

Quote from Matthew Whitewood on September 2, 2021, 5:43 am

For New Customers

1) Request Access Via Given Link (Link Left Out As It Should Only Be Known to Customers)

We can include the link to the GitLab group in the purchase email.
Maybe as a new bullet point after the download links:

Upon clicking the link, it brings you to the following page below.
Click Request Access encircled in red.

You should see the following after clicking "Request Access":

2) Wait to be Granted Access to GitLab Group

All members of this GitLab Group will have access to the GitLab repository.
However, we may revoke the group's access to this repository in the future.

You will take some time to be added as we do not check the group every day.

3) Access the GitLab Repository Via the Following Link

https://gitlab.com/datingpowerdynamics/ebook

Find the ebook and click the download button encircled in red.

For Current Customers

1) Forward the Email Proof of Purchase to Lucio

Forward the invoice to connect(ȧt)thepowermoves(döt)com

2) Upon Verification, You Will Receive the Link to be Added to GitLab Group

We can include the link to the GitLab group in the purchase email.
Upon clicking the link, it brings you to the following page below.
Click Request Access encircled in red.

You should see the following after clicking "Request Access":

3) Wait to be Granted Access to GitLab Group

All members of this GitLab Group will have access to the GitLab repository.
However, we may revoke the group's access to this repository in the future.

You will take some time to be added as we do not check the group every day.

3) Access the GitLab Repository Via the Following Link

https://gitlab.com/datingpowerdynamics/ebook

Find the ebook and click the download button encircled in red.

For Admins

1) Verify Customer

2) Send the Link to GitLab Link to Customer (Link Left Out As It Should Only Be Known to Customers)

3) Under the GitLab Group, a) go to Members on the Left Menu, b) Scroll Down & Click Access Requests Tab, c) Click the Green Tick to Approve

4) Delete Old Versions of the Ebook

5) Upload New Versions of the Ebook

@lucio

Quote from Lucio Buffalmano on September 2, 2021, 9:05 am

First of all:

Thank you so much, Matthew!

Much much appreciated.

I'm thinking whether there are any advantages to putting the ebook on a WordPress page, and password-protect it. And then share that password with the purchasers.

Quote from Matthew Whitewood on September 2, 2021, 12:21 pm

It is indeed less simple.

I do tech work so I'm biased. But it's one of the greatest tools in tech in my opinion.

Advantages

1. Easy for one person to access update while making it not so easy to share with many people. Even if he reuploads the book, the pirated copies don't get updated.
2. Keeps track of changes and can be viewed by every member so you don't need to announce updates
3. (Advanced) Potentially crowdsource typos and mistakes for those who are savvy with Git in a convenient manner. People submit a request and if it's right, you just approve. Less communication overhead. All developers know Git. It's how thousands of developers collaborate on a single codebase.
4. (Advanced) You can sync your ebook locally on your computer real-time with GitLab. No worries about making multiple versions. Just roll back if you delete an entire page.

Disadvanatges

1. More complex, some learning curve
2. The user interface admittedly is not the best

Maybe you can think of this as another choice. The WordPress option is indeed simpler.

OFF-TOPIC

Asking for a developer's GitLab or GitHub is a good way to screen the experience and skill level.

OFF-TOPIC

Quote from Lucio Buffalmano on September 2, 2021, 5:22 pm

Thank you, Matthew.

I think the simple method might be the best solution in this case.

Less moving parts, less overhead, fewer things that can go wrong -and fewer support requests-.

I'll probably also add a note that saving and storing the file safely is up to the user, finding and downloading the latest version is up to the user, and then provide instructions and ignore all requests.

Ruthless prioritization.
If you wanna move agile, that's what's sometimes needed.

Quote from Matthew Whitewood on September 2, 2021, 11:22 pm

Let's go for the WordPress upload then :).

I think charging for new book versions could work too.