166
results for "problem solve tantek"
-
Hmm, I read that and I don't see a clear problem statement of what problem you’re trying to solve, so I'd suggest doing that first (writing up specifically what problem you're trying to solve, and if you're not sure, describing maybe an "ideal" in terms of user-actions and expected results — purely in terms of user actions, with zero mention of protocols)
[tantek]
at
2022-05-16 23:14
-
tantek: It's a hard problem but I am unsure how much more time we should spend on this. I _want_ e2e encryption but wishes don't make it so. Solve it for the simpler case email first, then solve it for this more complex scenario
MMN-work
at
2017-06-07 17:32
-
tantek: yeah, just thinking that those three user stories maps to POSSE, Webmention and Micropub – so one has to check what problem one wants to solve and then look how IndieWeb can solve that
voxpelli
at
2016-07-08 19:36
-
also, it's typically premature to solve "eventually ... " type problems on a wiki, because you can just wait til they actually become a problem, and in the meanwhile solve *immediate* problems first, intead of "eventually" problems.
tantek
at
2017-03-10 19:54
-
hi beler, I recommend starting with what problems you're trying to solve for yourself on your personal website! depending on which problem(s) you want to solve, there are different protocols etc.
[tantek]
at
2022-04-01 17:45
-
every question you ask is you figuring out how to solve that problem
tantek
at
2011-06-28 21:04
-
turns out that doesn't actually help you solve the UX, which is the real problem
tantek
at
2013-08-22 20:29
-
well at least people are showing a desire to solve the problem(s)
tantek
at
2013-11-12 17:22
-
which is why I'd prefer to scope it to just the group problem and see if it's possible to even solve it for that
tantek
at
2014-01-03 19:24
-
tantek: Did the problem that technorati was trying to solve get solved?
GWG
at
2014-07-19 01:58