Pesquisar

Search results for: dev

Fabio
3 meses atrás de Friendly
Got into Distributed Web dev room. Missed first two talks because wake up late and room was full... #fosdem2017
Fabio
8 meses atrás

turbo/alwsl

alwsl - Install archlinux as the WSL (Windows Subsystem for Linux) host.
Fabio
10 meses atrás
Looks like twitter use a nested item object called 'retweeted_status'
https://dev.twitter.com/faq#76

(it's really like what I wanted to do when I started this changes :-) )
Bordesholm
Tim Schlotfeldt
12 meses atrás
Tim Schlotfeldt wrote the following post:
#Network-Manager upgrade brakes #OpenVPN
<span class="bookmark">FS#47535 : [networkmanager]1.0.10-1 openvpn plugin fails to add routes.</span>
Description:
OpenVPN connections (which serve a default route) initiated via NetworkManager fail to add essential routes -> VPN does not work.
Downgrading to 1.0.8-1 is a possible workaround (not that you would want that).

Additional info:
* networkmanager 1.0.10-1
* log output
Dez 26 14:08:11 antares NetworkManager[1391]: platform-linux: do-add-ip4-route: failure adding ip4-route '5: 172.17.1.1/32 50': Unspecific failure (1)
Dez 26 14:08:11 antares NetworkManager[1391]: VPN connection 'somename' (IP Config Get) complete.
Dez 26 14:08:11 antares NetworkManager[1391]: (tun0): link connected
Dez 26 14:08:11 antares NetworkManager[1391]: platform-linux: do-add-ip4-route: failure adding ip4-route '5: 0.0.0.0/0 50': Unspecific failure (1)
Dez 26 14:08:11 antares NetworkManager[1391]: default-route: failed to add default route 0.0.0.0/0 via 172.17.1.17 dev 5 metric 50 mss 0 src vpn with effective metric 50

Steps to reproduce:
Connect to an OpenVPN server which pushes a default route to its clients.






@Arch Linux
Bordesholm
Tim Schlotfeldt
1 ano atrás
#Network-Manager upgrade brakes #OpenVPN
<span class="bookmark">FS#47535 : [networkmanager]1.0.10-1 openvpn plugin fails to add routes.</span>
Description:
OpenVPN connections (which serve a default route) initiated via NetworkManager fail to add essential routes -> VPN does not work.
Downgrading to 1.0.8-1 is a possible workaround (not that you would want that).

Additional info:
* networkmanager 1.0.10-1
* log output
Dez 26 14:08:11 antares NetworkManager[1391]: platform-linux: do-add-ip4-route: failure adding ip4-route '5: 172.17.1.1/32 50': Unspecific failure (1)
Dez 26 14:08:11 antares NetworkManager[1391]: VPN connection 'somename' (IP Config Get) complete.
Dez 26 14:08:11 antares NetworkManager[1391]: (tun0): link connected
Dez 26 14:08:11 antares NetworkManager[1391]: platform-linux: do-add-ip4-route: failure adding ip4-route '5: 0.0.0.0/0 50': Unspecific failure (1)
Dez 26 14:08:11 antares NetworkManager[1391]: default-route: failed to add default route 0.0.0.0/0 via 172.17.1.17 dev 5 metric 50 mss 0 src vpn with effective metric 50

Steps to reproduce:
Connect to an OpenVPN server which pushes a default route to its clients.





@Arch Linux
Berlin
Tobias
1 ano atrás de open socialverse
Code of Conduct
During this years Hackathon in Berlin @Silke proposed a Code of Conduct (CoC) for the Friendica Project. She made her proposal in German, so I wanted to revive the conversation in English so everyone of the development community can contribute to it.
The proposed CoC is the following (from Contributor Covenant, which is adopted by more then 10k FLOSS projects, among other our friends from the Diasoira project.):

Clique para abrir/fechar


This is nothing to regalement every day postings from any Friendica user.

It is meant as guideline for the interaction in the development and support forums, the mailing list, the issue tracker (ant other dev/support places I've missed). And in essence, this is basic human behavior.

Personally I think the Friendica development community, as it is now, is a healthy and open community. But it is a small community, most of the core developers have met once or twice and read each others postings for years. It is also a growing community (this years Hackathon has twice the number of participants then last year) but I don't want to awake one day when the atmosphere has shifted and hate speech is there.

Having a CoC is also a sign for people who had bad experiences in the past, that this community does have a healthy spirit. Some advertisement like having the code licensed under the AGPL.

Hence I think that now is a perfect time for the project to discuss this and hopefully agree on a / the CoC. One does not take a lifeboat on a sailing trip because one wants to use it, but to be prepared in case the ship is sinking. If we do not need it, all the better.


@Friendica Developers
Linux Walt
1 ano atrás
Indentation remains the same, regardless of the editor setting. (Which could be set wrong if someone is working on multiple projects with differing style rules.)

Stray spaces in a line are always visible, so you can deal with them. With tabs, it depends on how many and where the spaces are relative to the tabs.

Someone in this thread has already mentioned PEP-0008. See https://stackoverflow.com/questions/119562/tabs-versus-spaces-in-python-programming
Moritz Strohm
1 ano atrás
I think the most important thing is left out: Coding style for functions, variables, class methods, class attributes and classes themselves.

I would recommend the following, as specified in PEP-0008 (Style Guide for Python Code):

- Write class names with capital letters for each word, for example: DiasporaProfileLoader

- write variables, class methods and attributes in lowercase with underscores between each word, for example: get_newest_posts

More details can be found here: https://www.python.org/dev/peps/pep-0008/

I'm deploying PEP-0008 at least on all my python software projects at the moment. But PEP-0008 would also make sense in other languages :)
Tobias
1 ano atrás de open socialverse
my node knows 20 nodes on -dev, the chances should not be that high ;-) and we need a reason why develop was separated from master from time to time :-)
24837,DE
Jan Montag
1 ano atrás
Hallo @Friendica Support @Friendica Developers,

ich habe jetzt einmal das XMPP-Plugin installiert, dabei ist mir ein Fehler aufgefallen. Wenn ich versuche, einen normalen Post zu editieren, wird das Eingabefeld geleert, sobald den Curser hineinsetzt. Wenn ich das XMPP-Plugin deaktiviere, funktioniert wieder alles ganz normal.

Als Theme nutze ich Vier und meine Friendica-Version ist die 3.4.3-dev - 1191 und mein Browser ist der Firefox.

Vielen Dank,
Jan

#friendica
Berlin
Tobias
3 anos atrás de Open Socialverse
Isabel Drost-Fromm wrote the following post:
To everyone contributing to free software projects: Wish you a happy "I love free software day"

Fsfe: I ♥ Free Software - Valentine's Day 2014 - FSFE

Valentine's Day traditionally is a day to show and celebrate love. So why do not take this as a chance to show your love for Free Software this year? #ilovefs day 2014 As every year, Valentine's Day will be celebrated on the 14th of February, which will be a Friday this year.
Mr. X
5 anos atrás
"No failures". :-)

http://friendica-dev.dyndns.org/job/Friendica/95/

But I had to resort to some hackery to get there. We need a lot more tests and a review of some of the questionable ones.
Matthew Exon
4 anos atrás
Any standard techniques for improving performance?
@Friendica Developers

I've just had a go at moving my Friendica site to an Amazon EC2 instance. I was hoping that with a slightly larger memory size it would be faster. In fact it's now taking several minutes just to load the network page! A quick and dirty test suggests that disk access is three times slower on my EC2 instance than my old system, so I guess that's the main problem:
mat@alice:~$ time dd if=/dev/zero of=testfile bs=1M count=1024<br />real    0m9.320s<br />mat@rei:~$ time dd if=/dev/zero of=testfile bs=1M count=1024<br />real    0m28.136s
I'm just using a standard EC2 micro instance and my database is sitting on a standard EBS volume. There are probably things I can tweak to get better performance out of that volume, which I may or may not have to pay for. But I'm wondering if there are any standard tips for improving performance?

Watching browser requests in the firefox console, there's a couple of things that bother me:

<ul>
  • Every time I load a page, it requests a bunch of avatars for friendica developers. These have something to do with ancient notifications which I never see, pre-loaded by some AJAX code I haven't been able to decipher. I can't even figure out how to display those notifications. Some of the avatars don't even exist!

  • </ul>


    <ul>
  • My network page also requests my entire profile page at "profile/mat". This page currently takes a minute and a half to load. What could it possibly need from there?

  • </ul>

    Apart from those, my initial thoughts on how I might speed things up:

    <ul>
  • Photos seem reasonably fast to load, especially when they haven't been modified since the last read. Still, I'm wondering if a reverse proxy in front of Friendica would help?

  • </ul>


    <ul>
  • My database is far too large to fit into RAM. The largest table is photos, which is due to my retriever plugin downloading photos for every article in my feeds. The mechanism for expiring articles doesn't expire the corresponding photos - photos in Friendica are forever. I've long had it in mind to write a plugin to tidy this up. It'll be a fair bit of work though, and I'm not sure it's actually going to improve performance.

  • </ul>


    <ul>
  • Apart from that, I guess I'll just modify q() so that it logs queries and measures how long they take, maybe find something that can be cached somewhere.

  • </ul>

    I'm know that performance is not the top priority right now, but still. You can get a free EC2 micro instance for a year, and you can set up a standard Friendica image that people can copy to get a running system with minimal effort. So if it actually worked, it would be a nice way to convince people to try out the system.
    Abinoam Jr
    5 anos atrás
    Docblox: automatic documentation generator
    (Just in case somebody has not noticed)... @Alexander has added docblox support to our source tree.
    First commit was: Enabled automated doc building.

    The idea is everybody willing the parsed/generated documentation should run docblox on its own clone of the repo.
    (Not commiting the generated documentation into the master repo).

    I've run it on my ubuntu desktop (not on my server [dreamhost]account).

    Basically what i did was (in a step-by-step):
    sudo apt-get install graphviz
    sudo apt-get install php5-xsl
    sudo apt-get install php-pear
    sudo pear channel-discover pear.phing.info
    sudo pear install phing/phing
    sudo pear channel-discover pear.docblox-project.org
    sudo pear install docblox/DocBlox
    sudo pear install docblox/DocBlox_Template_abstract



    changed dir into my friendica local clone and runned docblox without command-line arguments.
    The doc index.html was generated inside the friendica/data/output.

    Imagem/foto

    The docblox documentation: http://docs.docblox-project.org/

    #docblox #documentation #dev
    Mike
    5 anos atrás
    Friendica themes redux
    TL;DR - we will be deprecating some Friendica themes and providing an admin interface to select which available themes will be visible to site members.

    I probably need some help on this as I've got a lot of projects. But I think it's time to phase out the loozah themes, and the universally hated "easterbunny". There are several people currently using the loozah themes so we won't remove them. We will just consider them deprecated, and when a new theme management interface is implemented, they will become unsupported.

    Theme Management

    In order to pull this off with the least amount of disruption and angst, here's the plan....

    The theme management (admin) interface should closely mimic the plugin administration page, but in this case will choose which themes are available for members to select. If they aren't ticked "green", they won't be offered as a choice (but existing members using those themes may still continue to use them). However, if somebody changes from one of these themes to something else, they won't be offered a choice to switch back.

    I'm thinking each theme entry on this page should display the contents of a README.md or README.bb and provide a screenshot.

    We should also provide a dynamically updated screenshot on the end-user theme selection so somebody can see at a glance if they want to try the theme or not - and without committing to it.

    Once this interface is completed, we will generate a config list of supported themes as an automatic update and supply the same in the default htconfig for new installations - and this will remove the deprecated themes from the list of available choices for end-users, but allow the files to remain.

    Also at this time, the deprecated themes will become unsupported and will require volunteer support to update with any future code changes.

    At the present time, I'll maintain the zeros and testbubble. Fabio and/or Tobias will likely keep Quattro current, and Fabio and myself will manage templates for these three families. Derivatives of all of these should be fine. Others such as vier and dispy will need to be maintained by others.

    (It isn't clear but perhaps vier might work better as a derivative theme, depending on the number of changes anticipated from its quattro roots. This will make it easier to support. Unless somebody is willing to commit to maintaining Dispy it will likely become unsupported also.)

    Once all this is in place, new themes (except for low-maintenance derivatives) will most likely require a maintainer. We will probably also need a theme-dev forum to communicate core changes which might affect themes, so that maintainers aren't caught off guard.

    And of course all of this may change completely based on community feedback. Let it begin.
    Kiel
    Tim Schlotfeldt
    5 anos atrás
    *gnargl* #Gigaset and #Bluetooth under #Linux :-( The works for the SX685 isdn as well.

    Ip-phone-forum: Sinus 501 Bluetooth Sync


    Der Zugriff auf Telefonbuch und Bilder ist nur über OBEX möglich - allerdings unterstützt das Gerät nicht das OBEX Bluetooth Profile, sondern "tunnelt" OBEX über das Serial Profile.Dazu kann man das Gerät mit AT^SQWE=3 in den OBEX Modus schalten. Den Modus verlassen kann man dann mit "+++".
    Für den OBEX Zugriff habe ich OpenObex/ObexFTP verwendet. Allerdings wird das Telefon nicht als Siemens Gerät erkannt und versucht daher mit einem falschen Kommando in den OBEX Modus zu schalten.
    Das läßt sich jedoch über die folgende kleine Quellcode Änderung beheben:
    - Quellen von obexftp-0.23 herunterladen.
    - In der Datei bfb/bfb_io.c in Zeile 448 ein "gotonewsiemens;" einfügen
    - Das ganze wie in der Doku beschrieben kompilieren und installieren. Unter debian Sid brauchte ich noch die Pakete libopenobex1-dev und libbluetooth-dev
    Mike
    5 anos atrás
    Maxwell Salzberg (via Diaspora-dev):
    Also worth noting, the federation protocol has not changed much, as we want to get these new interactions working awesome, but then the federation protocol v2(codename: K-Fed) should be rolling out shortly thereafter, possibly as a separate service(subject to change).

    And this protocol is described/documented exactly where? :-(
    Mr. X
    5 anos atrás
    Good progress made on converting all "conversations" to ajax loading. Still only 25% complete but after the back-end is sorted it should fall into place pretty quickly. Reasonable progress also made on a "show more" utility which does away with item scrollbars, yet cannot be fooled by long images and large font sizes. These things haven't been pushed yet because the changes are pretty radical and my dev tree at the moment is pretty well stuffed until these things stabilise.
    I've also granted full (write) access to all current Friendica developers to the Red codebase. You're welcome to start issuing pull requests or even fixing stuff, just be aware that the entire tree is in a state of flux at the moment and you might want to ask if a change will even work in the new world of Red before spending a lot of time on it.
    Fabio Comuni
    5 anos atrás
    Got some free time in this holidays...
    Setup dev environment in my new arch installation at home, working to update friendica intall procedure.
    Next, some updates to quattro theme are waiting to be merged..

    Imagem/foto
    Mike
    5 anos atrás
    Will soon begin the final push towards Friendica 2.4 - the only big thing left is zot, and a lot of work has already been done on it (in my private dev branch - i.e. it isn't yet in the repository). We're also not going to even try to get all of zot into this release but run for a while with a hybrid, using zot where it makes sense for added performance - and phasing it in slowly to avoid instabilities.

    In the meantime, I'm pretty burned out from the recent dev work and unless something serious pops up, I'm going to break for a few days from serious coding and just chill a bit. Might do some little and/or fun stuff but otherwise it will just have to wait.
    Mike Macgirvin
    6 anos atrás
    Privacy issue introduced yesterday on dev head - some replies to private messages could leak. Was just fixed. Please pull an update.
    -19.815731 -43.954223
    Mike Macgirvin
    A lot happening in Friendika land. For those that haven't been keeping up, we're currently working on *native* Diaspora federation, and hope to have something to show in a couple of weeks or so. Friendika profiles should appear on the web as Diaspora* pods and we're hoping for seamless communications (pretty much everything but remote profile access). Fabrixxm is working on some really nice UI improvements. You can have a look at the new ACL (post permissions) selector or the mockup on the dev forum to get an idea of what's coming. A warm welcome to David Sugar who is exploring how to integrate Skype-like functionality via the GNU Telephony project. Zot! - our next generation protocol is currently on the sidelines as we begin the final push to version 2.3 - the zot project will likely merge later this year (fall for those in the northern hemisphere, spring down under) and provide a lot of structural code changes and a more streamlined code base going forward. 

    If you are a developer, we could really use your help. We've got several new features which need just a bit of tweaking to finish up - and there isn't enough time in the day for us to do it all on our own. These include an invite system (mostly there, needs exposing in the admin interface), Mustard  (for Android) access - which requires at least one additional function added to the statusnet/twitter API , and any help you can provide with the larger projects. You could start by merging the diaspora and friendika hcard formats, or firing up our OAuth server and connecting it to the API.

    These are things we need urgently *now*. You can also check the dev forum for some longer term projects to work on.

    Just roll up your sleeves and jump in. Don't be shy. And don't lollygag - Friendika moves pretty quickly. We aren't going to wait for you.
    Mike Macgirvin
    6 anos atrás
    A lot happening in Friendika land. For those that haven't been keeping up, we're currently working on *native* Diaspora federation, and hope to have something to show in a couple of weeks or so. Friendika profiles should appear on the web as Diaspora* pods and we're hoping for seamless communications (pretty much everything but remote profile access). Fabrixxm is working on some really nice UI improvements. You can have a look at the new ACL (post permissions) selector or the mockup on the dev forum to get an idea of what's coming. A warm welcome to David Sugar who is exploring how to integrate Skype-like functionality via the GNU Telephony project. Zot! - our next generation protocol is currently on the sidelines as we begin the final push to version 2.3 - the zot project will likely merge later this year (fall for those in the northern hemisphere, spring down under) and provide a lot of structural code changes and a more streamlined code base going forward. 

    If you are a developer, we could really use your help. We've got several new features which need just a bit of tweaking to finish up - and there isn't enough time in the day for us to do it all on our own. These include an invite system (mostly there, needs exposing in the admin interface), Mustard  (for Android) access - which requires at least one additional function added to the statusnet/twitter API , and any help you can provide with the larger projects. You could start by merging the diaspora and friendika hcard formats, or firing up our OAuth server and connecting it to the API.

    These are things we need urgently *now*. You can also check the dev forum for some longer term projects to work on.

    Just roll up your sleeves and jump in. Don't be shy. And don't lollygag - Friendika moves pretty quickly. We aren't going to wait for you.
    Robertson, NSW Australia
    Mike Macgirvin
    6 anos atrás
    Zot! discussion group created.

    http://groups.google.com/group/zot-dev

    This probably won't see much activity until I finish the initial spec.
    antigo