Searching We.Love.Privacy.Club

Twts matching #like
Sort by: Newest, Oldest, Most Relevant

Hey @manton I got this email this morning from name.com – Just wondering if I could have my prologic.blog domain transferred to me? 🤔 Whilst I have enjoyed using my micro.blog service I’d like to move away off of micro.blog and host my own blog, which I intend to use my own static tool for.

Thank you for providing such a great service over the years I’ve used micro.blog 🙇‍♂️

Image

Read more

⤋ Read More

@adi@f.adi.onl Ugh sorry for not replying. If the file list is dynamic, usually you use something like autoconf to generate the Makefile. I’ve also used wildcards in the past and that works okay. You should be able to use shell commands to populate the file list.

⤋ Read More
In-reply-to » Ugh why does Emojipedia sell my data. This is so silly.

@prologic@twtxt.net Yeah like normally I’m just a little annoyed and just say “whatever” and shrug it off, but come on I am searching for emojis here. Do you really need to harvest my user data for what is essentially a fuzzy search in the Unicode table?

⤋ Read More
In-reply-to » @movq Another feature request: sometimes I start writing a twt but then would like to discard it. It would be great if jeny could detect that I did not wrote (or saved) anything and then discards the twt instead of creating an "empty" one.

@movq@www.uninformativ.de My workflow is as follows.

I hit “reply” hotkey and my editor comes up.

With or without writing something I close my editor without saving the content.

Of course I close it by C-x C-c, not by :q! ;-)

Jenny finds the temp file unchanged, e.g. it’s content is the same as it was when my editor was started. I would like that jenny discards the reply then.

Autosaving is no problem either. Real editors do this to a temporary (kind of backup) file. Only in case of a crash that file is consulted and the user is asked if she would like to continue with that stored content.

⤋ Read More

Peter Saint-Andre: Philosophy vs. Ideology
Today I’d like to explore some implications of my recent series of posts about the nature of opinion; specifically, the dangers of ideology. (As a reminder, so far I’ve discussed holding fewer opinions, opinions about opinions, holding multiple opinions, opinions vs. truths, and opinions weak and strong.)… ⌘ Read more

⤋ Read More

Funny bug in LG TV: last Saturday I scheduled some film from yesterday for recording. Actual recording yesterday started 1 hour late. Looks like although TV knows actual time perfectly well it was not capable to “translate” schedule from CEST to CET.

⤋ Read More

Ignite Realtime Blog: Smack 4.4.4 released
We are happy to announce the release of Smack 4.4.4. Thanks to numerous contributors this patch level release includes many fixes and improvements. I’d like to especially thank the folks from Jitsi, namely Boris Grozev, Damian Minkov, Ingo Bauersachs, and Jonathan Lennox. Who tracked down multiple bugs, including a nasty concurrency bug. Furthermore, thanks to Ingo, Smack and its important dependencies [jxmpp](https://github.com/ign … ⌘ Read more

⤋ Read More

@movq@www.uninformativ.de
I’m not a Python programmer, so please bear with me.
The doc about encodings does also mention:

If you require a different encoding, you can manually set the Response.encoding property

Wouldn’t that be a one liner like (Ruby example)?

'some text'.force_encoding('utf-8')

I understand that you do not want to interfere with requests. On the other hand we know that received data must be utf-8 (by twtxt spec) and it does burden “publishers” to somehow add charset property to content-type header. But again I’m not sure what “the right thing to do” ™ is.

⤋ Read More

@prologic@twtxt.net @movq@www.uninformativ.de
Exactly, you see correct UTF-8 encoded version (even with content-type: text/plain leaving out charset declaration).

After following utf8test twtxt myself I now see that jenny does not handle it as UTF-8 when charset is missing from HTTP header, just like @quark@ferengi.one has observed.

So should jenny treat twtxt files always as UTF-8 encoded? I’m not sure about this.

⤋ Read More
In-reply-to » My thoughts about range requests

@movq@www.uninformativ.de

Don’t miss step 0 (I should have made this a separate point): having a meta header promising appending twts with strictly monotonically increasing timestamps.

(Also, I’d first like to see the pagination thingy implemented.)

In jenny I would like to see “don’t process previously fetched twts” AKA “Allow the user to archive/delete old twts” feature implemented ;-)

⤋ Read More

My thoughts about range requests

Additionally to pagination also range request should be used to reduce traffic.

I understand that there are corner cases making this a complicated matter.

I would like to see a meta header saying that the given twtxt is append only with increasing timestamps so that a simple strategy can detect valid content fetched per range request.

  1. read meta part per range request
  2. read last fetched twt at expected range (as known from last fetch)
  3. if fetched content starts with expected twt then process rest of data
  4. if fetched content doesn’t start with expected twt discard all and fall back to fetching whole twtxt

Pagination (e.g. archiving old content in a different file) will lead to point 4.

Of course especially pods should support range requests, correct @prologic@twtxt.net?

⤋ Read More

My thoughts about pagination (paging)

Following the discussion about pagination (paging) I think that’s the right thing to do.

Fetching the same content again and again with only a marginal portion of actually new twts is unbearable and does not scale in any way. It’s not only a waste of bandwidth but with increasing number of fetchers it will also become a problem for pods to serve all requests.

Because it’s so easy to implement and simple to understand, splitting twtxt file in parts with next and prev pointers seems a really amazing solution.

As in RFC5005 there should also be a meta header pointing to the main URL, e.g. current or baseurl or something like that. This way hashes can calculated correctly even for archived twts.

⤋ Read More

13 short and scary games plus source to play (or hack) this Halloween 🎃
It’s that time of year again where I like to share seasonally spooktacular games plus source code—a goldmine of material for (a) those looking for coffee-break entertainment, (b) those interested in learning more about game ⌘ Read more

⤋ Read More
In-reply-to » Dug out my old usb audio device and now my Plan 9 raspberry pi can play music. 💯

Lots. 🤣 The system is small, coherent, and understandable in a way no modern unix is. The namespace operations remain incredibly powerful. And several of the tools built on it, like the way network listeners and the mail server are built, are just much nicer to use, modify, and build on.

⤋ Read More

My nutritional supplements aim should be:

  • 1 or 1.5 cups of lentils (or any beans you might like better).
  • 2 or 2.5 cups of bitter greens.
  • 1 cup of your favourite protein (or an egg), grilled, or fried with a little of olive oil.
  • 1 or 2 tomatoes, or a handful if of the cherry type.
  • No added sugars. If it is sweet, make it have fibre.
  • No added salt (or very little and ionised), as salt is everywhere.

Related, I tried wild rice for the first time yesterday. It was different, in a good way.

⤋ Read More

Got to love the sense of humour:

Blog.txt supports multiple options for the chronological order of posts. If you start writing new posts below old posts, the default post sort is descending. If you start writing new posts above all the old posts, like I do, then the post sort algorithm will default to ascending. But if the user would like to change the sort order of the posts, they can press the “End” button on their keyboard to reverse the default chronological order!

⤋ Read More

Bookmarked : Fix Facebook by Making It More Like Google+ - The Atlantic
My colleague Adrienne LaFrance has named the fundamental assumption, and danger, of social media megascale: “not just a very large user base, but a tremendous one, unprecedented in size.” Technology platforms such as Facebook assume that they deserve a user base measured in the billions of people—and then excuse their misdeeds by noting that effectively controlling such an unthinkably la … ⌘ Read more

⤋ Read More

@prologic@twtxt.net
Thank you, that’s the correct one.

Still I have this in my logs (first access of “eleven” by yarnd):

ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “GET /eleven.txt HTTP/2.0” 200 344 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”
ip.ip.ip.ip - - [21/Oct/2021:20:05:36 +0000] “HEAD /avatar.png HTTP/2.0” 200 0 “-” “yarnd/0.2.0@46bea3f (Pod: twtxt.net Support: https://twtxt.net/support)”

And I guess without avatar.png sitting there I would have seen even more requests like /eleven.txt/avatar.png.

I’ve copied stackeffect.png to avatar.png to make yarnd happy when accessing stackeffect.txt.

So in this setup yarnd fetched eleven.txt along with avatar.png which belongs to another twtxt. This feels buggy.

⤋ Read More
In-reply-to » @movq OK, I am on request/question asking mode today. 😋 How do you cancel a twt, or a reply to a twt? Say I hit my reply, and then I change my mind? Right now, even exiting vi is creating an empty line on my twtxt.txt. Is there an obvious way to cancel a twt, reply, or fork that I am missing?

@movq@www.uninformativ.de
Aha! Cool! Not just deleting, but proceeding as if the twt is going to be send. If I :q! on vi it will add an empty line. If, instead, I go :x like I normally do, it works as you said—and as I wanted it. Thanks!

⤋ Read More

@movq@www.uninformativ.de What I would really like to see if jenny could use HTTP range requests to fetch only new content.

E.g. it could refetch only last twtext line of last request to make sure it starts off at correct position.

I guess there are twtxt files that only grow, then this will save a lot bandwidth over time.

For twtxt files that “forget” older content this situation would be detected and as a fallback the whole twtxt file could then be fetched.

⤋ Read More

@prologic@twtxt.net I would like to see “header” lines in twtxt.txt parsed.

Personally I started looking at some twtxt files with curl and saw information about avatar images.

I assumed that to be sort of standard and mentioned my avatar image in my stackeffect.txt. But it was not “avatar.png”.

Later I saw in logfiles that the info was totally ignored and instead several “avatar.png” locations were tried by the pulling side.

When information in “header” of twtxt file were respected one could easily change avatar file to one with a new filename and there would be no caching problem.

⤋ Read More