Show newer
corburn boosted

@Gargron could Mastodon be more rigorous in creating RDF definitions of the arbitrary assortment of properties and types it's pioneered?

For example, for practical reasons I merged this:
github.com/go-fed/activity/pul

But it's not accurate to say "manuallyApprovesFollowers is an ActivityStreams property".

It is why we generally only support a partial vocabulary of the "Mastodon types": github.com/go-fed/activity/iss

I think i mentioned this to @nightpool before too.

corburn boosted

The go-fed/activity library (github.com/go-fed/activity), for and in , now has a v1.0.0 tagged release! Woo hoo!

The supporting website, go-fed.org/, is still a work in progress, though the tutorial should be mostly accurate.

socialhub.activitypub.rocks/t/
The ActivityPub spec cites test.activitypub.rocks as the official test suite, but it's 2021 and the blog post by the maintainer is from 2019 where it's already been down for a while. go-fed sounds like the leading reference library. Where is a good place to get started?

corburn boosted

@aw cool!!

I saw you forked apcore. Do you intend to build on top of #gofed ?

As soon you have a project, if you intend to OSS, then I'd like to add it to the #activitypub watchlist at git.feneas.org/feneas/fedivers

corburn boosted

@emersion @humanetech

I agree 馃憤 #ActivityPub is no good as a transport to synchronize data repositories (which forges are).

And...

I disagree 馃憥 ActivityPub is perfect to be notified when there is activity on a forge and #forgefed is way to express what happened.

When thinking about #forge #federation both are needed.

This is explained in more details in a 6 minutes video published last month in the context of @fedeproxy.

bittube.video/videos/watch/ff9

corburn boosted

I think it'd be nice to see a visualization of the fediverse as it is perceived from a given instance.

Something like torflow.uncharted.software/ would look pretty cool, but would fall apart with domains such as onion addresses without an IP address to presume its location.

webtorrent.io/ has an awesome real-time P2P network visualization that can be found here: github.com/feross/p2p-graph
github.com/webtorrent/webtorre

Setting up the wireless router to route traffic from port 80/443 to the istio ingress ports is one way to expose them. Still haven't figured out how to use the iptables or calicoctl option and I don't understand metallb.

I'd like to expose Istio ingressgateway on port 80 and 443. I thought I could use an iptables redirect, but it seems the Calico rules take precedence and I don't know how to interpret them. serverfault.com/questions/1049

Digging into the Calico docks to see what I can figure out. docs.projectcalico.org/getting

The trick to running ssh-agent on Microsoft WSL is to eval the output of ssh-agent -s:
eval $(ssh-agent -s); ssh-add

My tailscale app on Windows has been in a broken state for a while where the app said to restart the service. Restarting/reinstalling/upgrading the service did nothing. Running tailscaled in a terminal showed 'tailscale ui: trayClicked: state=NoState'. tailscaled --help listed this path in the arguments:
"C:\\Users\\<USER>\\AppData\\Local\\Tailscale\\server-state.conf
I deleted the files there, restarted the service, logged in, and tailscale is working again.

corburn boosted

@zacchiro i can't find the original source any more, but i think somebody made this for me

I'm struggling to understand the purpose of metallb for kubernetes. This is the best resource I've found though it's still not clicking. youtube.com/watch?v=Ytc24Y0YrX

corburn boosted
corburn boosted

enableNamespacesByDefault didn't seem to work. I presume because revision is set. How would it know which revision to use?
istioctl install --set profile=demo --set meshConfig.enableTracing=true --revision 1-10-3 --set values.sidecarInjectorWebhook.enableNamespacesByDefault=true

Show thread

The setup instructions for Istio show you how to install Istio without revisions and examples mention the istio-injection=enabled label. Hidden in the upgrade instructions is a recommendation to install with revisions and use the istio.io/rev label. The catch is there is a bug in the creation of the ValidatingWebhookConfiguration during install requiring the initial installation to not specify a revision.
istio.io/latest/docs/setup/upg
github.com/istio/istio/issues/
design document: docs.google.com/document/d/1k9

Show older
Mastodon for Tech Folks

This Mastodon instance is for people interested in technology. Discussions aren't limited to technology, because tech folks shouldn't be limited to technology either!