Show Navigation
Notices by mike (mike@loadaverage.org), page 2
-
I don't know if the situation changed in the more recent releases, but in version 11, what was provided was ActivityStreams but *not* ActivityPub; though that is what was described in the official documentation. Somebody let the marketing department generate press without letting the technical folks proof-read it for accuracy. I looked at it early on to make sure I could federate it with Hubzilla and found that it was simply *not* ActivityPub and could not be coerced to federate with that protocol.
-
No worries.
If you don't care about centralisation, there are a number of potential solutions to your needs, with a lighter footprint. I can't suggest anything specific as I haven't seriously looked at centralised tools in years.
Hubzilla is a bit heavyweight because it deals with some really hard decentralisation problems such as cross-domain authentication and social media privacy as well as federated communications with a number of decentralised protocols and projects.
It does provide the features you asked for, (and many more) but ultimately you need to find whatever works for you.
Cheers.
-
We use Hubzilla for these kinds of things.
I understand zatnosk doesn't agree but I'm not certain what the reasons are, or what the project could do differently to appeal to his/her particular use case or requirements. It's a pretty flexible platform, so if it doesn't solve some particular use case today, it's extensible and adaptable; which is often better than starting from scratch.
-
Ya' got me. I'm drawing a blank.
-
Was amused by an AP co-chair suggesting earlier that Facebook and Twitter will never endorse AP because they want to keep their walled gardens.
AP is in fact federates with nothing but itself (the classic definition of a walled garden), and Facebook or Twitter could take it over completely and subsume it - lock, stock and barrel the same way Mastodon did. If either sees AP or the federated web as a viable threat that's exactly what will happen. If you think it can't happen, look at USENET (ehr I mean Google Groups).
-
There's a blank line before the xml declaration, which is throwing fits for every feed reader and validator I throw at it. WordPress has an atom plugin and I always used that instead of RSS. That may not fix the original problem but it will probably work around it.
-
Once upon a time we called them 'plugs' and 'sockets'.
-
hubzilla has federated public and private groups. They are called forums in that software. You can post via tags or post wall-to-wall from other sites across the network (assuming you're a member). They are searchable in the directory.
Rival facebook? So you want groups that spy on and sell shit to you?
-
Probably depends on whether or not the wanker is any good.
-
http://www.undergroundtour.com
-
Dude, you've got more cool in your little finger right now than most people will be able to collect in a lifetime.
-
Hubzilla and Friendica both have federated forums and GNU-Social has a marginal implementation.
There are a few issues with some networks seeing comments from members of other protocols which their projects don't personally implement. So I can provide a forum on Hubzilla that can be used by Mastodon folks and/or a forum that can be used by Diaspora folks and all is hunky-dory (and Hubzilla can see conversations by everybody involved), but providing a forum that can be used by both of these other projects simultaneously would require each of them to understand each other's protocols.
Otherwise their network won't see comments and likes from the other network.
It's possible to work around this, but it's a huge development effort and it wouldn't be necessary if other projects and protocols were actually open to cross protocol federation; but mostly because I'm working on more important things at the moment.
-
As noted in a followup I thought you were referring to my protocol alliance snapshot from last year (only); but it seems you were mostly referring to a different wiki webpage which I personally had nothing to do with and take no responsibility for. Again my apologies for not understanding the original issues, as this thread was slightly fragmented.
-
My bad. I thought you were referring to my protocol alliance map - I just looked at the sobac.com page and I agree it does seem to have a number of factual errors. My apologies for responding defensively before tracking down the rest of this thread from other sites.
-
> there is a lot misleading information on that page. And I only took a quick look on that page.
Your comment indicates you don't really understand what that chart represents.
The referenced chart was a snapshot of the protocol "alliances" of the metaverse in mid 2017. the metaverse is a superset of the fediverse and federation and the ActivityPub community and a number of other protocol alliances. It was also obsolete before the ink dried, but that is the nature of the beast. The world changes. We deal with it.
Yes, I know what protocol Friendica uses. I wrote it. Yes, I know what protocol Diaspora uses. I've implemented the Diaspora protocol 9 times now for 5 different projects and helped define some critical pieces of the second iteration (which was used from 2011 to 2016).
-
Yeah, that sounds like a perfect match for what I experienced. Thanks. We've got two feeds - a legal one and an OStatus one with fixes for a lot of quirks and bad behaviour by GS and mastodon. Some older GS sites are stuck with the legal feed and they can't deal with it so a lot of content ends up being buggered on their side. We can't fix it because we can't get them to use the feed which was butchered especially for their consumption.
-
Hubzilla is completely self-healing in its own network (with about a 24 hour granularity), but for other networks it only probes and corrects once a month because probing for all the different protocols involves a fair bit of resources.
Diaspora will never correct "basic communication data", caching it forever. That's why my home site can only talk to newer Diaspora instances; as it was once a Friendica site and they are still holding the old public key for my webfinger address. Hopefully I'll be able to correct this by sending an account_migrate message once they finally make that work.
GS also holds basic comms data forever from my experience; hopefully this has been fixed but I haven't seen it from here. We changed our feed url slightly a year or two ago and many GS sites still insist on using the old one, so it seems pretty slow to correct.
I can't comment on Friendica or Mastodon.
-
Instance blocks have been available on several other projects for at least a few years now; we just have never used them because as a filtering technology it is irreparably flawed. You need go no further than hubzilla to find out how badly it is flawed. There your identity is nomadic and is not tied to any particular site.
Incidentally, several projects implemented site blocks in response to an influx of the free web by Islamic State a few years ago and started sharing videos of people getting their heads chopped off. But IS members didn't setup their own sites where a site block might have had marginal effect. They just signed up at popular instances where site blocks would never work.
-
and blacklisting doesn't scale.
-
Many people seem to have forgotten that the whole concept of a 'social network' was created to solve the problem of unwanted or undesirable people and ideas being shoved in your face. Instead of choosing who to block (blacklist), you could choose who to connect with (whitelist). If you bypass this mechanism, you're back in the wild west of the internet and all the drama and spam and other undesirable content associated with it.
mike
All Jonkman Microblog content and data are available under the