This community twitter account (@EnsTimeKeepers) with authenticate your Ethereum address and (timekeeper) @ensdomains ENS before it allows you to tweet.
For example: If you own 14h20.eth, then you can tweet during 1400-1459 (inclusive) on the UTC timezone
I recently came across a very niche "subsection" of the EthereumNameService that involved people minting ENS names around the 24H clock.
Over a weekend, I thought it would be a good use of my time π to create a small project to allow those who own part of the clock to tweet from a "community owned Twitter account" by authenticating users who owned a time to tweet only on the hour they have the ENS name for.
I've honestly no idea if it's a good idea (probably not in the grand scheme of things π ) but having seen some other experiments on shared accounts, such as @TheTweetDao that sold NFTs for access...
I thought I'd make one where I have no financial incentive to (ENS fees to ENS)
I am not a #enstimekeeper but I am interested to see what a sub-community of a sub-community can and will do now they have some more utility with their @ensdomains domain
I'll be updating the blog post with learnings and what not as the shared account grows in activity - maybe we some graphs π and images πΌοΈ
Oh, I've done some testing with this - if you come across anything that looks like a bug π, reply here or DM me
πππ
ps. yes i just deleted the previous thread and reposted because I had a grammatical error on one of the tweet images π€¦
1/ A bad actor could look at public videos and use open tools to download the video
There are videos of many different people on video hosting sites that scammers can export from. On YouTube alone there is many videos returned searching "picture every day", "selfie a day", ...
2/ They would then use a tool, such as ffmpeg, to extract each frame to a PNG file automatically (maybe even de-duplicate any frames or set the framerate in the ffmpeg command to ensure uniqueness)
Refresh our memory on what we learned in 2017/2018, which ultimately led to us removing that "feature" from our web platform (redd.it/8wenmw) and started an effort to get other projs to remove this antipattern.
Tweet thread will be for DeSo but other projs take note
First, let's start with what DeSo is and isn't, so we can describe its potential scope to users.
DeSo itself is a L1 blockchain, however it offers an identity solution on its subdomain with a public code lib that apps can use to help user onboarding