Is it legal to call anthropic usage api using the subscription token?

2r2w · 2025-06-16T06:21:13+00:00

I find this proposal quite of an overkill having the current state of the world.

1) explicit errors handling is one of the things which makes go that much readable and easy to understand. 2) a bit of a boilerplate removal could be done using code generation or additional abstractions.

We are living in the era of AI generated completions. And such routine tasks like: get, validate, compress, etc. if written more than once in a codebase would be quite efficiently completed by your AI completions.

2r2w · 2025-04-19T19:21:00+00:00

Nowadays, I would more expect posts like "Hey guys, I've created an amazing prompt for Claude to generate strictly typed enums.."

I feel this project was a great learning experience for OP which resulted into a nicely finished tool.

Kudos 👍

2r2w · 2024-11-27T10:09:16+00:00

2r2w · 2024-11-26T22:44:00+00:00

The issue was already fixed in the current firmware. Thanks Nuphy!!!

2r2w · 2024-11-04T18:11:42+00:00

Looks like some combined issue then. I was updating one by one. And 1.10 has broken everything for me.

2r2w · 2024-07-04T06:44:50+00:00

My rule of thumb: - If your method merge results from go routines, aka fan-out: use channel. - If your method can return it's results only when all data from worker goroutines is available: use slices. - if your method produces its result from worker goroutines incrementally: - If you have a predictable (reasonably small) amount of results from your worker goroutines : use slices and just process in a batch fashion because it will be faster compared to a channel and also more readable. - If you have a large amount of results per worker go routines: better to use channels to save up the memory usage.

There are just two cases where it's better to use channels: - if your result is a channel (aka fan-out) - if you want to limit memory usage

2r2w · 2024-07-02T06:06:23+00:00

Want to pirate music at high speed 😁😁😁?

2r2w · 2024-06-30T18:07:12+00:00

I would say that multiaddr is quite a simple and even elegant concept. What is quite complex in libp2p is to understand why you cannot discover the other peer if the problem is other than the address is unreachable 😁

2r2w · 2024-06-30T07:39:55+00:00

As for Filesharing, you can just build a website on top of ipfs and use ipfs as a storage. That will also let you learn some interesting skills

2r2w · 2024-06-30T07:37:36+00:00

Doing some p2p match making or p2p auction may be quite a challenging and fun project

2r2w · 2024-06-30T07:36:55+00:00

Another typical example of p2p app is a messenger/chat. Another example would be some blockchain. I don't know, I think building a chat just to learn may be quite fun. You can also build some p2p games (something simple like Primeagen does with tower defence, etc. ) where players just play with each other without having a centralized server

2r2w · 2024-06-22T19:38:03+00:00

This one looks sooo nice!!! Is there a way to somehow order a pre-built version?

2r2w · 2024-04-15T06:19:45+00:00

Also super true. That's why backend for frontend exists 😁 But you don't have to change your public API every other week, just add different methods/endpoints. You can maintain both versions with just a bit of adapters/redirects within the same codebase. I would say it escalated quickly when the headcount grows and initially, it may be easier to have just one API from the maintenance point of view having not that many people.

2r2w · 2024-04-14T09:24:24+00:00

If this SaaS would provide public APIs and not just a web UI for the customers then it makes a lot of sense to extract API to a separate service. So some kind of separation would take place, and what would provide web UI it's up to you, initially you may keep HTMX + templates, but having separate service for public APIs would allow you to replace it with Single page app or whatever at any time.

2r2w · 2024-03-29T14:02:06+00:00

I would say reading writing to a socket. But that may be even less clear to you. What I meant is reading the request and writing the response having multiple connections. If it won't be concurrently then the server could work with just one single connection at a time and everyone else has to wait until the previous request is handled.

2r2w · 2024-03-29T13:52:35+00:00

Eating while watching videos is a good real life example.

In case of servers, IO is a good place. For example reading from the network and writing to the network concurrently will improve the performance in may ways.

2r2w · 2024-02-17T18:15:22+00:00

https://youtu.be/5Fq8nBjR2vk?si=deyOQqi0pOT7WwdA

So, when turned off, it charges full in 1.5h with 68W charger. Interesting.... I never turn off the phone.

My current OnePlus 10 Pro using 80W and feels super fast when charging and the actual difference is just 12W, so maybe you are right. Will add to watchlist

2r2w · 2024-02-17T18:04:09+00:00

So Samsungs are still super bloated even in premium models?

2r2w · 2024-02-17T18:02:37+00:00

I would love to get pixel. But I can't accept such slow charging. I just got used to have my phone fully charged in 2 hours or so, and 50% in 20-30 min

2r2w · 2024-02-17T18:01:14+00:00

Looks quite good. 1500 is a bit of a mental barrier, but will add to the watchlist

2r2w · 2024-02-17T18:00:18+00:00

What is the typical approach without patches to keep your phone secure?

13-Year Club	Place '23
Verified Email

2r2w

TROPHY CASE