You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First one
That's a big one for me, it is up to you guys if you going to understand how important it is, how much it has impact on proper media share, and actual consumption of your product.
Stop using hash # in your URLs, at least avoid doing it as much as possible.
It impacts how people can share links with their friends.
It impacts how other crawling engines can browse and take a screenshot for your pages.
a) Try linking on twitter https://mainnet.port.finance/#/markets and https://mainnet.port.finance/#/dashboard, it is a different page that should be displayed, but the systems will pick up only the default one before the hash tag. Maybe not the best example with twitter, but I hope you get what I mean.
Please understand I don't want to discredit the developers practices, but It is just a bad practice.
Second one
It is a production site, that has debug information in the console being printed out, this is consuming resources on every clients browser. While it doesnt affect you directly, it does run computer code on every clients browser, which is not very eco friendly.
SPL: 2TooLbSn4wySZPwyprTXuJUp7vByhVqB1yArrwndXpSo
The text was updated successfully, but these errors were encountered:
First one
That's a big one for me, it is up to you guys if you going to understand how important it is, how much it has impact on proper media share, and actual consumption of your product.
Stop using hash # in your URLs, at least avoid doing it as much as possible.
a) Try linking on twitter https://mainnet.port.finance/#/markets and https://mainnet.port.finance/#/dashboard, it is a different page that should be displayed, but the systems will pick up only the default one before the hash tag. Maybe not the best example with twitter, but I hope you get what I mean.
Please understand I don't want to discredit the developers practices, but It is just a bad practice.
Second one
It is a production site, that has debug information in the console being printed out, this is consuming resources on every clients browser. While it doesnt affect you directly, it does run computer code on every clients browser, which is not very eco friendly.
SPL: 2TooLbSn4wySZPwyprTXuJUp7vByhVqB1yArrwndXpSo
The text was updated successfully, but these errors were encountered: