#Claude

:rss: Qiita - 人気の記事's avatar
:rss: Qiita - 人気の記事

@[email protected]

NRI Hackathon に11年前から参加し続けて学んだこと。2024年は生成AI Cody でした。
qiita.com/t-kurasawa/items/dc1

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

The main reason I use as my primary service is because of the projects. I've created projects for Fedify, Hollo, and LogTape on Claude and use them for authoring docs. However, I'm not 100% satisfied with Claude's models, so I wish other LLM services would offer similar features to Claude's projects.

Marcus Anthony Cyganiak's avatar
Marcus Anthony Cyganiak

@[email protected]

vs. :
Which do you prefer?

OptionVoters
ChatGPT0 (0%)
Claude0 (0%)
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

I recently wrote a manual in Korean, and then translated it into English and Japanese. It's quite a long post, but it's relatively easy to accomplish with . Here's how I used it:

• Utilize projects to provide prior knowledge.
• Translate the table of contents first.
• Define a glossary.
• Translate chapter by chapter.

However, this method assumes you speak the target language—it's a way to reduce the labor of , not a way to become fluent in a language you don't know.

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected] · Reply to 洪 民憙 (Hong Minhee)'s post

Trying out .ai as a web designer… Here's what it designed, which is a website. Does it look fine?

A prototype design of the Hollo website, designed by Claude.ai.
A prototype design of the Hollo website, designed by Claude.ai.
洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

Trying out .ai as an editor… 😂

洪 民憙 (Hong Minhee)'s avatar
洪 民憙 (Hong Minhee)

@[email protected]

A quite fair comment on by .

—In your opinion, what is Fedify's weakest point? Based on my review of the Fedify documentation, I think one potential weak point of Fedify is: The learning curve and complexity involved in properly implementing all the components of a federated ActivityPub server. While Fedify aims to simplify building ActivityPub servers, there are still many concepts and pieces that developers need to understand and implement correctly, including: • Actor dispatchers • Inbox listeners • Collection dispatchers (outbox, followers, etc.) • Key pair management • Object dispatchers • Access control • Integration with web frameworks The documentation is quite extensive, which is good, but also indicates there's a lot for developers to learn and configure properly. Even with Fedify abstracting away some of the low-level details, building a fully-featured and interoperable ActivityPub server requires understanding many moving parts. Additionally, since Fedify provides flexibility in how these components are implemented, developers still need to make many decisions about data storage, business logic, etc. This flexibility is powerful but also puts more onus on developers to implement things correctly. So while Fedify seems to be a very capable framework, the inherent complexity of building a federated server means there's still a significant learning curve and potential for implementation mistakes…
—In your opinion, what is Fedify's weakest point? Based on my review of the Fedify documentation, I think one potential weak point of Fedify is: The learning curve and complexity involved in properly implementing all the components of a federated ActivityPub server. While Fedify aims to simplify building ActivityPub servers, there are still many concepts and pieces that developers need to understand and implement correctly, including: • Actor dispatchers • Inbox listeners • Collection dispatchers (outbox, followers, etc.) • Key pair management • Object dispatchers • Access control • Integration with web frameworks The documentation is quite extensive, which is good, but also indicates there's a lot for developers to learn and configure properly. Even with Fedify abstracting away some of the low-level details, building a fully-featured and interoperable ActivityPub server requires understanding many moving parts. Additionally, since Fedify provides flexibility in how these components are implemented, developers still need to make many decisions about data storage, business logic, etc. This flexibility is powerful but also puts more onus on developers to implement things correctly. So while Fedify seems to be a very capable framework, the inherent complexity of building a federated server means there's still a significant learning curve and potential for implementation mistakes…
-0--1-'s avatar
-0--1-

@[email protected]

My project I prompt & the same prompt to compare the responses, return the results in a table I have asked them to write this code in I use because it has 18000+ packages that I am treating them as Some can see, touch the web Some can't remember Packages in R are like the specialized regions of the human brain Maybe value in packages Building the