Notices tagged with gnusocial, page 46
-
#vinilox will stop the 1.1.2017 and !gnusocial group is hosted at vinilox. anybody has a plan to move it ? https://status.vinilox.eu/group/gnusocial
-
@xj9 @hobbsc nope. pump.io is simply crap and had never been on the 'market' at all. !gnusocial is actively developed.
-
New note by d0e
-
@bobjonkman also the Vinilox-hosted groups must be renamed before Vinilox goes down, to avoid name conflicts. Unless this is no longer an issue due to !GNUsocial code fixes.
There was a time when remote users just couldn't join groups on quitter.se b/c of the defunct identica group with the same name.
-
!GNUsocial is another significant group on https://status.vinilox.eu/groups but it's probably best hosted by @mmn@social.umeahackerspace.se
-
Try !GNUSocial
https://gnu.io/social/try/
No matter which server you're on, you're part of the family!
-
Miles de españoles cambian Twitter por !GNUsocial — Free Software Foundation — working together for free software
https://quitter.no/url/791767
-
"The Secret Lives of Tumblr Teens. A fascinating look at the rise and fall of teen empires on Tumblr, the blogging platform and social network favored by young people who view themselves as outcasts."
https://newrepublic.com/article/129002/secret-lives-tumblr-teens?src=longreads
!goodreads !gnusocial
-
!gnusocial you're going to love this
https://www.reddit.com/r/unixporn/comments/5crgng/gnome_when_people_ask_why_i_use_gnulinux/#link
#GNOME #DIY
-
Sometimes I realise that what we are all doing with !gnusocial is so very important and cutting edge, fighting against the oncoming data dystopia.
-
@deavmi I meant maybe the plugin is unstable but yeah, that can be looked up easily. Unfortunate that many !gnusocial instances has not enabled it, kind of a lock-in for users who are in similar situation as I am in right now. :)
-
@6gain We do have "Messages by someuser@somehost" menu item in the context menu. So you can see messages, posted and reposted by a User that you found in any other timeline. This works even for users, mentioned in a message: select "Users of message" menu item, see a list of users, and then select "Messages by ..." in the context menu of that User. Unfortunately, due to current…
-
New note by archaeme
-
@andstatus the URI (as in the context of Atom post id, which !GNUsocial uses as a transport format) cannot be assumed to have a discernible structure. It can be any character combination, or at least only as restricted as in the Atom standard. The URI is available in the post's raw atom formatted representation. It is probably still not available in the Twitter compati…
-
http://status.hackerposse.com/url/13390 - renewed certificate Hello, I've renewed the SSL certificate of my server. Here are the details of the new one... Subject *.libranet.de Fingerprint SHA1: 373cb6dc7372427bfb3fc1dc7f5740c282deb658 Common names *.libranet.de Alternative names *.libranet.de http://status.hackerposse.com/url/13391 Valid from Fri, 16 Dec 2016 22:02:11 UTC Valid u…
-
@maiyannah 1. As we are thinking about good interoperability with !gnusocial instances that have old API only, I think we better add "local I'd part" not only to the newly formed "message/notice id", but to other IDs also. So a User UID will be: http://status.hackerposse.com/url/13370 i.e. it will include local user I'd as the third part of the UID 2. Regarding message/notice …
-
Submitted my first merge request to !GnuSocial https://git.gnu.io/gnu/gnu-social/merge_requests/133 :)
-
@oplch You can archive the #Atom feed. It has all the data in the feed to be programmatically browsable. I wrote an atom-ripper sometime. Importing it is probably not well-supported in !GNUsocial yet but keep the feed as a backup.
-
@indi I don't think redirects will work. First, the http scheme is used in URLs in the data being sent, and a redirect won't change the content of the data, only the URLs used to send/receive that data. Second, all the federated instances know my instance as http and so won't use https; third, my own instance believes it's http and won't accept or send https, so I don't think redi…
-
@maiyannah 1. I agree, adding new field into each "object" of the JSON message with UID in addition to each existing ID will be a good compromise preserving compatibility with old clients. 2. Regarding choice of the UID format/structure I strongly support a UID, which allows to identify easily the GNU Social instance that generated the UID. This way clients will be able to requ…