177 karma · joined June 27, 2015
Anyway, there is a discovery mechanism, and clients do adapt the version used by peers, so there is no incompatibility. Kaidan choose for a while to have only OMEMO:2, because resources are limited and they were going for the latest version first, but resource are limited for everybody, and it took times for others to implement OMEMO:2 too.
NLnet/NGI did (and still does) gave financial support on several XMPP projects (including mine, huge thanks to them), and, curiously, when there is money to help, implementations happen. That's problem nb 1 with XMPP: lack of financial resource.
() GUI (notably web UI) is being reworked, not stable yet, but the CLI is pretty solid.
I've proposed a specification for SFU hosting (check https://bloggeek.me/webrtcglossary/sfu/ if you don't know what's a SFU), and wrote a component based on the excellent Galène SFU, as well as client implementation (in Libervia) as part of a NLNet/NGI grant (https://nlnet.nl/project/Libervia-AV/).
XMPP council (disclaimer: I'm a council member for the current term) asked me to some modifications and to re-propose, which I'm about to do. I couldn't find the time so far (cause I'm working on ton on stuffs), but will go back to it very soon.
To sum-up: this is very much worked on.
Also note that Libervia is using a backend/frontends architecture with a D-Bus API, you can use it to make your own frontend with any language you like.
For UI there is https://github.com/kivymd/KivyMD for Material design on top of Kivy.
And the team is nice (I've met some of them at PyCon or FOSDEM).
The framework is pleasant to use, and there is a descriptive language, kv, which is really great.
Cross compiling may be painful though (I did it for Android) and the app loading time is a bit long, but it's working.
Some things may be missing in comparison to big frameworks such as Qt, there is no WebView for instance, and accessibility is unfortunately not as good.
It's overall a very good project and it's a pity that it's not more known and used.
I'm using XMPP for chatting of course, but also for blogging (my blog is XMPP based), A/V calls, events organization, file sharing, photo albums sharing, as a remote (with ad-hoc command, I've even built an specific UI to control MPRIS supporting player). I'm building an agenda, a forum, a generic list tool (TODO, shopping list), and other stuff.
I'm using Snikket to host a small server for family and friends, with accompanying mobile clients.
I've also built an XMPP <=> ActivityPub gateway (soon to be released, but dev version is already available), so my blog is accessible from any AP supporting client, and I can access the AP ecosystem (including events as seen in Mobilizon).
There is Slidge IM if you wanna talk to legacy network such as Signal, Whatsapp, Telegram, Discord, Mattermost, Steam, Skype, Facebook Messenger, Matrix, VoIP.ms.
There is Biboumi if you wanna talk to IRC.
There are old and new email gateways on the work (I'll be working on one myself).
XMPP is used in many fields (from healthcare to games), you can have an idea at https://xmpp.org/uses/instant-messaging/ but I have the feeling that this list is not up-to-date and is incomplete. I think that it's used in Fornite for instance.
So yeah, we may not be the best for marketing, and we not have as much resources as we should, but XMPP is still well alive and kicking!
edit: Fornite is actually mentioned at https://xmpp.org/uses/gaming/ .
Note: I'm very involved in XMPP, and the author of the latter XEP.
Edit: forgot to mention that it's also available to ActivityPub thanks to the XMPP <=> AP gateway (that I've authored too)
But no data on license, weight, or whatever, it looks like the repos are in the process of being uploaded.If what we can see on the demo is not faked, it's quite impressive.
How is it for app development? I've seen that they have started to showreels for apps (https://godotengine.org/article/announcing-godot-2022-showre...) and it's quite impressive. I'm wondering if it can be a good alternative to stuff like Qt/Qt Quick for rapid prototyping, or even production app.
The easy export to multiple platforms is a really an interesting point. I'm mostly wondering if it can handle correctly stuff like accessibility, desktop integration, and if it's good at handling texts (Unicode, RTL, etc).
For diagrams, I'm using draw.io (it seems that it's called diagrams.net nowadays), it's FOSS, easy to use and feature-full. It's then easy to add it in the presentation by using the markdown syntax for images.
> probably but GIMP plugins are not something I've looked into
I was just thinking about a black and white or grey level output image with the desired area , no need to integrate it in GIMP of whatever. I've tried a prompt like "keep only the face", but no luck so far.
A few questions:
- would it be possible to use this tool to make automatic mask for editing in something like GIMP (for instance, if I want to automatically mask the hair)?
- would it be possible to have a REPL or something else to make several prompt on the same image? Loading the model takes time, and it would be great to be able to just do it once.
- how about a small GUI or webui to have the preview immediately? Maybe it's not the goal of this project and using `instruct-pix2pix` directly with its webui is more appropriate?
Thanks for the work (including upstream people for the research paper and pix2pix), and for sharing.
I'm wondering also how Rich compares to something like Python Prompt Toolkit.
- I like terminals because there is nearly nothing disturbing you, and it's usually quick to have something
- there are many little features that looks like nothing but are really really useful when you use them. I'm a big fan of C-a / C-x to increment / decrement a number, coupled with https://github.com/nishigori/increment-activator it's super useful (to change a boolean, a date, a number, etc). The "." to repeat last command, the "*" to search what is under the cursor are other great features. An occasional macro made with "q" may save a lot of time when you need to do a repetitive task, for refactoring for instance, and you can even repeat them according to some patterns with ":g". I'm not sure if those features have handy equivalents on other IDEs.
- I didn't spent that much time doing my config, just adding little changes here and there when necessary, over the years I've got a environment really adapted to my taste.
- I'm currently doing mostly Python, and vanilla (neo)vim is normally good enough, but I'm using Coc (https://github.com/neoclide/coc.nvim) for a little while, and it add a lot of helping stuff easily. Pyright + snippets are useful.
- when something cool happens somewhere else, you often have somebody adapting it to vim. I can use snippets and emmet which are occasionally very useful.
At the end, I don't feel the need to change, it works well, and over the time I could add some neat features to improve it (snippets, emmet, CoC, tagbar, etc). I'm not sure if changing to something like VScodium would worth the time to learn something new (and I like working with terminals).
for 2), it's actually written in the description: "phrase-level timestamps", so it should be possible (phrase level is neat for skipping to a special location on a video, but maybe not for audio editing).
2 questions:
1) how does it compare to state of the art FOSS solutions? I'm seeking about DeepSpeech or Vosk
2) would it be somehow possible to associate timestamp to the words recognized? That would be amazing for things such as audio editing or skipping to a particular location on a video
I have a second-hand Nexus 7 (repartitioned flo), probably the same as you, and I'm super happy with it thanks to Lineage OS. LineasOS 19 doesn't seem to be available for it though (yet?).
> Hard to figure a new tablet to buy that will get that same 10 year life, some custom rom development just vanishes over time. Popularity doesn't seem to be a guarantee.
If I would be buying a new tablet today, beside second hand (better for Earth, more guaranties to have a FOSS ROM running on it, and cheaper), I guess that I would go for open hardware like what Pine64 is doing: the community is dynamic, and I would not be surprised to see the device still updated in 10 years.
For phones, I guess that Fairphone is a very good option too: FOSS friendly, easily fixable, and minding about resources.
I'm currently using my own implementation for style/colors and tables in my main CLI tool, including highlighting with Pygments, and I'm wondering if it would make sense to move to Rich (it would a least bring Windows and Mac support).
Regarding progress bars, Python Prompt Toolkit already implements them, thus I have the feeling that Rich is quite redundant. Any feedback from experienced user?
Maybe have a look at the Fairphone, the last iteration seems neat, and it's compatible with several FOSS OSes (at least Android based ones, but I think other too).
Best is to use a second hand/refurbished phone: better for the planet, the price, and you can choose carefully a model compatible with the FOSS OS you would like to have.
PinePhone (Pro) is not (yet?) good as a daily driver, but it's a great platform if you want to develop for various OSes (booting on a new OS is as easy as switching SD card). With the new keyboard accessory, it's a great super small and portable computer, and the community is very active.
For async code, the issue with normal profiler is that we end up mostly in the event loop. In Python there is https://github.com/sumerc/yappi which has a notion of coroutine profiling (check the README there), so I'm wondering if this would make sense in the context of Austin.
Anyway thanks for your work!
How does it play with async code?
Speaking of transports, OSMAnd has a beta transport mapping for a while which is working quite well by my experience (use in combination of Transportr which is also really good, depending on the city where I am, one may be better than the other).
The only important missing thing is indeed traffic information, but depending on where you're living, it may not be such a big deal.