so, we were getting spam on our prosody xmpp. it never happened before, and i wonder where the spammers get our jids from. may it be they were able to scan diaspora pages and get the jid’s from there?

still, so i tried to configure mod_firewall and it wasn’t that easy, i just blocked everything. (: then i used the block-spam.pfw script from the mod_firewall, and tried to send me a message from other server’s users that is not in my roster. did not help.

so eventually mod_block_strangers helped me, and i believe i won’t get spam anytime soon.

#jabber #diaspora #prosody #xmpp #spam #antispam #internet

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

so, we were getting spam on our prosody xmpp. it never happened before, and i wonder where the spammers get our jids from. may it be they were able to scan diaspora pages and get the jid’s from there?

still, so i tried to configure mod_firewall and it wasn’t that easy, i just blocked everything. (: then i used the block-spam.pfw script from the mod_firewall, and tried to send me a message from other server’s users that is not in my roster. did not help.

so eventually mod_block_strangers helped me, and i believe i won’t get spam anytime soon.

#jabber #diaspora #prosody #xmpp #spam #antispam #internet

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

this answer to @{Dennis Schubert; denschub@pod.geraspora.de} post seems reasonable.

it is indeed seems possible to map some subset of activitypub to the current diaspora functionality.

moreover that ruby libraries for ap already exists, there needs to be work done on integration, which is not easy, of course, but i think necessary - because otherwise diaspora stays isolated from the rest of federated world.

i think we have to try to create a social demand for this. if there is a demand, these functionality is more likely to be implemented - whether by diaspora team or by the fork.

well, the main problem is, that we have lack of developers, which is because diaspora is not that popular, and it is already a miracle that we have diaspora, and we have the existing team.

#activitypub #diaspora #activity_pub #ap #decentralization #federation #internet

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

the problem with #fediverse and #diaspora is that when you get a new instance/pod, then the new user of that instance, if they did not have other fediverse presence before, don’t see anyone, and have limited means to discover/find other people: your new instance is not aware of them.

solution often used: create a bot and follow a lot of people from different instances, so that new users have some content. but may be the user would follow someone else, than the bot followed

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

վերջապէս կը կարողանանք ունենալ տեքստ, ուր նշուած կը լինի, որ հանգոյցը փակ ա, բայց հրաւէր ստանալը՝ հնարաւոր։ #սփիւռք


Avatar @{ diaspora* HQ ; hq@pod.diaspora.software} 6/25/2019, 4:18:36 AM

diaspora* version 0.7.12.0 released!

As scheduled, a new minor release is now released. Over the past six weeks, we have managed to collect 15 commits made by 6 contributors for this minor release.

A huge thanks to all the contributors from diaspora*’s amazing community! If you want to help make diaspora* even better, please check out our getting started guide. Please see the changelog for a complete list of changes made in this release.

Notable Changes

  • Fixed a regression where enabling Two-Factor authentication did not remember logins
  • Added info message for people without an account reaching a closed pod
  • Made headline sizes more appropriate
  • Smaller fixes for some papercuts

Updating

For podmins, update instructions are available as usual in the wiki. For those of you who have been testing the release candidate, run git checkout master before the update to get back to the stable release branch.


Next minor freeze (0.7.13.0): 2019-07-28
Next release (0.7.13.0): 2019-08-04

diaspora* Rapid Release: ICS feed, HTML version.


#diaspora #announcement #release #07120


բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

since @{Fla; fla@diaspora-fr.org} told me diaspora keeps the full versions of the uploaded images, and it will be possible to get full versions via click after update, and also since #flickr changes the way it works, i may consider to again show off my photos on diaspora.

for that i think of ways to automate that, because i did not share on diaspora for years, and i’d like to have many photos in my profile.

i guess i might use this https://github.com/produnis/myscripts/blob/master/python/pic2diaspora.py and try to not flood here by posting one picture in an hour? because i have so many pictures that haven’t been uploaded to diaspora.

or may be there’s a better script. i am not an expert in python, i see the https://github.com/marekjm/diaspy/tree/master/diaspy gets deprecated, and may be i’ll end up writing something myself from scratch.

#diaspora #automation

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)

are there decentralized photo communities out there? i only know mediagoblin. diaspora is not actual since they started to reduce sizes of photographs.

what would you suggest? the ideal solution is not only the software which i can host on my server, but also a community of photographers. #photo #diaspora #mediagoblin #decentralization

բնօրինակ սփիւռքում(եւ մեկնաբանութիւննե՞ր)