From: Dave Taht <dave.taht@gmail.com>
To: "Robert Chacón" <robert.chacon@jackrabbitwireless.com>
Cc: dan <dandenson@gmail.com>, libreqos@lists.bufferbloat.net
Subject: Re: [LibreQoS] billing integrations
Date: Fri, 21 Oct 2022 09:40:56 -0700 [thread overview]
Message-ID: <CAA93jw7njDZk48N-YAStMCeETU6iK5L2JbUNgMBD-Z-0rqwhKw@mail.gmail.com> (raw)
In-Reply-To: <CAOZyJotET+7rc7Wn=2fQwr6aD8TUVPzftP2uPSdvt5tCpkPymA@mail.gmail.com>
On Wed, Oct 19, 2022 at 6:36 PM Robert Chacón
<robert.chacon@jackrabbitwireless.com> wrote:
>
> Agree with Dan on the prominent platforms being UISP, VISP, Splynx, Powercode, Sonar V1, and Sonar V2.
>
> Poll added here to gauge the community on which CRMs/NMSs are most desired.
> https://github.com/rchac/LibreQoS/discussions/133
>
> Integration complete:
>
> UISP v1.2+
>
> Mostly Done:
>
> Splinx v1.3-alpha+ (work needed to confirm it works - volunteers welcome).
>
> Work in Progress:
>
> VISP
>
> GraphQL is an awful API but I'm trying my best with it.
>
> Not started yet:
>
> Powercode
> Sonar V1
> Sonar V2
I see the poll there, and a sudden shift back to github (which I'm
cool with), and who knows what the future holds for email 'round here.
I did want to discuss that what was on my mind was a piece of feature
set outside what I think most are thinking so far.
At the tippy top of my list was multiple language support. For most of
western europe, english suffices, allthough the brits can get a bit
stuffy sometimes about american rather than "proper" english. :)
However elsewhere in the world, where I think libreqos might become
popular, it's a grabbag.
So of these integrations above, which, if any, support Polish,
Portuguese, Spanish, Croatian, or Russian? I am not sure what
languages are common
in Africa, although I think there's a strong french influence in kenya?
The related problem in billing is currencies. Being able to not only
bill in the native (or more than one) currency is very important
elsewhere. Also payment schemes are fungible, a very common scheme for
cellular is the gift card, and in Nicaragua, at least, the post is
very unreliable and credit cards scarce, so banks and grocers take
payments of various kinds.
I did a LOT of i18n work in the 90s and am intimately familiar with
the "iconv" _(string) facility we used to cope internationalizing C.
I'm scared to look
for what exists for pythoin and rust? or for that matter, web pages?
It was extremely easy, once you started using iconv, to sit down with
a multi-lingual speaker and get a decent translate done, without
knowing anything about the code. I did the ardour.org translation with
my spanish speaking gf over a couple weeks (it was GREAT FUN! for both
of us)
>
> - Robert
>
> On Wed, Oct 19, 2022 at 6:31 PM dan via LibreQoS <libreqos@lists.bufferbloat.net> wrote:
>>
>> meh. Industry features matter.
>>
>> Leading platforms:
>> Ubiquiti's UISP (cause it's free). somewhat mediocre so people like to migrate off of it. zero support from ubiquiti but well documented API.
>> VISP. very popular, API available, they are happy to integrate. This is the 'rising star'
>> Splinx. also quite popular, second up and comer.
>> Powercode. older, very popular, steady userbase and generally well liked..
>> Sonar V1. being depreciated, well liked but not long for this world.
>> Sonar V2. Complete rewrite, well well well hated.
>>
>> This is probably 95%+ of the wISP market right now.
>>
>> Fiber market is pretty similar but there are modules for a lot of other more generic platforms for fiber so I'd say the above list is more like maybe 60% of the minor league fiber players.
>>
>>
>>
>> On Wed, Oct 19, 2022 at 6:25 PM Dave Taht via LibreQoS <libreqos@lists.bufferbloat.net> wrote:
>>>
>>> https://github.com/killbill/killbill
>>>
>>> bill.com is popular
>>>
>>> zillion others. ?
>>>
>>> --
>>> This song goes out to all the folk that thought Stadia would work:
>>> https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
>>> Dave Täht CEO, TekLibre, LLC
>>> _______________________________________________
>>> LibreQoS mailing list
>>> LibreQoS@lists.bufferbloat.net
>>> https://lists.bufferbloat.net/listinfo/libreqos
>>
>> _______________________________________________
>> LibreQoS mailing list
>> LibreQoS@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/libreqos
>
>
>
> --
> Robert Chacón
> CEO | JackRabbit Wireless LLC
--
This song goes out to all the folk that thought Stadia would work:
https://www.linkedin.com/posts/dtaht_the-mushroom-song-activity-6981366665607352320-FXtz
Dave Täht CEO, TekLibre, LLC
next prev parent reply other threads:[~2022-10-21 16:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 0:25 Dave Taht
2022-10-20 0:31 ` dan
2022-10-20 1:36 ` Robert Chacón
2022-10-21 16:40 ` Dave Taht [this message]
2022-10-21 19:28 ` Herbert Wolverson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/libreqos.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw7njDZk48N-YAStMCeETU6iK5L2JbUNgMBD-Z-0rqwhKw@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=dandenson@gmail.com \
--cc=libreqos@lists.bufferbloat.net \
--cc=robert.chacon@jackrabbitwireless.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox