Show newer

@sofia Oh that might be a GNOME thing. Tracking it here but I'm not certain what I'm doing wrong with regards to packing the icon. github.com/AgregoreWeb/agregor

Maybe the URL is wrong in the system tray and we need to use the unpacked asar directory? 🤷

@sofia Nice, I thought the latest version was supposed to just work without flags but I may be wrong. 🤔 Might need to add a wrapper for wayland users to use instead. TY for testing!

I'm gonna be migrating to wayland soon for mmy @stardustxr setup so maybe I'll figure out something more solid then

@sofia Does using the keyboard shortcut to open devtools work? ctrl+shift+i

@sofia Dang. 🤔 Nothing is rendering at all? I thibk there was some sort of "ozone wayland" flag for electron that folks were using. I think `--enable-features=UseOzonePlatform --ozone-platform=wayland`?

@sofia Well shit. :P Does using an older version work by any chance? I currently don't have a GOME / deb machine to test one. Also, does using the appimage help?

@sofia the built in libp2p pubsub support has you covered. Use a shared "topic" between the peers and send whatever you want. agregore.mauve.moe/docs/ipfs-p

Bonus is that there's also an Android app in addition to mac/win/linux ehich supports the same APIs. No ios tho cause they don't allow custom browser engines still.

@sofia @agregore for libp2p via ipfs desktop users would still need to configure some flags to allow for cors 🤔

@sofia also if you're happy runnimg a libp2p sidecar or the such, you might enjoy using tauri and writing networkibg in rust + using native webviews

@jonny Fleshgraft some forager snouts into my SemHog to access new InfoTruffles? View your DataTroph to sort through the slop

@sofia impossible without *somebody* running a server unless you use a funky browser like @agregore

Sometimes if you're in physical proximity and on the same network you can exchange sdp via audio or qr codes tho.

@jonny Lemme datasuck those old tweetd into my SemHog. My forager agent picked up some new feeds for my SemHog on the data sea.

@cmdrmoto yup! Gonna be ingesting different sources into semantic web data and using a nosql datavase of some sort. Probably my ipld prolly trees one tbh.

Thinking of names for a new app that loads data from *anywhere*.

So far thinking as in "Semantic hog which eats all your data and rolls around in the mud and you give it belly pats to search through stuff".

Also sounds a bit like "send hog".

free software? aye comrade, and food should be free as well! and housing, and the hospital, and the library and post office too. ah, but why are these things not gratis? that is a dangerous question, isn’t it? why when there is more food than even all of us could eat, is there poverty all around us? do not limit your query to the business of software, comrade, for the villains of this play have a far greater span than your meager discipline.

Had to dial remotely into this team building thing all my coworkers are doing cause I'm sick and I'm getting to roleplay being a lil homonculus in a jar on the table.

*parent voice* If ChatGPT told you to jump off a bridge would you?!

Many people seem still unaware of just how bad Chrome Sync is for your privacy. By default, Chrome will sync all your data – including e.g. your passwords, bookmarks, browsing history and open tabs. And by default, Chrome will not encrypt any of this data. All of it will be accessible by Google, by anyone who subpoenas Google to turn up your data and whoever else managed to get access to these servers.

If you want this data encrypted before it is first uploaded, you need to click “Settings” instead of confirming sync, then expand “Encryption options” and set up a sync passphrase. The default option “Encrypt synced passwords with your Google Account” is essentially a disguised “We can access all your data but we promise not to look. Don’t you trust us?”

Except that they will look of course. Apparently, they now started censoring your synced bookmarks: strangeobject.space/@silvermoo

The only positive aspect here: Chrome Sync used to be a lot worse. It used to enable automatically when you signed into Chrome. It used to encrypt only passwords and none of the other data even if you set up a passphrase. It used to warn you when setting a passphrase because Google’s web services would no longer be able to access your passwords. It used to upload data without encryption first, only allowing to enable encryption after the fact. And its encryption used to be horribly broken. I wrote about that five years ago: palant.info/2018/03/13/can-chr

But even now, Chrome Sync requires you to take action in order to get privacy. Because Google knows that you won’t. Compare that to Firefox Sync which has always been encrypting all data by default. I criticized the implementation here as well, but that was really a minor issue compared to the mess which is Chrome Sync.

#Google #GoogleChrome #privacy

Honestly it's kinda amazing how much information we have access to at a moments notice. 🤯

Show older
Mauvestodon

Escape ship from centralized social media run by Mauve.