search

d-buzz / d.buzz-client

A New Era of Social Media on the Hive Blockchain
https://d.buzz/
The Unlicense
6 stars 6 forks source link

Add a Custom Built TRENDING, LATEST, HOME system. #723

Open hivephilippines opened 3 years ago

hivephilippines commented 3 years ago

Hi @stinkymonkeyph ,

Out of the issues I assigned to you, this one is the biggest.

HIVE has a standard system for organizing the posts found on:

  1. https://d.buzz/#/ and https://hive.blog/@chrisrice/feed
  2. https://d.buzz/#/trending and https://hive.blog/trending
  3. https://d.buzz/#/latest and https://hive.blog/created

But what we want to do, is fork it, then create our own system so that we can insert content posted to D.Buzz via logins from other platforms.

The other platforms that we want people to be able to login to D.Buzz from, include:

1. Mastodon https://joinmastodon.org/ 2. Google 3. Facebook 4. Twitter 5. LinkedIn

( many more to follow )

The content people post to D.Buzz from any of the above logins would NOT publish to the HIVE blockchain, but would instead, just show up on our site, which we could then offer an API for other frontends to implement (but not right away).

Our own custom built TRENDING, LATEST and HOME (Feed) system should be made so that it's easy for us to insert content that is posted from any of the above logins, in a way where it would organize itself perfectly, almost identical to the TRENDING, LATEST and HOME ( Feed ) rules found on HIVE, but with our addition inputs instead.

Lastly, this should be made with the forethought that eventually, we want users to be able to cross-post to as many of the Logins we integrate that happen to be content platforms such as Facebook, LinkedIn, Twitter, etc., so that we can compete with https://www.hootsuite.com/ by offering a similar or better service, but for free, or as cheap as possible.

Here are some resources you can use @rmcuenen :

A. https://guiltyparties.com/developing-on-hive/ B. https://gitlab.syncad.com/hive C. https://github.com/ecency

Please ask @stinkymonkeyph if you have any questions @rmcuenen, he is available here in the comment section, or on Facebook, you can message him from your wife's account, like you do me.

( @rmcuenen does not have an FB account, only his wife does )

hivephilippines commented 3 years ago

P.S Another thing worth considering, is that this would open the door for us to create our own ReBuzz feature, different from the Reblog found on HIVE, where the ReBuzz's are instead stored via custom JSON. This is a huge systematic change, and can solve our onboarding and user retention issues in amazing ways @rmcuenen @nathansenn @PostNZT

aaashir commented 3 years ago

@hivephilippines - I'm going to start working on this issue from now onwards. So I have a question:

Do we need to show the posts from the user's other platform profiles or just let them sign up from other platforms and store those posts on a separate database then show those post on our custom TRENDING, LATEST, HOME system? This way, they don't need to specifically login from Hive but instead, they can easily login from other platforms.

Okay, so I have some ideas to do this. We can show label on the user's profile for clarity and that label should be like where they signed up from i.e Signed up from: Facebook or Signed up from Hive.

@stinkymonkeyph - Let me know your thoughts about this.

hivephilippines commented 3 years ago

  1. We won't make Profile pages for people who login from third party services.

  2. Profile links from 3rd party logins will direct to the Profile at the 3rd party site.

  3. Buzz's from 3rd party logins will not show earnings at the botton, but will instead have the text:

--> Turn on $

Which will direct to Hiveonboard.con so they can create a Hive account.

  1. This new system will allow us to also create an in-house reBuzz feature, separate from reBlogging, as it will just show up as a rebuzz on our site, will not create a new post, and could possibly be saved in custom JSON.

  2. Buzz's from third party logins should not be saved in a private server, but should instead be saved via IPFS, with the user being allowed to delete their Buzz's and data from IPFS.

  3. Keep in mind, we will eventually be integrating a free and more expanded version of https://hootesuite.com, where each 3rd party login, could somehow be linked to a Hive username, that could then be used to Buzz from D.Buzz to every single Web2 to Web3 site/app, that it is compatible with.

stinkymonkeyph commented 3 years ago

If I understand this correctly, you would like to

  1. Add functionality so NON HIVE users can use d.buzz
  2. NON HIVE users will be able to buzz but their post will be publish on our own database not on hive network
  3. NON HIVE users will not be entitled a payout

Please correct me if I'm wrong @hivephilippines

stinkymonkeyph commented 3 years ago

Could you list here a minimum viable product of this feature @hivephilippines, the simplest form you can think of so we can have a base solution we can improve later

hivephilippines commented 3 years ago

Could you list here a minimum viable product of this feature @hivephilippines, the simplest form you can think of so we can have a base solution we can improve later

The MVP would be:

  1. Our own forked version of the LATEST, TRENDING, FOLLOWING and maybe the HOT category too.

After that, we'd insert one additional service, one by one, to mix and integrated into our feeds, starting with Mastadon.

So the MVP would not be noticed by our users at first, but once we start adding 3rd party integrations into our feeds, they'd notice.

I am not sure, but I think we should use OpenAUTH, or whatever open source service there is out there.

I heard there are entire projects, focusing on scaling multiple logins, and I think OpenAuth is one of them.

Please use the best, most developed, and most active multiple login, open source system šŸ‘ @stinkymonkeyph @aaashir

hivephilippines commented 3 years ago

If I understand this correctly, you would like to

  1. Add functionality so NON HIVE users can use d.buzz
  2. NON HIVE users will be able to buzz but their post will be publish on our own database not on hive network
  3. NON HIVE users will not be entitled a payout

Please correct me if I'm wrong @hivephilippines

Correct! šŸ˜€

hivephilippines commented 3 years ago

If I understand this correctly, you would like to

  1. Add functionality so NON HIVE users can use d.buzz
  2. NON HIVE users will be able to buzz but their post will be publish on our own database not on hive network
  3. NON HIVE users will not be entitled a payout

Please correct me if I'm wrong @hivephilippines

I'd like to store people's content from 3rd parties to IPFS though @stinkymonkeyph , not a private database.

AND, people will eventually be able to delete their data from IPFS on demand.

Meaning, they will truly own their data šŸ‘