Live data from Hacker News

I inspected the mastodon.social website

catalin.red

41–50 of 50 posts

Re: I inspected the mastodon.social website

#41

I didn’t understand the paragraph about CSS reset. As in, it was poorly written: > Personally, I like to preserve useful defaults instead of clearing everything with a CSS Reset. A tool like normalize.css, comparing to the classic CSS Reset helps to learn how elements are meant to display actually. OK, the thumbs-down and the first sentence give me the clue that you don’t like CSS reset (although I still have no idea…

Well, english is my second language.

Besides that, what I was really trying to say was that a tool like Normalize.css or Bootstrap's Reboot may be more helpful than the classic CSS reset.

Re: I inspected the mastodon.social website

#42
post #38

I didn’t understand the paragraph about CSS reset. As in, it was poorly written: > Personally, I like to preserve useful defaults instead of clearing everything with a CSS Reset. A tool like normalize.css, comparing to the classic CSS Reset helps to learn how elements are meant to display actually. OK, the thumbs-down and the first sentence give me the clue that you don’t like CSS reset (although I still have no idea…

I think they recommend using normalize.css instead of resetting styles.

Thank you :)

Re: I inspected the mastodon.social website

#43
post #39
post #24

Earlier quoted context omitted.

I just tried out Mastodon quickly after reading this, and what a disaster. Icons are overused, there's no onboarding of the UI and it just throws you in with a bunch of icons, I wasn't sure what most of them did. I started at mastodon.technology and it immediately follows the instance creator which confused me, when I checked his profile there was an icon with which I could unfollow(an X on top of a person icon), whi…

Those UX issues would be far more useful being reported on GitHub than they are on HN.

That assumes GP's primary motivation is to support/improve the particular project, rather than discuss UX and kvetch with fellow hackers and designers.

Re: I inspected the mastodon.social website

#44
post #30

Earlier quoted context omitted.

Yes, I read that. That massive (and likely deliberate) mischaracterisation of free speech is exactly what the comment you're replying to is objecting to. > it's okay to promote e.g. National Socialism Not, it's not OK. If you promote Nazism I'll point out you're an idiot and so will most right minded adults. Something being not banned in not the same thing as it being 'OK'.

Note that it's quoted, in contrast to the other definitions. This is presumably in reference to the abuse of "free speech" rhetoric by neo-Nazis and the like (who typically do not value freedom of expression beyond their own views), rather than tootcafe making that claim about free speech. Maybe that presentation is too subtle to get the point across to most people, but I think it's a valid distinction to make.

> the abuse of "free speech" rhetoric by neo-Nazis

How common are neo nazis in 2018? There's a fringe element on the left who believes anyone on the right of, say, Bernie Sanders, is a Nazi. Tootcafe seems to subscribe to this convenient way of dismissing people that disagree with one's current viewpoint.

Re: I inspected the mastodon.social website

#45
post #40
post #28

Earlier quoted context omitted.

> I have Jewish and gay friends and Nazis want them executed. Same here. Wanting someone executed is already covered by banning threats, as mentioned in the comment you're replying to. Removing unwanted speech which isn't threatening isn't necessary. The most likely outcome of blocking free-speech nodes is control of conversation, eg, deeming supporting national borders as 'hate speech'. Which is fine if you want tha…

> The most likely outcome of blocking free-speech nodes is control of conversation, eg, deeming supporting national borders as 'hate speech'. Why would that be the most likely outcome? I'm pretty sure that "deeming supporting national borders as 'hate speech'" is a fringe position, which would be unlikely to take over a popular instance. Even if it did, people whose posts about national borders are deleted could easi…

> I'm pretty sure that "deeming supporting national borders as 'hate speech'" is a fringe position

I'm not sure if you use Twitter or live in the bay area but it's relatively common in both these places. Even TechCrunch UK recently described supporting Brexit as a racist position.

> Filtering what you see and share with others isn't inherently wrong.

Totally agreed, but the mischaracterisation of networks supporting free speech as a place where "It's OK to be a Nazi" is. It's also not particularly original, with similar arguments being commonly used by most totalitarian regimes.

That said, the 'nazism is OK on those instances' may have been accidental (or perhaps just unthinkingly partisan) - I've sent a PR with a fix: https://github.com/tootcafe/blocked-instances/pull/22

Re: I inspected the mastodon.social website

#46

Kind of off topic, but like the author I was looking at Mastodon yesterday (reading the ruby code, ha ha!). One thing struck me, though. The documentation seems to imply that it doesn't matter what instance you're on and to simply look for an instance that has people you get along with. However that doesn't seem to be a good idea in some cases and I'm wondering if I'm wrong. Some instances are blocked by other instan…

> And even though some are only "silenced", if you happen to join an instance that is blocked by a lot of other instances, then nobody will see what you are writing.

If you are on a "silenced" instances you can still be directly followed by users on the instance doing the silencing and they will see all of your posts on their Home timelines. From what I've seen, any boosts/replies by those users following you to your statuses still make those individual statuses eligible for them to show up on Federated feed on that instance, even if your every post is not eligible.

Arguably the game is the same whether or not you are on a majority "silenced" instance: the more people that directly follow you the more likely you show up in people's Home timelines and thus the more likely you show up in Federated feeds. You don't necessarily need to know if a remote instance is silencing your instance if you make enough friends on that instance that are directly following you.

I'd also argue that worrying about which Federated feeds you show up on is counter-productive in Mastodon. As with Twitter, it's better to reach users in their Home timelines, with direct relationships, or in some cases on Local Timelines for interesting interests, than to ever count on Federated feeds. Many instances the Federated feed isn't that useful (too busy, for instance) and people don't bother checking it anyway. (My main account is currently the only user on a small instance and the Federated feed is mostly repetitive with stuff on the Home feed and so I check it very irregularly.)

Instance "suspensions" obviously are a different matter entirely, but I don't feel like it is worth worrying about "silences".

> It almost seems to me that I really need multiple accounts on multiple instances to ensure that I can get what I want -- but since the client is tied to the instance (as a web sever), that's a difficult trick...

It's easy enough to just open multiple tabs in your browser and tab between them, if that is what you want to do. There are also some native clients with good multi-account support.

Re: I inspected the mastodon.social website

#47
post #18

Earlier quoted context omitted.

I agree this is BEM, not SASS nesting. I dislike BEM because it requires modification of CSS classes to change how something looks - you add and remove classes to your `.login-box` to make it bigger or bluer or wider. I prefer CSS auto-nesting (using Svelte) or SASS nesting (for older projects) so I can just modify my `.login-box` to add whatever styles it needs and not touch my HTML.

Please read my comment above, also here's how the above "nesting" compiles to: .compose-form .compose-form__modifiers .compose-form__upload-description input::placeholder { opacity: 1; }

I did.

    .compose-form .compose-form__modifiers .compose-form__upload-description input::placeholder { opacity: 1; } 
That looks like BEM, with all the underscores and modifiers.

Proper nested SASS would look like:

    .compose-form .upload-description input::placeholder { opacity: 1; } 
Scoped CSS would look like:

    .compose-form-abc123 .however-deep-or-shallow-you-want { opacity: 1; }

Re: I inspected the mastodon.social website

#48
post #28
post #27

Earlier quoted context omitted.

I’m 100% behind the idea that instances should be able to refuse to carry (literal) nazi propaganda (read the footnote; this is what we are talking about here. I agree that isn’t great wording though). Isn’t that the whole idea of federation? Instances can do what they want? Also Nazism is a threat. I have Jewish and gay friends and Nazis want them executed.

> I have Jewish and gay friends and Nazis want them executed. Same here. Wanting someone executed is already covered by banning threats, as mentioned in the comment you're replying to. Removing unwanted speech which isn't threatening isn't necessary. The most likely outcome of blocking free-speech nodes is control of conversation, eg, deeming supporting national borders as 'hate speech'. Which is fine if you want tha…

deeming supporting national borders as 'hate speech'.

Making up stuff like that doesn’t help your argument here.

Re: I inspected the mastodon.social website

#49
post #2

This is cool. I wish this sort of analysis existed for many major websites! The reason I think this would be useful is the accessibility of the results - we'd be able to consider the various analytics within the context of something highly familiar (the mention of Slack still using "text/..." is one such example). Although... hmm, maybe I don't want all websites scored. Arc (ie, HN) would probably rank 0.5/10 in term…

Glad you found it interesting. I enjoy to dig into this kind of analysis stuff from time to time: A while ago I made an HTML study on around 8 million web pages: https://www.advancedwebranking.com/html/ Also, I wrote about this journey on CSS-Tricks: 1. https://css-tricks.com/average-web-page-data-analyzing-8-mil... 2. https://css-tricks.com/random-interesting-facts-htmlsvg-usag... On accessibility, I'd have loved to…

The plugs are cool, thanks! :)

The 8 million webpage one was really interesting. I don't know why yet though. (I'm serious - I know this info will come in hand for figuring something out one day. Thanks.)

TIL about [aria-hidden] from "HTML/SVG usage"/"Hiding DOM elements"! I wonder what the raw stats on display:none vs visibility:hidden are (especially considering that they have different effects). I wouldn't have expected 117000 webpages (is this a discrete page count or a website count?!) to use the highly specific ".visuallyhidden"... oh it's part of the HTML5Boilerplate framework, that explains it.

The main issue with screen readers is that, AFAIK, JAWS doesn't offer a developer-access program! Or if it does, I've never heard of it. A LOT of people still use JAWS, AFAIK, in spite of the newer offerings out there. The main difficulty here is the differing-client-behavior problem, although NVDA and ChromeVox's free-ness are surely shifting the usage share (something I've wondered about for a while).

Re: I inspected the mastodon.social website

#50
post #20

Kind of off topic, but like the author I was looking at Mastodon yesterday (reading the ruby code, ha ha!). One thing struck me, though. The documentation seems to imply that it doesn't matter what instance you're on and to simply look for an instance that has people you get along with. However that doesn't seem to be a good idea in some cases and I'm wondering if I'm wrong. Some instances are blocked by other instan…

> https://github.com/tootcafe/blocked-instances Wow. tootcafe, according to their own page, blocks any instances where free-speech is tolerated. Not threats, or harassment, just social views they deem unlikable.

And? There are plenty of other instances to choose from and that is the beauty of Mastodon.

Some may choose to have very strict rules about what is allowed, others may be wide open.

I don't see a problem here.

Post reply on HN