# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 194364
# self = https://watcher.sour.is?offset=194162
# next = https://watcher.sour.is?offset=194262
# prev = https://watcher.sour.is?offset=194062
It was raining cats and dogs for a few minutes, I almost couldn't see the houses down in the valley anymore. Pretty sick. :-)
@bender Haha, yeah, we're also better off rolling dice sometimes. I usually don't mind liquid sunshine either. But I have to be prepared for it. As a matter of prudence, I brought my rain jacket along. In the end, I was wet from the inside as well, though. The breathability of this plastic bag isn't as good as they always claim it to be. Especially in summer.
Three weather services with three different forecasts. We got a little bit rained on, so at least some of them were not completely wrong. The timing was off by an hour, though. And nobody expected the Spanish inqui^W^Wthunder either. It was a nice walk.
Oh cool, as I type this, lighning and thunder very close by now. At most a kilometer away. Glad I'm home and not in the woods anymore. And heavy rain kicks in, too.
replies and following implemented! next step is further parsing of post contents, rendering threads, and then maybe i can finally start adding remote feeds...! though i kinda wanna redo the whole ui ^^'
demo showing two users following and unfollowing eachother, showing up in eachothers timelines, and replying to one another
You can also buy stickers and other items... soon my "Python Reading Club" and "Python is also for artists!" designs will be available. This will help support my free and open source activities. I make free and open educational resources, I teach at several places and I need to make ends meet.
#python #numpy #shapely #trimesh #py5 #creativeCoding #FLOSS Redbubble shopping catalog image of a smiling woman wearing a blue T-Shirt with an image of a "purple slab" with holes in a stencil font forming the words: "numpy, shapely, trimesh, & py5."
@lyse I usually only have my GPS tracker with me. That trip yesterday was probably a one-time thing. 😅 It was fun, but I’d rather not carry so much stuff around. 🥴
Não sei se é inteiramente justo ou não, mas para a #musiquinta sobre "one hit wonders", aqui fica a música da cabra, conhecida por muitos mais do que sabem que ela é de "The Farmlopez": https://youtu.be/g1BT-6koP7I
If I'm in the woods, I'd like to not waste my time with computers and focus on the beauty of nature. ;-) So, I'm not gonna participate in that event. But I'd read your articles on that subject anytime. :-)
@bender Oh, there’s an easy explanation. But maybe some mysteries are best left unexplained. 😃 If you want to solve this riddle: The solution is in the phlog! Somewhere! 😅
Mas qual destas características faz realmente s diferença?
É o facto de ser um projecto público? É por ser um projecto de investigação? É por ser de código aberto? É uma conjugação de dois ou mais desses factores? Quais? Porquê? Já estabelecemos atrás que *iniciar* os trabalhos não é proibído (só má prática). Em que é que estes outros factos fazem a diferença? E, já agora, quais são as implicações dessa diferença? A Amália assim treinada pode ser usada por projectos que não sejam públicos? E se forem projectos que não sejam de investigação? Quais são as licenças de código aberto qie a Amália vai ter, e que obrigações de licenciamento terão os seus clientes ou derivados?
As perguntas não foram feitas, e, está claro, também ficaram sem ser reapondidas. Também não há resposta para as tentativas de contacto de vários dos detentores de direitos de autor de conteúdos utilizados para o treino - lá está, talvez porque a análise que poderá dar essas respostas ainda não sstá - no mês de lançamento! - concluída.
Ainda assim, temos garantias: a “versão base” do Amália será disponibilizada publicamente já no final de setembro. “A partir desse momento qualquer entidade poderá utilizar o modelo”. Como é que conseguem dar essa garantia sem ter a análise legal feita é que fica por compreender.
Este pôs-me ligo a resmungar com o título - e não melhorou.
O título é: “Equipa de peritos” está a analisar “possíveis impactos legais” do Amália, incluindo nos direitos de autor
Pôs-me a resmungar porque o projecto até já era para ter sido lançado, agora tem data de lançamentk para setembro (sim, este mês) e afinal... ainda nem fizeram aquele que devia ser o primeiro passo? Então e se agora afinal os dados não podem ser usados? Ou uma parte deles - vão tirá-los da base de dados iniciais e retreinar os modelos?
A questão é tão óbvia que até os jornalistas se lembraram de a fazer. E aí é que comecei mesmo a resmungar. O responsável pelo projecto podia ter dito "a legislação não impossibilita o início dos trabalhos." Porque claro que não impossibilita. Mas o problema é que iniciar os trabalhos com todos os dados sem saber quais é que vão ser excluídos pode até ser contraproducente. E se afinal nenhum pode? Lá se foram os 5.5M€ que a brincadeira custou?
Mas a resposta foi pior, foi "Sendo um projeto público, desenvolvido em ambiente de investigação e seguindo um modelo de código aberto, a legislação não impossibilita o início dos trabalhos."
½ Captura de ecrã vinda do artigo, que cita João Magalhães, Coordenador do desenvolvimento do projecto Amália, a dizer "Sendo um projecto público, desenvolvido em ambiente de investigação e seguindo um modelo de código aberto, a legislação não impossibilita o início dos trabalhos."
@prologic haven't had too much time to really try it out yet ^^' i'm um too busy staring at code i wrote while sleep deprived and wondering why i did the things i did, while sleep deprived \@.@
Welp, my rent's gone out and my student loan won't be in for another week, so I'm not spending anything for a while. How's everyone else's September going?
Chances are the database bought wasn't cheap at all and was aold by some scam company that probably ripped them from six figures or more for a database that's full of rubbish. 🤣
That is obviously completely wrong. But I can explain it. Some *years* ago, I screwed up my nginx rewrite rules, and that’s how these broken URLs came to be.
It all redirects to /git now, which is why that endpoint sees so much traffic lately.
But what does that mean? Why do they start there? I can only speculate that this company bought an old database of web links and they use that to start crawling. And it was probably a cheap one, because these redirects have been fixed for quite a long time now.
@prologic I’m doing that now as well, but I don’t think this is a good solution. This is going to hurt “self-hosting” in the long run: I cannot afford true self-hosting where I actually do host everything here at home – instead, I must use a cloud provider / VPS for that. It is only a matter of time until *my* provider starts doing AI shit as well (or rather, the customers do it) and then what? I get blocked, e.g. I can’t send email to (some) people anymore. This is already bad and it’s going to get worse.
@movq I heard about a defence against badly-behaved crawlers a while ago: an HTML zip bomb. This post explains how to do it. Essentially, web servers can serve compressed versions of webpages and, with a little trickery, one can replace the compressed page with a different file. After that, any bot that tries to crawl the page will instead download and unpack a zip bomb that will cause it to crash.
@prologic Yeah, I’ve blocked some large subnets now (most likely overblocking a lot of stuff) and it has died down.
I’m not looking forward to doing this on a regular basis. This is supposed to be a fun hobby – and it was, for many years. Maybe that time is just over.
“But all your stuff is MIT licensed! They are allowed to do that!”
Haha. As if they would care. They crawl everything they get their hands on.
Besides, that’s not true, the license states that the copyright notice must be retained. “AI” breaks that. They incorporate my code and my articles in their product and make it appear as if it was their work.
1. The load will become a problem at some point. 2. These crawlers and the current “AI” in general are breaking the rules. *I* am supposed to be paying for every little thing, *I* get sued for “piracy”. But apparently, these rules only apply to me. If I had more money, I could break them. Fuck that. 3. I simply don’t want it. Period.
Redbubble shopping catalog image of a smiling woman wearing a blue T-Shirt with an image of a "purple slab" with holes in a stencil font forming the words: "numpy, shapely, trimesh, & py5."
Captura de ecrã vinda do artigo, que cita João Magalhães, Coordenador do desenvolvimento do projecto Amália, a dizer "Sendo um projecto público, desenvolvido em ambiente de investigação e seguindo um modelo de código aberto, a legislação não impossibilita o início dos trabalhos."
orange marigolds