@
0 reply
0 recast
0 reaction

notdevin  pfp
notdevin
@notdevin.eth
😳
1 reply
0 recast
0 reaction

memes4airdrop pfp
memes4airdrop
@wake
I guess this is cheaper than liking. :)
1 reply
0 recast
0 reaction

@
0 reply
0 recast
0 reaction

Ayush pfp
Ayush
@ayushm.eth
Do you really care though if your earlier likes get deleted?
1 reply
0 recast
0 reaction

@
0 reply
0 recast
0 reaction

Ayush pfp
Ayush
@ayushm.eth
Bookmarks can be implemented by clients without it being in protocol The data point is good; i wonder, if a hub runner can choose to store all data (never prune)? Seems like an implementation detail for the node without affecting the protocol? @v @dwr.eth
0 reply
0 recast
0 reaction

@
0 reply
0 recast
0 reaction

Ayush pfp
Ayush
@ayushm.eth
Don't think a lot of people care about storing/browsing their historical likes And if they do, they can always rent more units I see your point though that the reactions tab gets filled much faster than the other two
0 reply
0 recast
0 reaction

@
0 reply
0 recast
0 reaction

Ayush pfp
Ayush
@ayushm.eth
Could see this working if one can pay (lower amt) to fill any of the three baskets on top of the bundled storage unit Kind of a power user feature
0 reply
0 recast
0 reaction

@
0 reply
0 recast
0 reaction

notdevin  pfp
notdevin
@notdevin.eth
If the use case for likes is varied enough, it’s also probably fair to say it’s not useful for data analytics other than just a meta count
0 reply
0 recast
0 reaction