Show Navigation
Notices by Mike Macgirvin (mike@macgirvin.com), page 6
-
You can delete those since they are well and truly dead.
-
@maiyannah Correct - and that's why we have a problem. Multi-media content is not restricted by ActivityStreams or ActivityPub. It is restricted by Mastodon's interpretation of unwritten rules and their own policies. This is why these 'specs' are so laughable - the things they specify aren't really important for anything that matters and the things they don't bother to specify are crucially important to inter-operation.
-
thanks
-
It's probably just a link in somebody else's archives. I still have people hitting my site for 'sonicamusica.com'; which hasn't existed for a dozen years.
-
It appears that red core (and Hubzilla dev) recently broke through 20,000 commits. Cheers.
-
@bob @GrooveStomp The reason gopher failed was due to lack of flexibility. In less than two weeks we went from 90% gopher traffic to 5% gopher, vs 5% www to 90% www. The other 5% was ftp. This happened at precisely the time that mosaic introduced inline images - which gopher simply couldn't compete with and couldn't provide a workable mechanism to implement. The licensing stuff was a sideshow - the University of Minnesota saw dollar signs and wanted a piece of that pie; but most of the community had already forked long before that threat became tangible.
-
I have a solution and it is permitted in the ActivityStreams specification so it's the right thing to do. Basically, the microblog folks will send 'Note' activities (which somebody along the line took to mean *cannot* have embedded media) and we will produce 'Article' activities which are allowed to have embedded media.
-
Your site was a directory server and some of those represent photos for the directory. But it's difficult to know which ones to remove as they are associated with active xchans which you may or may not be using.
-
Polling webfinger each time the content is rendered could be trouble.
That's why we have xchans.
-
@mike They know what they're doing, Mike. They just don't care about networks other than their own.
-
Trying to come up with a workaround for Mastodon's brain-dead media behaviour. The only solution I've got currently is
if(your friend is using mastodon)
do the wrong thing
else
do the right thing
The issue is that half the metaverse does the wrong thing; which is basically stripping media from HTML content and adding it back as attachments. This is fine for OStatus and public networks but doesn't work with privacy enhanced services because the messages need to be signed, If you mangle multi-media messages to work on these primitive nets it breaks the signature, so you're basically stuffed. The messages will not federate because the service your friends are using is doing the wrong thing. If you don't mangle the posts to fit that network's policies, the media content will be stripped. If you do mangle the content, the message won't verify and will be discarded.
I do so wish that the people designing these protocols and systems would take a look at what the hell they're doing sometime. They're really screwing up everything for everybody.
-
@Gargron Australia has Dijabringyabeeralong and of course 'the Boobs'. Just thought i'd let you know.
-
Mexican time moves a bit slower iirc
-
We did this several years ago, but the mail access libraries suck up huge amounts of memory processing large mailboxes - and everybody has large mailboxes. Memory use is traditionally a problem in PHP. So python would be a good choice for reading the mailbox (I might suggest using 'imapclient').
-
What is it you're trying to accomplish?
-
That's fixed in the next release. We'll show the feed url as the "primary address" since they usually don't have webfinger addresses. It should work ok either way.
-
Let us know where you're having troubles. One I know about is that the name of the feed that works in the channel sources page (and triggers the autocomplete) isn't always the url or name you connected with, You might have to look at your connections to figure out the name that was discovered from the feed and that will work on the sources page.
-
Those are OAuth1 tokens - which many 3rd party auth libs and apps support. But yeah, you can use username/password and we've recently added http signature auth. If you activate the twitter_api addon you can use Hubzilla with a couple dozen third party twitter and statusnet clients. Most of these handle OAuth1 or username/password. We're also slowly moving towards OAuth2 and OpenID Connect.
-
@bob Hubzilla is slightly ahead in this space. I don't claim that any privacy is perfect, but people with special needs can choose higher security if they want it. Javascript based E2EE has been working for a few years. Last year we put in place everything needed for full client E2EE; mostly waiting for somebody to create an external app to shuffle content in and out and do the actual encryption. Encrypted message contents aren't displayed in your stream but are offered for download. All an app needs to do is attach to the message mimetype. Posting is done via API. This is available for stream content as well as direct messages. Hubzilla itself does not care what the content is or how it is encrypted; which is how it should be. If you have a client side app instead of a webservice you can encrypt/decrypt on the fly and display content inline. For the webservice you can only display inline using the built-in JS encryption.
-
A virtual nomadic identity can include channels on other services and protocols. There are a number of uses when it comes to identity management. We currently base identity on possession of your private key; and most/all other services base it on your server login. I need to completely remove the actual identity from *anything* that could change. You can change your key now, but it's clumsy and involves updates to a lot of tables all over the network. With a virtual identity you just attach a new key to your identity and you're done. We don't have to fix data in 20-30 tables. As a side effect you could also link your identity to a Mastodon account (for instance) and sync posts/comments from there with your Hubzilla channel.
Mike Macgirvin
All Jonkman Microblog content and data are available under the