@coreysnipes at @lhc, our local hackerspace in Brazil, people are very interested in this topic and trying to create nodes all over the city, but I agree with you that I didn't see anyone with a better use case than sending "hello" messages to each other.
Side effect of being reading a SQL book: instead of using Django ORM to perform some queries and data cleanup in the DB of a project, I am running a bunch of SQL commands and I am considering them so much easier to understand (even with some weird aggregates)! #sql
@juliobiason@anna@anna I am using https://migadu.com/ with my own domain paying a small amount yearly. Self-hosting email is something that I will never try to do myself ...
@Roneyb@skarnio@cadusilva@fediadminbr não vi nenhum comentário do Cory Doctorow no site dele, nem nas contas do Fediverso. E dado o histórico dele, é muito, muito estranho ele colocar o nome dele em algo desse tipo ...
Estava procurando alguma ferramenta para me ajudar a organizar meus livros digitais (apesar de eu não ter o hábito de ler livros assim) e descobri o Kavita. Parece ser bem interessante e ainda permite que outras pessoas tenham acesso (com autenticação) aos meus livros ...
@bmispelon I did some research and you are right. Custom aggregates are the cleanest solution for this problem and it can be as simple as:
```class Median(Aggregate): template = 'PERCENTILE_CONT(.5) WITHIN GROUP (ORDER BY %(field)s)'```
Unfortunately, it should't be possible to have built-in, as median isn't an ANSI SQL function, so a different implementation is needed for each DB (the one I tested in PostgreSQL).
The hack also is worried about annotations. Need to test a bit more.
Do you know when I will really believe that AI will take our jobs and we will have a revolution in tech world? In the moment when an AI will be capable of configuring and sending one single page PDF to a printer, any printer and we get that page printed in a paper sheet! Just a f***** printer! I dare you AI! You will never be able to accomplish that!
@oni you can clearly know who you are paying for a Peertube instance as well (if you chose it with care). The only difference is that the money for Vimeo is going to a NASDAQ traded company that needs to answer to stakeholders (not you) or to a community/person hosting an open source project, federated, that is more likely to listen to your needs.
It is more a philosophical choice than technical anyway ...
@oni moving to another PeerTube instance that is open for new users isn't a viable choice? Using (and paying) Vimeo doesn't look better than using YouTube ...