@hellpie in other words, you don't know what you mean by "security" and you want me to do your research for you. If you do not know or care about security stuff at all, you have zero(0) chance of having any level of security. It doesn't matter how secure a designer makes your door, if you don't know that you have to lock it when you leave the house, or how a key works. I suggest starting here: https://ssd.eff.org/en/module/your-security-plan @kaniini
@hellpie users join the fediverse because of an affinity with the concept of federation, or frustration with the corporate #datafarms, not the UX of Mastodon, which hasn't always been that great. It's best features mostly came about because of its activist user base pushing for them. Gargron seems to be a good engineer and does a reasonable job as BDFL. But it's invented history to give him sole credit for the whole Mastodon project, let alone the whole fediverse. @kaniini
@dredmorbius sure, these are all valid filtering concerns for users (and admins if Super Cow Powers are necessary). But they have nothing whatsoever to do with whether the data is being stored and processed on one supercomputer, a corporate "cloud" (eg FB or G+), a network of VPS (most on corporate "clouds" like AWS), or an open "cloud" made up of any computer that contribute timeslice at any given time. @clacke
@alcinnz maybe this is where the confusion lies. I'm not proposing an entirely new social network. I'm proposing a different way of provisioning the server resources and providing the user identification and storage for the existing fediverse. In other words, it is just a dumb "cloud" server, like the VPS we already use thousands of. The social network sits on top. @dredmorbius
@teaneedz I'm not saying they're nobody's problem. A more detailed proposal to implement my back-of-a-napkin sketch would hopefully seek out feedback on elements it could include to support community management tools at the UI level. But before giving that feedback is worth anyone's time, we need to know if the concept is even technically feasible, and roughly how it might be implemented. For now, I'm just sharing some ideas and tech that could be used for it. @dredmorbius
@dredmorbius wow. This is an incredibly aggressive response to some idle shower thoughts, about how to hack around the observable problems caused by treating instances as the fundamental unit of the fediverse. If you have any potential solutions to the problems your listed in the context of the infrastructure I sketched out, please share. Otherwise what's your goal here? To publicly shame me for sharing some ideas? To what end?
@_emacsomancer finally! An actual real world example of the name causing an issue. But there's a quicker and easier (not to mention guaranteed effective) way to solve this than guilt tripping GIMP folks into changing their project name: https://mastodon.nzoss.nz/@strypey/102404698734120052
@brainblasted so if your real goal is > to have a gratis & libre program that more organizations can use and doesn’t invoke harmful memories.
... forking is the quickest and easiest way to achieve that. If you know that, but you keep harassing the GIMP project anyway, then your real goal is not the fluffy-bunny one you've stated here. Rather, it's about proving you can assert control over other people, and feeling powerful and effective without actually creating anything useful. @MatejLach
@brainblasted there's a much quicker and easier way to achieve this. Just fork the project and call it whatever you want. All this time and energy you're putting into guilt tripping GIMP about their name could be used to do that work yourselves, rather than demanding a bunch of volunteers do it for you. If you're right that most people want the name changed, your fork will attract more users and developers, and eventually the two projects will probably re-merge under the new name. @MatejLach
@_emacsomancer there's a cost associated with just accepting that GIMP is called GIMP, and that it's not and never was referring to the niche use of that term as an insult, but presumably that's not insurmountable either. I mean if it was called Nicely Integrated Graphic imaGe Editing Resource, that refers to a word with only one common meaning, clearly isn't self-deprecating geek humour, so it would be a different story. @MatejLach@brainblasted
#SyncThing is awesome! I wish I'd got around to installing it years ago, when I first heard about it. It solves the file sync problem proprietary tools like #DropBox solve, and #ownCloud/ #NextCloud aim to replace with #FreeCode. All purely #P2P, with no servers or #DNS required. I'm sharing folders between my laptops and some with a friend back in #Aotearoa (#NZ).
@macgirvin ah, ok. It seems like both one-way 'following' and two-way 'friending' need to be part of a comprehensive social web spec. It doesn't make sense to me for a micro-blog app to require a PeerTube channel to friend them back, just to follow its videos. Obviously that would needed for the channel to accept comments from a follower, but I can't see why it needs to be compulsory just to follow the feed. Seems like this is implementation choices, rather than inherent to AP though, right?
@macgirvin I see, so if I search for a #Zap user's user@instance.foo address or home URL in an AP app, I can find and follow it. But if I reply to their posts, my comments will only be visible in AP apps, not Zap. Am I understanding you correctly?
@null how do you think the #IMF got away with financial colonization? Part of it was a compliant news media whose corporate owners were making too much money out of it to allow proper reporting. A big part of how we pushed back was using the free and open internet to break the corporate media blockade, expose the grim realities of "structural adjustment" and organize against the IMF. FB replacing both the news media and the free net is incredibly dangerous.
Don't get me wrong, I'm not against splitting up FB, far from it. I agree with Hughes that the Instagram and WhatsApp acquisitions never ought to have been approved and reversing them is low-hanging fruit that needs to be plucked before they get digested. All I'm saying is regulating for #DataPortability and #Interoperability is more important to protecting both consumer rights and fair competition. Splitting up FB won't fix the similar problems with Goggle, the Amazone etc @jack@Wolf480pl
@null intriguing comparison. During the heydey of financial colonization ("structual adjustment"), the IMF effectively governed a lot of people. But I doubt it was ever 2 billion and I'd be very surprised if it is now. Go ahead, surprise me! I'd love to know more about their current operations
@jcbrand also spare me the red-baiting. Given two options, I take the third. Eg neo-liberal capitalism or command economy? Neither. Both have clearly failed (collapse of USSR and of Washington Consensus with GFC). Whatever economic systems will carry us into the post-carbon era, it won't those industrial dinosaurs. Maybe a hybrid of both (eg #P2PF's "partner state"), or something totally new.