crablar / podsheets Goto Github PK

The tag in the RSS feed reads "Podcast for Node". I believe this tag is intended to describe who generated the feed, which in this case is "Podsheets (https://podsheets.com)"

What if we had a page that listed all of the podcasts created with Podsheets? It could be searchable by category and/or other fields. This could improve discoverability.

• Sendgrid from email address
• mongodb collections
• AWS S3 bucket sd-profile-pictures
• Stripe
• Ad free URL/bucket
• remove event stream url config
• mail chimp
• we can remove all raccoon and Redis references

@andrewmarklloyd I'm not sure you can do this without having GitHub Enterprise. Do you know?

• merge into master of API or front end project fires webhook to lambda
• lambda clones sedaily-monorepo, runs update script that clones master branch of both projects, creates new release of sedaily-monorepo using github api
• new release of sedaily-monorepo triggers webhook to lambda
• lambda triggers build of all podsheet-social apps

Hello,

I just want to know if there is a fork of this project or if it's totaly dead ?

the best

[ ] 5 small issues for backend
[ ] 5 small issues for frontend

Why did we change the logo for Podsheets?

Here is a folder with a basic splicing experiment I made several years ago: https://www.dropbox.com/s/e0iefvm2qaok4ad/ffmpeg%20basic%20splicing.zip?dl=0

Edaena had an idea for an Electron app that would interface with local storage to allow faster editing of audio files

This could be a useful product. I believe there are constraints on how you cannot fit big audio files completely into memory on local browser storage, so this makes it hard to do editing, because you have to have a very chatty network connection with a server-based rendering playback.

The atom:link in the RSS feed has an extra forward slash which creates a broken link. Also, both simplecast and transistor use a type of "application/atom+xml" and a title of "MP3 Audio" inside this tag. I am not sure what affect this has if any.

-create team of Jeff and Mo as CEO and CTO
-add Edaena, Erika as founder+advisors
-add Andrew as Advisor, director of open source and release

Let's get a framework and start adding some unit tests for the fronted. Please add some comments on which framework would be a good fit for Podsheets

Currently this is possible

When a user submits their podcast to Podsheets, an email should be sent to [email protected]. The email should include:

- RSS feed url
- name of the podcast

The URL generated for each mp3 in Google storage uses http instead of https.

An example URL for an episode:

https://www.podsheets.com/p/<podcast>/episode/<uuid>/download/http%3A%2F%2Fstorage.googleapis.com%2Fpodsheets-qa%2F<file-name>.mp3

should be

https://www.podsheets.com/p/<podcast>/episode/<uuid>/download/https%3A%2F%2Fstorage.googleapis.com%2Fpodsheets-qa%2F<file-name>.mp3

Remove podsheets-staging-pr-24 from authorized domains on google after branch has been merged.

One issue we have had in SE Daily is that we often engage with a potential sponsor who is afraid that they won't be able to accurately measure results of their campaign because they do not have an incentive program in place.

For example, MongoDB is advertising with us, but there is not a good way for them to measure engagement. Going to Mongodb.com/sedaily gives a user the same set of offers they get from MongoDB.

It would be a nice feature if we could offer nice hosting + custom landing pages + full fledged incentive programs. So for example, "Go to softwareengineeringdaily.com/mongodb and get a free Software Engineering Daily sticker pack by signing up for MongoDB"

That way this backend referral stuff is not required by the customer.

For some reason the build will not complete only when run on Heroku. This error occurs on Heroku but not locally in a Docker container using the same npm and node versions

Module not found: Error: Can't resolve '../assets/icons/search.svg'

ERROR in ./src/components/NavigationBarMobile.vue
Module not found: Error: Can't resolve '../assets/icons/search.svg'

ERROR in ./src/components/ForumThreadCompose.vue
Module not found: Error: Can't resolve '@/assets/icons/Aa.png'

ERROR in ./src/components/BaseListView.vue
Module not found: Error: Can't resolve '@/assets/icons/Github.png'

ERROR in ./src/components/post/PostSelectionIcons.vue
Module not found: Error: Can't resolve '@/assets/icons/comments.png'

ERROR in ./src/components/ForumThreadSummary.vue
Module not found: Error: Can't resolve '@/assets/icons/podcast.png'

ERROR in ./src/components/post/PostSelectionIcons.vue
Module not found: Error: Can't resolve '@/assets/icons/post.png'

ERROR in ./src/components/post/PostSelectionIcons.vue
Module not found: Error: Can't resolve '@/assets/icons/relatedlinks.png'

ERROR in ./src/components/ForumThreadCompose.vue
Module not found: Error: Can't resolve '@/assets/icons/x.png' 

Since few days i noted that the website podsheets.com is down.

• Access to AWS bucket for profile pics
• Configure or remove Zendesk?

Let's get a framework and start adding some unit tests for the backend. Please add some comments on which framework would be a good fit for Podsheets

• remove old service accounts and passwords
• confirm validity of any passwords and/or sensitive configs

The home page is missing “podcast” on mobile. All of the text is hidden on desktop for smaller window sized.

@crablar I'm not sure where we have the DNS. Can you make this change or give me access to do so?

In the settings for a podcast, there should be an option to delete the podcast. There should be ample warnings letting the user know the ramifications:

• all website data will be removed
• all episodes will be deleted from storage and will not be retrievable
• the RSS feed will be removed
• the podcast will be removed from iTunes and Google Play

There should be a confirmation where the user must type in the name of the podcast to ensure the podcast is not deleted on accident.

We should consider giving the option to export all of the data.

This could be split up into separate backend and frontend issues.

When a user schedules an episode to be released, the episode should not be included in the RSS feed until it is published. Currently the episode is included in the RSS feed.

Steps to reproduce:

• create a new episode scheduled for sometime in the future
• open the RSS feed in a browser
• see that the episode is shown in the feed

Mo--I think you should create a Podcasts Connect account so you understand how it works.

Getting this error when logging in using Google
Error: invalid_request
Missing required parameter: redirect_uri