1/12 @HathorNetwork offers a unique set of features for both builders and users. Some well known ones, others not so much. Let’s look at why you might want to consider Hathor as the layer 1 solution for your project. $HTR @HTRFDT #BuildOnHathor

2/12 Easy tokenization is the obvious one. You create your own token in less than a minute, no coding required. $HTR
https://t.co/kZwv4TlmRB
3/12 As opposed to ERC tokens, your custom Hathor token is a layer 1 token. It inherits the same features and security as the native token, $HTR, effectively giving your token the same level of security as the #Bitcoin $BTC blockchain.
4/12 Hathor Network also passed their security audit by @SlowMist_Team so you can feel safe knowing that your L1 token fulfills the same security requirements as $HTR.
5/12 By configuring built-in nano contracts you will be able to add logic to your token. No coding required. Native nano contracts also mitigate the risk of bugs and security issues that comes with custom smart contracts development on other platforms. $HTR
6/12 You will be able to list your token for free on #HathorSwap, Hathor’s first DEX (beta launching Q1, public release Q2) and letting users start trading instantly. Again, no coding required. $HTR
7/12 Adding your token is plug-and-play for CEXes that have listed $HTR as well. They modify a configuration string and that’s it. No coding required.
8/12 No more skyrocketing gas fees when network traffic spikes—always predictable costs. Developer grants are coming and Hathor Labs will support you on the business, architecture and development side. $HTR
9/12 Familiar L2 infrastructure is being built on Hathor right now. Chrome extensions like the Metamask-like wallet from @htrfdt will make transitioning from #Ethereum to Hathor seamless and pain free for both users and developers. Oh, and debit card app 👀 $HTR
10/12 Hathor has no congestion issues and the implementation of side-DAGs will ensure that the network scales to support future throughput requirements from blockchain-enabled industries. Hathor mainnet currently handles 200 TPS, fully decentralized, tech potential is 2000+. $HTR
11/12 With Hathor’s ease of use and the team’s focus on delivering great user experiences with minimal development and onboarding efforts, Hathor could be the ideal host for the next generation of ICOs, and fuel mass adoption. $HTR
12/12 Finally, Hathor’s simplicity reduces risk and time to market for businesses wanting to dip their toe into the potential of product and business model tokenization. With—you guessed it—no coding required $HTR

Your turn—add the stuff I forgot, in the comments 👇🤓

More from Tech

Recently, the @CNIL issued a decision regarding the GDPR compliance of an unknown French adtech company named "Vectaury". It may seem like small fry, but the decision has potential wide-ranging impacts for Google, the IAB framework, and today's adtech. It's thread time! 👇

It's all in French, but if you're up for it you can read:
• Their blog post (lacks the most interesting details):
https://t.co/PHkDcOT1hy
• Their high-level legal decision: https://t.co/hwpiEvjodt
• The full notification: https://t.co/QQB7rfynha

I've read it so you needn't!

Vectaury was collecting geolocation data in order to create profiles (eg. people who often go to this or that type of shop) so as to power ad targeting. They operate through embedded SDKs and ad bidding, making them invisible to users.

The @CNIL notes that profiling based off of geolocation presents particular risks since it reveals people's movements and habits. As risky, the processing requires consent — this will be the heart of their assessment.

Interesting point: they justify the decision in part because of how many people COULD be targeted in this way (rather than how many have — though they note that too). Because it's on a phone, and many have phones, it is considered large-scale processing no matter what.

You May Also Like

Following @BAUDEGS I have experienced hateful and propagandist tweets time after time. I have been shocked that an academic community would be so reckless with their publications. So I did some research.
The question is:
Is this an official account for Bahcesehir Uni (Bau)?


Bahcesehir Uni, BAU has an official website
https://t.co/ztzX6uj34V which links to their social media, leading to their Twitter account @Bahcesehir

BAU’s official Twitter account


BAU has many departments, which all have separate accounts. Nowhere among them did I find @BAUDEGS
@BAUOrganization @ApplyBAU @adayBAU @BAUAlumniCenter @bahcesehirfbe @baufens @CyprusBau @bauiisbf @bauglobal @bahcesehirebe @BAUintBatumi @BAUiletisim @BAUSaglik @bauebf @TIPBAU

Nowhere among them was @BAUDEGS to find
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.