Hoje abriram as inscrições para os tutoriais, grátis, vagas limitadas!
(Aproveite e avise aquele seu amigo gringo que ele pode comprar um ingresso de estudante doação para alguém que não poderia participar do evento completo com as palestras! :D)
https://pybr2025.eventbrite.com.br/
#Python
#<https://example.com/twtxt.txt#2025-09-22T06:45Z> with the timestamp in an anchor link. the need for a mention is avoided like this as well since it's already linking to the replied-to feed!🐀💭 i should just implement it into bbycll and force it into existence
https://www.youtube.com/watch?v=yXTDslxVfdM&list=PLLIPpKeh9v3ZFEHvNd5xqUrCkqLgXnekL
«Graciliano Ramos: Quem adulterou as memórias do escritor?
“Memórias do Cárcere” tinha diferença entre manuscritos do autor e edições publicadas em livro»
https://archive.ph/UuIQw
#GracilianoRamos #LiteraturaBrasileira
#Portugal #Palestine #recognition
Screenshot of https://en.m.wikipedia.org/w/index.php?title=International_recognition_of_Palestine&diff=prev&oldid=1312606019&diffonly=1 where we can see a change to an wikipedia page, adding Portugal to the list of countries that recognize Palestine
https://www.youtube.com/live/XoQipHFMZVU
No wonder I think I've heard this is one of the things that distinguishes professional software development from [my preferred domain of] things such as "end-user programming" etc.
The problem is that when you start sharing code in the context of a FLOSS project you almost immediately get enmeshed in concerns about packaging and how other people will install stuff, when sometimes you just don't want to be a professional software developer! 😿
I'm always borrowing terms (learning ideas) from @lr like: *incidental complexity*. I hate *incidental complexity* or maybe I just fear *incidental complexity*. Can we escape *incidental complexity*? I guess not.
After seeing so many resolutions, I think you're only missing a *matrioska* version of it. 🪆
The order of
SOURCE > POST does make more sense indeed.
BTW, the feed on https://feeds.twtxt.net/ seem down? It says it's in maintenance.
https://arstechnica.com/science/2025/09/meet-the-2025-ig-nobel-prize-winners/
...também conta que os nenês curtem o leita materno quando a mãe comeu alho.
https://arstechnica.com/science/2025/09/meet-the-2025-ig-nobel-prize-winners/
...também conta que os nenês curtem o leite materno quando a mãe comeu alho.
https://arstechnica.com/science/2025/09/meet-the-2025-ig-nobel-prize-winners/
Mate in 5 I think... :)
#chess #ChessPuzzle #lichess
If you want to learn more about it, why not see this video with its founder?
@dff@dff https://videos.trom.tf/w/gVBnrHUypajuZkVKrafwz4
Like this: https://www.linkedin.com/posts/paulwaynewalter_urban-gis-people-great-free-self-paced-activity-7373022072685506560-z0S5
«Oh, also, here is a link to Transitland's map of open #GTFS data: https://www.transit.land/map#3.5/40.41/-104.84»
Like this: https://www.linkedin.com/posts/paulwaynewalter_urban-gis-people-great-free-self-paced-activity-7373022072685506560-z0S5
Geo-Python and Automating GIS Processes (‘#AutoGIS’) have been developed by the Department of Geosciences and Geography at the University of Helsinki, Finland. The course has been planned and organized by the #DigitalGeographyLab. The teaching materials are openly accessible for anyone interested in learning.»
https://autogis-site.readthedocs.io/en/latest/
(via Paul Walter no linkedin)
#GIS #geoPython #geopandas #shapely #osmnx #networkx
Geo-Python and Automating GIS Processes (‘#AutoGIS’) have been developed by the Department of Geosciences and Geography at the University of Helsinki, Finland. The course has been planned and organized by the #DigitalGeographyLab. The teaching materials are openly accessible for anyone interested in learning.»
https://autogis-site.readthedocs.io/en/latest/
#GIS #geoPython #geopandas #shapely #osmnx #networkx
https://www12.senado.leg.br/ecidadania/visualizacaomateria?id=160575
Precisa logar com gov.br e tal, mas acho que vale a pena votar para mandar uma mensagem, a diferença andou diminuindo :-S
I called it a day, yes. \o/
Enjoy your weekend! (I hope, you just called it a day and don't have to drive to the office or silly shenanigans like that.)
Now guess what manufacturers are pushing for ...
Now guess who couldn't complete a task at work this Saturday morning, because a certain cloud service was down ...
IT is fucked. Throw it all away and start over.
https://cbers4asat.readthedocs.io/pt-br/latest/
cc @elmoneto@elmoneto (você viu isso? eu não manjo nada mas já fiquei animado...)
I thought it was a general thing for browsers, but it that was actually allowed in a newer specification, yet it's still not implemented in Chrome, it does work in Firefox though.
https://movq.de/v/9df0437d27/MVI_8891.MOV.mp4
Now everything looks like it has that silly slogan as a background image:
https://movq.de/v/9df0437d27/smol.jpg
tt, I recognize umlauts in nicks, but they cannot include whitespace, @, !, #, (, ), [, ], <, >, " (but ' is okay). Whitespace also acts as a separator between nick and URL. @<Hello World http://example.com> ends up exactly like that and is not a mention.
https://umapenca.com/villares (BR)
#Python #CreativeCoding #Processing #py5 #TShirt #GenerativeArt #SupportArtists
white T-shirt with abstract geometric pattern made of recursively placed unfilled black stroke hexagons and lines
Seems that more feeds work correctly this way. 🤔
You can even "wrap" it into a packaged installation and publish it on stores, theres even projects to streamline it https://www.pwabuilder.com/.
A thread is a single post of a single feed as a root, but the hash has the drawback of not referencing the source, in a distributed network like twtxt it might leave some people out of the whole conversation.
I suggest a simpler format, something like:
(#<TIMESTAMP URL>)This solves three issues:
- Easier referencing: no need to generate a hash, just copy the timestamp and url, it's also simpler to implement in a client without the rish of collisions when putting things together
- Fetchable source: you can find the source within the reference and construct the thread from there
- Allow editing: If a post is modified the hash becomes invalid since it depends on
[ timestamp, url, content ]
Currently my regex is like this:
/@<((?<nick>[^\s]+)\s)?(?<url>\w+:\/\/[^>]+)>/gIt takes everything until the space and the nick is optional.
After a long while away, I'm back on twtxt with this new feed.
Some of you might remember me as
justamoment@twtxt.net, that was a test account I made for trying things out, but I ended up keeping it more than planned.I also tried other social platforms in search of a place that felt right for me.
In the end twtxt was the one that ticked all of my boxes:
- Slow social: it act more like a feed reader and I really appreciate that there's no flood of content that I can't keep up with.
- No server needed: I absolutely love to have total control over my content, I tend to avoid having moving parts that might break, plus you can put your feed under version control and it's all backed up.
- Ownership: I can put my feed anywhere I want and nobody can decide if I can access it or not.
- For hackers: a single .txt file allows me to join a community, how cool is that!
This is why I decided to build my own twtxt client, one that allows you to decide how the feed is presented on your "instance".
It's still in the making but I'll try to share a bit of it once I defined how things should work.
Coincidentally, I discovered that @itsericwoodward and @zvava were also building a twtxt client, seems like twtxt is set to grow!
I've been working on a couple of twtxt-related projects, and one of them is a reader (tentatively called
twtstrm) written in JS. I used dummy data for the first few stages of development, but now I'm at the point where I need some _real_ data, and that meant hitting up my actual following list.Of course, it didn't help that I had a typo in my
If-Modified-Since headers, but all that has since been resolved.Anyways, if I accidentally spammed you with requests today, I am sorry, and it shouldn't happen anymore.
We thank you for your patience, and apologize for the inconvenience.