Notices by @reiver ⊼ (Charles) :batman: (reiver@mastodon.social)

What is the motivation for encouraging LitePub implementors to "supply a locally hosted version of the LitePub JSON-LD Context"?

Is it just for people using full-out JSON-LD parsers?

Won't this create problems for people using parsers that do NOT go download and interpret context-URIs? And instead just hard-code the vocabulary in their code?

#ActivityPub #ActivityStreams #DeSo #FediDevs #Fediverse #JSONLD #LitePub

Pixelfed has a Mascot.

How did I not know this.

Pixelfed's mascot is a Red Panda.

(source: https://github.com/pixelfed/brand-assets )

#DeSo #Fediverse #Pixelfed #RedPanda

📚 Mastodon History

Back in February 23rd, 2016 — Mastodon first described itself as:

“Mastodon is a federated microblogging engine. An alternative implementation of the GNU Social project.”

The history of Mastodon is tied to GNU Social.

https://github.com/mastodon/mastodon/blob/fa33750105389110a3395ca19167f789d21a149e/README.md

https://github.com/mastodon/mastodon/tree/fa33750105389110a3395ca19167f789d21a149e

#DeSo #Fediverse #FediverseHIstory #GNUSocial #Mastodon #MastodonHistory

3/

Issue №1:

host-meta is yet another format to write encoders and decoders for.

(host-meta is used to specify where WebFinger is. It does not necessarily have to be at "/.well-known/webfinger". And doesn't have to be on the same host.)

...

#ActivityPub #FediDevs #Fediverse #WebFinger

2/

Their reason (for wanting to replace WebFinger):

“While useful, Webfinger is not part of the ActivityPub specification”

Why does that matter?

Having said that, (I do think) there some issues with WebFinger that could motivate one to replace it.

But that would mean that — any replacement MUST address these issues.

...

#ActivityPub #FediDevs #Fediverse #WebFinger

1/

It seems like someone wants everyone on the Fedivese to stop using WebFinger.

https://github.com/mastodon/mastodon/issues/17030

(WebFinger is used to resolve a Fediverse ID like "＠joeblow＠example·com" to an activity document ("application/activity+json").)

...

#ActivityPub #FediDevs #Fediverse #WebFinger

6/

Issue №4:

Having to make one HTTP to WebFinger to resolve a Fediverse ID (such as "＠joeblow＠example·com"), and then make another HTTP request to get the activity document ("application/activity+json") — adds an extra HTTP request.

Using a well-known path to resolve the Fediverse ID and get the activity document ("application/activity+json") — in one HTTP request would be better.

...

#ActivityPub #FediDevs #Fediverse #WebFinger

5/

Issue №3:

If we are going to use Internet domain-names, maybe host-meta could be replaced by a DNS TXT or DNS SRV record — that is used to specify what host to connect to to resolved a Fediverse ID like "＠joeblow＠example·com" to an activity document ("application/activity+json").

...

#ActivityPub #FediDevs #Fediverse #WebFinger

4/

Issue №2:

host-meta is in XML (where everything else is in JSON).

I am NOT saying I am a fan of JSON, but — I think it would be easier for developers if only JSON xor XML was used (but not both).

(host-meta is used to specify where WebFinger is. It does not necessarily have to be at "/.well-known/webfinger". And doesn't have to be on the same host.)

...

#ActivityPub #FediDevs #Fediverse #WebFinger

@julian

Regarding:
“(a) My impression from some semi-recent discussions here and on the Mastodon Discord is that there's much more momentum for abolishing host-meta support than for abolishing WebFinger.”

One (I think) useful thing that people use host-meta for is — to specify that WebFinger is on another host.

If host-meta is abolished, do you know if they have a plan to replace that functionality using some other mechanism?

(Maybe a DNS TXT or DNS SRV record?)

@nixCraft

package main

import (
"fmt"
)

func main() {
fmt.Println("Hello World")
}

@nixCraft

Turbo Pascal was the 3rd programming language I learned.

@pixelfed @dansup

Did Pixelfed post-scheduling make it into the v0.11.2 (and later) release of Pixelfed?

Or was the feature deferred to a later future release?

(A friend of mine, who recently started using Pixelfed, was asking about it. And I cannot seem to find it.)

A friend sent this.

He added the comment:

“And they call it "Bard policy" and not "privacy policy" anymore.”

Google renamed the Google Bard "Privacy Policy" to "Bard Policy". Assumingly because it violates the user's privacy.

#Google #GoogleBard #Privacy

@itsfoss

I started using Linux in 1996.

I was using Solaris & IRIX before that.

The #HTTP protocol's "101 Switching Protocols" response is severely underused.

(And no, this is not a comment about WebSockets.)

3/

"Yes", there is WebDAV — but WebDAV is no more HTTP than AtomPub is.

And also, WebDAV does a mediocre job of trying to shoehorn directories into HTTP.

2/

For example, there is no HTTP method to list the contents of a directory.

Also, there is no HTTP method to pull all the contents of a directory (as a single operation).

There are no recursive HTTP methods for directories.

Etc.

1/

The #WorldWideWeb dominated #Internet would have been a different place if #HTTP had support for directories.

Because except for an atavism on how relative URIs resolve against a base URI —

HTTP does not support directories.

"Jim Clarke and Marc Andreessen approached me [John Ousterhout, the creator of the Tcl programming language] about the possibility of my joining Netscape as a founder, but I eventually decided against it (they hadn't yet decided to do Web stuff when I talked with them). […] If I had gone to Netscape, I think there's a good chance that Tcl would have become the browser language instead of JavaScript"

https://pldb.com/posts/JohnOusterhout.html

#tcl #javascript #programming #netscape #worldWideWeb