Iām giving a shot talk about twtxt/yarn/timeline tommow around noon CET at Piksel Festival in Norway. More info and link for live stream at: https://24.piksel.no
(So I will most likely not be joining the call)
@prologic@twtxt.net Iāve just seen that one as well as MicroBin on selfh.st , it looks prettier on your instance than it did on their live demo š. But Iāve already started playing around with microBin and will see how things go from there.
Alright, I gave #htwtxt container a quick spin. The thing lives and feels dead simple, like, echo -e ādate -Im
\tHello world!ā >> twtxt.txt kind of simple but with a GUI. and I LOVE IT! Now letās see if we can rebuild the image with the latest version of htwtxt.
āSelfishness is not living as one wishes to live, it is asking others to live as one wishes to live. And unselfishness is letting other peopleās lives alone, not interfering with them.
Selfishness always aims at creating around it an absolute uniformity of type. Unselfishness recognizes infinite variety of type as a delightful thing, accepts it, acquiesces in it, enjoys it.
It is not selfish to think for oneself. A man who does not think for himself does not think at all. It is grossly selfish to require of oneās neighbor that he should think in the same way, and hold the same opinions. Why should he? If he can think, he will probably think differently. If he cannot think, it is monstrous to require thought of any kind from him.
A red rose is not selfish because it wants to be a red rose. It would be horribly selfish if it wanted all the other flowers in the garden to be both red and roses.ā
āOscar Wilde, The Soul of Man & Prison Writings
@bender@twtxt.net cos I live outside the United States and they donāt send to my country
I wish I could absorb some of the horrors the rescue workers will encounter in Valenciaās underground garages and basements, so they could somewhat manage on with their own lives after⦠#realheroes #cannotunsee
@xuu@txt.sour.is done, and done, and done. The three of us dropped our mail-in ballots, and received confirmation they are counted. Living in a red state (well, kid said it is more like purple now) makes me sad, and mad, but I have done what I canāand that includes explaining things to others, and encouraging them to vote.
Three days from today, towards the end of the day, we in the US will have an idea of who the nationās presiding person will be for the next four years. In the 32 years I have lived here, I have never been more worried about an election outcome.
Inversion by Aric McBay was another random library pick. Like The Fall of Io, itās the most recent in a series, though I think this series is pretty loosely connected. In contrast, the villain in this book is simple and cartoonishly evil. The book presents a design for utopia which was interesting but a little cloying. Iām not sure if Iām supposed to want to live there, but I donāt think I do. I enjoyed the book as easy reading, and might try the others in the series some time. (4/4)
Iām planning to be there tomorrow (message from yesterday, since we can not all live in the future;)
Reading about browser security measures and getting sad we donāt live in a world where cross-site scripting is a feature instead of a bug.
@off_grid_living@twtxt.net I gave it a try, unfortunately itās a scanned document (just a bundle of Images), the only real text in there, is the first two pages.
@off_grid_living@twtxt.net is it locked because of a DRM thing or something else?
Otherwise you can check if you already have the pdftotext
command that comes with the poppler-utils package, try converting converting the pdf into a text file and copy to your heartās content. I have just tried it myself.
If you donāt have it already hereās what you can do on Ubuntu or any Debian based distribution of Linux:
- Update and upgrade your packages:
> sudo apt update && sudo apt upgrade
- Install the
poppler-utils
package
> sudo apt install poppler-utils
- Now you can convert your pdf to txt file with:
> pdftotxt -layout -enc UTF-8 name_of_source_file.pdf name_of_destination_file.txt
You can always do a pdftotxt --help
to see the rest of possible options.
Hope this helps.
@off_grid_living@twtxt.net mind sharing the PDF, to take a look? Some PDF containing text as images, which makes it more difficult to complete the task you want to perform.
Definitely NOT editing that Oupsie⦠+ It looks all the same in terminal, so I can live with it.š¤£
@lyse@lyse.isobeef.org on this:
3.2 Timestamps: I feel no need to mandate UTC. Timezones are fine with me. But I could also live with this new restriction. I fail to see, though, how this change would make things any easier compared to the original format.
Exactly! If anything it will make things more complicated, no?
Good writeup, @anth@a.9srv.net! I agree to most of your points.
3.2 Timestamps: I feel no need to mandate UTC. Timezones are fine with me. But I could also live with this new restriction. I fail to see, though, how this change would make things any easier compared to the original format.
3.4 Multi-Line Twts: What exactly do you think are bad things with multi-lines?
4.1 Hash Generation: I do like the idea with with a new uuid
metadata field! Any thoughts on two feeds selecting the same UUID for whatever reason? Well, the same could happen today with url
.
5.1 Reply to last & 5.2 More work to backtrack: I do not understand anything youāre saying. Can you rephrase that?
8.1 Metadata should be collected up front: I generally agree, but if the uuid
metadata field were a feed URL and no real UUID, there should be probably an exception to change the feed URL mid-file after relocation.
@prologic@twtxt.net Thanks for writing that up!
I hope it can remain a living document (or sequence of draft revisions) for a good long time while we figure out how this stuff works in practice.
I am not sure how I feel about all this being done at once, vs. letting conventions arise.
For example, even today I could reply to twt abc1234 with ā(#abc1234) Edit: ā¦ā and I think all you humans would understand it as an edit to (#abc1234). Maybe eventually it would become a common enough convention that clients would start to support it explicitly.
Similarly we could just start using 11-digit hashes. We should iron out whether itās sha256 or whatever but thereās no need get all the other stuff right at the same time.
I have similar thoughts about how some users could try out location-based replies in a backward-compatible way (append the replyto: stuff after the legacy (#hash) style).
However I recognize that Iām not the one implementing this stuff, and itās less work to just have everything determined up front.
Misc comments (I havenāt read the whole thing):
Did you mean to make hashes hexadecimal? You lose 11 bits that way compared to base32. Iād suggest gaining 11 bits with base64 instead.
āClients MUST preserve the original hashā ā do you mean they MUST preserve the original twt?
Thanks for phrasing the bit about deletions so neutrally.
I donāt like the MUST in āClients MUST follow the chain of reply-to referencesā¦ā. If someone writes a client as a 40-line shell script that requires the user to piece together the threading themselves, IMO we shouldnāt declare the client non-conforming just because they didnāt get to all the bells and whistles.
Similarly I donāt like the MUST for user agents. For one thing, you might want to fetch a feed without revealing your identty. Also, it raises the bar for a minimal implementation (Iām again thinking again of the 40-line shell script).
For āwho followsā lists: why must the long, random tokens be only valid for a limited time? Do you have a scenario in mind where they could leak?
Why canāt feeds be served over HTTP/1.0? Again, thinking about simple software. I recently tried implementing HTTP/1.1 and it wasnāt too bad, but 1.0 would have been slightly simpler.
Why get into the nitty-gritty about caching headers? This seems like generic advice for HTTP servers and clients.
Iām a little sad about other protocols being not recommended.
I donāt know how I feel about including markdown. I donāt mind too much that yarn users emit twts full of markdown, but Iām more of a plain text kind of person. Also it adds to the length. I wonder if putting a separate document would make more sense; that would also help with the length.
@aelaraji@aelaraji.com This is one of the reasons why yarnd
has a couple of settings with some sensible/sane defaults:
I could already imagine a couple of extreme cases where, somewhere, in this peaceful world oneās exercise of freedom of speech could get them in Real trouble (if not danger) if found out, it wouldnāt necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for⦠letās just say āTheir well beingā, would it heart if a pod just purged their content if itās serving it publicly (maybe relay the info to other pods) and call it a day? It doesnāt have to be about some law/convention somewhere ⦠𤷠I know! Too extreme, but Iāve seen news of people whoād gone to jail or got their lives ruined for as little as a silly joke. And it doesnāt even have to be about any of this.
There are two settings:
$ ./yarnd --help 2>&1 | grep max-cache
--max-cache-fetchers int set maximum numnber of fetchers to use for feed cache updates (default 10)
-I, --max-cache-items int maximum cache items (per feed source) of cached twts in memory (default 150)
-C, --max-cache-ttl duration maximum cache ttl (time-to-live) of cached twts in memory (default 336h0m0s)
So yarnd
pods by default are designed to only keep Twts around publicly visible on either the anonymous Frontpage or Discover View or your Timeline or the feedās Timeline for up to 2 weeks with a maximum of 150 items, whichever get exceeded first. Any Twts over this are considered āoldā and drop off the active cache.
Itās a feature that my old man @off_grid_living@twtxt.net was very strongly in support of, as was I back in the day of yarnd
ās design (nothing particularly to do with Twtxt per se) that Iāve to this day stuck by ā Even though there are some š that have different views on this š¤£
@movq@www.uninformativ.de @falsifian@www.falsifian.org @prologic@twtxt.net Maybe I donāt know what Iām talking about and Youāve probably already read this: Everything you need to know about the āRight to be forgottenā coming straight out of the EUās GDPR Website itself. It outlines the specific circumstances under which the right to be forgotten applies as well as reasons that trump the oneās right to erasure ā¦etc.
Iām no lawyer, but my uneducated guess would be that:
A) twts are already publicly available/public knowledge and such⦠just donāt process childrenās personal data and MAYBE youāre good? Since thereās this:
⦠an organizationās right to process someoneās data might override their right to be forgotten. Here are the reasons cited in the GDPR that trump the right to erasure:
- The data is being used to exercise the right of freedom of expression and information.
- The data is being used to perform a task that is being carried out in the public interest or when exercising an organizationās official authority.
- The data represents important information that serves the public interest, scientific research, historical research, or statistical purposes and where erasure of the data would likely to impair or halt progress towards the achievement that was the goal of the processing.
B) What I love about the TWTXT sphere is itās Human/Humane element! No deceptive algorithms, no Corpo B.S ā¦etc. Just Humans. So maybe ⦠If we thought about it in this way, it wouldnāt heart to be even nicer to others/offering strangers an even safer space.
I could already imagine a couple of extreme cases where, somewhere, in this peaceful world oneās exercise of freedom of speech could get them in Real trouble (if not danger) if found out, it wouldnāt necessarily have to involve something to do with Law or legal authorities. So, If someone asks, and maybe fearing fearing for⦠letās just say āTheir well beingā, would it heart if a pod just purged their content if itās serving it publicly (maybe relay the info to other pods) and call it a day? It doesnāt have to be about some law/convention somewhere ⦠𤷠I know! Too extreme, but Iāve seen news of people whoād gone to jail or got their lives ruined for as little as a silly joke. And it doesnāt even have to be about any of this.
P.S: Maybe make X
tool check out robots.txt? Or maybe make long-term archives Opt-in? Opt-out?
P.P.S: Already Way too many MAYBEās in a single twt! So Iāll just shut up. š
@movq@www.uninformativ.de Iām glad you like it. A mention (@<movq https://www.uninformativ.de/twtxt.txt>
) is also long, but we live with it anyway. In a way a replyto:
is just a mention of a twt instead of a feed/person. Maybe we chould even model the syntax for replies on mentions: (#<2024-09-17T08:39:18Z https://www.eksempel.dk/twtxt.txt>)
?!
Pinellas County - Long Run: 11.04 miles, 00:11:22 average pace, 02:05:22 duration
body was a bit worn out today. switched it up to walk-run after about 5 miles because i have a daddy-daughter dance this afternoon and did not want to be too stiff. met another runner who actually only lives about a mile or less from me. maybe i will try to meet with him after my business trip next week.
#running
i know i canāt keep living in this dead or dying dream..
Hello twtxt! Iām James (or @falsifian@www.falsifian.org). I live in Toronto. Recent interests include space complexity, simple software, and science fiction.
Could you perhaps just have a check box to do the opposite, like āDonāt remember meā? Iāve seen that a couple of places I think. Sort of an opt in short lived login, if youāre at a public library or something etc.
Referer
is /post
then consider that total bullshit, and ignore? š¤
@prologic@twtxt.net I was wondering if my reverse proxy could cause something but itās pretty standardā¦
server {
listen 80; server_name we.loveprivacy.club;
location / {
return 301 https://$host$request_uri;
<a href="https://yarn.girlonthemoon.xyz/search?q=%23proxy_pass">#proxy_pass</a> http://127.0.0.1:8000;
}
}
server {
listen 443 ssl http2;
server_name we.loveprivacy.club;
ssl_certificate /etc/letsencrypt/live/we.loveprivacy.club/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/we.loveprivacy.club/privkey.pem;
client_max_body_size 8M;
location / {
proxy_pass http://127.0.0.1:8000;
}
}
Modes of Transportation
ā Read more
36/2 = 18
at 25 Twts per page, that's about ~72% of the search/view real estate you're taking up! wow 𤩠-- I'd be very interested to hear what ideas you have to improve this? Those search filters were created so you could sift through either your own Timeline or the Discover view easily.
@prologic@twtxt.net It was one of (if not THE) first feed(s) I got to follow after discovering Twtxt and setting up my own.
It was quite nice for the first couple of hours, Iāve even got to explore a couple of @dfaria.eu@dfaria.euās articles.
Theeeeen⦠Things started to feel a bit overwhelming I had to āClean Things Up!ā.
Flushed my whole Jenny/Mutt cached twtxt feed and re-synced everything all over again.
But hey,
Good evening! š§šµGuns Nā Roses - Live and let die.
@bender@twtxt.net @prologic@twtxt.net Well, Imagine getting to wake up around that same time, every, single, day. š„±
(It aināt as good of a live as it sounds though.)
Added support for #tag clouds and #search to timeline. Based on code from @dfaria.eu@dfaria.euš
Live at: http://darch.dk/timeline/?profile=https://darch.dk/twtxt.txt
Does everyone who posts from ciberlandia live in the same house in Portugal ?
Sad to see moc
removed from the official arch linux repos, but also cool to learn the debian project has been quietly patching it and keeping it up to date in recent years. Long live the music on console player. (And debian!) :-)
@movq@www.uninformativ.de the location is real. A few in the āhood mentioned seeing this person directly. They live somewhere on the hillside in the background of the video.
Sam Scrantonās new album Body Pillow lives up to its name. Giving it a big hug again this morning. #nowplaying
AI made from living human brain cells performs speech recognition
A biocomputing system consisting of living brain cells learned to recognise the voice of one individual from hundreds of sound clips ā Read more
I would love to be able to time travel back to the days when Talking Heads toured and witness one of their epic live concerts.
Under the Stars
ā Read more
new website is live!! https://www.noizhardware.com
Terminator model has living skin made from fungus
By fusing fungi and robots, researchers hope to create a sustainable and biodegradable skin capable of sensing a variety of stimuli, as demonstrated by a model of the Terminator ā Read more
Erlang Solutions: Blockchain in Sustainable Programming
The benefits of blockchain implementation across multiple sectors are well-documented, but how can this decentralised solution be used to achieve more sustainable programming?
As the effects of the ongoing climate crisis continue to impact weather patterns and living conditions across the planet, we must continue to make every aspect of our lives, from transport and energy usage to all of our technology, greener and more sustain ⦠ā Read more
The hottest 21 days ever recorded on Earth were the last 21 days.
There are climate scientists saying that this summer will be the coolest summer of the rest of our lives. It wonāt get cooler.
They can say that with confidence because Earthās energy imbalanceāthe difference between how much energy comes in versus how much is radiated back to spaceāhas been positive since around 2010. Prior to that, the balance would shift negative sometimes, so Earth would radiate a bunch of energy back into space. Not anymore. Earth is an energy sponge now. And net positive incoming energy means temperatures go up.
Climate disaster has been here for awhile, but itās kicking into high gear now. This will not change until we take drastic action.
A house is a machine for living in
@prx@si3t.ch I like this idea but usually I am living in a terminal or Emacs.
Do they legitimately believe that end users will encounter videos of gruesome murders, live streams of school shootings, etc etc etc, and be like āoh, tee hee hee, thatās not what I want to see! Iād better block that!ā and go about their business as usual?
No, they canāt possibly be that foolish. They are going to be doing some amount of content moderation. Just not of Nazis, fascists, or far right reactionaries. Which to me means they want that content on there.
There is a ārightā way to make something like GitHub CoPilot, but Microsoft did not choose that way. They chose one of the most exploitative options available to them. For that reason, I hope they face significant consequences, though I doubt they will in the current climate. I also hope that CoPilot is shut down, though Iām pretty certain it will not be.
Other than access to the data behind it, Microsoft has nothing special that allows it to create something like CoPilot. The technology behind it has been around for at least a decade. There could be a āpublicā version of this same tool made by a cooperating group of people volunteering, āleasingā, or selling their source code into it. There could likewise be an ethically-created corporate version. Such a thing would give individual developers or organizations the choice to include their code in the tool, possibly for a fee if thatās something they want or require. The creators of the tool would have to acknowledge that they have suppliersāthe people who create the code that makes their tool possibleāinstead of simply stealing what they need and pretending thatās fine.
This era weāre living through, with large companies stomping over all laws and regulations, blatantly stealing other peopleās work for their own profit, cannot come to an end soon enough. It is destroying innovation, and we all suffer for that. Having one nifty tool like CoPilot that gives a bit of convenience is nowhere near worth the tremendous loss that Microsoftās actions in this instace are creating for everyone.
@carsten@yarn.zn80.net Animals have inner lives. Computers do not.
Are you really so desperate to make this point thst youāre citing Quora??? Believe what you want to believe.
Entwives
ā Read more
#event Upcomming Meetup in Copennhagen: algolab(the_art_of_live_coding) @ StĆøberiet / Computer Klub