JanKusanagi @i jankusanagi@identi.ca

Between Jabberia and the Pumpiverse!

Developer of the Dianara pump.io client. Mageia GNU/Linux + KDE Plasma user. I also use Debian GNU/Linux and Archlinux. Jabber/XMPP chatter, Pumper, C/C++/Qt coder. Pump.io User Guide: https://pumpio.readthedocs.org/en/latest/userguide.html Users by language: https://github.com/e14n/pump.io/wiki/Users-by-language Some tips: http://communicationfreedom.wordpress.com/2014/03/17/pump-io-tips/ And if your Pump.io server is identi.ca, check this out: https://identi.ca/jankusanagi/note/IpfiW7kBQYuXt6H7odMzQQ This is an alternate account to jankusanagi@datamost.com

  • Call For Testing: Backporting Dianara 1.3.6 From Ubuntu Zesty Zapus To Other Supported Versions

    Stephen Michael Kellat at 2017-01-16T02:59:55Z

    Slipped in as of January 12th was a new version of Dianara that I've been waiting on. It is in Zesty Zapus which will come out in April. Since Debian is entering a freeze period this will be the last version to roll down the pike into Ubuntu. I could start fiddling with snapcraft but I've got enough on my plate at the moment.


    Your help is needed in testing the proposed backport. You need to be running any of the Ubuntu flavors on 14.04, 16.04, or 16.10. Mint users are appreciated for their enthusiasm but won't be able to play along in this game as they're running a Frankenstein's Monster that isn't quite binary-compatible with Ubuntu anymore.


    First you need to run the following command to add the testing PPA: sudo add-apt-repository ppa:skellat/tests


    There will be disclaimers asking if you're out of your mind as this PPA has stuff in it that may make your machine go kaboom. Accept that and add the PPA. After that please go to your favorite package management tool and either upgrade only Dianara or install it for the first time. Once that is done, please open Dianara and use the program. Leave a comment on this post. Like somebody else's post. Otherwise use the package.


    If the program works, please leave a comment here saying which version of Ubuntu you were using. After that, please visit https://bugs.launchpad.net/trusty-backports/+bug/1656729, click on the "This bug affects you" link, and select "Yes, it affects me".


    When you are done testing, please quickly run sudo apt-add-repository --remove ppa:skellat/tests to remove the PPA from your package archives. Many things go into that testing PPA. You do not want to break your system.


    If we can wrap up testing in a week or two, that would be great.

    Alex Jordan, nukem, der.hans, Claes Wallin (韋嘉誠) and 1 others likes this.

    Alex Jordan, Alex Jordan, Alex Jordan, JanKusanagi @i and 7 others shared this.

    I'm running Dianara 1.3.4-1 from Ubuntu's universe repository. About to switch to the PPA version.

    James Dearing 🐲 at 2017-01-16T15:22:04Z

    The upgrade to 1.3.6 went flawlessly. I'm running Ubuntu 16.10.

    James Dearing 🐲 at 2017-01-16T15:26:07Z

  • Modern XMPP Server

    Elena ``of Valhalla'' at 2017-01-13T12:25:12Z

    I've published a new HOWTO on my website:

    Enrico already wrote about the Why (and the What, Who and When), so I'll just quote his conclusion and move on to the How.

    I now have an XMPP setup which has all the features of the recent fancy chat systems, and on top of that it runs, client and server, on Free Software, which can be audited, it is federated and I can self-host my own server in my own VPS if I want to, with packages supported in Debian.


    How



    I've decided to install prosody, mostly because it was recommended by the RTC QuickStart Guide; I've heard that similar results can be reached with ejabberd and other servers.

    I'm also targeting Debian stable (+ backports); as I write this is jessie; if there are significant differences I will update this article when I will upgrade my server to stretch. Right now, this means that I'm using prosody 0.9 (and that's probably also the version that will be available in stretch).

    Installation and prerequisites



    You will need to enable the backports repository and then install the packages prosody and prosody-modules.

    You also need to setup some TLS certificates (I used Let's Encrypt); and make them readable by the prosody user; you can see Chapter 12 of the RTC QuickStart Guide for more details.

    On your firewall, you'll need to open the following TCP ports:


    • 5222 (client2server)

    • 5269 (server2server)

    • 5280 (default http port for prosody)

    • 5281 (default https port for prosody)



    The latter two are needed to enable some services provided via http(s), including rich media transfers.

    With just a handful of users, I didn't bother to configure LDAP or anything else, but just created users manually via:

    prosodyctl adduser alice@example.org

    In-band registration is disabled by default (and I've left it that way, to prevent my server from being used to send spim).

    prosody configuration



    You can then start configuring prosody by editing /etc/prosody/prosody.cfg.lua and changing a few values from the distribution defaults.

    First of all, enforce the use of encryption and certificate checking both for client2server and server2server communications with:


    c2s_require_encryption = true
    s2s_secure_auth = true



    and then, sadly, add to the whitelist any server that you want to talk to and doesn't support the above:


    s2s_insecure_domains = { "gmail.com" }


    virtualhosts



    For each virtualhost you want to configure, create a file /etc/prosody/conf.avail/chat.example.org.cfg.lua with contents like the following:


    VirtualHost "chat.example.org"
    enabled = true
    ssl = {
    key = "/etc/ssl/private/example.org-key.pem";
    certificate = "/etc/ssl/public/example.org.pem";
    }


    For the domains where you also want to enable MUCs, add the follwing lines:


    Component "conference.chat.example.org" "muc"
    restrict_room_creation = "local"


    the "local" configures prosody so that only local users are allowed to create new rooms (but then everybody can join them, if the room administrator allows it): this may help reduce unwanted usages of your server by random people.

    You can also add the following line to enable rich media transfers via http uploads (XEP-0363):


    Component "upload.chat.trueelena.org" "http_upload"

    The defaults are pretty sane, but see https://modules.prosody.im/mod_http_upload.html for details on what knobs you can configure for this module

    Don't forget to enable the virtualhost by linking the file inside /etc/prosody/conf.d/.

    additional modules



    Most of the other interesting XEPs are enabled by loading additional modules inside /etc/prosody/prosody.cfg.lua (under modules_enabled); to enable mod_something just add a line like:


    "something";

    Most of these come from the prosody-modules package (and thus from https://modules.prosody.im/ ) and some may require changing when prosody 0.10 will be available; when this is the case it is mentioned below.



    • mod_carbons (XEP-0280)
      To keep conversations syncronized while using multiple devices at the same time.

      This will be included by default in prosody 0.10.



    • mod_privacy + mod_blocking (XEP-0191)
      To allow user-controlled blocking of users, including as an anti-spim measure.

      In prosody 0.10 these two modules will be replaced by mod_privacy.



    • mod_smacks (XEP-0198)
      Allow clients to resume a disconnected session before a customizable timeout and prevent message loss.



    • mod_mam (XEP-0313)
      Archive messages on the server for a limited period of time (default 1 week) and allow clients to retrieve them; this is required to syncronize message history between multiple clients.

      With prosody 0.9 only an in-memory storage backend is available, which may make this module problematic on servers with many users. prosody 0.10 will fix this by adding support for an SQL backed storage with archiving capabilities.



    • mod_throttle_presence + mod_filter_chatstates (XEP-0352)
      Filter out presence updates and chat states when the client announces (via Client State Indication) that the user isn't looking. This is useful to reduce power and bandwidth usage for "useless" traffic.




    @Gruppo Linux Como @LIFO

    Fabián Bonetti, der.hans, Laura Arjona, B. Ross Ashley and 4 others likes this.

    Fabián Bonetti, Jorge, Kevin Everets, JanKusanagi @i shared this.

  • Pump.io 1.0.0 is now available!

    Pump.io Community at 2016-08-27T07:57:44Z

    Greetings, pumpers!

    Pump.io 1.0.0 is now available! You can get it from npm or GitHub.

    Note that this release does contain security improvements. Admins are strongly encouraged to upgrade.

    Curious to find out more? Check out the release announcement!

    ostfriesenmärz, archaeme, Marcos, Sotitrox and 31 others likes this.

    ostfriesenmärz, archaeme, Marcos, Jose Carlos Jimenez and 18 others shared this.

    Show all 6 replies

    >> JanKusanagi:

    "Why would it not be? =)”

    I was watching Alex's talk about the Pump.io network the other day, and he mentioned that Identi.ca is a super special snowflake because it's been modified to read from the old Status.net data store as well as the new Pump.io one, so I figured it might not be a supported configuration.

    Screwtape at 2016-08-28T01:55:36Z

    It's already Pump.io just like the other nodes, there's no reason not to upgrade it.


    It has extra data from the StatusNet import, but that was converted loooong ago.

    JanKusanagi @i at 2016-08-28T01:57:51Z

    Alex Jordan, Claes Wallin (韋嘉誠), Screwtape likes this.

    @Screwtape unfortunately my answer to that particular question was misinformed. Jan is correct - identi.ca is a special snowflake, but that's just because of the sheer size of the database, not because of any custom code. (Maybe I should add a note to the video...)

    In any case, identi.ca will, in fact, probably get 1.0.0 at some point :)

    Alex Jordan at 2016-08-29T00:14:34Z

    Claes Wallin (韋嘉誠), Screwtape likes this.

  • The State of Mobile in XMPP 2016

    Jorge at 2016-06-03T14:32:43Z

    XMPP is not suited for mobile devices. That’s a myth that has been around for ages. It is mostly spread by people who want to sell you their own proprietary instant messaging solution. But it also gained some popularity through a blog post entitled The (Sad) State of Mobile XMPP in 2014 by Georg Lukas. While Georg wasn’t wrong with his status report per se, it is important to understand that he describes a temporary problem. There was a brief period of time where XMPP actually had some catching up to do. XMPP was fine before, when we had different requirements—In fact I was using an XMPP client on my Nokia E71 back in 2008 (That’s more than two years before WhatsApp was even invented)—and it’s fine now in 2016…


    https://gultsch.de/xmpp_2016.html


    via: https://primatemind.info/notice/37454

    CUENTA NO ACTIVA, Colegota, Matteo Bechini, Timo Kankare and 6 others likes this.

    CUENTA NO ACTIVA, Colegota, Arcee, Arcee and 4 others shared this.

    Show all 7 replies

    >> Morgan McMillian:

    “[...] However even then it almost always ends up being SMS. [...]”

    Then SMS it is. As long as they can 'find' you on WhatsApp or $CURRENTSILO, they won't touch anything else. Why would they? ;)

    JanKusanagi @i at 2016-06-04T00:07:22Z

    lnxwalt@microca.st likes this.

    Are there stable public servers again?

    jasonriedy@fmrl.me at 2016-06-04T22:33:22Z

    >> jasonriedy@fmrl.me:

    “Are there stable public servers again?”

    In the +10 years I've been using jabber/XMPP, there have been, so... yes?

    JanKusanagi @i at 2016-06-04T23:05:42Z

    List of public servers if your looking for one. https://xmpp.net/directory.php

    Morgan McMillian at 2016-06-05T03:12:27Z

  • Evan Prodromou at 2015-09-21T16:46:09Z

    Next steps for pump.io

    I don't have the time, energy, or money to put into keeping the pump network going by myself any more. I'd like to get some help.

    Ideally, what I'd like to do is transfer the copyrights, domains and data to a non-profit that could collect donations to keep the servers running. Budget-wise, it's about $5K/year, including servers, domain registration, and SSL certs.

    It'd also be great if some of the people who have been sending in pull requests could start working on the software directly. There are a lot of PRs backed up.

    I'm open to any suggestions on this stuff; I don't feel like I've been a good steward to pump.io lately, and I'd like to get us back on track.

    jasonriedy@fmrl.me, Matteo Bechini, Evan Prodromou, l30bravo and 26 others likes this.

    Fabián Bonetti, victorhck, João Patrício, Lars Wirzenius and 29 others shared this.

    Show all 7 replies

    I would definitely like to assist on the administrative side though my current employer keeps tightening the reins as time goes by. If one of these pending transfer proposals goes through, that may change. I have a period with my hands tied on certain functions if I were an operator at a corporate entity if that were a new job for me.


    If @Christopher Allan Webber and @Bradley M. Kuhn want to loop me in on e-mail discussion my Launchpad page ~skellat has a current & correct e-mail for me.


    I have some co-workers with BBAs who are willing to jump ship if the price is right...

    Stephen Michael Kellat at 2015-09-21T19:05:14Z

    Being realistic with myself, I can't donate time on the coding. I could probably donate some time for administration, but since I'm not in anybody's "web of trust" (cryptographically or socially) here, I won't suggest it. However, I would like to say I am definitely willing to contribute my meager funds to an appropriate place to help keep the lights on. Thank you for carrying the pump.io network as much as you have, Evan!

    Charles Stanhope at 2015-09-21T19:42:32Z

    Claes Wallin (韋嘉誠), Evan Prodromou, Christopher Allan Webber, pingi likes this.

    Thank you for evanrything, which includes a whole whole whole lot!

    Mike Linksvayer at 2015-09-22T18:10:27Z

    Claes Wallin (韋嘉誠), Evan Prodromou, jrobb, mnd and 6 others likes this.

    Thank you so much for everything!!

    l30bravo at 2015-09-24T17:42:22Z

  • KDE Plasma 5.4 Released

    Jure Repinc (JLP) at 2015-08-25T14:34:05Z

    New in this release

    This release of Plasma brings many nice touches for our users such as new fullscreen application launcher, much improved high DPI support, KRunner auto-completion and many new beautiful Breeze icons. It also lays the ground for the future with a tech preview of Wayland session available. We’re shipping a few new components such as an Audio Volume Plasma Widget, monitor calibration tool and the User Manager tool comes out beta.

    More: KDE Plasma 5.4 Released

    #KDE #Plasma #Desktop #Linux #BSD #UNIX #OpenSource #FreeSoftware #Software #IT

    Adrián Perales, eomer, l30bravo, dbillyx and 3 others likes this.

    eomer, dbillyx, juancuyo, Martin S. and 3 others shared this.

    Wooohoooo!! \o/


    I've been using the beta and it worked great =)

    JanKusanagi @i at 2015-08-25T14:39:24Z

  • Maria Chiara Pievatolo at 2014-01-28T16:37:51Z

    I'm here again. Eventually I found a suitable pump.io client for Linux, Dianara: http://dianara.nongnu.org/

    Let's see how it works...

    JanKusanagi @i likes this.

    JanKusanagi @i shared this.

    Then if you see a current version you'll be surprised =)

    JanKusanagi @i at 2015-08-21T12:56:19Z

  • roelofpieter at 2015-03-26T14:49:03Z

    As @JanKusanagi suggested I will now post a public notice to see if a like from Koendekat reaches my instance. Since it is public anyway I have removed followers from the CC field. This is still a test. Please ignore...

    JanKusanagi @i likes this.

    But can we comment on it? :D

    Dana at 2015-03-26T14:52:06Z

    Just so you know, there's no harm in leaving the "Followers" in the Cc field =)

    JanKusanagi @i at 2015-03-26T14:52:57Z

    Hi Jan. I just noticed your like on the original post in this thread! This one does show up. What's the difference between your like and the like is Koendekat?

    roelofpieter at 2015-03-27T06:10:53Z

  • Miguel Anxo Bouzada at 2015-01-27T11:07:55Z

    Chegou a hora de pensar en empregar Dianara ... mais antes terei que poñerme a traducila :-)

    JanKusanagi @i, EVAnaRkISTO likes this.

    Traductor oficial a galego del soft de JanCoding =)

    JanKusanagi @i at 2015-01-27T21:41:23Z

  • Share to whom?

    Timo Kankare at 2014-12-30T20:56:28Z

    When I press share button in pump.io client, to whom is the note shared? Can I someway specify that the note is shared to this and that people or list?

    JanKusanagi @i likes this.

    cmhobbs shared this.

    Show all 6 replies

    That's a good question. I think sharing is just another action in pump.io, like posting, liking etc. So probably clients could allow you to select to whom you are sharing. I should investigate this when I have time... :-)

    Or has any of the other client devs already looked into this? @JanKusanagi @Owen Shepherd @Tsyesika?

    Of course it raises some issue that you can share a private post with "Public", i.e. post it to the rest of the world. At the very least the client should warn you if you do that so you don't do it by mistake.

    sazius at 2014-12-30T21:04:11Z

    Yes, it seems so. Dianara shows it cc my followers.

    I think that the selecting could be useful feature. And also that warning about mistake.

    Timo Kankare at 2014-12-30T21:13:07Z

    sazius likes this.

    OK, I added it to an old feature request for Pumpa: http://pumpa.branchable.com/bugs/Allow_public_sharing/.

    sazius at 2014-12-30T21:16:22Z

    Sharing without specifying recipients, as with many things in pump.io ATM, defaults to "CC:followers".


    >> sazius:

    “That's a good question. I think sharing is just another action in pump.io, like posting, liking etc. So probably clients could allow you to select to whom you are sharing. I should investigate this when I have time... :-)
    Or has any of the other client devs already looked into this?”

    AndStatus shares to Public (as with many things it does to Public, but they're fixing that now, I think...), so we know that addressing a share works.


    >> sazius:

    “Of course it raises some issue that you can share a private post with "Public", i.e. post it to the rest of the world. At the very least the client should warn you if you do that so you don't do it by mistake.”


    Well, it's actually close to the current problem, where you can happily share with all your followers a very private message, very easily.


    I'd say sharing a non-public message shouldn't be allowed, at the server level.


    That being said, having the possibility of "sharing to especific people" is on my TODO list for Dianara, but I also might limit it to public posts. That brings a different set of problems, because if you see a post via someone sharing it, your client can't know if it was public...

    JanKusanagi @i at 2014-12-31T01:13:51Z

    jpope likes this.

  • Pump.io, what's going on?

    Björn Schießle at 2014-12-30T19:33:21Z

    I just had a look at the github page of pump.io and was surprised that the last commit is six months old. Is https://github.com/e14n/pump.io still the official repository or does the development happens somewhere else? Do I have to worry about the future of pump.io?

    Gustavo S. Ulloa, l30bravo, JanKusanagi @i, Evan Prodromou likes this.

    Aqa-Ib, l30bravo shared this.

    While I agree it's a bit worrying, and there are some things that still need work in the pump.io core, I wouldn't be that worried :-) Pump.io shouldn't be seen as a single big code base, the idea is to have a very minimalistic server and most of the action (and development) would be in clients and services built around it.

    I guess you are already aware of the clients (since you're using Impeller :-) but the most exciting recent development is that Mediagoblin now supports the pump.io protocol as well (should be coming in the next release). You can see it as a new special-purpose server implementation of pump.

    That said, I wish Evan would bring more people from the community e.g. to maintain the code. I understand he is very busy with other things at the moment, and could use the help.

    sazius at 2014-12-30T19:46:30Z

    Scott Sweeny likes this.

    I'd quote what Sazius said, word by word =)


    Pump.io is muuuuch more than just the core, and there are lots of possibilities to explore already, even if the core system isn't improved.

    However, that being said, the core system has several important issues that need addressing, and it certainly be great if Evan could find the time to work on it again (maybe if we could get him some decent funding) and/or be able to delegate on other people. Problem for #2 is... who really knows how the internals of a Pump.io server work? =)



    There's also the work on W3C's SocialWG to consider. Since plenty of things will need to be adapted to the "common" agreed protocol, I guess it makes sense to wait until there's something solid.

    JanKusanagi @i at 2014-12-31T01:19:40Z

    Well, for the record, Pump.io already _has_ groups, but there are several features missing (like easily looking up which groups you're in), so it's not really usable yet.

    K' at 2014-12-31T14:21:27Z

  • Dianara 1.2.5 beta

    Adrián Perales at 2014-11-27T23:06:40Z

    Soy usuario de Dianara desde hace mucho, y me maravillo cuando veo lo que evoluciona día tras día. Lo mejor para usarlo es compilarlo periódicamente desde GIT, ya que nunca ha habido problemas demasiado grandes con las versiones en desarrollo. Lo último que me encuentro es una manera mucho más clara de visualizar las notas que han sido compartidas, que unido a los otros "Mientras tanto" y el resto de novedades, hacen que la experiencia con Pump.io gane muchos enteros. Incluso uno llega a olvidarse del estado tan relativamente temrpano del software nuclear.


    Enhorabuena, Jan. Y al resto de usuarios, no os asustéis y compilad desde el repositorio de Gitorius, que merece la pena.

    Bd Sn, JanKusanagi @i, Alberto Moshpirit, Panko and 1 others likes this.

    Colegota shared this.

    Show all 11 replies

    >> JanKusanagi:

    “Lo del software nuclear me ha encantado, por cierto xD”


    Suena a bomba atómica, sí xD


    Pumpa es el otro gran cliente y se puede alternar entre ambos sin problemas. Yo soy "dianarista" confeso :P

    Adrián Perales at 2014-11-28T14:32:52Z

    Me gustaría que distribuyeran las ultimas versiones compiladas.

    Es solo por un tema de practicidad. Si queremos que Pump.io llegue a cualquier tipo de usuario básico, nadie va a querer estar compilando el código fuente de las últimas versiones cada vez que quiera actualizarse.


    También hay que pensar en los usuarios comunes, no solo en los informáticos.

    Eduardo at 2014-11-30T18:57:22Z

    >> Edward:

    “También hay que pensar en los usuarios comunes, no solo en los informáticos.”


    Le estas cantando al coro, pero vamos... esto es una beta, no algo que deba llegar a cualquier "usuario comun".


    Y de todas maneras, empaquetar las ultimas versiones es cosa de cada distribucion. Si tu distribucion no esta al dia, pidele a ellos que actualicen el paquete.


    Pero vamos, que la actual estable es la v1.2.4 aun, eh?


    Debian Sid o Mageia 5 tienen la ultimisima. Tu distribucion podria tener lo mismo.

    JanKusanagi @i at 2014-11-30T19:21:24Z

    >> Edward:

    “Me gustaría que distribuyeran las ultimas versiones compiladas.
    Es solo por un tema de practicidad. Si queremos que Pump.io llegue a cualquier tipo de usuario básico, nadie va a querer estar compilando el código fuente de las últimas versiones cada vez que quiera actualizarse.

    También hay que pensar en los usuarios comunes, no solo en los informáticos.”


    Aparte de que en la nota se está hablando de la versión de desarrollo y no de una versión final, hay una razón de por qué en general se desaconseja que el empaquetado lo haga el desarrollador "upstream": el empaquetado implica conocer las reglas que impone cada distribución y estas las conocen mejor que nadie los propios mantenedores de las distribuciones. Puede haber problemas como incompatibilidades binarias con las bibliotecas instaladas (esto se soluciona solo recompilando... y por tanto, ya no te sirve el paquete binario), rutas de archivos diferentes en una u otra distribución (ojo, esto pasa entre Debian y Ubuntu... no hace falta comparar Mageia con Slackware) o que el empaquetado no esté bien y provoque problemas en la gestión de paquetes.


    La fórmula ensayada y que funciona es que el desarrollador publique un tarball y las distribuciones interesadas toman el tarball y lo transforman en un paquete binario.

    Eugenio M. Vigo at 2014-11-30T21:24:42Z

  • Undefined at 2014-11-19T20:24:57Z

    Yo también me cansé de "lavar el cerebro" a la gente con el tema de las redes libres y descentralizadas. Pero eso de "si no puedes con ellos únete a ellos" no me parece una buena opción. Si los demás no quieren unirse a lo mío no tengo por qué unirme yo a "lo que usa todo el mundo", eso sería pasar de ser parte de la solución a ser parte del problema.

    Simplemente informo del tema cuando me preguntan lo típico (oye, ¿tienes guasap/feisbuc/tuiter/inserteaquíelnombredecualquierotrosilo/etc?); y si se interesan por ello, perfecto; pero si no veo ningún interés, pues paso. Cada uno con lo suyo.

    Total, si alguien quiere algo de mí todavía existen muchas otras vías de contacto "aptas para todos los públicos" (email, el teléfono fijo de toda la vida, y el invento más revolucionario de toda la historia: las quedadas en persona, sin pantallitas, ni cables, ni wifis ni ná' por medio).

    Quizás suena un poco a imposición por nuestra parte, pero es que precisamente son ellos los que nos están imponiendo sus mierdas sin ni siquiera saber ellos mismos lo que están usando. Esto de que el mundo cada vez esté más centrado en internet y que ese mismo mundo esté dominado por analfabetos en dicha materia es muuuuy peligroso. Y luego somos nosotros los frikis que imponen cosas raras...

    phoenixrlv, Icaro Perseo, JanKusanagi @i, Akari and 1 others likes this.

  • Why I think pump.io should join the Federation

    sazius at 2014-11-03T21:21:34Z

    I just wrote a blog post with my thoughts from FSCONS 2014. Summary: I think pump.io should join the Federation: we should build interoperability with GNU Social and Diaspora right now.

    JanKusanagi @i, Digital Roffey, gryps75, Adrián Perales and 18 others likes this.

    gryps75, Cuenta cancelada. Estoy en https://hubzilla.nl/channel/manuel-jf, Stephen Sekula, jrobb and 6 others shared this.

    Show all 56 replies

    >> heluecht:

    “When calling https://hotpump.net/api/user/heluecht/inbox before, there was no comment from you at all. I would have to poll the "proxyURL" from time to time, since there is no notification at all.”

    No, you're not supposed to get activities done by people you don't follow (this is a point that needs enhancement, and it's actually addressed, I think, in Owen's 'demo' spec).


    But if you query a public post's replies, you'll see every reply, no matter who you follow.

    JanKusanagi @i at 2014-11-06T23:04:52Z

    Querying replies would mean regular polling of all posts in a specific time frame.

    Michael at 2014-11-06T23:14:29Z

    @heluecht I agree that is a problem, and one that I've had with Pumpa as well. But @JanKusanagi is right, @Owen's demo spec does indeed propose to solve this problem. I just read it through this morning, and it has the concept of notifications propagating back. It should cause the replies to appear as new actions for everyone that got the original post.

    sazius at 2014-11-07T12:39:39Z

    while something like a firehose would do what I'm wanting, it's far more centralized and less federated than I would like for this sort of thing. so I was thinking that some sort of peer to peer discovery protocol or mechanism would be able to accomplish what I'm thinking. I was stuck on how nodes/hosts would find each other without some sort of centralized list, but i figured perhaps something like how i imagine discovery to work on decentralized ptp sharing networks. if each host had a list of what nodes it knew about and where the public posts go for said node (either itself or a firehouse node), my host or even client could propagate to me posts out there for public consumption on any federated host/network by bouncing around to all the known nodes a host knows about when it lands there. and a given node could decide to not respond to requests from outside or non-whitelisted nodes if the admin doesn't want to join the public network. this would also help solve the problem of finding people on different nodes or even networks as the search could go through the network and ask each host to search for whatever.

    David "Judah's Shadow" Blue at 2014-11-07T14:46:04Z

    Dylan likes this.

  • TecnoParanoids at 2014-10-13T18:57:54Z

    TecnoParanoids nº18: FINDENEGRO, Hackmeeting y divagaciones.

    http://www.radioela.org/TecnoParanoids-no-18-Finde-negro.html

    JanKusanagi @i, Fanta, elbinario, PuppetMast3r and 1 others likes this.

    Fanta, Fanta, Fanta, elbinario and 3 others shared this.

    Allí que andamos escuchando los jueves :). Genial.
    Veo que publicais desde la web. Lo cierto es que dianara es un buen cliente para escritorio y permite sacarle buen rendimiento a la red PUMP más que usando la interface web.

    elbinario at 2014-10-15T10:03:22Z

    ayer estuve trasteando con dianara, pero en el curro no puedo instalarlo, así que tocará ir alternando web y dianara. Lo guapo sería tener una app en Firefox OS.

    TecnoParanoids at 2014-10-16T09:08:05Z

    elbinario likes this.

    >> TecnoParanoids:

    “estuve trasteando con dianara, pero en el curro no puedo instalarlo”


    Por algo particular?

    JanKusanagi @i at 2014-10-16T10:44:15Z

    Pues si. Una app para firefox es algo que tenemos en mente desde hace tiempo. Poc a poc.

    elbinario at 2014-10-16T12:52:39Z

  • Question

    Blog Reader at 2014-10-08T07:09:10Z

    Are there users in the pump network speaking and writing in other languages than English? :-)

    JanKusanagi @i likes this.

    Show all 14 replies

    >> JanKusanagi:

    “In Dianara you can set up filters for several things. In Pumpa I think you can use "auto-minimise posts".

    Ok, I will give Dianara a try :)

    Blog Reader at 2014-10-08T13:49:18Z

    >> Blog Reader:

    “Yes please - German and French user list would be cool :) ”


    OK, let's see:


    German:


    French:


    And from these people's Following and Followers lists you can find more people, some of which might also post mainly in french or german.


    Cheers! o/

    JanKusanagi @i at 2014-10-08T13:57:10Z

    Stephen Sekula likes this.

    lots! (but not me)

    jrobb at 2014-10-08T14:11:45Z

    I just compiled Pumpa 0.9 on Ubuntu 14.04 and searching for the "auto-minimise posts"... Let's see :)

    Update: I found it :)

    Blog Reader at 2014-10-08T18:34:18Z

  • Tutorial of Dianara in linuxmint community site

    talo at 2014-09-16T10:48:12Z

    I have made a easy tutorial of Dianara for the linuxmint community , the distro what i use.

    you can see here ( if you are a registered user you can vote and comment ).


    You will see some html code in the doc , but is a bug of the webapp i think , i have tried but allways it is wrong.

    if you see some error , tell me please :)


    lostson, n2t, JanKusanagi @i, jrobb likes this.

    jrobb shared this.

    Show all 6 replies

    >> talo:

    “>> jrobb:
    “very good!
    It may be a good idea to also link to one of the wiki docs on people to follow and such, for new users not familiar with pump.io”

    yes , i had taht idea , but the rules are you can only write about linuxmint software.
    well , is a first step i think , when the people comes here will can see more stuffs of pump.io :)”


    Yes, but some links, at least, doesn't break rules about "mint software" (I think), it's just a web service, and can be a good tutorial complement... Maybe as a note at the end of article/howto (you can put it there as "sources").

    Panko at 2014-09-16T11:30:47Z

    Nice work, thanks!


    Some notes:

    • As Panko said, just linking to a couple of places where it talks about what Pump.io is and how to find people shouldn't hurt. It's very related to this software and its proper use.
    • The posts in the Messages tab are not necessarily private. They're messages addressed to you, but they can still be sent to more people, or be public.
    • Where you say "You can also follow people that you follow along by clicking on the followers tab", I guess you mean "also follow people who follow you, by clicking on....".
    • I think the sentence "On To Button whom will you send the message" could be reworded to be clearer. Something like "Click the 'To' button to select who will see your message". Also, there's no problem with this field being empty. What is recommended is that the post be sent to Public, to avoid the problems with comments in "followers only" posts.

    Cheers! o/

    JanKusanagi @i at 2014-09-16T11:54:20Z

    Nice!

    If you link to the sources of the tutorial, people can send you patches, not only "tell" you if they find errors.

    You can also state the license of your tutorial, and if it's a free culture license, you make easy for people to translate, reuse, etc. at the same time that you get more dissemination :)

    Laura Arjona at 2014-09-16T12:13:19Z

    UPDATED. I have written some links at the end of document with information about using pump.io., changed the stuff about what @Jankusanagi says.

    Thanks to all!

    talo at 2014-09-16T15:18:19Z

  • capngloval at 2014-08-26T17:43:24Z

    luq, bing qamuSHa' DaH HoSqu'mo' tlhIngan mugh 'oH.

    JanKusanagi @i likes this.

    Show all 6 replies

    >> sazius:

    “That's Klingon I think :-)”


    Hmm.. the lack of any mention of "petaQ!!" (p'tak, patahk, etc) threw me off =)

    JanKusanagi @i at 2014-08-26T18:29:41Z

    The lack of "Qapla'" confused me for a while ... :-)

    I recognised "tlhIngan", though :-)

    sazius at 2014-08-26T18:44:40Z

    capngloval likes this.

    I figured I would let the geeky klingon speaking world know with klingon that bing offers english to klingon and klingon to english translations.

    As a matter of fact, I know not a single stitch of klingon, so if it where not for bing's goofy option, this phrase above would not exist.

    now on to more important matters, how would I send a message to 1realtime from identi.ca or vice versa? i also have a quitter account which i think uses pump.io...?? never knew I could use just one account...??

    capngloval at 2014-09-11T14:39:05Z

    I'm just following you from @identi.ca... And I can transparently comment on this post you made from your @1realtime.net account.


    Identi.ca and 1realtime.net are just two of many Pump.io servers, and they are federated, which means they can talk to each other. Just like you can send an e-mail from a @gmail.com account to an @hotmail.com account, you can follow people on any other public Pump.io server.



    Also, as a former user of identi.ca (and apparently, still using it in parallel with 1realtime.net), you should read this:

    https://identi.ca/jankusanagi/note/IpfiW7kBQYuXt6H7odMzQQ

    JanKusanagi @i at 2014-09-11T14:54:53Z

  • at 2014-08-19T06:45:46Z

    sazius, jrobb, Eugenio M. Vigo, JanKusanagi @i likes this.

    Eugenio M. Vigo shared this.

    Oh, nice! =)

    Thanks for the info!


    Pretty outdated version of Dianara, though... I wonder why :\

    JanKusanagi @i at 2014-08-19T07:18:37Z

    Eugenio M. Vigo likes this.

    Cool, no idea what they are saying though :-)

    sazius at 2014-08-19T13:00:39Z

  • Chris Warburton at 2014-03-12T15:42:37Z

    Finally got identi.ca messages showing on my blog again, since the switch to pump.io. The solution:
     - Use pump2rss to get an ATOM feed URL
     - Put a script in cron to wget that URL
     - Pipe the results through "xmllint --format --recover - 2> /dev/null" to fix dodgy markup
     - Pipe that through xsltproc to strip out the empty title elements
     - Pipe that through xsltproc again to turn content elements into title elements
     - Pipe that into a Web-accessible file
     - Point ocPortal's side_rss block at that file's URL

    sazius, JanKusanagi @i, Christopher Allan Webber likes this.