Searching txt.sour.is

Twts matching #1:
Sort by: Newest, Oldest, Most Relevant

**R to @mind_booster: “2045 não é bom?”

Não: tendo em conta o carbon budget de 2022, precisamos de atingir net-zero carbónico o mais tardar em 2040 para atingir mas não ultrapassar os 1.5°C.**
“2045 não é bom?”

Não: tendo em conta o carbon budget de 2022, precisamos de atingir net-zero carbónico o mais tardar em 2040 para atingir mas não ultrapassar os 1.5°C. ⌘ Read more

⤋ Read More

Isto: investir em combustíveis fósseis até 2047 é incompatível com os compromissos que temos na luta contra a crise climática. Ainda ontem Guterres alertava, o “planeta está prestes a superar o limite de 1,5 grau exigido por um futuro habitável.” O Gasoduto é irresponsabilidade.
Isto: investir em combustíveis fósseis até 2047 é incompatível com os compromissos que temos na luta contra a crise climática. Ainda ontem Guterres alertava, o “planeta está prestes a superar o limite de 1,5 grau exigido por um fut … ⌘ Read more

⤋ Read More

RT by @mind_booster: Novidades acerca do famoso #artigo17 (o dos filtros de upload)
Amanhã, na Assembleia de República (AR), é votada uma proposta de autorização legislativa em que a AR autoriza o Governo a legislar sozinho a transposição da directiva.
🧵⬇️
1/5
#copyright #Artigo17 href=”https://txt.sour.is/search?q=%23Article17
”>#Article17**
Novidades acerca do famoso #artigo17 (o dos filtros de upload)

Amanhã, na Assembleia de República (AR), é votada uma proposta de autorização legislativa em que a AR autoriza o … ⌘ Read more

⤋ Read More

R to @mind_booster: Faça-se justiça, isto é “tapado” pelo facto de quem recebe pensão social de velhice recebe também um complemento extraordinário de solidariedade (19.52 a quem tem até 70 anos), e é ainda elegível ao complemento solidário para idosos. 1/3
Faça-se justiça, isto é “tapado” pelo facto de quem recebe pensão social de velhice recebe também um complemento extraordinário de solidariedade (19.52 a quem tem até 70 anos), e é ainda elegível ao complemento solidário para idosos. 1/3 ⌘ Read more

⤋ Read More

Consciousness and Materialism

Hume’s Parallel

David Hume has often been quoted for his “Is” vs. “Ought” distinction.
The argument is that fact and morality are two different domains, and from no accumulation of statements of fact alone can we ever jump to a statement of morality.

We can say statements of fact such as:

  1. To be murdered is potentially painful.
  2. To be murdered is irreversible.
  3. Murder causes social dysfunction.
  4. Etc.

By merely my collecting these, we haven’t proven that _M … ⌘ Read more

⤋ Read More

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

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
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
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
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

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

RT by @mind_booster: Na próxima sexta (06/01), o Dia do #DomínioPúblico 2023 vai ser celebrado na Biblioteca Nacional. O evento é aberto a todos, mas se conhecerem professores, bibliotecários, e outras pessoas que trabalhem na área partilhem, porque é um tema particularmente interessante para 1/n
Na próxima sexta (06/01), o Dia do #DomínioPúblico 2023 vai ser celebrado na Biblioteca Nacional. O evento é aberto a todos, mas se conhecerem professores, bibliotec … ⌘ Read more

⤋ Read More

**RT by @mind_booster: Remember:

  1. We’re at 1.25/1.75°C of global warming and rising fast.

  2. Fossil fuel emissions should have peaked in 2022 to avoid 2.5°C, but they didn’t.

  3. Forest degradation is getting worse.

  4. Capitalism has put world-ending 2.25/2.75°C by 2045- 2090 in the pipelines. 🧵**
    Remember:

1. We’re at 1.25/1.75°C of global warming and rising fast.

2. Fossil fuel emissions should have peaked in 2022 to avoid 2.5°C, but they didn’t.

3. Forest degradation is getting worse.

4. Capitalis … ⌘ Read more

⤋ Read More

**RT by @mind_booster: 1/ 🧵What if ‘living with Covid’ literally means living with it inside you for a long time? 🦠🤔

This year has produced several studies around viral persistence that really have not had enough airtime.
These could have far reaching consequences
I will summarise..**
1/ 🧵What if ‘living with Covid’ literally means living with it inside you for a long time? 🦠🤔

This year has produced several studies around viral persistence that really have not had enough airtime.

These could have far reac … ⌘ Read more

⤋ Read More

**RT by @mind_booster: 1.

‘equilibrium climate sensitivity is at least ~4°C with a likely range of 3.5-5.5°C.

global warming in the pipeline is greater than prior estimates.’

James Hansen and colleagues release new work for discussion.

This should be front page news.

https://arxiv.org/abs/2212.04474**
1.

‘equilibrium climate sensitivity is at least ~4°C with a likely range of 3.5-5.5°C.

global warming in the pipeline is greater than prior estimates.’

James Hansen and colleagues release new work for discus … ⌘ Read more

⤋ Read More

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
In-reply-to » I made a thing. Its a multi password type checker. Using the PHC string format we can identify a password hashing format from the prefix $name$ and then dispatch the hashing or checking to its specific format.

Here is an example of usage:

func Example() {
	pass := "my_pass"
	hash := "my_pass"

	pwd := passwd.New(
		&unix.MD5{}, // first is preferred type.
		&plainPasswd{},
	)

	_, err := pwd.Passwd(pass, hash)
	if err != nil {
		fmt.Println("fail: ", err)
	}

	// Check if we want to update.
	if !pwd.IsPreferred(hash) {
		newHash, err := pwd.Passwd(pass, "")
		if err != nil {
			fmt.Println("fail: ", err)
		}

		fmt.Println("new hash:", newHash)
	}

	// Output:
	//  new hash: $1$81ed91e1131a3a5a50d8a68e8ef85fa0
}

This shows how one would set a preferred hashing type and if the current version of ones password is not the preferred type updates it to enhance the security of the hashed password when someone logs in.

https://github.com/sour-is/go-passwd/blob/main/passwd_test.go#L33-L59

⤋ Read More
In-reply-to » I made a thing. Its a multi password type checker. Using the PHC string format we can identify a password hashing format from the prefix $name$ and then dispatch the hashing or checking to its specific format.

Here is an example of usage:

func Example() {
	pass := "my_pass"
	hash := "my_pass"

	pwd := passwd.New(
		&unix.MD5{}, // first is preferred type.
		&plainPasswd{},
	)

	_, err := pwd.Passwd(pass, hash)
	if err != nil {
		fmt.Println("fail: ", err)
	}

	// Check if we want to update.
	if !pwd.IsPreferred(hash) {
		newHash, err := pwd.Passwd(pass, "")
		if err != nil {
			fmt.Println("fail: ", err)
		}

		fmt.Println("new hash:", newHash)
	}

	// Output:
	//  new hash: $1$81ed91e1131a3a5a50d8a68e8ef85fa0
}

This shows how one would set a preferred hashing type and if the current version of ones password is not the preferred type updates it to enhance the security of the hashed password when someone logs in.

https://github.com/sour-is/go-passwd/blob/main/passwd_test.go#L33-L59

⤋ Read More