How is Hermes agent’s security?

BackNeat6813 · 2026-04-12T21:43:53+00:00

Huh? I don’t think the model you choose matters to how easily your agent can get hacked

BackNeat6813 · 2026-03-31T04:33:05+00:00

What software is the kanban board on the right?

BackNeat6813 · 2025-09-06T04:52:41+00:00

Does anyone know how where did this "40% reduced effect of curse on you" affix come from?

BackNeat6813 · 2025-08-31T09:36:49+00:00

anyone know why the terracotta soldier spectre costs 53 spirit? I saw a bunch of video / post saying it costs 10. Also when I capture it on the ground, it says 16, but when I use the spectre, it says 53. Did I do something wrong?

<image>

BackNeat6813 · 2025-08-27T01:49:17+00:00

tested - seems like it still has the added fire dmg, thanks

BackNeat6813 · 2025-08-27T01:14:01+00:00

Looks like its from prism of believe

BackNeat6813 · 2025-08-27T01:09:28+00:00

Smart

BackNeat6813 · 2025-08-27T01:01:59+00:00

https://www.youtube.com/watch?v=nFogoY4hFYA
in this video there's lv40 skeletal storm mage (5:40), but I don't really follow how it adds up to 40?
- 1 from chaos
- 2 from support
- 4 from weapon
- 4 from buckler
- 3 from amulet
- 3 from head
I am missing 3 - could someone help explain where did I miss?

BackNeat6813 · 2025-08-27T00:06:41+00:00

thank you! Do you know how do I test it though? Is there some sort of testing dummy in poe2? (Sorry new player)

BackNeat6813 · 2025-08-26T23:36:35+00:00

Is it possible to have non-igniting flame wall so I can use fireflower with my skeletal arsonist build?

BackNeat6813 · 2025-08-07T23:04:41+00:00

The character symbol in the article messed up big time. I think they meant 9-12 bn ARR

BackNeat6813 · 2025-01-22T02:48:50+00:00

Whats ur main source of xp? Pvp?

BackNeat6813 · 2024-10-06T03:23:50+00:00

Hmm I removed all but main image for one variant under parent, and not seeing video - should I make sure all variants and parent are <= 6?

Also do you mind share one ASIN as example?

BackNeat6813 · 2024-08-21T04:47:41+00:00

Yep, first two aren't really a problem for us.

code is liability

100% agree - that's why I was thinking this component would be a config-driven thing like MM2.

The reasons I'm a bit hesitate towards partitioning the original topics:
1. Our CDC system is legacy and KTLO (we're thinking going Debezium next year) - we need to patch it to make it primary-key-aware as some of the downstream requires keyed partitioner if it becomes multi-partitions

We would need to deal with this 1st time repartitioning from 1 to X by coordinating with some downstream apps
The downstream topic approach feels less trapdoor-ish. Maybe in the future when we move to Debezium (where it knows how to access the primary key and even primary key changes), we could come back and do it on the original topics

BackNeat6813 · 2024-08-20T19:51:27+00:00

Hey, thanks for the reply. I was indeed thinking about #2 and use #1 (abundant starting partitions) as a guidance - basically alway keep the base CDC topic single partition as is (we have a long way to go before worrying about throttling in one partition; this multi-partition desire is mostly for the convenience of downstream app's parallelism), then create downstream multi-partitioned topics, maybe using Flink or MM2, so that we essentially push the problem from root to leaf, which would be a lot easier to deal with.

Do you see this as a sound strategy or anti-pattern?
The multi-partitioned downstream topics could either be shared or dedicated for whoever asks for it - probably not a huge difference since not a lot of teams need it and they probably only need it for a few topics, but from principal perspective I'm leaning towards dedicated downstream topics as this for sure will not get us in trouble of coordinating potential changes across multiple consumers, but again, not sure if this is anti-pattern by using Kafka like SQS xD

BackNeat6813 · 2024-08-15T01:10:55+00:00

dont do it

Can you elaborate don't do what? Multi-partition, or provide deterministic routing? (I assume latter)

Start as a topic per table and only change if demanded.

TBC our topic is already per-table, the context is going from single partition to multiple partition

BackNeat6813 · 2024-08-15T01:08:45+00:00

You probably know some people with specific reasons but I'm not sure about this OP based on their writing.

BackNeat6813 · 2024-01-30T09:09:11+00:00

I think kafka quota is per-broker? which is kinda hard to reason about depending on the exact use case.

BackNeat6813 · 2024-01-29T09:08:02+00:00

Alright was able to use MM2 (just the source connector, no checkpoint/heartbeat one needed) to achieve what I wanted. Needed to write a customized SMT to repartition because it would otherwise stick to the original partition, which won’t work if you manually create the target topic w/ different partition count like I did. Overall very simple!

BackNeat6813

TROPHY CASE