Salta al contenuto principale



I've got a lighting-fast #GNOME dashboard disabling most of the search providers. I'm not using them anyway.. I keep only File and Calculator 👍







#ratemyrig #diy #diywhy

with a spare piece of wood, some wire, two clothespins...




#iorestoacasa



from instagram.com/ortolanileo/


Leo: "and now some tips to live this day with lightheartedness!"
"you can read a good book"
"or study a foreign language"
"or exercise"
"or tidying wardrobes"
"or"

Tv: "tearing down this wall will cost you $ 3000, but you'll have the well-lit kitchen you wanted!"


Unknown parent

Fabio
"rate my setup"



Look ma! New site!

yes, ma. I copied it from Foliate.. sorry..

Thib reshared this.





What's new in #confy today:

- nice button in headbar to update main menu list or event cached data
- nice overlay toaster to show notifications

- main menu data is updated automatically at start if older than one day
- event cache is updated automatically at open (if network is available).
- event data is downloaded asynchronously. This leave the UI responsive while downloading.
- talk detail page show "conflicting" starred talks

- Remind upcoming starred events with a system notification

What's wrong in #confy today:

- flatpak doesn't work anymore (see #1. I think it's related to sandbox permissions, but I can't understand how fix it. So, flatpak building in builds.sr.ht is disabled.
- The "+" button ("Add event from URL") is just a placeholder. More work must be done to support it correctly
- apart from event data, other downloads are still sync and block the ui
- I still have issues with Leaflet and folding.... I'm missing something here...

please, send help...

What's missing, in "likely it will land" order:

- Download all data asynchronously.
- An app menu is needed, with things like "options" and "back to event list" ...
- An options window, with things like "update event cache every" and "clear all cached data"
- The "Map" page is still a placeholder
- Support for FOSDEM's room status API

Thib reshared this.



#WIP #confy #flatpak built on sourcehut build service, with a nice artifact. :)

builds.sr.ht/~fabrixxm/job/165…

still a test. Next step, trigger build of master branch when pushed.







Hardware Acceleration is approximately 9.8 m/s² and is achieved by tossing your computer out the fucking window




but it's easy to organize at #fostdem

1. Find the bar
2. Drink beers watching the live streams

😎

(cc @fabrixxm @fosdem)




So, yesterday evening @Gruppo Linux Como hosted the first "virtual meetup" using #JitsiMeet .
We had a very nice experience (keeping the video stream at minimum), and friends abroad were able to join us!
I only missed the pizza together 😄
in reply to Fabio

But Jami was very unreliable for me


yes. also for me.

I was told Jitsi was bought by a company and other messengers should be preferred.


Never heard of.

Anyway, Jitsi Meet it's fully opensource and self-hostable. Don't see any problem..

in reply to Fabio

Found:
jitsi.org/news/we-have-a-new-h…

8×8 announced it has acquired the Jitsi team and our technology from Atlassian

"from Atlassian" looks like an improvement, to me.
Again, all the source code is available :)

in reply to Fabio

Sounds good. I guess there are not many other alternatives.




They simply declared what they wanted to happen, entering into a negotiation with the borrow checker, and then revised their design until both parties were left satisfied.


- fasterthanli.me/blog/2019/decl…





Sometimes I comment on a git* issue and forget about it, until I get a notification email and it's a 'what are you?' moment...




Benno Rice

systemd is, to put it mildly, controversial. As a FreeBSD developer I decided I wanted to know why.

I delved into the history of bootstrap systems, and even the history of UNIX and other contemporary operating systems, to try and work out why something like systemd was seem as necessary, if not desirable. I also tried to work out why so many people found it so upsetting, annoying, or otherwise rage-inducing.

Join me on a journey through the bootstrap process, the history of init, the reasons why change can be scary, and the discovery of a part of your OS you may not even know existed.

Questa voce è stata modificata (4 anni fa)





Hola Fedivers!

Quin goig anunciar que la #FediConf2020 se celebrarà a La Lleialtat Santsenca del 25 al 27 de setembre.

¡Hola Fediverso!

Qué alegría anunciar que la #FediConf2020 se celebrará en la Lleialtat Santsenca del 25 al 27 de septiembre.

Hi Fediverse!

What a joy to announce that the #FediConf2020 will take place at la Lleialtat Santsenca from 25th to 27th Septembre.

talk.feneas.org/t/work-in-prog…

#FediConf #Fediverse #Fediverso #DecentralizeAll




For sailors coming to #FOSDEM : FOSDEM QML app, porting to #SailfishOS of Ubuntu Touch app, is avaible on #Jolla's Store



Thunderbird calendar addon Year View is now in "(very) low maintenance mode".

It will not be updated to support TB68 or TB70.
As the readme says, I don't have time, resources and motivation to keep work on this.

I'm not really using this plugin anymore from a while now.
I'm using TB only on my office Mac, where I'm still on TB60 because 90% of the addons I need still doesn't work in a way or another on TB68.

Writing "Year View" was a quite painful experience: overall documentation was too old ad outdated or non existent. And that's only on Thunderbird/XUL side: I had to read and understand Lightning code because I couldn't find any other docs. Most of the code in "Year View" is an edited copy of Lightning code. There are also a number of ugly hacks.

From what I read in Thunderbird docs, if I manage to make this thing run on TB68 I will need to rewrite it anyway to make it run on TB70 (where my needed addons will not run anyway). I'm very sorry, but It's not worth the pain.

If you want a proper year view in calendar in the future, please bugs Lightning devs.



Still today, when I want to impress someone showing what free software can do, I spin up Ardour 👍

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.