close
  • chevron_right

    Bits from the Release Team: Debian 10 'buster' is now in the soft freeze

    debacle – Wednesday, 13 February - 00:30 edit

Bits from the Release Team: Debian 10 'buster' is now in the soft freeze

Niels Thykier of the Debian release team writes:

We're pleased to announce that the freeze for Debian 10 'buster' has now migrated to the soft freeze stage.

[...]

The next stage of the release is on target. It is:

2019-03-12 Full freeze

[...]

Please take this opportunity to check packages are in their final shape and stay vigilant for release-critical bugs.

#debian #debian10 #buster #freesoftware #release #freeze

  • chevron_right

    Ignite Realtime Blog: Dele's FOSDEM presentation on Pàdé!

    debacle – Tuesday, 5 February - 16:03 edit

This was a very nice talk!


  • chevron-right

    Ignite Realtime Blog: Dele's FOSDEM presentation on Pàdé!

    @guus wrote: Last weekend, a number of Ignite Realtime community members attended FOSDEM (in Brussels, Belgium) the yearly free event for software developers to meet, share ideas and collaborate. @Dele_Olajide prepared a presentation for the Real Time Communications devroom, in which he elaborated on Pade, and focused on how the plugin architecture of the Chromium web browser, ConverseJs and Openfire made it possible to quickly integrate HTTP and SIP with XMPP and create a feature-rich and very extensible unified communications solution for small and medium businesses. For your convenience, a recording of his rather entertaining presentation: http://bofh.nikhef.nl/events/FOSDEM/2019/H.1309/pade.webm Posts: 1 Participants: 1 Read full topic

    group_work PlanetJabber 5 February

  • favorite

    1 Like

    ericbuijs

  • chevron_right

    If you ever think about using Electron

    debacle – Monday, 28 January - 00:25 edit

If you ever think about using Electron for your next application, think twice. Or thrice. It's probably a bad idea:

Github user miksuhwrites:

It is an really bad idea to use Electron. Electron is completely 100% inaccessible and unusable with the Orca screen reader on Linux. None of the Electron applications work with the Orca screen reader. All of the Electron applications are completely unusable if you are visually impaired or blind like I am. Orca screen reader speaks absoletely nothing when you try to use Electron based applications. Electron is based on Chromium technology. Chromium web browser is also completely inaccessible and unusable with the Orca screen reader. During the last 10 years people have requested several times that Chromium developers should start to support the Orca screen reader. But nothing has happenened. People have requested the same from Electron developers but nothing has happened. Chromium and Electron are still completely inaccessible and unusable. Blind users like me must use computer using screen reader which speaks the content on scree. blind and other visually impaired people can not use any Electron applications because Electron does not work with the Orca screen reader. It also looks like situation will not change, looks like Chromium and Electron developers have no plans to supoort the Orca screen reader. There is now applications like Skype which is made using Electron. Because of that Skype on Linuxx is completely inaccessible and unusable if you are visually impaired. So visually impaired users can not use e.g Skype or e.g Signal on Linux. that is simply discriminitaing visually impaired users. So no, use of Electron is not ok.

#orca #accessability #a17y #blind #visuallyimpaired #electron #signal #chromium #screenreader #jaws

  • chevron_right

    Sony macht Aibo zum Überwachhund

    debacle – Wednesday, 23 January - 20:09 edit

Sony macht Aibo zum Überwachhund

"Sony kann prüfen, wie es entfernt lebenden Familienmitgliedern geht oder was Kinder so machen, wenn sie nach Hause kommen", sagte Projektleiter Izumi Kawanishi vor Journalisten. "Wir wollen, dass Sie sich durch das Leben mit Aibo ein bisschen kontrollierter fühlen und zugleich Angst haben." Sony spricht in diesem Zusammenhang von "Surveilltainment".

#sony #surveillance #surveilltainment #aibo #überwachhund #derspiegel

  • chevron_right

    debacle – Wednesday, 23 January - 19:51

    ProcessOne: Moving away from Facebook


  • share chevron-right

    ProcessOne: Moving away from Facebook

    ProcessOne is a company deeply invested in building the Open Internet. We build ejabberd, a leading Open Source product, implementing the XMPP protocol, an IETF standard. It is used around the world to power tens of thousands of instances, used for community servers, small companies or huge internet services. We also support MQTT and SIP standards, all of which are used to power interoperable services. If you read “Become A Facebook-Free Business“, by DHH from Signal v. Noise, it becomes painfully apparent that even having a minimal presence on Facebook is not helping the Open Internet. That’s why we decided to join this Basecamp’s initiative and remove our fanpages from Facebook, as well as the Facebook links we had on our websites. We hope this statement will help promote a more open and decentralized web. We invite you to join us in having a Facebook-free online presence. If you used to follow us through Facebook, I now suggest you subscribe to our RSS feed on our blog. We are still using other services that we are not totally happy with the way they handle our data. This is something we will keep on actively working on to ensure that ProcessOne web presence is helping grow the decentralized web in a sustainable way. Stay tuned!

    group_work PlanetJabber 23 January

  • chevron_right

    Adrien Plazas: My Name is Handy, Lib Handy

    debacle – Sunday, 20 January - 11:16

Btw. libhandy is also used by chatty, the Librem 5 SMS & XMPP application.


  • share chevron-right

    Adrien Plazas: My Name is Handy, Lib Handy

    Libhandy 0.0.7 just got released! I didn't blog about this mobile and adaptive oriented GTK widget library since the release of its 0.0.4 version three months ago, so let's catch up on what has been added since. List Rows A common pattern in GNOME applications is lists, which are typically implemented via GtkListBox. More specific patterns arose, where rows have a title at the start, an optional subtitle below it, actions at the end and an icon or some other widget like a radio button as a prefix. These rows can also be expanded to reveal nested rows or anything else that fits the need. So far every application using these patterns implemented the rows by hand for each and every row. It made using these a bit cumbersome and it led to inconsistencies in sizing, even inside a single application. To make these patterns easier to use, we implemented HdyActionRow, HdyComboRow and HdyExpanderRow. HdyActionRow The action row is a simple and flexible row, it lets you give it a title, a subtitle, an icon name, action widgets at its end, prefix widgets at its start and other widgets below it. It takes care of the base layout of the row while giving you control over what to do with it. HdyComboRow The combo row lets the user pick a single value from a list model, it is quite convenient to use as you can even set it for an enumeration GType. HdyExpanderRow The expander row allows you to reveal a widget below the row, like a nested list of options. It lets you optionnaly have a switch triggering whether it is possible to expand the row to access the nested widget or not. Adaptive Dialog HdyDialog is a dialog which behaves like a regular GtkDialog on normal conditions, but which automatically adapt its size to the one of its parent window and replace its window decorations by a back button if that parent window is small, e.g. if it is used on a phone. This will mean that HdyDialog will act like a regular dialog on form factors like a desktop, a laptop or a tablet, but it will act like another view of the main window if it is used on a phone or on a really narrow window. HdyDialog has been written by Zander Brown, thanks a lot! Adaptive Search Bar HdySearchBar is a reimplementation of GtkSearchBar that allows the search entry to be expanded to take all the available space up. This allows for an expanded HdyColumn between the search entry and the search bar, allowing to automatically adapt the width allocated to the search entry to the one allocated to the bar. GtkSearchBar from GTK 4 already handles that correctly so HdySearchBar will not be ported to GTK 4. Internationalization Libhandy now supports internationalization, there are no end-user-facing strings but developer-facing strings like property descriptions can now be localized. Initialization The `hdy_init()` function has been added, it will initialize the internationalization, the types, and the resources, ensuring Libhandy will work in any context. Annotation of Symbols Introduction We started annotating when symbols were added to the API, which will better explain to you via the documentation what is available with your current Libhandy version and which version of Libhandy you should require to use a specific feature. glade_catalog and introspection Options The glade_catalog and introspection options have been turned from booleans into features, that means that we broke the build system's interface as true and false are not valid values anymore and should be replaced by enabled, disabled or auto. Their default value is auto which means that if you don't care about the availability of these features, you don't have to care about these options anymore. Making Libhandy Static The static boolean option have been added to allow Libhandy to be built as a static library. Note that the introspection and the Glade catalog can't be built when building Libhandy as a static library. Bundle Libhandy in a Flatpak Manifest To bundle the master version of Libhandy in your Flatpak manifest, simply add the following module: { "name" : "libhandy", "buildsystem" : "meson", "builddir" : true, "config-opts": [ "-Dexamples=false", "-Dtests=false" ], "sources" : [ { "type" : "git", "url" : "https://source.puri.sm/Librem5/libhandy.git" } ]} Bundle Libhandy as a Meson Subproject To use Libhandy 0.0.7 as a Meson subproject, first add Libhandy as a git submodule: git submodule add https://source.puri.sm/Librem5/libhandy.git subprojects/libhandycd subprojects/libhandygit checkout v0.0.7 # Or any version of your choice.cd ../..git add subprojects/libhandy Then add this to your Meson build system (adapt the package sub-directory name to your needs): libhandy_dep = dependency('libhandy-0.0', version: '>= 0.0.7', required: false)if not libhandy_dep.found() libhandy = subproject( 'libhandy', install: false, default_options: [ 'examples=false', 'package_subdir=my-project-name', 'tests=false', ] ) libhandy_dep = libhandy.get_variable('libhandy_dep')endif If you don't require introspection and you don't care about localization, you can alternatively build it as a static library: libhandy_dep = dependency('libhandy-0.0', version: '>= 0.0.7', required: false)if not libhandy_dep.found() libhandy = subproject( 'libhandy', install: false, default_options: [ 'examples=false', 'static=true', 'tests=false', ] ) libhandy_dep = libhandy.get_variable('libhandy_dep')endif Librem 5 DevKits As a sidenote: the Librem 5 devkits shipped at the very end of 2018, here are photos of mine! I'm eager to play with Libhandy on it.

    group_work PlanetGnome 19 January