social.coop is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Fediverse instance for people interested in cooperative and collective projects. If you are interested in joining our community, please apply at https://join.social.coop/registration-form.html.

Administered by:

Server stats:

487
active users

@privacysafe @techcrunch@threads.net

This is great, but where is the policy? Are you compliant?

Something is off until you do not handle this well. It makes seem suspicioius, esp. since you hammer on the privacy aspect and then don't comply with basic rules thereof.

The privacy policy at privacysafe.app/# is missing.

And it would also be nice knowing the party with whom we share our viewing habits, the people or business that is behind it, and their proposition/plans.

privacysafe.appPrivacySafe – Private Chat, Calls & Storage.

@privacysafe @techcrunch@threads.net

Furthermore your links make use of some URL shortener, that is from an unknown party, also able to collect data.

Unfortunately this is seen a lot with launches of new online products and services. Landing pages of some anonymous party, no PP, no hint of biz model, and issues could be a lack of attention or they could be deliberate on motives.

And people just use low-barrier things thrown at them, sign up and start feeding .

small circle 🕊 in calmness

@privacysafe @techcrunch@threads.net

@yaleprivacylab I found this neat project via your boost. Did these things pass notice in your review?

A fedi account themed by an official party or institution has a moral responsibility that by its activities it does not lend credibility to potentially unsafe projects, unless these are appropriately addressed or communicated to people using the service.

I advocate for , Sustainable open social software, who address all this in their dev lifecycle.

@smallcircles @privacysafe @techcrunch @yaleprivacylab

Hello and thank you for the fast feedback on this.

1. StickTock.com collects ZERO personal data and only the diagnostics and metrics required to operate the server. This can be audited freely via the code repository.

1/4

@smallcircles @privacysafe @techcrunch @yaleprivacylab

2. The link to the Terms of Use on StickTock.com now properly resolves to the Privacy Policy and Terms of Use, which is one short document. privacysafe.tools/terms/stickt

PrivacySafe had been linking this to the LICENSE file in the code repo to make sure the policy/terms for the StickTock.com website do not apply to other instances people fork and deploy.

A BIG THANK YOU for pointing out it wasn't resolving correctly on StickTock.com

2/4

privacysafe.toolsterms

@smallcircles @privacysafe @techcrunch @yaleprivacylab

3. StickTock.com but NOT the code in the repo uses Plausible.io (self-hosted) which is a) cookie-less, b) complies with GDPR, and c) anonymizes HTTP headers.

By all metrics it is more private and anonymous than the HTTP request your browser sends to the server.

See privacysafe.tools/terms/stickt

Feedback on this is welcome and PrivacySafe will make changes if needed.

3/4

privacysafe.toolsterms

@smallcircles @privacysafe @techcrunch @yaleprivacylab

4. PrivacySafe is my private org and StickTock.com is 100% gratis (cost-free) and 100% libre (FOSS).

@yaleprivacylab does not officially endorse any software, products, or services and a boost/reply/RT of a message/toot is not an endorsement.

Almost all the links shared by @yaleprivacylab are * less * private than StickTock.com As is the same for the EFF etc.

Community feedback is very important. Please contact me with any issues.

4/4

@profdiggity @privacysafe @techcrunch@threads.net

Thank you in return, as Responsiveness and Receptiveness are qualities of the , the development lifecycle that initiatives address and tailor for their particular line of work.

On point 4, I think there's more obligation. I was wrong-footed by the boost of @yaleprivacylab and unaware that the same party was behind it. This should be made clear, or there's conflict of interest. Someone might use accounts like that to growth-hack.

@profdiggity @privacysafe @techcrunch@threads.net

What @yaleprivacylab might have done, lacking quote toots, is create a new toot instead of a boost, explain StickTock's proposition as a free software project, and mention there is an affiliation.

@profdiggity @privacysafe @techcrunch@threads.net @yaleprivacylab

With regards to code being open-source.. is the build also reproducable? Can we be sure that the service runs the same compiled release? This is not what most services offer, and not needed for a heartfelt initiative intent to help people. But for the brand 'PrivacySafe' it would be a boon and unique selling point. Just saying.

@smallcircles @privacysafe @techcrunch @yaleprivacylab Yes, I know all about this, teach it, and love #Debian for it. Too soon to do this w/ StickTock + there may not be enough interest or resources to accomplish it. The project may also not matter much if politics change next week.

Right now it is an easily-deployable docker swarm.

For binaries that run on desktops, this is a goal. @privacysafe is building those but no prod release yet. Stay tuned! I agree, the bar for proper security is high

@smallcircles @privacysafe @techcrunch @yaleprivacylab No worries! I think if you look into who I am you'll see I've been working in #FreeSoftware for two decades or so, volunteering for the FSF, etc. I'm very receptive to these ideas and it's exciting that the project elicits community feedback like this.

Enjoy your day and thanks again :)

@profdiggity @privacysafe @techcrunch@threads.net @yaleprivacylab

Yes, I gave you the 'social follow' seeing lotsa interesting topics and exciting activities you are involved in.

the Code is beautiful. If only it weren't so inherently unsustainable (in general practice) to produce quality solutions for those who want to make their living with it doing sustainable business.

Difference in capability between production systems operating under hypercapitalism vs open commons is fascinating.

@smallcircles @privacysafe @techcrunch @yaleprivacylab Noted and will probably result in a policy.

I am also drafting new docs for the @yaleprivacylab digital self-defense workshops, and do not want any conflict (as there has not been in the past). But it is unlikely privacysafe is mentioned there at all due to concerns about confusion. Those docs will be published by @yaleprivacylab in its repos.