Feature: Allow users to post blogs from (RSS) multiple platforms

[CBID2]

Type of feature

🍕 Feature

Current behavior

I tried posting my Hashnode blog post as a highlight but I received this message:

This can be a turn-off for people who either don't use Dev.to or use other platforms alongside with it.

Suggested solution

Create some sort of code to allow blog posts from all platforms to be shared as highlights.

Additional context

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Contributing Docs

• I agree to follow this project's Contribution Docs

[bdougie]

A lot of the context around the decision to only allow did not make it here, but my solution is leveraging RSS directly and bing platform agnostic. This would require us build a social card fetcher that is DEV agnostic.

current implementation

app/components/molecules/DevToSocialImage/dev-to-social-img.tsx

Line 19 in 172c61e

const response = await fetch(`https://dev.to/api/articles/${username}/${slug}`);

I have a thing that fetches meta data from og data

I have some code that fetches social cards using the og lib. We could fetch from blog post that have open-graph data in lieu of RSS.

https://github.com/bdougie/social-carding/blob/main/pages/api/fetchMeta.js#L1

[CBID2]

Ok that could work @bdougie

[RitaDee]

When the endpoint is ready, I will .take this.

[bdougie]

When the endpoint is ready, I will take this.

To be clear, I don't believe a new endpoint is needed. All changes can be add in this repo's lib folder.

The fetching just needs to be non DEV specific.

[CBID2]

Go ahead @RitaDee

[RitaDee]

Hello @bdougie,

https://github.com/bdougie/social-carding/blob/main/pages/api/fetchMeta.js

Looking at the implementation, it seems as though the open-graph package works only on the server side. Is this correct?

I thought to implement the og lib in the Api route but the folder "page/api" is not there.

[RitaDee]

Here is an update on my progress regarding this issue @bdougie:

I've been working on this task and have made significant progress on several fronts. I encountered some challenges when attempting to access the endpoints for Medium and Hashnode just like @diivi did with the dev.to platform. Despite my efforts, I have not been able to find a resolution. So, I will unassign myself 😞.