Searching txt.sour.is

Twts matching #0
Sort by: Newest, Oldest, Most Relevant
marcos-marado-atmind_booster
feeds.twtxt.net
 (3y ago)

**Sondagem (e comparação com os resultados nas últimas eleições):

PS 32 (-9.4), PSD 31 (+3.3), CH 11 (+3.8), IL 8 (+3.1), BE 7 (+2.6), CDU (-0.3), PAN 2 (+0.4), L 2 (+0.7), CDS 1 (-0.6)**
Sondagem (e comparação com os resultados nas últimas eleições):

PS 32 (-9.4), PSD 31 (+3.3), CH 11 (+3.8), IL 8 (+3.1), BE 7 (+2.6), CDU (-0.3), PAN 2 (+0.4), L 2 (+0.7), CDS 1 (-0.6)

nitter.net/RuidoCorvo/status/1628501716843876356#m ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Prosodical Thoughts: Prosody 0.12.3 released
We are pleased to announce a new minor release from our stable branch.

This is a bugfix release for our stable 0.12 series. Most notably, it fixes a
regression for SQL users introduced in 0.12.2, and a separate long-standing
compatibility issue with archive stores on certain MySQL/MariaDB versions.

It also fixes an issue with websockets discovered by the Jitsi team, some
issues with our internal HTTP client API, and we’ve improved the accuracy of
‘prosodyctl check dns’ in … ⌘ Read more

⤋ Read More
marcos-marado-atmind_booster
feeds.twtxt.net
 (3y ago)

**RT by @mind_booster: It’s ❤ Free Software day and KDE’s brand new Plasma 5.27 desktop is out! Get the new tiling system and cherish the tidiness; or the improved Discover and adore all the apps; or the multi-screen system and don’t miss a thing.

More ❤ here:

https://kde.org/announcements/plasma/5/5.27.0/

#ilovefs**
It’s ❤ Free Software day and KDE’s brand new Plasma 5.27 desktop is out! Get the new tiling system and cherish the tidiness; or the improved Discover and adore all the apps; or the multi-screen … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Isode: Cobalt 1.3 Release Features
Cobalt 1.3 depends on M-Vault 19.0 or subsequent versions

M-Vault Management Supporties
  • M-Vault Bootstrap.   Enables operation in conjunction with M-Vault 19.0 to support headless bootstrap.
  • Managing users in M-Vault groups, such as Directory Server Administrators  and Messaging Configuration Read/Write.  This enables Cobalt to control user and operator rights to access M-Vault.
  • AD/LDAP passthrough support
    • Allow users (per domain) to support mand … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Dino: Dino 0.4 Release
Dino is a secure and open-source messaging application.
It uses the XMPP (Jabber) protocol for decentralized communication.
We aim to provide an intuitive and enjoyable user interface.

The 0.4 release adds support for message reactions and replies. We also switched from GTK3 to GTK4 and make use of libadwaita now.

Reactions and Replies

Image

Reactions give you a quick and light-weight way to respond to a message with an emoji.
They … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Gajim: Gajim 1.7.0
Gajim 1.7.0 is mostly a bug fixing release. Due to fundamental changes in the build system, we decided to jump from 1.6.x to 1.7 directly. Thank you for all your contributions!

What’s New

Gajim’s build system had significant changes, which makes it necessary for package maintainers to change some things, as documented in the readme file.

More Changes
  • Account creation: Don’t allow to add account twice
  • File previews: Y … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Isode: Icon-5066 3.0 – New Capabilities
We are thrilled to announce the latest update to our STANAG 5066 server, Icon-5066. With this new release, we’ve incorporated a host of exciting features and enhancements, designed to not only add new functionality to your deployment but also increase the performance of your HF Radio Network.

The below is a list of the changes, and updates that can be found within Icon-5066 v3.0.

ALE Management

This major new feature enables management of ALE conf … ⌘ Read more

⤋ Read More
marcos-marado-atmind_booster
feeds.twtxt.net
 (3y ago)

**Sondagem (comparação com os últimos resultados):

PSD 30.6 (+2.9), PS 26.9 (-14.5), CH 14.3 (+7.1), IL 8 (+3.1), BE 5.6 (+1.2), CDU 2.2 (-2.1), L 1.9 (+0.6), PAN 0.9 (-0.7)**
Sondagem (comparação com os últimos resultados):

PSD 30.6 (+2.9), PS 26.9 (-14.5), CH 14.3 (+7.1), IL 8 (+3.1), BE 5.6 (+1.2), CDU 2.2 (-2.1), L 1.9 (+0.6), PAN 0.9 (-0.7)

nitter.net/Eva1Helena/status/1618341289552154624#m ⌘ Read more

⤋ Read More
marcos-marado-atmind_booster
feeds.twtxt.net
 (3y ago)

Sondagem Intercampus (e comparação com as últimas eleições): PS 31.1 (-10.3), PSD 29.5 (+1.8), CH 10.7 (+3.1), IL 7.6 (+2.7), BE 7.5 (+3.1), CDU 3.7 (-0.6), PAN 3.7 (+2.1), L 2.4 (+1.1), CDS 0.7 (-0.9)
Sondagem Intercampus (e comparação com as últimas eleições): PS 31.1 (-10.3), PSD 29.5 (+1.8), CH 10.7 (+3.1), IL 7.6 (+2.7), BE 7.5 (+3.1), CDU 3.7 (-0.6), PAN 3.7 (+2.1), L 2.4 (+1.1), CDS 0.7 (-0.9)

[nitter.net/JosMatias17/status/1614565255312736257#m](https://nitter.net/JosMatias17/status/161456525531273 … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Gajim: Gajim 1.6.1
Gajim 1.6.1 is mostly a bug fixing release, but it also brings some important improvements and adds more convenience. Thank you for all your contributions!

What’s New

After we ported Gajim and python-nbxmpp to libsoup3, you might have noticed issues with file transfers. Now, python-nbxmpp 4.0.1 has been released, and it fixes an error which prevented transfers of files containing spaces in their file name.

Gajim s … ⌘ Read more

⤋ Read More
abucci
anthony.buc.ci
 (3y ago)
↳ In-reply-to » Trying to wrap my head around webfinger..

@xuu@txt.sour.is that doesn’t seem to fit the spirit of the spec, at least by my read (I could be wrong obv). The example on Wikipedia’s webfinger page,

{
	"subject": "acct:bob@example.com",
	"aliases": [
		"https://www.example.com/~bob/"
	],
	"properties": {
		"http://example.com/ns/role": "employee"
	},
	"links": [{
			"rel": "http://webfinger.example/rel/profile-page",
			"href": "https://www.example.com/~bob/"
		},
		{
			"rel": "http://webfinger.example/rel/businesscard",
			"href": "https://www.example.com/~bob/bob.vcf"
		}
	]
}

and then the comparison with how mastodon uses webfinger,

{
    "subject": "acct:Mastodon@mastodon.social",
    "aliases": [
        "https://mastodon.social/@Mastodon",
        "https://mastodon.social/users/Mastodon"
    ],
    "links": [
        {
            "rel": "http://webfinger.net/rel/profile-page",
            "type": "text/html",
            "href": "https://mastodon.social/@Mastodon"
        },
        {
            "rel": "self",
            "type": "application/activity+json",
            "href": "https://mastodon.social/users/Mastodon"
        },
        {
            "rel": "http://ostatus.org/schema/1.0/subscribe",
            "template": "https://mastodon.social/authorize_interaction?uri={uri}"
        }
    ]
}

suggests to me you want to leave the subject/acct bit as is (don’t add prefixes) and put extra information you care to include in the links section, where you’re free to define the rel URIs however you see fit. The notion here is that webfinger is offering a mapping from an account name to additional information about that account, so if anything you’d use a "subject": "acct:SALTY ACCOUNT_REPRESENTATION" line in the JSON to achieve what you’re saying if you don’t want to do that via links.

⤋ Read More
xuu
txt.sour.is
 (3y ago)
↳ In-reply-to » Trying to wrap my head around webfinger..

@prologic@twtxt.net That was exactly my thought at first too. but what do we put as the rel for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta:

# http GET https://example.okta.com/.well-known/webfinger  resource==acct:bob
{
    "links": [
        {
            "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#",
            "properties": {
                "okta:idp:type": "OKTA"
            },
            "rel": "http://openid.net/specs/connect/1.0/issuer",
            "titles": {
                "und": "example"
            }
        }
    ],
    "subject": "acct:bob"
}

It gives one link that follows the OpenID login. So the details are specific to the subject acct:bob.

Mastodons response:

{
  "subject": "acct:xuu@chaos.social",
  "aliases": [
    "https://chaos.social/@xuu",
    "https://chaos.social/users/xuu"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://chaos.social/@xuu"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://chaos.social/users/xuu"
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe"
    }
  ]
}

it supplies a profile page and a self which are both specific to that account.

⤋ Read More
xuu
dev.txt.sour.is
 (3y ago)
↳ In-reply-to » Trying to wrap my head around webfinger..

@prologic@twtxt.net That was exactly my thought at first too. but what do we put as the rel for salty account? since it is decentralized we dont have a set URL for machines to key off. so for example take the standard response from okta:

# http GET https://example.okta.com/.well-known/webfinger  resource==acct:bob
{
    "links": [
        {
            "href": "https://example.okta.com/sso/idps/OKTA?login_hint=bob#",
            "properties": {
                "okta:idp:type": "OKTA"
            },
            "rel": "http://openid.net/specs/connect/1.0/issuer",
            "titles": {
                "und": "example"
            }
        }
    ],
    "subject": "acct:bob"
}

It gives one link that follows the OpenID login. So the details are specific to the subject acct:bob.

Mastodons response:

{
  "subject": "acct:xuu@chaos.social",
  "aliases": [
    "https://chaos.social/@xuu",
    "https://chaos.social/users/xuu"
  ],
  "links": [
    {
      "rel": "http://webfinger.net/rel/profile-page",
      "type": "text/html",
      "href": "https://chaos.social/@xuu"
    },
    {
      "rel": "self",
      "type": "application/activity+json",
      "href": "https://chaos.social/users/xuu"
    },
    {
      "rel": "http://ostatus.org/schema/1.0/subscribe"
    }
  ]
}

it supplies a profile page and a self which are both specific to that account.

⤋ Read More
prologic
twtxt.net
 (3y ago)

Anyone know what this might be about?

[1134036.271114] ata1.00: exception Emask 0x0 SAct 0x4 SErr 0x880000 action 0x6 frozen
[1134036.271478] ata1: SError: { 10B8B LinkSeq }
[1134036.271829] ata1.00: failed command: WRITE FPDMA QUEUED
[1134036.272182] ata1.00: cmd 61/20:10:e0:75:6e/00:00:11:00:00/40 tag 2 ncq 16384 out
                          res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
[1134036.272895] ata1.00: status: { DRDY }
[1134036.273245] ata1: hard resetting link
[1134037.447033] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[1134038.747174] ata1.00: configured for UDMA/133
[1134038.747179] ata1.00: device reported invalid CHS sector 0
[1134038.747185] ata1: EH complete

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Gajim: Gajim 1.6.0
For Gajim 1.6.0 we ported Gajim’s and python-nbxmpp’s underlying HTTP library to libsoup3. Also, audio previews now look nicer and allow for more control (playback speed, jumping). We fixed emoji rendering on MacOS and we implemented many fixes under the hood. Thank you for all your contributions!

What’s New

For all HTTP requests (e.g. file downloads, update checks, websocket connection, …) both Gajim and python-nbxmpp rely on libsoup. With Gajim 1.6.0, we ported to libsoup3. You shou … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Erlang Solutions: GraphQL interfaces in MongooseIM 6.0
MongooseIM is a robust, scalable and highly extensible instant messaging server. Recent releases have improved its configurability and opened new use cases, and the latest version 6.0 continues that trend. By introducing the brand new GraphQL API, we made MongooseIM much easier to integrate with external web services. The entry barrier is also lower than ever because of the automatically generated API documentation, interactive web UI, an … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Prosodical Thoughts: Prosody 0.12.2 released
We are pleased to announce a new minor release from our stable branch.

This is a regularly delayed release containing a number of fixes for
issues that we have come across since the last release of the 0.12
series.

A summary of changes in this release:

Fixes and improvements
  • util.stanza: Allow U+7F when constructing stazas
  • net.unbound: Preserve built-in defaults and Prosodys settings for luaunbound (fixes#1763: luaunbound not read … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: Spark 3.0.1 Released
The Ignite Realtime community is happy to announce the release of Spark 3.0.1 version.

This release contains mostly fixes. macOS now uses the default FlatLaf LaF. The user can also choose the type of tabs “scroll” as in Spark 3.0.0 or “wrap” as in Spark 2.X. See screenshot below. And also for some users, Spark not saved history.

Image


… ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: HTTP File Upload plugin 1.2.0 released
We have now released version 1.2.0 of the HTTP File Upload plugin!

This plugin adds functionality to Openfire that allows clients to share files, as defined in the XEP-0363 ‘HTTP File Upload’ specification.

This release primarily enhances functionality when running in an Openfire cluster. All changes can be reviewed in [the changelog for this release](https://www.igniterealtime. … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: Openfire Monitoring Service plugin 2.4.0 release
Earlier today, we have released version 2.4.0 of the Openfire Monitoring Service plugin. This plugin adds both statistics, as well as message archiving functionality to Openfire.

In this release, compatibility with future versions of Openfire is added. A bug that affects MSSQL users has been fixed, and the dreaded “Unable to save XML properties” error message has been resolved. A few other minor tweaks h … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: Spark 3.0.0 Released
The Ignite Realtime community is happy to announce the release of Spark 3.0.0 version.

We decided to increase major version to 3.x to coincide with a complete UI refresh of Spark which was contributed by Amos. Now Spark uses only FlatLaf Look and Feel. We are very much grateful for his incredible work. Along that Pade Meetings plugin was added by [Dele](https://discourse.igniterealtime. … ⌘ Read more

⤋ Read More
lyse
lyse.isobeef.org
 (3y ago)
↳ In-reply-to » Atom vs. RSS: https://mckinley.cc/blog/20221109.html

@mckinley@twtxt.net Thank you! I didn’t even know about signing and encrypting XML documents. Right, RSS is a little bit messy.

Unfortunately, the autodiscovery document in one of your linked resources does not exist anymore. What annoys me in Atom is the distinction between <id> and <link>. I always want my URL also to be my ID, so I have to duplicate that – unnecessarily in my opinion.

Also, never found a good explanation why I should add <link rel="self" … /> to my feeds. I just do, but I don’t understand why. The W3C Feed Validation Service says:

[…] This value is important in a number of subscription scenarios where often times the feed aggregator only has access to the content of the feed and not the location from which the feed was fetched.

This just sounds like a very questionable bandaid to bad software architecture. Why would the feed parser need access to the feed URL at this stage? And if so, why not just pass down the input source? Just doesn’t make sense to me.

Also, I just noticed that I reference the http://purl.org/rss/1.0/modules/syndication/ namespace, but don’t use it in most of my feeds. Gotta fix that. Must have copied that from my yfav feed without paying attention what I’m doing.

Your article made me reread the Atom spec and I found out, that I can omit the <author> in the <entry> when I specify a global <author> at <feed> level. Awesome! Will do that as well and thus reduce the feed size.

⤋ Read More
docker_blog
feeds.twtxt.net
 (3y ago)

Security Advisory: Critical OpenSSL Vulnerability
The OpenSSL Project will imminently release a security fix (OpenSSL version 3.0.7) for a new-and-disclosed CVE. In the meantime, learn how Docker tooling helps you uncover and remediate image vulnerabilities. ⌘ Read more

⤋ Read More
docker_blog
feeds.twtxt.net
 (3y ago)

Resolve Vulnerabilities Sooner With Contextual Data
OpenSSL 3.0.7 and “Text4Shell” might be the most recent critical vulnerabilities to plague your development team, but they won’t be the last. In 2021, critical vulnerabilities reached a record high. Attackers are even reusing their work, with over 50% of zero-day attacks this year being variants of previously-patched vulnerabilities.  With each new security vulnerability, we’re […] ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: REST API Openfire plugin 1.10.0 released!
We are happy to announce the immediate availability of version 1.10.0 of the REST API plugin for Openfire!

This release will see the performance on lookups of MUC rooms based on case-insensitive room names, or non-existing rooms. This will be particularly notable in systems that hold many chat rooms.

Another feature that is added is that basic statistics on REST endpoint usage are now exposed. These can be viewed thro … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: New Openfire plugin: Push Server!
The Ignite Realtime Community is pleased to announce the 1.0.0 release of the Push Server plugin for Openfire. This plugin is developed by the company Busoft Teknoloji A.Ş. It is inspired by Conversations Push Proxy and developed for Openfire.

Your instance of Openfire should automatically display the availability of the new plugin in the next few hours. Alternatively, you … ⌘ Read more

⤋ Read More
docker_blog
feeds.twtxt.net
 (3y ago)

Clarifying Misconceptions About Web3 and Its Relevance With Docker
This blog is the first in a two-part series. We’ll talk about the challenges of defining Web3 plus some interesting connections between Web3 and Docker. Part two will highlight technical solutions and demonstrate how to use Docker and Web3 together. We’ll build upon the presentation, “Docker and Web 3.0 — Using Docker to Utilize Decentralized […] ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Ignite Realtime Blog: Openfire ThreadDump plugin 1.1.0 released
Earlier today, we have released version 1.1.0 of the Openfire Thread Dump plugin. This plugin uses various evaluators to trigger the creation of a Java thread dump. These thread dumps provide valuable information that is typically used when analyzing issues within Openfire’s implementation.

In the new version of the plugin, two new evaluators have been added: one that looks at the usage pattern of Openfire’s TaskEngin … ⌘ Read more

⤋ Read More
Planet_Jabber_XMPP
feeds.twtxt.net
 (3y ago)

Kaidan: Kaidan’s End-to-End Encryption Trust Management
We worked several months on Kaidan’s upcoming end-to-end encryption and trust management.
Once Kaidan 0.9 is released, it will provide the latest OMEMO Encryption.
But it will also make trust decisions in the background for you if it’s possible.
Some trust decisions have to be made manually but there are many others Kaidan automates without decreasing your security.
That is done by automatically sharing … ⌘ Read more

⤋ Read More
xuu
txt.sour.is
 (3y ago)
↳ In-reply-to » @prologic I think we could use deltachats new decentralising app format for it: https://delta.chat/en/2022-06-14-webxdcintro

Huh… Nope.

HTTP/1.1 200 OK
Content-Length: 407
Content-Type: text/calendar
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: ETag
Permissions-Policy: interest-cohort=()
Content-Security-Policy: default-src 'none'; sandbox
Referrer-Policy: same-origin
Vary: Authorization


BEGIN:VCALENDAR
VERSION:2.0;2.0
PRODID:SandCal
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTAMP:20220822T180903Z
UID:bb63bfbd-623e-4805-b11b-3181d96375e6
DTSTART;TZID=America/Chicago:20220827T000000
CREATED:20220822T180903Z
LAST-MODIFIED:20220822T180903Z
LOCATION:https://meet.jit.si/Yarn.social
SUMMARY:Yarn Call
RRULE:FREQ=WEEKLY
DTEND;TZID=America/Chicago:20220827T010000
END:VEVENT
END:VCALENDAR

⤋ Read More
xuu
dev.txt.sour.is
 (3y ago)
↳ In-reply-to » @prologic I think we could use deltachats new decentralising app format for it: https://delta.chat/en/2022-06-14-webxdcintro

Huh… Nope.

HTTP/1.1 200 OK
Content-Length: 407
Content-Type: text/calendar
Access-Control-Allow-Origin: *
Access-Control-Expose-Headers: ETag
Permissions-Policy: interest-cohort=()
Content-Security-Policy: default-src 'none'; sandbox
Referrer-Policy: same-origin
Vary: Authorization


BEGIN:VCALENDAR
VERSION:2.0;2.0
PRODID:SandCal
CALSCALE:GREGORIAN
BEGIN:VEVENT
DTSTAMP:20220822T180903Z
UID:bb63bfbd-623e-4805-b11b-3181d96375e6
DTSTART;TZID=America/Chicago:20220827T000000
CREATED:20220822T180903Z
LAST-MODIFIED:20220822T180903Z
LOCATION:https://meet.jit.si/Yarn.social
SUMMARY:Yarn Call
RRULE:FREQ=WEEKLY
DTEND;TZID=America/Chicago:20220827T010000
END:VEVENT
END:VCALENDAR

⤋ Read More