janttoExperiences of Coding an Open Source Winston Transport
NOTE: Originally published on March 23rd, 2019 Lately I've had the time to think about logging in microservices. There seem to be a lot of options, but after looking at them I felt that the open source community around SRE isn't as mature as I thought it would be. What I mean by this is that the most common options seem to require a lot of configuration and require at least some sort of deep dive into the documentation just to get a simple central point for microservice logs. Since ...
janttoUsing Notion as a CMS for anything that reads markdown
PrefaceAs you might see from the fact that this blog resides on Mirror instead of Notion, I didn’t end up using this, but I reckon some might get usage out of the code that I wrote. :) TL;DR? *The finished code can be found, forked and tinkered with behind this link: * https://github.com/JaniAnttonen/notion-to-md-workerBackgroundWhile looking out for fun new things to try out on my personal website, I thought of using an external CMS for my blog posts, music and photos. Notion works well for ...
janttoExperiences of Coding an Open Source Winston Transport
NOTE: Originally published on March 23rd, 2019 Lately I've had the time to think about logging in microservices. There seem to be a lot of options, but after looking at them I felt that the open source community around SRE isn't as mature as I thought it would be. What I mean by this is that the most common options seem to require a lot of configuration and require at least some sort of deep dive into the documentation just to get a simple central point for microservice logs. Since ...
janttoUsing Notion as a CMS for anything that reads markdown
PrefaceAs you might see from the fact that this blog resides on Mirror instead of Notion, I didn’t end up using this, but I reckon some might get usage out of the code that I wrote. :) TL;DR? *The finished code can be found, forked and tinkered with behind this link: * https://github.com/JaniAnttonen/notion-to-md-workerBackgroundWhile looking out for fun new things to try out on my personal website, I thought of using an external CMS for my blog posts, music and photos. Notion works well for ...
Subscribe to jantto
Subscribe to jantto
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
Lately ConsenSys announced that they will be logging each user’s IP addresses who use Infura as their default RPC on Metamask. RPC or remote procedure call is the “backend” server you use for communicating with blockchain networks for both inbound (loading transactions) and outbound (submitting transactions) interactions.
Since ConsenSys is a company that’s located in the US, their move is not surprising given the constant regulatory uncertainty, and Infura has made promises to decentralize its services. Before that happens, it’s announcements like these that guide users towards decentralized options, which do already exist.
One of those options is POKT or Pocket Network, which is a decentralized blockchain node network / RPC provider supporting multiple blockchains. You can create an account for free and get RPC access through Pocket Network quite easily and change your used RPC provider in Metamask to bypass ConsenSys IP logging.
I wanted to go all-in though. Gone are the days of yore when using an Ethereum node locally meant staring up a photo of a skyscraper and waiting for Ethereum node to sync, gobbling up space on the hard drive.
Nowadays running your own node is pretty easy with helios, which is a light client for Ethereum that can even be embedded into websites and dApps, freeing them of RPC-related shackles.
Currently I run Helios manually whenever I need to do something on Ethereum, but it could be easily automated to run each time you turn on your computer. Take the RPC URL you got from POKT or any other RPC provider, and run helios --execution-rpc $ETH_RPC_URL. Boom. You’re off to the races :)
Lately ConsenSys announced that they will be logging each user’s IP addresses who use Infura as their default RPC on Metamask. RPC or remote procedure call is the “backend” server you use for communicating with blockchain networks for both inbound (loading transactions) and outbound (submitting transactions) interactions.
Since ConsenSys is a company that’s located in the US, their move is not surprising given the constant regulatory uncertainty, and Infura has made promises to decentralize its services. Before that happens, it’s announcements like these that guide users towards decentralized options, which do already exist.
One of those options is POKT or Pocket Network, which is a decentralized blockchain node network / RPC provider supporting multiple blockchains. You can create an account for free and get RPC access through Pocket Network quite easily and change your used RPC provider in Metamask to bypass ConsenSys IP logging.
I wanted to go all-in though. Gone are the days of yore when using an Ethereum node locally meant staring up a photo of a skyscraper and waiting for Ethereum node to sync, gobbling up space on the hard drive.
Nowadays running your own node is pretty easy with helios, which is a light client for Ethereum that can even be embedded into websites and dApps, freeing them of RPC-related shackles.
Currently I run Helios manually whenever I need to do something on Ethereum, but it could be easily automated to run each time you turn on your computer. Take the RPC URL you got from POKT or any other RPC provider, and run helios --execution-rpc $ETH_RPC_URL. Boom. You’re off to the races :)
No activity yet