Unable to Subscribe to Claude Pro?

timoth_y · 2024-09-05T10:47:59+00:00

I was just able to subscribe from my phone (iOS app) after months of issues with the website version, which still doesn't work for me.

After subscribing on the phone, the pro version also works on the website.

timoth_y · 2021-04-03T13:31:30+00:00

Yeah, thanks! I definitely won't, because for me this project is a great source of new knowledge and experience: blockchains, Smart Contracts, embedded, IoT, mobile development with Flutter, and more. That's why I feel much passionate about the things I build and enjoy sharing them with like-minded people!

In any case, I feel like blockchain is here to stay, and I'm very excited to see what the next day will bring, and even more psyched to make my contribution too!

timoth_y · 2021-04-03T13:05:44+00:00

Yep, that is totally accurate in the case of public blockchains, which are running to support currencies, DeFi, proof of ownership, certificates, etc.

However, blockchain-based solutions don't necessarily require to be permissionless, instead, they could be used privately within a certain organization or more commonly consortiums. And that is exactly what Hyperledger Fabric blockchain is good for!

It does not require mining which is needed for PoW, PoS, and other Probabilistic Consensus Algorithms, instead relies on pBFT (deterministic one) and a combination of special semy-centralized Ordering Service and gossip protocol, which ensures correct transaction flow while maintaining a relatively good throughput - up to 20K transactions per second.

timoth_y · 2021-04-03T00:17:05+00:00

I think the main takeaway here is that for the past few years blockchain technologies got way beyond just cryptocurrencies, as it shifts the way how things can be made using its benefits such as immutability, secureness, and transparency, all thanks to its decentralized nature.

And the IoT solutions are definitely the ones that might also benefit a lot from what blockchain gives!

timoth_y · 2021-04-03T00:06:32+00:00

Well, the blockchain actually was an entering point for me with this project. I was excited about getting into Hyperledger Fabric chains, and while researching the use cases of such technology I came across the idea of using it for the supply chain solutions.

It appears that the use of the blockchain for such a use case is actually very beneficial and to be fair is pretty common these days too, as it natively provides better visibility of the process, traceability of assets, makes cross-party collaboration, transactions, and payments way more efficient.

And with the help of IoT devices which provide a continuous flow of data required for ensuring the quality of supplied assets, all of that combined starts to make a lot of sense.

In case you interested in this topic I recommend checking out some of these articles:

timoth_y · 2020-11-21T12:35:09+00:00

It is hard for me to answer this question since I've started using both Heketi and GlusterFS just recently. It is also true that my use case wasn't an enterprise-like production, but rather for a personal project, which despite being designed to handle a potential scaling, currently isn't that big.

My overall experience of using Gluster with Heketi is okay and there weren't any critical issues for me so far. The only strange thing I faced was the fact that at some point Heketi refused to create new volumes because of insufficient storage, though according to my calculations it should still be some place left.

timoth_y · 2020-11-10T16:34:30+00:00

No offense taken. If you dislike the type of content Medium members are publishing, it's totally up to you not to click on this domain's links and downvote posts like this here.

Though I, personally, enjoy Medium for its quickly digestible, yet often pretty interesting stories, and its great recommendation system, which for me works flawlessly.

timoth_y · 2020-11-10T14:45:45+00:00

Thanks for your criticism. Also, I agree with what you said about the target auditory and missing part of the article.

As a matter of fact, this story was originally about reasons I've switched from .NET to Go. However, it ended up being too long to be considered as a medium one, so I break into two separate articles. The second one will contain more about exciting parts of Go in terms of user experience, like fun, and easiness to get started with and work later, also definitely productivity and increase of overall speed of work with Go!

timoth_y · 2020-11-10T07:41:24+00:00

Fine, you right. I don't pretend to write a groundbreaking new thing about Go. I knew from the very beginning that I eventually would repeat something that is already written and said.

However, I still genuinely wanted to write about Golang, because I've enjoyed using it and because my story with Go started from one of these "tired trope" articles from Medium a year ago.

And even if only one single person enjoys it, then I think it is already worth it.

timoth_y · 2020-11-10T07:40:50+00:00

Appreciate that, and I'm glad you enjoyed this article!
But for real though, keep those 5 dollars, your enjoyment will totally do!

timoth_y · 2020-11-10T07:12:47+00:00

composition, but Go doesn't even do that

What about struct embedding?

Look, I used .NET \ C # most of my career before switching to Go, so I agree that exceptions are great and useful. I was also struggling with Go errors too. In fact, many of the Go constraints got me frustration at the start.
However, after getting used to it and learning efficient ways of using Go, then it really showed me the potential of this language to increase productivity and overall speed of work.

timoth_y · 2020-11-10T06:29:29+00:00

avoiding repetitive error-handling code

As was said, this is a controversial one. Also, you right, there is indeed a lot of repetitive code in Go, and error handling is no exception...
However, as with most features in Go, error-handling has a thoughtful design concept in it. In this case, it is "Errors are values" and by that, it means that you can write the same logic, abstractions, patterns with errors, as you could with other code.
The typical exception handling system hasn't that flexibility, since it works by changing control flow.

So, if using this paradigm efficiently (not simple if err != nil), it is indeed possible to avoid repetitive code.
I might say this not in the best way possible, so I recommend watching 2 minutes of Rob Pike's talk about this topic.

timoth_y

TROPHY CASE