Does it take any unicode character? Wonder what this does:

  ˆ ͜⃢ ˆ

I don’t see why they wouldn’t. No way to verify I guess but it’s really hard to think Amazon wouldn’t come up with a system equivalent or better than what I did while reading this thread.

I imagine it’d be a one time convenience thing, or maybe you could open amazon and click ‘set up this device again’ or something and it reactivates

Can’t this all be prevented by the already connected devices checking if the new device matches a newly purchased, not yet set up device in your purchase history? Really slim chance someone eavesdrops on its id and retransmits fast enough to hijack the setup

Does this matter if it needs a password? Luks stores the key in storage too

There’s no password involved in that demo

Channel?
Code?

Does Firefox on android support sandboxing nowadays?

Don’t forget creating riverszity

Wd40

I wish the color coding matched with the animals

Supergirl doesn’t need hilts, she just holds the blade

What’s the music player

Okay, thanks for replying. Your points make sense, especially

It’s a lot easier to add categories there than remove them later on which is why I want to keep the initial amount of types to the absolute minimum needed.

this one. I also wasn’t aware that the document was a part of a larger discussion and sorry about the rfc meaning confusion😅

Hope you could have a meal :)

• There will be 3: NSFW, CW and Generic. Excuse the passive aggressiveness but this tells me you didn’t read the RFC at all

I thought it was obvious that generic is even broder than nsfw or cw, and is irrelevant since we’re talking about nsfw type not being specific enough. And your writing isn’t passive aggressive, it sounds angry. If you didn’t want comments why name it request for comment?

Your example makes no sense as people not wanting to see will block the entire NSFW tag type in the settings,

Your rfc doesn’t mention that, it only mentions blocking tags.

This is what your outlook section says:

There have already been several discussions about future expansions, in particular filtering tags has been requested. Given this proposal tag filtering in the feed view should be possible without further changes to the backend.

Do you see tag type filtering anywhere?

Preset tags can and will definitely be included… What you are describing here is pretty much what I wrote in the RFC

You wrote of only having the nsfw and cw (and general) types in the rfc. I didn’t see anything about expanding that to more specific types. And if you mean having an nsfw tag with the name porn, it’s not clear in the rfc that tag names can be used for filtering.

Using the object ID optional tag federation can also be achieved, allowing for communities across multiple instances to share content via tags

Makes it sound like only tags with the same id would be considered the same in the interface, so the same preset tag from different instances/communities would not be interchangeable.

See my point regarding NSFW filtering,

If your point was:

Theoretically NSFW could be implemented using a preset “Content Warning” tag but seperating out this tag allows instances to better filter it out for moderation purposes

Then your point is that it does make sense to have more tag types if they’re important enough, so that’s not a point against having a spoiler tag type. Anyways, I wrote that because I thought every post would be limited to 1 tag like on reddit and didn’t see the news example. Mb.

You are almost literally describing my RFC, i ask again did you actually read it?!

Stop being so flippant about it. I read your post. It talks about a single tag system that also takes the role of content warnings. I specifically wrote that (imo) content warnings (for filtering out) should be seperate than tags (for filtering in). Also your post doesn’t mention platform wide default tags.

With #2, my problem was that without the ability to block categories, different instances would need to use the same shared id for the nsfw tag to let users block all nsfw at once; which is a regression from the current sceme.

general tags are additional to tags above to specify content type

So like hastags? I had assumed 1 tag per post

5. Proposition is for different architecture

Put that in there in case someone asks why I’m criticizing the current plan without providing an alternate one.

Anyways, this scheme doesn’t solve what op has asked for, which is to block porn posts platform wide without blocking all nsfw posts. With this scheme they’d need to add every community / instance’s porn tag to their blacklist one by one, and it’s not even guaranteed that posters would use the porn tag in addition to a more specific tag. Letting moderators set default tags for communities could solve the second problem. But to solve the first one either tags need to be blockable by name (instead of id) or there needs to be a seperate tag category for porn

I read the thing, but that’s still no reason not to seperate nsfw category further. It makes no mention of a technical limitation that prevents creation of more categories, it’s just a person suggesting how a tag system could look like.

there he explained that it won’t work like that

The entire reason I’m commenting is because I don’t want it to work like that. I have no idea how to reply to a git commit, if I did I’d object there too.

1. CW and NSFW are too broad to be the only 2 types of tags.

2. The suggestion to use tag urls as ids don’t work with the idea of using ids to share tags across instances. I don’t want the entire threadiverse to decide https://lemmy.world/t/nsfw is the global nsfw tag and smaller instances being forced to use that or risk people facing unsolicited nsfw from their instance.

3. There is no mention of filtering posts based on their tag category, which would make it impossible to block nsfw posts across instances without using the shared id. There needs to be platform level tag categories (especially for things people might not want to see) so content filtering works in a consistent and decentralised manner. Then individual instances or communities can create their their own tags based on those categories to fit their needs.

4. The author seems to want to replace the spoiler mark with a (cw) tag called spoiler, but things can be both spoilers and fall under other tags (ie an image post, a leak, a discussion etc). Also this would pointlessly filter out regular spoiler content if a user blocks tags with the cw category.

The way I’d want things is tags and spoilers / content warnings being completely seperate from each other at the platform level:

Content warnings to let people filter out content they don’t want to see. They wouldn’t a content discovery tool. And they would be nestable. There would be platform wide default ones like

• Spoiler
• Nsfw
  • Artful nudity
    • Nudity
      • Porn
  • Shock
    • Injury
      • Gore
  • Slurs

. Users would be able to choose whether to show, blur or block content with these warnings in the settings. Instances and communities would be able to make their own content warning as well, managed by the user in the settings of a community. A user creating a post would see a menu to pick the content warnings (multiple if they want) that describe their post. Tags describe content to people who want to find such content. There could be generic platform wide ones like news, qna etc, but the majority would be community specific. Tags could also include default content warnings (eg ‘leak’ tag could activate the spoiler content warning).

I think this would be the most elegant way to do it, but even what we have now feels better than what is proposed in that link

I still don’t think it’d be enough to leave nsfw tag creation to communities. Even if a porn community created multiple tags under nsfw to classify their posts that would do nothing to help people block all porn on the platform. Porn, gore etc need to be their own tag types under the general nsfw type.

I don’t think tags would be a solution as they wouldn’t be standard threadiverse-wide. Also porn communities would want to mark their posts with specifying tags like every other community does instead of a generic porn tag.

What’s needed is expansion of the nsfw mark into subcategories

Horror doesn’t mean gore and people use the nsfw tag for things other than porn, gore or horror too.