36 results for "problem solve tantek"

  • capjamesg[d], I'd ask you to first define what user problem you are hoping to solve by using srcset, to see if it really is a problem worth solving (in opportunity cost of all other potential user problem solutions / human experience improvements for your personal site)
    [tantek] at 2025-01-02 02:07
  • Maybe too abstract a question? What problem are you trying to solve? (By moving away from a frontend framework)
    [tantek] at 2024-09-02 15:54
  • the problem that URLs solve is sharing across/between users, especially between *strangers*, e.g. the "billboard or the back of a t-shirt" example I gave above
    [tantek] at 2024-06-25 20:54
  • jimwins you have already solve this problem with rel=me yourself! <li><a rel="me" href="https://mefi.social/@jimw">@jimw@mefi.social</a></li>
    [tantek] at 2024-06-21 00:27
  • to2ds what problem are you trying to solve with a .edu domain name?
    [tantek] at 2024-03-08 22:26
  • Yeah we need to solve the well known redirects problem.
    [tantek] at 2024-01-10 05:04
  • ^ that's the user-problem I was trying to solve
    [tantek] at 2023-12-26 22:37
  • omz13++ yes! Implementations, prototypes, even if they "only" solve a problem for one person, you, are 1000x more useful & valuable than purely theoretical discussions (AKA architecture astronomy)
    [tantek] at 2023-10-26 16:05
  • capjamesg, using IndieAuth would solve the problem of having to have chat users pick a username (or impersonate)
    [tantek] at 2023-03-21 22:42
  • or we solve the problem from other side, where if HTML is returned by the conneg request, the consuming code sends it through an mf2 parser and then ... ?
    [tantek] at 2022-12-26 04:40
Sort by:

Filter results by:

Tag

Query took 0s.


Search tips

Exclusion
+foo -bar
Logical OR
foo OR bar
Exact phrase
"foo bar"
Partial words
foo*
Particular fields only
title:foo
domain:example.org
nick:somebody
after:2016-11-23
before:2016-11-23
date:2016-11-23