FreeFacts

joined 1 year ago
[–] FreeFacts@lemmy.world 4 points 7 months ago* (last edited 7 months ago) (3 children)

It was utter horse crap when it released. The military green Steam was among the worst pieces of software ever conceived. So they worked a lot to make it as good as it is today.

[–] FreeFacts@lemmy.world 81 points 7 months ago (5 children)

I think it's ironic this is posted here on Lemmy, which is what it is today mainly thanks to users of another service freaking out over how they will manage without their API access to bullshit aggregated content mixed with astroturfing.

[–] FreeFacts@lemmy.world 0 points 9 months ago* (last edited 9 months ago) (1 children)

I know of one use case that seems viable, there is a digital housing market service in my country (called Dias). It uses blockchain to verify transactions related to selling and buying houses. That includes proof of sales, ownership, bank transaction status etc. The blockchain is operated by all the major banks. Their incentive is that it increases the security of the transactions thanks to the immutable digital trail, and also the fact that no single entity owns the "database" so no entity can alter it, or skim service fees etc from the others.

[–] FreeFacts@lemmy.world 17 points 9 months ago (1 children)

Why this hasn't been done is pretty baffling to me.

Because the blockchain needs an incentive. Who is going to be taking part in the blockchain if there is nothing in it for them? That's why these tokens are often tied to crypto currencies, as mining is the incentive.

[–] FreeFacts@lemmy.world 5 points 10 months ago* (last edited 10 months ago)

People are smart enough to understand the difference between someone copying for personal use and a billion dollar corporation copying to generate millions while laying off all the creative people. The latter is what these non-open-source AI companies are enabling - for profit too.

[–] FreeFacts@lemmy.world 19 points 11 months ago* (last edited 11 months ago) (15 children)

Email standard sucks anyway. By the official standard, User@email.com and user@email.com should be treated as separate users...