GNU social JP
  • FAQ
  • Login
GNU social JPは日本のGNU socialサーバーです。
Usage/ToS/admin/test/Pleroma FE
  • Public

    • Public
    • Network
    • Groups
    • Featured
    • Popular
    • People

Conversation

Notices

  1. Embed this notice
    stux⚡ (stux@mstdn.social)'s status on Saturday, 23-Mar-2024 07:49:40 JST stux⚡ stux⚡

    @zuck Arrived! :nkoWave:

    In conversation about a year ago from mstdn.social permalink
    • Embed this notice
      Nartagnan ⏚ (nartagnan@mstdn.fr)'s status on Saturday, 23-Mar-2024 07:49:36 JST Nartagnan ⏚ Nartagnan ⏚
      in reply to
      • latsss

      @stux @latsss

      Technical question : Do a personal block protect my data ?

      I remember threads users conditions saying something like "as long as we are able to access your data we will consider them ours".

      Is a personal block enough ?

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      stux⚡ (stux@mstdn.social)'s status on Saturday, 23-Mar-2024 07:49:37 JST stux⚡ stux⚡
      in reply to
      • latsss

      @latsss We let our users decide for themselves :ablobwink: An user-level instance block is super easy and quick if one wants to

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      latsss (latsss@mastodon.social)'s status on Saturday, 23-Mar-2024 07:49:39 JST latsss latsss
      in reply to

      @stux
      Sorry, I don't really remember. Weren't you against federation with threads?

      In conversation about a year ago permalink
    • Embed this notice
      Jennifer (chromaticliteralist@mastodon.social)'s status on Saturday, 23-Mar-2024 07:49:49 JST Jennifer Jennifer
      in reply to
      • Nartagnan ⏚
      • latsss

      @nartagnan @stux @latsss if you put your information publicly onto the internet, anyone with access to the public internet can access, save, manipulate, and reproduce your data at will

      If someone from Threads follows you, your private/followers-only posts will also be sent to the Threads server to be shown to your Threads follower, and so Meta can access that data too

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Saturday, 23-Mar-2024 07:54:07 JST HistoPol (#HP) 🏴 🇺🇸  🏴 HistoPol (#HP) 🏴 🇺🇸 🏴
      in reply to
      • latsss

      @stux

      Hey Stux,
      thought so, too, but the user-level block doesn't seem to work properly:

      https://astronomy.social/@2ndStar/112140391376401898

      (same for me)

      @latsss

      In conversation about a year ago permalink
    • Embed this notice
      stux⚡ (stux@mstdn.social)'s status on Saturday, 23-Mar-2024 07:54:58 JST stux⚡ stux⚡
      in reply to
      • Nartagnan ⏚
      • latsss
      • Jennifer

      @chromaticliteralist @nartagnan @latsss But this goes with all posts 😉

      Keep in mind that Mastodon is a public social network and when posting in the "public" status your post will be "broadcasted" onto the web via ActivityPub for example, like shouting it thorugh a megaphone :blobcatgiggle:

      If you want your posts protected, post in followers-only and set the account to approve followers :cat_hug_triangle:

      In conversation about a year ago permalink
    • Embed this notice
      Jennifer (chromaticliteralist@mastodon.social)'s status on Saturday, 23-Mar-2024 07:56:49 JST Jennifer Jennifer
      in reply to
      • Nartagnan ⏚
      • latsss

      @nartagnan @stux @latsss if your user account blocks the threads domain, no one there can follow you and so your private/followers only posts will not be shared to Meta’s instance

      Regardless of your block strategy, Public posts are always accessible to anyone in the web for any purpose they please (including Meta).

      Unlisted posts can also be scraped out from the APub network, regardless of block strategy, which an industrial player like Meta would do.

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      Nartagnan ⏚ (nartagnan@mstdn.fr)'s status on Saturday, 23-Mar-2024 07:56:50 JST Nartagnan ⏚ Nartagnan ⏚
      in reply to
      • latsss
      • Jennifer

      @stux @chromaticliteralist @latsss

      You say blocking at user level has no effect ?

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      Nartagnan ⏚ (nartagnan@mstdn.fr)'s status on Saturday, 23-Mar-2024 07:57:24 JST Nartagnan ⏚ Nartagnan ⏚
      in reply to
      • latsss
      • Jennifer

      @chromaticliteralist @stux @latsss

      Sorry, that was not what I wanted to know.
      I know the whole public things.

      My question is :
      - blocking at a user level do the same (for my account) than a defederation ?
      - if, on a 2-users instance, both decide to block tread, is it the same than a defed ?
      - concerning Threads conditions too ? Do they treat user-block the same way than a full defed ?

      In conversation about a year ago permalink

      Attachments


      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      Jennifer (chromaticliteralist@mastodon.social)'s status on Saturday, 23-Mar-2024 07:57:43 JST Jennifer Jennifer
      in reply to
      • Nartagnan ⏚
      • latsss

      @nartagnan @stux @latsss you’re going to need to look at the docs if you want to split hairs this far into the weeds.

      Defederation is the more powerful tool. Metadata is still passed around otherwise.

      Threads doesn’t “treat” blocks or defeds at all. The protocol does. Threads doesn’t get a say.

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      Nartagnan ⏚ (nartagnan@mstdn.fr)'s status on Saturday, 23-Mar-2024 07:58:29 JST Nartagnan ⏚ Nartagnan ⏚
      in reply to
      • latsss
      • Jennifer

      @chromaticliteralist @stux @latsss

      Of course they scrap. But is it the same amount of scrapping ?

      And considering where they have a say:
      If they say "we will consider opt-out of consent if you defederate, but not if you only user-block", they have a say.

      I don't have money to go to court for that.

      In conversation about a year ago permalink
    • Embed this notice
      patricus (patricus@piggo.space)'s status on Saturday, 23-Mar-2024 07:59:18 JST patricus patricus
      in reply to
      • Piggo :verified_horse:
      @stux @piggo well, I prefer my hoster to block the evil IP's server-side + if someone doesn't like, they can move onto other instance.
      In conversation about a year ago permalink
    • Embed this notice
      stux⚡ (stux@mstdn.social)'s status on Saturday, 23-Mar-2024 07:59:19 JST stux⚡ stux⚡
      in reply to
      • Piggo :verified_horse:
      • patricus

      @patricus @piggo We leave it as a personal choice for people on our instances and don't force it on them 😉

      In conversation about a year ago permalink
      HistoPol (#HP) 🏴 🇺🇸 🏴 repeated this.
    • Embed this notice
      patricus (patricus@piggo.space)'s status on Saturday, 23-Mar-2024 07:59:21 JST patricus patricus
      in reply to
      • Piggo :verified_horse:
      @stux booooo! luckily we have a block on him here. it's why @piggo is an epic admin if comes to fediverse.
      In conversation about a year ago permalink
    • Embed this notice
      HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Thursday, 28-Mar-2024 19:04:50 JST HistoPol (#HP) 🏴 🇺🇸  🏴 HistoPol (#HP) 🏴 🇺🇸 🏴
      in reply to
      • Qazm
      • latsss

      @Qazm
      Thanks.

      "You'll still be able to see replies from users elsewhere made in response to posts on threads, and you'll also still see when someone else mentions threads users."

      That sounds rather reasonable.
      So it would be rather like a discussion here where the setting is "followers only," so everyone will only see posts by people (or bots 😉) whom they follow, correct?
      (Which still puts me off at times, having comments apparently coming out of thin air, which is why I...

      @stux @latsss

      In conversation about a year ago permalink
    • Embed this notice
      Qazm (qazm@tiggi.es)'s status on Thursday, 28-Mar-2024 19:04:52 JST Qazm Qazm
      in reply to
      • HistoPol (#HP) 🏴 🇺🇸 🏴
      • latsss

      @HistoPol @stux @latsss

      I saw this late, but yes, if you block that domain, that only blocks and hides accounts and posts from there.

      You'll still be able to see replies from users elsewhere made in response to posts on threads, and you'll also still see when someone else mentions threads users.

      In conversation about a year ago permalink
    • Embed this notice
      HistoPol (#HP) 🏴 🇺🇸 🏴 (histopol@mastodon.social)'s status on Thursday, 28-Mar-2024 19:05:57 JST HistoPol (#HP) 🏴 🇺🇸  🏴 HistoPol (#HP) 🏴 🇺🇸 🏴
      in reply to
      • Qazm
      • latsss

      @Qazm @stux @latsss

      (2/2)

      ...often put a link of the post I'm replying to so as not to confuse my followers as much.

      //

      In conversation about a year ago permalink

Feeds

  • Activity Streams
  • RSS 2.0
  • Atom
  • Help
  • About
  • FAQ
  • TOS
  • Privacy
  • Source
  • Version
  • Contact

GNU social JP is a social network, courtesy of GNU social JP管理人. It runs on GNU social, version 2.0.2-dev, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All GNU social JP content and data are available under the Creative Commons Attribution 3.0 license.