Pesquisar

Search results for: friendica

Berlin
Tobias
3 dias atrás
Viva la Federation!
☠️ Grumpy Oldman wrote the following post:
zum #SCDay17 weise ich gerne darauf hin, dass "Social Media" nicht den Konzernen "gehört": #GNUsocial #mastodon #friendica #FLOSS


Und es hat nur einen halben Tag gedauert, bis ich dahinter gestiegen bin was es mit dem #SCDay17 auf sich hat. Huldigt ihr mal schön den Kommerziellen-"Sozialen"-Netzwerken.
Michael Vogel
4 dias atrás
What to do with outdated addons?
@Friendica Developers I really would like to archive them in a way so that their code isn't visible anymore when I grep for function names and so on.

I wouldn't want to delete the code, but want to have it archived to be able to access it again. How could we do this?
Michael Vogel
4 dias atrás
Remove "service class"?
@Friendica Developers In the core there is the "service class" functionality that was once planned for having additional features where users could pay for (like defining the maximum numbers of allowed contacts).

This is not used at all and cannot be configured, so it really doesn't make no sense to keep the code.

Does anyone disagree to remove it?
Fabio
4 dias atrás
@Friendica Developers

I leave this here because I don't have time to check if exists in issue tracker.

Mail and RSS import should ignore message with "message date" < ( today - "item expiration days").

Some not-so-updated rss feeds keeps showing up again after they have been deleted from db by the expiration tool, and I get the "show by commented order" network view flooded by old messages...
Rabuzarus
2 semanas atrás
@Michael Vogel
Which means that we have to store the data elsewhere. But: I would like to do this only on the transport, not the storing and processing.
.
Can you describe this point a bit more, so I understand how this would look like (transport, storing, processing).

Some side notes:
For the would I would really love to see that friendica get rid of having objects as bbcode in the item['body']. In some way we have talked about this at the last hackathon. Objects (events, share, attachments) belong to the item but are very different form some formatted text. So we should store them not in $item['body'].

To the actual problem:
I won't touch the protocol part because because I'm afraid to break something. Nor will I write very, very complex sql queries. For such a case I would wisch a function which give me the results.

So I would stop at this point and would leave it up to you to provide the basics so I could step up to do the gui part.

Back to the code in my repository:
What about the handling of nested arrays in function xml::from_array() and the extension of function xml::to_array()?
I would like to have such a functionality in the code to replace written xml elements (like we do it now for e.g. objekcts - e.g. https://github.com/friendica/friendica/blob/develop/include/event.php#L280 and many other places) to arrays.
This arrays should be easily converted to xml (with an easy possibility to convert it back). At the moment (develop branch) it is the situation that if you have a string with xml with values and attributes (or the extended case if it does have more of the same element - e.g. <link>) you won't be able to convert it to an array and back to xml.
Rabuzarus
2 semanas atrás
events in network stream
@Friendica Developers @Friendica Theme Developers

One of the many things which are not that good solved in friendica is from my point of view that fact that all objects which belong to a post are saved as bbcode in the item body. With objects I mean something like shares, attachments, events and so on. Since the beginning of using friendica I very unsatisfied that there are only limited possibilities to theme such objects because they are hard-coded. While I tried to fix https://github.com/friendica/friendica/issues/2646 some time ago I started to do some experiments how to extend the possibilities for displaying events.

Before I continue polishing and finishing the could I would like to have some feedback. There are some questions in my head and some (lets call it) designing decision to do (or which I have done and needs to discussed).

You will find the present code at https://github.com/rabuzarus/friendica/tree/20170904_-_extend_event_html and an example frio event at https://test.kommune4.de/display/9fd9b54c1359dcc60b622dd589375790

To explain what the code does:
In a short, the activity stream object (the one which is saved in the item table in the object column) will be extended with information which are needed for the event (e.g. start time, end time, author, location and so on). (I saw this in the hubzilla project and I like the idea to make more use of the object field if there are embedded object in the posts - events, share, attachments and so on).
While frindica does the preparing of the item for displaying its content, it verifies if the event item is an event and if the event object does contain additional data (for compatibility reasons with older objects). If it is an an event object it will extract the event data from the event object and will format this data in a special event template. The template formatted output will replace the existing $item['body'].
So every theme can decide how an event should be presented in the network stream.

To improve the speed, friendica does cache the html of an item. This would mean that we would need to parse the event everytime when a user would change the theme (and the event template would be a different one). To solve this only the event description (the part which should not change when selecting a different theme) is saved in the event cache.

There are some parts I want to talk about with you.
1.) I'm not sure if you like this approach (it was inspired by the hubzilla project)

2.) The created event object looks like:
[code=xml]
<object>
<type>http://activitystrea.ms/schema/1.0/event</type>
<id>urn:X-dfrn:test.kommune4.de:2:9fd9b54c3759dcc60b584d0456260405</id>
<title>Friendica Hackathon</title>
<startTime>2017-11-24 15:00:00</startTime>
<endTime>2017-11-26 19:00:00</endTime>
<description>Hackathon in Berlin to prepare the 3.6 release of Friendica.[url=https://friendica.kommune4.de/search?tag=xD]xD[/url];
&#[url=https://friendica.kommune4.de/search?tag=xD]xD[/url];
Room is limited, so please let us know if you plan to join us in Berlin.</description>
<location>
<name>Jugendclub [url=http://zope2.in-berlin.de:8100/wsb/elok]E-LOK[/url]</name>
<address>Laskerstra&#[url=https://friendica.kommune4.de/search?tag=xDF]xDF[/url];e 4-6, Berlin</address>
</location>
<content>[event-summary]Friendica Hackathon[/event-summary][event-description]Hackathon in Berlin to prepare the 3.6 release of Friendica.&#[url=https://friendica.kommune4.de/search?tag=xD]xD[/url];
&#[url=https://friendica.kommune4.de/search?tag=xD]xD[/url];
Room is limited, so please let us know if you plan to join us in Berlin.[/event-description][event-start]2017-11-24 15:00:00[/event-start][event-finish]2017-11-26 19:00:00[/event-finish][event-location]Jugendclub [url=http://zope2.in-berlin.de:8100/wsb/elok]E-LOK[/url]&#[url=https://friendica.kommune4.de/search?tag=xD]xD[/url];
&#[url=https://friendica.kommune4.de/search?tag=xD]xD[/url];
[map]Laskerstra&#[url=https://friendica.kommune4.de/search?tag=xDF]xDF[/url];e 4-6, Berlin[/map][/event-location]</content>
<link rel="alternate" type="text/html" href="https://test.kommune4.de/display/9fd9b54c8359dcc61152d76696294856"/>
<author>
<name>Ronny Rabuzarus</name>
<address>rabuzarus@test.kommune4.de</address>
<link rel="alternate" type="text/html" href="https://test.kommune4.de/profile/rabuzarus"/>
<link rel="photo" type="image/jpeg" href="https://test.kommune4.de/photo/58c7a30eeacc6492c43daf582cfb3cba-5.jpg"/>
</author>
</object>
[/code]

I'm unsure about the used tag names startTime and endTime. The naming was taken from https://github.com/activitystreams/activity-schema/blob/master/activity-schema.md#event . (should we use it or should we rather use the friendica names start and finish or should we use rather other tag names - e.g. hubzilla usesdtstart and dtend).

3.) Because I'm not familiar with xml handling in php I extended xml::from_array( ) to handle nested arrays. In addition I extended xml::to_array( ) to have a 'mixed' (Please: If some one does have a better name for this mode, please let me know) priority mode. It does convert xml in the following way: http://www.lalit.org/lab/convert-xml-to-array-in-php-xml2array/ .
In addition I changed the behavior of xml::to_array( ) in 'attribute' priority mode a little bit. Formerly the

[link]=> array(
[value]= http://irgendwas.de
)


Now it @value represents the content of a xml element:

[link]=> array(
[@value] = http://irgendwas.de
)


I did some tests to convert a xml with xml::to_array( ) and back with xml::from_array( ). The results look very good (Note this only works if the the array is created in 'attribute' or the new 'mixed' mode). I did several tests but I couldn't be sure if it doesn't break something (@Michael Vogel can you have a look - sry for disturbing your holiday).

4.) For frio I create short naming versions for the month and the day (eg. Mon, Tue and so on or Jan, Feb, Mar) in format_event_object( ). This code for this is inspired by other places in friendica where dates are created. I'm not familiar with date/time formats of other countries so this was the best way of preventing doing some mistakes. If anybody does have better solutions of solving this he/she is welcome to tell me.

5.) I have thought about creating a template for the content of function format_event_html() . But since this function is also used in function bbcode( ) I can not estimate the effects of having the possibility of different templates. Any thoughts about this?

Maybe I have other questions but I can't remember it at the moment. So I will end at this point and hope about some feedback :-)
Tobias
2 semanas atrás
The addon is not active on my node as I like the babylonian chatter; but it does not interfere with master branch of friendica core.
Michael Vogel
2 semanas atrás
There is a possible problem concerning this pull request: https://github.com/friendica/friendica-addons/pull/428
Berlin
Tobias
2 semanas atrás
Friendica 3.5.3 released
I hope I've not forgotten anything ;-) Anyhow - we have just gotten Friendica 3.5.3 :-)

@Friendica Support

https://friendi.ca/2017/10/05/friendica-3-5-3-released/
Andreas Hannusch
1 mês atrás
LINUS ! Wie kommt dein Pfotenabdruck in den Himmel ?
:dog

@Linus von der Ohrewiese
Jason Robinson
2 meses atrás
:D

Btw, wonder why I don't receive any posts from your friendica node on socialhome hmm... need to investigate logs.
Berlin
Tobias
3 meses atrás
Guten Morgen @Friendicatreffen 2017 Zwenkau

Imagem/foto

good morning and TZAG everyone! c[_]
Berlin
Tobias
3 meses atrás
Fabio
3 meses atrás
ok

https://github.com/fabrixxm/friendica-clippy

I think some of the enterprise functionalities will work only with Frio theme..

There will be a service pack with multiple, user configurable, assistants. And more annoying functionalities
Fabio
3 meses atrás
Now, anyone wants this https://www.smore.com/clippy-js as a plugin for Friendica?
Thomas Willingham
6 meses atrás
It is a snapshot of RedMatrix at the moment RedMatrix, Friendica, and Hubzilla directories could all sync with each other. That is, as the directories could share the profiles and updates they were aware of, rather than just import from the various networks.

I'm stripping out all the bits of RedMatrix that aren't a directory. Arguably, I should have started with nothing, and added all the bits that are a directory, but this way it works, right now and can be cleaned up incrementally.

What will be left (tl;dr = a standalone application you can just install and have a working, federated directory that syncs automatically, and can be searched locally or remotely):

The ability to import Friendica, RedMatrix, Diaspora, Hubilla, and oStatus profiles.
The ability to import RSS authors.
The ability to import arbitrary vCards(*).

The ability to expire profiles.
The ability to remove profiles.
The ability to censor/self-censor profiles (with a user option to turn safe search on or off).
The ability for profile owners to hide profiles.

The ability for directories to sync knowledge of the profiles (and updates to profiles) so that all directories have knowledge of all profiles for the protocols they serve, and importantly, sync changes to the vcard searchable flag so a user may remove themselves from the results of all directories just by changing their own personal vcard.

Distributed search. Distributed search sucks, but it's basically okay with a very limited number of peers. One will be able to run a directory that serves just one protocol, but deliver results for all protocols via a distributed search to directories. That is, your directory may only serve Diaspora, and sync with other Diaspora directories, but when the directory is searched, it can ask a different directory to provide results for Friendica.

Ability to filter results based on protocol (federated directories are all well and good, but you're probably only interested in those you have some way of actually connecting to), as well as profile fields like location, interest, keywords, names, etc

Directory POCO ratings. There has been some strong opposition to this from the Friendica side of things, but they're absolutley required on the RedMatrix side of things, and wanted on the Hubzilla side of things, so we're not sure how this is going to work yet. We're going to thrash it over when it gets closer to a thing that works properly.

An interface for searching the directory directly.

Ability for observers to store their personal search settings at a given directory (will require some authentication layer).

JSON feeds for search results so that an arbitrary website can act as a directory client, and include results within their own website. (Screen shots of a prototype of this working in Friendica are in my photo albums )

An admin panel.

Ostatus does not work at all yet. Distributed search does not work at all yet. Everything else is either already working, or already partially working.



(*) When I talk about vCards, in this post, and in general, that's for berevity. I'm aware they're often hCards, jCards, or whatever.
Thomas Willingham
6 meses atrás
You'll still have nomadic identity, and you'll be able to access your Friendica stream from any of them.

Clones are more complicated - not all sites will have the same capabilities, so it won't always be possible to sync all your data with all your sites - but it will be in principle possible.
Thomas Willingham
6 meses atrás
Both, and neither.

We're going to use Friendica In the same way Horde or SquirrelMail, or RoundCube use Postfix. In the short term, we still have Zot, and we still have Diaspora. In the longer term, we're only keeping the authentication and permission layers. Friendica will do all communication.
James Lamentus
6 meses atrás
Frien­dica will do our fed­er­a­tion for us?

Can you explain better ? As using the friendica protocol (not diaspora protocol) ?
Thomas Willingham
6 meses atrás
Yeah, well, maybe keeping the name was a poor choice, but it's done now. We're not getting into the rebranding every six months game.

If it becomes a problem in future, it doesn't really matter - Friendica will do our federation for us, it doesn't matter if I'm the only person in the world who uses RedMatrix, we'll still have access to the userbase.
Fabio
6 meses atrás
Tobias
6 meses atrás de Friendly
We communicate over the Diaspora protocol. So my BBCode is converted by Friendica to Markdown, send to yor node, which converts it back to Hubzilla BBCode...
James Lamentus
6 meses atrás
maybe ...maybe.... is this https://bitbucket.org/tobiasd/friendica-typography the problem
James Lamentus
6 meses atrás
yes , i know, but this post is different compared to others I get from friendica ( from @Thomas Willingham for ex.)
Rebeka Catalina
6 meses atrás
I don't know if you use markdown from friendica


No, we use bbcode in here
James Lamentus
6 meses atrás
I don't know if you use markdown from friendica , but here in hubzilla came with Typo Error ( i think this is the name of this kind of error ?) and we can not see the img. (A round parenthesis at the end of the url)
antigo