sirxdaemon

joined 1 year ago
[–] sirxdaemon@lemmy.ca 1 points 9 months ago

That was one of many factors that I think the invocation was necessary. Th residents, as well as affected businesses, in Ottawa were left to fend for themselves as leadership(including the police) could not end the occupation of the downtown core. There were multiple blockades of varying degrees that were also problematic. What came out of the Coutts blockade was worrisome to say the least. The one at the Ambassador Bridge was cleared but who knew if people would come back or setup elsewhere. No one knew how things would play out at the time but there was a lot of concern across Canada. Even by the judge's admission, he may have advised the same conclusion the government decided on.

At the end of the day I agree with the public inquiry that didn't find it unreasonable and perhaps revisions to the Emergencies Act is something to consider.

[–] sirxdaemon@lemmy.ca 1 points 9 months ago (2 children)

The second interview of a CBC piece answered some similar questions I had. This ruling provides precedence and can stop a future invocation of the Emergencies Act in its tracks through an injunction from the Federal Court of Appeal, if it's granted.

The government is appealing the decision because they believe the invocation was reasonable and justified. The Liberals are currently behind in the polls, so politically it's within the government's interest to appeal this. The act itself is decades old and never invoked prior to this so both the civil liberty groups and the government are probably keen on getting clarification on the legal usage of the act from the Supreme Court of Canada.

Personally, I fully support the usage of the act. What I found unreasonable was the lack of accountability with the provincial police.

[–] sirxdaemon@lemmy.ca 32 points 10 months ago (4 children)

I always thought Santa was a communist, what with the redistribution of wealth and all that red he wears. But nope, he was a fossil fuel venture capitalist through and through.

[–] sirxdaemon@lemmy.ca 6 points 11 months ago* (last edited 11 months ago)

Capitalism doesn't believe in Robin Hood. Robbin' hoods on the other hand...

[–] sirxdaemon@lemmy.ca 8 points 11 months ago

And how do you know the mysterious illness is simply not giving staves sentience?

 

With the option enabled, you can see post downvote tallies as well but it's displayed as a ratio. Unless I'm forgetting or just missed it, I haven't seen anyone comment on it either. Good or bad.

Personally, I don't like it and would prefer separate numbers for the upvotes and downvotes. The ratio stands out. Not just within Connect UI but also compared to other platforms' design. Separate numbers would make the UI more standard and also reduce the extra spacing to make room for the height difference.

If you completely disagree, that's totally valid and I'm actually more curious to see these comments, for perspective.

[–] sirxdaemon@lemmy.ca 7 points 1 year ago

Username checks ou.. username does not check out. On a more serious note, Connect for Lemmy has the option to block instances at an account level.

[–] sirxdaemon@lemmy.ca 1 points 1 year ago* (last edited 1 year ago)

It's an app-specific feature so using another app or viewing through your browser would not have the feature. Hopefully it's baked into Lemmy/Kbin itself in the near future so users can manage it across access points, like blocking of users or communities.

 

As far as I know, Lemmy Connect is currently the only way for individual users to block instances themselves. Sure, you can do this if you host your own instance but not everyone wants to go to that length.

Specifically, you'll need to go into Settings, in the app, and tap on Blocked Settings, and from there you can manage your blocked instances, as well as communities and users.

I want to also mention that Lemmy Connect has the ability to tag users. Super useful with all of the bad actors that are creeping in.

EDIT: Unfortunately it seems blocking instances is broken in the current version, 1.0.68, but the dev has been updating practically daily recently so I think there'll be a fix out soon.

EDIT2: And it's fixed.