Martin Be

Never be somebody's second, but always be second to one!

:pixelfed:: https://pixelfed.social/MartinBe
CITY: Luxemburg 🇱🇺
Relationship: Married happily with [#Hotwife](https://mastodon.social/tags/Hotwife ) Martina Neumayer (npub17vq…vvkz)

Last Notes

2024-11-08 13:07:06 UTC

- reply

2/n It was few times proven that such services like fb doesn't really delete any of the users data even after the account is removed, deleted etc. Moreover they still can and use them for own purposes like ads and profiling, targeting friends of such user who are on fb for example. That's why such scripts/tools/browser add-ons (you name it) have been developed in the first place. Because of those corporate cheaters.

2024-11-08 13:00:36 UTC

- reply

Deleting account doesn't physically remove data from their servers, clusters or whatever else they are using. Same as on fb and plenty of other similar services. Of course "deleting" all content by hand is possible, why not, if someone has such amounts of patientce? What I meant, scripts are handy and can save lots of time. Also decent made scripts are able to replace your sensitive but undeletable data with some random gibberish. If someone is privacy freak. You know.

2024-11-08 12:26:10 UTC

- reply

You can do way simpler if you want your user name to never be usable again. But beware, that's permanent! Think twice before you use this way! The trick is: just delete anything from your account (there are scripts for that you can use) and post something that violates x/Twitter rules very badly. For example some ugly porn, abusive pictures, very shitty texts and so on. It doesn't matter what, but must be hard violating their tos. And then ask some friends/people to report this account.

2024-10-16 21:40:56 UTC

- reply

For me, an editorial office that publishes biased content is not worth the slightest attention. And they are known for pitting people against each other. This is not journalism. This is the bottom with a ton of mud, that a normal person will not bother with.
In other words, a rag. Anyone who reads something like that has only themselves to blame. And don't have much in own head. You just ignore idiots. As the old saying goes.

2024-10-16 21:21:48 UTC

- reply

Only absolute retards or some total morons are reading such trashy scumbags vomit like wired.

2024-10-14 07:22:33 UTC

- reply

This new toots look in the mobile android app is not particularly handy for me. How I can switch it back to the previous one? 🤔🙄

2024-09-25 22:08:16 UTC

- reply

https://files.mastodon.social/media_attachments/files/113/200/469/486/000/563/original/dd6a208152780137.png

2024-09-12 05:03:07 UTC

#Gardening #FreeFood #TakeWhatYouNeed
This is so awesome! Made my heart happy and me smiling.
https://files.mastodon.social/media_attachments/files/113/122/815/527/031/997/original/20b5592c1a454101.jpg

2024-08-29 21:26:30 UTC

- reply

3/n Sometimes Apple's system does the refreshing only partially from unknown reasons and that's why this re-login must be repeated until the synchro fully began to work. This issue is known for many years and sadly they didn't manage to fix it. I was also Apple user for very long time and we had this problem in the company few times. It takes sometime even few days to get it working back. Why is so? I totally have no idea, to be honest. It's just is. That's Apple 😉

2024-08-29 21:14:09 UTC

- reply

1/n Google account is added, otherwise it won't be visible at all.
The clou now is to bring back to work the whole synchronization again.
Only apple id must be logged out and later in. Google one leave logged in as it is.
The issue is in the new tokens which your system will have now. All of the old ones, all remainings of them etc., must be removed, cleaned, deleted and so on, otherwise the synchronization process will start but won't be completed successfully.

2024-08-29 20:50:08 UTC

- reply

2/n You may have to repeat this re-login process a few times before it catches on. But after a while it should start and be fine now. Unfortunately, this is the charm of the Apple systems. 😉

2024-08-29 20:44:52 UTC

- reply

Okay, adding google calendar works. Now try to log out from the Apple ID, reboot this laptop and log back in. If any other account you're using on this machine uses this Apple ID too, log them all out, before rebooting. After reboot log in only one of them. You can also try to clean the cache memory of this apple id app. I don't remember exact name of it. If you have some app for cleaning the junk files from the system, use it. On Linux I use BleachBit for that.

2024-08-29 15:50:53 UTC

- reply

Exactly what I thought about. On my Linux machine I had similar issue. Cron wanted to do their scheduled synchros and that prevented me from any changes on some folders they were hooked up to it. I turned cron off, rebooted and then I was able to change the folder name and everything was all right back again. Perhaps this is going on here in this case? It is fairly possible. Apple OS is unix based, so all the main rules are that same on both systems.

2024-08-29 15:08:41 UTC

- reply

Yeap.. I think this exactly happened.
While synchronizing the second user's data, something went wrong and the system automatically assigned root as the owner of this directory. Therefore, your user "rolle" cannot access the data stored in this directory and synchronize it correctly.
The issue will be present if both machine users are using same Apple ID.
Normally something like this shouldn't be even allowed by the system itself. You should be warned about that ootb.

2024-08-29 14:54:31 UTC

- reply

Seems like an wrong permissions problem of the directory where the calendar configs and/or files are stored.
Your ~/Library/Calendars directory can not be owned by the machine admin nor root.
Check that please. If it is owned by do this from terminal:
sudo chown -R <username>:staff ~/Library/Calendars
Then reboot and your gmail stuff should be okay.
If you get the second errorr talking about "DAErrorDomain blah blah blah.."
All you need is sign out and in of your AppleID fo fix it.
🙃 👍

2024-08-08 19:01:42 UTC

- reply

Great looking setup. Any specific things to pay attention for by making it on the already installed system? I am actually using EndeavourOS, but I will gladly try Plasma as well.

2024-05-06 06:51:18 UTC

- reply

Updated today to the 5.7.1 version from your fdroid repo and all I get after the app start is a white screen. Nothing else happens. In such state app remains indefinitely. Won't launch even to the pin lock screen.
Any advice on how to fix that issue?
https://files.mastodon.social/media_attachments/files/112/392/801/470/141/991/original/95995fa7672fb389.png