Favourite NFTs page

[fudgebucket27]

Would putting in some sort of favourite system for NFTs be useful? Say if someone wants to keep track of an NFT, instead of having many browser bookmarks, have it confined to one page on the site? On my other site https://looprare.io , I have implemented a favourite/starring system for NFTs. It just uses browser storage to store the nft ids:

[fudgebucket27]

@modersohn @danielsolistensvik

[daniel-soli]

I would love this! I have alot of shitty nfts, so to be able to only show starred like on looprare would be awesome! Nice idea @fudgebucket27

[daniel-soli]

Make it possible to also star others nft? To be able to keep track of nfts in general. F.ex. see all my fav nfts in an own tab or page

[modersohn]

Can you post a link how you’re using browser storage @fudgebucket27 ?

How persistent is this? If you’re loosing it because your browser is trying to keep things private then that would be a major downer.

And the alternative of having a proper login system with a database seems like a huge effort to me. Have you got experience with something like this @danielsolistensvik ?

[daniel-soli]

I don't know how it works on looprare, but I guess it uses blazor local storage or something of that kind and just store the id's? Would be simple enough. Just update local storage if one is added or removed. Used the nuget blazor.local.storage or something in that lane before. Pretty straight forward. Much much much simpler than dealing with accounts etc.

Edit: here, found link to nuget.. blazored

[modersohn]

Yeah of course I can see how much easier this is - but I'd also bet most users would be quite disappointed when finding out that their favourites do not sync across devices...

[fudgebucket27]

Yeh it's blazor local storage described here https://docs.microsoft.com/en-us/aspnet/core/blazor/state-management?view=aspnetcore-6.0&pivots=server Unless they specifically clear it out of storage it will stay persisted.

…

On Fri, 24 June 2022, 6:11 am Daniel Soli Stensvik, < ***@***.***> wrote: I don'r know how it works on looprare, but I guess it uses blazor local storage or something of that kind and just store the id's? Would be simple enough. Just update local storage if one is added or removed. Used the nuget blazor.local.storage or something in that lane before. Pretty straight forward. Much much much simpler than dealing with accounts etc. — Reply to this email directly, view it on GitHub <#180 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABIDWT2OCYC6JUJRMSI6C2LVQTAHJANCNFSM5ZR4S37Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[fudgebucket27]

So it looks kinda like this when using it

@using Microsoft.AspNetCore.Components.Server.ProtectedBrowserStorage
@inject ProtectedLocalStorage BrowserStorage;

@code
{
   var starStorageExistsResult = await BrowserStorage.GetAsync<Rankings>(shortName); // to Get an existing value
   await BrowserStorage.SetAsync(shortName, starRankingsList); //set a value in storage
}

[modersohn]

So that makes an independent list of stored favourite NFTs not too difficult (but I desperately want to refactor our NFT grid before we copy it a 3rd time! see #193).

But: to filter your own NFTs by favourite status is a completely different story! You would need to build a filter list for the graph QL and it could become quite huge. Or you would need to retrieve everything first and filter in our code.

Same thing would apply to filter for favourites in a collection for example.

[fudgebucket27]

I think we just go with the generic NFT favorites list to make it easier to implement, no worrying about filtering current NFTs and NFTs in collection.

People just send NFTs they don't like to the dead address anyways so I don't see the point of filtering at the moment, would be a nice to have but like you said the GraphQL query would get pretty large.