prologic @twtxt.net

Follow

"Problems are Solved by Method" 🇦🇺👨‍💻👨‍🦯🏹♔ 🏓⚯ 👨‍👩‍👧‍👧🛥 -- James Mills (operator of twtxt.net / creator of Yarn.social 🧶)

Block / Report User

If this user/feed is violating this Pod's (yarn.meff.me) community guidelines as set out in the Abuse Policy, please report them immediately!

You are also free to Unfollow or Mute this user or feed. Muting will also remove that user/feed's content from your view and you will no longer see content from that user/feed anywhere.

@prologic does not follow you (they may not see your replies!)

Recent Twts

Recent twts from prologic

(#fh6ymua) And @eaplmx@twtxt.net I thnik you’re overthinking this a big. what you’re proposing is actually a good idea for when a feed author decides to move their feed. Something we’ve wanted to add to yarnd specifically in the past, whereby a user could “delete” their feed/account but tell yarnd that it’s moved over here. Redirects would then be put in place for say up to 90 days or something so clients don’t have to be updated (or are automatically updated because of the redirect responses).


#eh4ijkq

(#fh6ymua) @lyse@lyse.isobeef.org I kind of agree with @mckinley@twtxt.net here in that centralising this goes against the grain of the Yarn/Twtxt ecosystem we’ve built. Instead why don’t we do one of two things (or both):

  • Figure out the source of the “bad data” in the first place, and fix it.
  • Build an interface for yarnd operators to write “rewrite rules” to handle this (assuming finding/fixing the bad data doesn’t work)
  • Something else?

I feel like this is just a case of “bad data” that can be fixed easily.


#ddmgxaq

(#5euzxra) @darch@neotxt.dk I think this line is confusing the Lexttwt and Markdown parsers:

2022-10-06T10:04:12Z	```	[by: @darch@neotxt.dk] and then the message

It would be better if this was:

2022-10-06T10:04:12Z	by: <a href="https://yarn.meff.me/external?uri=https://neotxt.dk/user/darch/twtxt.txt&nick=darch">@darch<em>@neotxt.dk</em></a> and then the message

I think 🤔”`


#l6eioiq

(#fv47lyq) @darch@neotxt.dk This is built-in to yarnd – Basically on every failed password auth, you cause a delay. Every time the same IP/User tries to login and fails, you increase this delay. It makes “brute force” attempts at password auth much much harder to do.


#am6n4lq

(#2fkr5fq) @justamoment@twtxt.net Your idea of embedding something on a website intrigues me. I know how we can do it, but there just hasn’t been enough of a demand to built it (yet). Basically (if I may):

  • [ ] Add microPub API to yarnd
  • [x] Add IndieAuth support (provider) to yarnd

Once we have these two pieces in place (we’re half-way there already) we can embed a little widget on websites that lets any visitor to your site login to the pod you choose to use, we’d create them an account on the fly, and then they can use the widget to make comments.

Does any of this make sense?


#wpccfmq

(#2fkr5fq) Yarn.social pods (running yarnd) also support Web Mentions too btw… In theory (even now) it is possibly to modify the code to accept inbound Web Mentions – Though I’ve never seen it used in practise 😢 Anyway we support a lot of IndieWeb features 👌


#hnur7sq

(#oddbvrq) @brasshopper@twtxt.net Thanks! 🙏 Again I’m sorry. One of the things I’m painfully aware of iw how “text” form (especially short-form) can be so misleading and intent misinterpreted. – Yes you’re probably right, short-form microBlogging such as Yarn/Twtxt is probably ill suited to “hard debates” like the one we just seemed to have 😅 – OTOH it can also be fine, this isn’t the first time “hot debate” has occurred in the Yarn/Twtxt ecosystem at large, sometimes they’ve gone on for days 😅


#nt2uj4a

(#ixzxfwq) I think I read somewhere similar things about the possibility of taxing unrealized gains too.

The problem is that it’s completely unfair as it’s unrealized. You actually haven’t made any gains at all, so you’re taxing something that may have artificially gone up in value, but then just as easily may go back down in value.


#xaujwqa